=0x97, t=2189.
Dec 17 05:35:39 butterfly kernel: [184437.367308] NETDEV WATCHDOG: eth3:
transmit timed out
Dec 17 05:35:39 butterfly kernel: [184437.367315] eth3: Tx timed out,
lost interrupt? TSR=0x3, ISR=0x3, t=1188.
Is this the same issue? Thanks.
--
John M Flinchbaugh
[EMAIL PROTECTED
=0x97, t=2189.
Dec 17 05:35:39 butterfly kernel: [184437.367308] NETDEV WATCHDOG: eth3:
transmit timed out
Dec 17 05:35:39 butterfly kernel: [184437.367315] eth3: Tx timed out,
lost interrupt? TSR=0x3, ISR=0x3, t=1188.
Is this the same issue? Thanks.
--
John M Flinchbaugh
[EMAIL PROTECTED
[] __might_sleep+0xac/0xc0
[] kmem_cache_alloc+0x5e/0x60
[] kmem_cache_create+0xe3/0x570
[] proto_register+0x99/0xc0
[] inet6_init+0x16/0x1d0 [ipv6]
[] sys_init_module+0x172/0x230
[] syscall_call+0x7/0xb
--
John M Flinchbaugh
[EMAIL PROTECTED]
signature.asc
Description: Digital signature
/0x20
[c0114e6c] __might_sleep+0xac/0xc0
[c014394e] kmem_cache_alloc+0x5e/0x60
[c0142aa3] kmem_cache_create+0xe3/0x570
[c0268d39] proto_register+0x99/0xc0
[e0bea096] inet6_init+0x16/0x1d0 [ipv6]
[c0132902] sys_init_module+0x172/0x230
[c01030e5] syscall_call+0x7/0xb
--
John M Flinchbaugh
[EMAIL
On Wed, Feb 16, 2005 at 02:59:40PM -0500, John M Flinchbaugh wrote:
> correcting the problem, so I can get swsusp and ACPI coexisting
> happily
> on my Thinkpad R40.
> Does anyone here on the ACPI list have some logical next steps for
> me to
> test?
> - Forwarde
On Wed, Feb 16, 2005 at 02:59:40PM -0500, John M Flinchbaugh wrote:
correcting the problem, so I can get swsusp and ACPI coexisting
happily
on my Thinkpad R40.
Does anyone here on the ACPI list have some logical next steps for
me to
test?
- Forwarded message from John M Flinchbaugh
enough to grep your swap
partitions out of your fstab.
--
John M Flinchbaugh
[EMAIL PROTECTED]
signature.asc
Description: Digital signature
to grep your swap
partitions out of your fstab.
--
John M Flinchbaugh
[EMAIL PROTECTED]
signature.asc
Description: Digital signature
.net drivers, and I've gotten the freeze without
even having those modules loaded, so I doubt that's it.
I'm currently testing booting with acpi=off. While, I've not had a
freeze yet (nearly 2 days), I may take your advice and test with
laptop-mode disabled as well, since I could definitely toler
testing booting with acpi=off. While, I've not had a
freeze yet (nearly 2 days), I may take your advice and test with
laptop-mode disabled as well, since I could definitely tolerate the loss
of laptop-mode better than the loss of my ACPI events and info.
--
John M Flinchbaugh
[EMAIL PROTECTED
g disabling ACPI causes my trouble to go away, what's my next
step in debugging this issue? I'd hate to just leave it at "Don't use
ACPI."
Thanks for your time.
--
John M Flinchbaugh
[EMAIL PROTECTED]
signature.asc
Description: Digital signature
step in debugging this issue? I'd hate to just leave it at Don't use
ACPI.
Thanks for your time.
--
John M Flinchbaugh
[EMAIL PROTECTED]
signature.asc
Description: Digital signature
Library routines
#
CONFIG_CRC_CCITT=m
CONFIG_CRC32=m
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y
thanks.
--
John M Flinchbaugh
[EMAIL PROTECTED]
signature.asc
Description: Digital signature
crypto devices
#
# CONFIG_CRYPTO_DEV_PADLOCK is not set
#
# Library routines
#
CONFIG_CRC_CCITT=m
CONFIG_CRC32=m
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y
thanks.
--
John M Flinchbaugh
ing swappiness up
to 100%, saving the hwclock, etc. having taken all that out, i find it
unnecessary anymore.
--
John M Flinchbaugh
[EMAIL PROTECTED]
signature.asc
Description: Digital signature
up
to 100%, saving the hwclock, etc. having taken all that out, i find it
unnecessary anymore.
--
John M Flinchbaugh
[EMAIL PROTECTED]
signature.asc
Description: Digital signature
stuck?
thank you everyone.
--
John M Flinchbaugh
[EMAIL PROTECTED]
signature.asc
Description: Digital signature
stuck?
thank you everyone.
--
John M Flinchbaugh
[EMAIL PROTECTED]
signature.asc
Description: Digital signature
G_CRC32=m
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y
--
John M Flinchbaugh
[EMAIL PROTECTED]
signature.asc
Description: Digital signature
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y
--
John M Flinchbaugh
[EMAIL PROTECTED]
signature.asc
Description: Digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i'm happy to see my cheap little camera working again.
i have observations though:
using uhci.o, i only get black image from video camera in xawtv.
using usb-uhci.o, i get a picture, but i periodically get:
kernel: usb-uhci.c: interrupt, status ,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i'm happy to see my cheap little camera working again.
i have observations though:
using uhci.o, i only get black image from video camera in xawtv.
using usb-uhci.o, i get a picture, but i periodically get:
kernel: usb-uhci.c: interrupt, status
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
did something change in the past 2 months to break cpia_usb cameras?
the last i remember using my webcam was toward the end of august.
it hasn't been working with test9 or test8 i don't think.
the device shows up just fine, the /proc/cpia/video0 is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
did something change in the past 2 months to break cpia_usb cameras?
the last i remember using my webcam was toward the end of august.
it hasn't been working with test9 or test8 i don't think.
the device shows up just fine, the /proc/cpia/video0 is
Package: esound
Version: 0.2.19
i've emailed various people about this already, but i've figured out a
couple new things.
basically, when i added ram to my linux-2.4.0-test8 box taking it from
96M to 192M of ram. esd over tcpip started popping, hesitating,
distorting. if i limit the memory at
Package: esound
Version: 0.2.19
i've emailed various people about this already, but i've figured out a
couple new things.
basically, when i added ram to my linux-2.4.0-test8 box taking it from
96M to 192M of ram. esd over tcpip started popping, hesitating,
distorting. if i limit the memory at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
is there something magical about the memory size of 128M of ram in the
kernel, on this system, in the sound driver, or in esound?
i recently upgraded my inspiron 3800 from 96M (32 + 64) to 192M (64 +
128), and now playing mp3s, wavs or any other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
is there something magical about the memory size of 128M of ram in the
kernel, on this system, in the sound driver, or in esound?
i recently upgraded my inspiron 3800 from 96M (32 + 64) to 192M (64 +
128), and now playing mp3s, wavs or any other
28 matches
Mail list logo