On 08/06/2007 03:03 AM, Ingo Molnar wrote: > > But, since level types don't need this retriggers too much I think > this "don't mask interrupts by default" idea should be rethinked: > is there enough gain to risk such hard to diagnose errors? > > I reverted those masking changes in Fedora and the baffling problem with 3Com 3C905 network adapters went away. Before, they would print: eth0: transmit timed out, tx_status 00 status e601. diagnostics: net 0ccc media 8880 dma 0000003a fifo 0000 eth0: Interrupt posted but not delivered -- IRQ blocked by another device? Flags; bus-master 1, dirty 295757(13) current 295757(13) Transmit list 00000000 vs. f7150a20. 0: @f7150200 length 80000070 status 0c010070 1: @f71502a0 length 80000070 status 0c010070 2: @f7150340 length 8000005c status 0c01005c Now they just work, apparently... So why not just revert the change? - 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/
- Follow-Ups:
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Jarek Poplawski <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Ingo Molnar <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- References:
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Thomas Gleixner <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: "Marcin Ślusarz" <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Jarek Poplawski <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Thomas Gleixner <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Ingo Molnar <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Jarek Poplawski <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Ingo Molnar <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: "Marcin Ślusarz" <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Jarek Poplawski <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: "Marcin Ślusarz" <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- From: Ingo Molnar <[email protected]>
- Re: 2.6.20->2.6.21 - networking dies after random time
- Prev by Date: Re: [PATCH] i386: convert mm_context_t semaphore to a mutex
- Next by Date: Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
- Previous by thread: Re: 2.6.20->2.6.21 - networking dies after random time
- Next by thread: Re: 2.6.20->2.6.21 - networking dies after random time
- Index(es):