| View previous topic :: View next topic |
| Author |
Message |
rojanu
Guru
Joined: 02 Feb 2004
Posts: 361
Location: London
|
 Posted: Mon Apr 04, 2005 2:25 am Post subject: very strange behaviour from eth0 |
 |
|
Hi everyone!
i am getting very strange behaviour from my ethernet card;
First of all I have to gentoo installations on my system one stable and one ~x86 both gentoo-sources. I just installed ~x86 and used config file of stable to compile ~x86 installs kernel and intalled e1000 module as I have done for the stable but it did not work, then I compiled the kernel with genkernel now I get connection for some time, however after few minutes connection dies .
Any ideas?
Thank you. |
|
| Back to top |
|
 |
Vanquirius
Retired Dev
Joined: 14 Jun 2002
Posts: 1297
Location: Ethereal plains
|
| Posted: Mon Apr 04, 2005 2:56 am Post subject: |
|
|
This sounds odd. If I understand you correctly, it works for sometime and suddenly stops working? It looks like a driver crash to me. Anyway, you might want to monitor eth0 with some tools, they may help you find an answer.
I suggest trying net-analyzer/nethogs, which allows you to monitor which PID is currently using your connection.
Also, watch the output of dmesg.
_________________
Hello. |
|
| Back to top |
|
|
rojanu
Guru
Joined: 02 Feb 2004
Posts: 361
Location: London
|
| Posted: Mon Apr 04, 2005 3:48 am Post subject: |
|
|
here is dmesg outputs from 2 different times
| Code: | e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
|
and this part keeps repeating even it is visible in the in any vc (e.g. CTRL+ALT+F1) | Code: | <1>Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
c02b89fa
*pde = 00000000
Oops: 0002 [#39]
Modules linked in: snd_pcm_oss snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device ohci_hcd parport_pc parport sata_promise ohci1394 ieee1394 snd_intel8x0 snd_ac97_codec snd_pcm snd_timer snd snd_page_alloc ata_piix libata ehci_hcd usb_storage usblp uhci_hcd intel_agp usbcore vfat fat e1000 nvidia agpgart
CPU: 0
EIP: 0060:[<c02b89fa>] Tainted: P VLI
EFLAGS: 00010202 (2.6.11-gentoo-r4)
EIP is at memcpy+0x1e/0x39
eax: 00000010 ebx: f597b200 ecx: 00000004 edx: 00000000
esi: f24ededc edi: 00000000 ebp: bfffe8d0 esp: f24edeac
ds: 007b es: 007b ss: 0068
Process artsd (pid: 19299, threadinfo=f24ec000 task=f7c4d020)
Stack: ffffffea ffffffea f24edeec f93478f8 00000000 f24ededc 00000010 f597b200
f9348630 f597b200 f24ededc 00000050 00000006 00000000 00000000 00000000
00000005 00000001 00000000 00000000 00008002 00000000 00000000 00000000
Call Trace:
[<f93478f8>] snd_timer_user_append_to_tqueue+0x40/0x49 [snd_timer]
[<f9348630>] snd_timer_user_params+0x21c/0x221 [snd_timer]
[<f934881d>] snd_timer_user_ioctl+0xdf/0x1f9 [snd_timer]
[<c016341f>] do_ioctl+0x53/0x7a
[<c0163610>] vfs_ioctl+0x65/0x1d4
[<c01637c4>] sys_ioctl+0x45/0x6d
[<c0102de3>] syscall_call+0x7/0xb
Code: fd 31 c0 c3 31 d2 b8 f2 ff ff ff c3 90 83 ec 0c 8b 44 24 18 8b 54 24 10 89 74 24 04 89 c1 89 7c 24 08 8b 74 24 14 c1 e9 02 89 d7 <f3> a5 a8 02 74 02 66 a5 a8 01 74 01 a4 89 d0 8b 74 24 04 8b 7c
|
and finally
| Quote: | | net-analyzer/nethogs |
is not in the portage |
|
| Back to top |
|
|
Vanquirius
Retired Dev
Joined: 14 Jun 2002
Posts: 1297
Location: Ethereal plains
|
| Posted: Mon Apr 04, 2005 8:26 pm Post subject: |
|
|
I added it recently, but it should be in Portage already. Anyway, I still think it looks like a driver crash. Hopefully someone with similar hardware can give you a hand...
_________________
Hello. |
|
| Back to top |
|
|
rojanu
Guru
Joined: 02 Feb 2004
Posts: 361
Location: London
|
| Posted: Mon Apr 04, 2005 8:45 pm Post subject: |
|
|
Thanks for replies anyway,
My specs are
Asus P4C800-E DELUXE Mobo
e1000 NIC |
|
| Back to top |
|
|
rojanu
Guru
Joined: 02 Feb 2004
Posts: 361
Location: London
|
| Posted: Tue Apr 05, 2005 12:18 am Post subject: |
|
|
I think I got it working at least its been 4-5 hours now my ethernet connection did not go down so it should be fine, ( I think)
I did few changes and not too sure which one worked 
First I unmerged e1000 module ( I checked my stable install and it has none, I remember now that when I tried to merge e1000 at the time it complained about being already in the kernel). After reboot connection still died. Guess that wasn't it.
Then I compiled the e1000 in to kernel rather than being a module and I had few other cards as modules (don't know what I was thinking when I compiled my kernel)
though still I have
| Code: | $ cat /etc/modules.autoload.d/kernel-2.6
nvidia
e1000
|
works now anyway |
|
| Back to top |
|
|
|
Networking & Security
