<div class="gmail_quote"><div>Hi Daniel. Thank you very much for your help on this problem.<br>
<br>
I've trawled through all the logs, and I previously provided a relevant section of the kernel log to the bug report:<br>
<br>
Jun 21 04:34:46 ppp kernel: [ 5493.104588] NETDEV WATCHDOG: eth0: transmit timed out<br>
Jun 21 04:34:46 ppp kernel: [ 5493.104738] eth0: Transmit timed out, status 0003, PHY status 786d, resetting...<br>
Jun 21 04:34:46 ppp kernel: [ 5493.105384] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1<br>
<br>
Which then sets into a repeating pattern:<br>
<br>
Jun 21 05:05:02 ppp kernel: [ 7308.203455] NETDEV WATCHDOG: eth0: transmit timed out<br>
Jun 21 05:05:02 ppp kernel: [ 7308.203606] eth0: Transmit timed out, status 1003, PHY status 786d, resetting...<br>
Jun 21 05:05:02 ppp kernel: [ 7308.204254] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1<br>
Jun 21 05:35:16 ppp kernel: [ 9121.303308] NETDEV WATCHDOG: eth0: transmit timed out<br>
Jun 21 05:35:16 ppp kernel: [ 9121.303457] eth0: Transmit timed out, status 1003, PHY status 786d, resetting...<br>
Jun 21 05:35:16 ppp kernel: [ 9121.304106] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1<br>
<br>
This occurs shortly before the first occurance in the kernel log:<br>
<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747505] irq 23: nobody cared (try booting with the "irqpoll" option)<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747514] Pid: 0, comm: swapper Tainted: P 2.6.24-19-generic #1<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747516] <br>
Jun 21 04:29:46 ppp kernel: [ 5193.747517] Call Trace:<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747519] <IRQ> [__report_bad_irq+0x1e/0x80] __report_bad_irq+0x1e/0x80<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747550] [note_interrupt+0x2ad/0x2e0] note_interrupt+0x2ad/0x2e0<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747562] [handle_fasteoi_irq+0xa1/0x110] handle_fasteoi_irq+0xa1/0x110<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747571] [do_IRQ+0x7b/0x100] do_IRQ+0x7b/0x100<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747577] [ret_from_intr+0x0/0x0a] ret_from_intr+0x0/0xa<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747583] [pci_conf1_read+0x0/0x100] pci_conf1_read+0x0/0x100<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747596] [__do_softirq+0x60/0xe0] __do_softirq+0x60/0xe0<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747609] [call_softirq+0x1c/0x30] call_softirq+0x1c/0x30<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747614] [do_softirq+0x35/0x90] do_softirq+0x35/0x90<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747618] [irq_exit+0x88/0x90] irq_exit+0x88/0x90<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747621] [do_IRQ+0x80/0x100] do_IRQ+0x80/0x100<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747624] [default_idle+0x0/0x40] default_idle+0x0/0x40<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747628] [default_idle+0x0/0x40] default_idle+0x0/0x40<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747630] [ret_from_intr+0x0/0x0a] ret_from_intr+0x0/0xa<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747633] <EOI> [lapic_next_event+0x0/0x10] lapic_next_event+0x0/0x10<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747648] [default_idle+0x29/0x40] default_idle+0x29/0x40<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747654] [cpu_idle+0x6f/0xc0] cpu_idle+0x6f/0xc0<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747662] [start_kernel+0x2c5/0x350] start_kernel+0x2c5/0x350<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747670] [x86_64_start_kernel+0x12e/0x140] _sinittext+0x12e/0x140<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747678] <br>
Jun 21 04:29:46 ppp kernel: [ 5193.747679] handlers:<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747680] [usbcore:usb_hcd_irq+0x0/0x60] (usb_hcd_irq+0x0/0x60 [usbcore])<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747702] [via_rhine:rhine_interrupt+0x0/0x7f0] (rhine_interrupt+0x0/0x7f0 [via_rhine])<br>
Jun 21 04:29:46 ppp kernel: [ 5193.747710] Disabling IRQ #23<br>
<br>
</div></div>As I said in the bug report comments, I am not using an Intel nic. My module is the via-rhine. as per lspci<br><br>00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c)<br> Subsystem: ASUSTeK Computer Inc. Unknown device 80ed<br>
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-<br> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-<br> Latency: 64 (750ns min, 2000ns max), Cache Line Size: 64 bytes<br>
Interrupt: pin A routed to IRQ 23<br> Region 0: I/O ports at 9400 [size=256]<br> Region 1: Memory at dffff800 (32-bit, non-prefetchable) [size=256]<br> Capabilities: <access denied><br><br>Therefore:<br>
<br>ppp@ppp:~$ sudo rmmod via-rhine<br>
ppp@ppp:~$ sudo modprobe via-rhine<br><br>I like the idea of a workaround :) I had one, where I manually added the default gateway but that failed after another suggestion of hacking up the aspci conf so I need to go back to the original conf to retest.<br>
<br>Will test your suggestions, thanks<br>