[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Procedure to replace a NIC - PLEASE HELP!

> Bob,
> Thank you for your help with my problem. I had changed modprobe.conf to 
> read 'alias eth0 r1000' when I last reported no success, so that hasn't 
> resolved the problem. I rmmod'ed the r8169 driver, but this seems to 
> remove it only until the system is rebooted. dmesg returns some 
> interesting output that may point us to the problem, but I am not able 
> to understand it fully. The pertinent part is as follows:
> PCI: Found IRQ 11 for device 0000:00:0f.0
> PCI: Sharing IRQ 11 with 0000:00:07.5
> PCI: Sharing IRQ 11 with 0000:00:0d.2
> eth0: Identified chip type is 'RTL8169S/8110S'.
> eth0: r10001.04, the Linux device driver for Realtek Ethernet 
> Controllers at 0xc800, 00:40:f4:ee:2f:ff, IRQ 11
> BUG: soft lockup detected on CPU#0!
>   <c043dad5> softlockup_tick+0x90/0xa1  <c0423d50> 
> update_process_times+0x35/0x57
>   <c0406134> timer_interrupt+0x60/0x98  <c043db72> 
> handle_IRQ_event+0x23/0x4c
>   <c043dc17> __do_IRQ+0x7c/0xd1  <c0405035> do_IRQ+0x63/0x80
>   =======================
>   <c04036f2> common_interrupt+0x1a/0x20  <c040d556> delay_tsc+0xb/0x13
>   <c04d8125> __delay+0x9/0xa  <e88160bd> R1000_WRITE_GMII_REG+0x36/0x3c 
> [r1000]
>   <e8817208> r1000_init_one+0x69f/0x892 [r1000]  <c053d851> 
> __driver_attach+0x0/0x8b
>   <c04dfc3b> pci_device_probe+0x36/0x57  <c053d78d> 
> driver_probe_device+0x45/0x9a
>   <c0419231> __cond_resched+0x17/0x28  <c053d8b4> __driver_attach+0x63/0x8b
>   <c053d21f> bus_for_each_dev+0x37/0x59  <c053d6ee> driver_attach+0x16/0x18
>   <c053d851> __driver_attach+0x0/0x8b  <c053cf25> bus_add_driver+0x6f/0x10d
>   <c04dfddf> __pci_register_driver+0x5b/0x7d  <c0433a69> 
> sys_init_module+0x134f/0x14b2
>   <c0423c25> __mod_timer+0x0/0x94  <c0402cb3> syscall_call+0x7/0xb
> Realtek RTL8169/8110 Family Gigabit Ethernet Network Adapter
> Driver version:1.04
> Released date:2006/07/07
> Link Status:Linked
> Link Speed:1000Mbps
> Duplex mode:Full-Duplex
> I/O Base:0xC800(I/O port)
> IRQ:11
> I am trying to research possible causes of the 'BUG: soft lockup 
> detected on CPU#0!', but the lines here are causing me nightmares! on 
> the other hand, there is much more recognition of the card in the final 
> lines than before the switch to the r1000 driver. If you need the rest 
> of the dmesg output, please let me know. I tried to parsse it down to 
> what I thought to be the essentials.
> Thanks again for your help!
> Steven


This will need someone with better hardware skills than I have. I can't
offer a solution. But can you please send me your entire dmesg output
anyhow? I only want to see the dmesg stuff if it is simple and easy for
you to do that. I don't mean to cause you hours of manual typing -- if
that is the case, don't bother sending it to me. It's too much work.

In my mind, plugging in a usb flash drive is pretty simple. You write
the dmesg output to a text file and put the text file on the flash
drive. Then walk it to an internet enabled machine and email it to me.

dmesg > dmesg.txt 

Also I'd like to see your ifconfig output which has to be done as root:

ifconfig > ifconfig.txt


Bob Cochran

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]