I saw a mention of interrupt handling for forcedeth cards is the 2.6.19.1 changelog, but I still see this error in 2.6.19.1. It started in 2.6.19, and it didn't happen in 2.6.18.1. Dec 17 05:35:29 butterfly kernel: [184432.371636] eth3: Tx timed out, lost interrupt? TSR=0x3, ISR=0x97, t=2222. Dec 17 05:35:31 butterfly kernel: [184433.370864] NETDEV WATCHDOG: eth3: transmit timed out Dec 17 05:35:31 butterfly kernel: [184433.370871] eth3: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=1190. Dec 17 05:35:34 butterfly kernel: [184434.869718] NETDEV WATCHDOG: eth3: transmit timed out Dec 17 05:35:34 butterfly kernel: [184434.869725] eth3: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=1189. Dec 17 05:35:37 butterfly kernel: [184436.368072] NETDEV WATCHDOG: eth3: transmit timed out Dec 17 05:35:37 butterfly kernel: [184436.368080] eth3: Tx timed out, lost interrupt? TSR=0x3, ISR=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]
Attachment:
signature.asc
Description: Digital signature
- Follow-Ups:
- Re: forcedeth trouble in 2.6.19(.1)
- From: Daniel Barkalow <[email protected]>
- Re: forcedeth trouble in 2.6.19(.1)
- Prev by Date: Re: Task watchers v2
- Next by Date: Re: Linux 2.6.20-rc1
- Previous by thread: mmap abuses in drm
- Next by thread: Re: forcedeth trouble in 2.6.19(.1)
- Index(es):
 |