Kernel panic - r8169 on 2.6.11-rc1-mm1
Every time i try to use eth1 which is r8169, i get a kernel panic, but
on the actual use of it, not the configuring it.
e.g.
laptop ~ # ifconfig eth1 up 192.168.1.1
laptop ~ # ping 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
Oops: [#1]
Modules linked in: snd_pcm_oss snd_mixer_oss snd_seq_oss
seq_midi_event snd_seq snd_seq_device irtty_sir sir_dev irda pcspkr
snd_intel8x0 snd_ac97_codec snd_pcm snd_timer
snd snd_page_alloc wlan_wep fglrx sis_agp psmouse r8169 ath_pci
ath_rate_onoe wlan ath_hal
CPU:0
EIP:0060:[] Tainted: P VLI
EFLAGS: 00010206(2.6.11-rc1-mm1)
EIP is at rtl8169_start_xmit+0x55/0x2b0 [r8169]
eax: 003f ebx: cf236140 ecx: cc9c6000 edx:
esi: cf236240 edi: cfd9b280 ebp: cfd9b280 esp: c0685e00
ds: 007bes: 007bss: 0068
Process swapper (pid: 0, threadinfo=c0684000 task=c05b6ba0)
Stack: c0107e50 cf236140 cf935080 cfd9b280 d14da000 cc9c6000
8000 cf236140 cf935080 cf236000 cfd9b280 c049141e cfd9b280 cf236000
cf236000 cfd9b280 cf236140 c048387f cf236000 cf935080
<0>Kernel panic - not syncing: Fatal exception in interrupt
I never had time to write down the whole stack trace (and there was no
core file created)
This driver used to work in a previous kernel version (but it did get
IRQ #x nobody cared messages, usually when there was some sort of a
disconnection of my ethernet cable for whatever reason). This is
always reproducable.
uname -a:
Linux laptop 2.6.11-rc1-mm1 #2 SMP Sun Jan 16 22:36:26 GMT 2005 i686
Intel(R) Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux
I would try a newer kernel, but the command line options for
specifying the framebuffer settings seems to have changed in the
latest kernel and i haven't had enough time to work out how to specify
it.
--
Cameron Harris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Kernel panic - r8169 on 2.6.11-rc1-mm1
Every time i try to use eth1 which is r8169, i get a kernel panic, but
on the actual use of it, not the configuring it.
e.g.
laptop ~ # ifconfig eth1 up 192.168.1.1
laptop ~ # ping 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
Oops: [#1]
Modules linked in: snd_pcm_oss snd_mixer_oss snd_seq_oss
seq_midi_event snd_seq snd_seq_device irtty_sir sir_dev irda pcspkr
snd_intel8x0 snd_ac97_codec snd_pcm snd_timer
snd snd_page_alloc wlan_wep fglrx sis_agp psmouse r8169 ath_pci
ath_rate_onoe wlan ath_hal
CPU:0
EIP:0060:[d15481e5] Tainted: P VLI
EFLAGS: 00010206(2.6.11-rc1-mm1)
EIP is at rtl8169_start_xmit+0x55/0x2b0 [r8169]
eax: 003f ebx: cf236140 ecx: cc9c6000 edx:
esi: cf236240 edi: cfd9b280 ebp: cfd9b280 esp: c0685e00
ds: 007bes: 007bss: 0068
Process swapper (pid: 0, threadinfo=c0684000 task=c05b6ba0)
Stack: c0107e50 cf236140 cf935080 cfd9b280 d14da000 cc9c6000
8000 cf236140 cf935080 cf236000 cfd9b280 c049141e cfd9b280 cf236000
cf236000 cfd9b280 cf236140 c048387f cf236000 cf935080
0Kernel panic - not syncing: Fatal exception in interrupt
I never had time to write down the whole stack trace (and there was no
core file created)
This driver used to work in a previous kernel version (but it did get
IRQ #x nobody cared messages, usually when there was some sort of a
disconnection of my ethernet cable for whatever reason). This is
always reproducable.
uname -a:
Linux laptop 2.6.11-rc1-mm1 #2 SMP Sun Jan 16 22:36:26 GMT 2005 i686
Intel(R) Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux
I would try a newer kernel, but the command line options for
specifying the framebuffer settings seems to have changed in the
latest kernel and i haven't had enough time to work out how to specify
it.
--
Cameron Harris
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: cifs connection loss hangs
On Mon, 21 Feb 2005 09:35:44 -0600, Steve French <[EMAIL PROTECTED]> wrote:
>
> >Being a wireless user i experience the occasional connection loss due
> >to walking out of range or something, recently after starting to use
> >cifs mounts instead of smbfs, I've noticed that stuff tends to break
> > if i lose connection.
>
> cifs does support reconnection after tcp session drops (including
> reattaching to the server shares and reopening open files, rewriting
> cached data).
>
> What kernel version ("cat /proc/version") or cifs vfs version ("modinfo
> /lib/modules//kernel/fs/cifs/cifs.ko) are you running?
>
> 2.6.10 includes one fix for a race in the cifs reconnection logic (which
> is included in cifs version 1.27 or later) and there was an earlier (and
> more important) reconnection fix in cifs version 1.10 (I think that came
> in mainline about at kernel version 2.6.6).
>
> There are test patches (or in some cases a copy of the fs/cifs
> directory) available for a few of the older but common kernels (SLES9,
> SuseWorkstation 9.2, FC3 etc.) at
> http://us1.samba.org/samba/ftp/cifs-cvs which include up to 2.6.10 level.
>
> Note that you can view the state of cifs connections by "cat
> /proc/fs/cifs/DebugData" (also interesting is "cat /proc/fs/cifs/Stats")
> which will show the cifs tcp sessions, smb sessions and tree connection
> (mount) and whether they need reconnection - it also shows the state of
> any pending [cifs] operations on the network.
>
I use 2.6.11-rc1-mm1. I'll check out the /proc/fs/cifs/ stuff next
time i get a problem. It isn't so much reconnection issues, it's if
the connection is completely lost for whatever reason it tends to put
the processes to uninterruptible sleep. It's as though it doesn't
actually return an error, but instead waits until it can access the
file again, even when the filesystem is umounted.
--
Cameron Harris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: cifs connection loss hangs
On Mon, 21 Feb 2005 09:35:44 -0600, Steve French [EMAIL PROTECTED] wrote: Being a wireless user i experience the occasional connection loss due to walking out of range or something, recently after starting to use cifs mounts instead of smbfs, I've noticed that stuff tends to break if i lose connection. cifs does support reconnection after tcp session drops (including reattaching to the server shares and reopening open files, rewriting cached data). What kernel version (cat /proc/version) or cifs vfs version (modinfo /lib/modules/kernel ver/kernel/fs/cifs/cifs.ko) are you running? 2.6.10 includes one fix for a race in the cifs reconnection logic (which is included in cifs version 1.27 or later) and there was an earlier (and more important) reconnection fix in cifs version 1.10 (I think that came in mainline about at kernel version 2.6.6). There are test patches (or in some cases a copy of the fs/cifs directory) available for a few of the older but common kernels (SLES9, SuseWorkstation 9.2, FC3 etc.) at http://us1.samba.org/samba/ftp/cifs-cvs which include up to 2.6.10 level. Note that you can view the state of cifs connections by cat /proc/fs/cifs/DebugData (also interesting is cat /proc/fs/cifs/Stats) which will show the cifs tcp sessions, smb sessions and tree connection (mount) and whether they need reconnection - it also shows the state of any pending [cifs] operations on the network. I use 2.6.11-rc1-mm1. I'll check out the /proc/fs/cifs/ stuff next time i get a problem. It isn't so much reconnection issues, it's if the connection is completely lost for whatever reason it tends to put the processes to uninterruptible sleep. It's as though it doesn't actually return an error, but instead waits until it can access the file again, even when the filesystem is umounted. -- Cameron Harris - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
cifs connection loss hangs
Being a wireless user i experience the occasional connection loss due to walking out of range or something, recently after starting to use cifs mounts instead of smbfs, I've noticed that stuff tends to break if i lose connection. I first noticed this when my bootscript brought down the wireless before it umounted the cifs share, and it hung the shutdown. Recently i was copying some files over with a nautilus window open. I lost connection and the nautilus window & the cp process froze. ps said that they were stuck in D (Uninterruptible Sleep). I read it's a kernel problem if something gets stuck in it. umounting the cifs filesystem didn't even wake up the process, I had to reboot (which didn't work right because something was stuck with a file open). Anyone got any ideas on how this could be fixed? Thanks -- Cameron Harris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
cifs connection loss hangs
Being a wireless user i experience the occasional connection loss due to walking out of range or something, recently after starting to use cifs mounts instead of smbfs, I've noticed that stuff tends to break if i lose connection. I first noticed this when my bootscript brought down the wireless before it umounted the cifs share, and it hung the shutdown. Recently i was copying some files over with a nautilus window open. I lost connection and the nautilus window the cp process froze. ps said that they were stuck in D (Uninterruptible Sleep). I read it's a kernel problem if something gets stuck in it. umounting the cifs filesystem didn't even wake up the process, I had to reboot (which didn't work right because something was stuck with a file open). Anyone got any ideas on how this could be fixed? Thanks -- Cameron Harris - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
