2.6.11rc4: irq 5, nobody cared

2.6.11rc4: irq 5, nobody cared

[Folkert van Heusden]

Hi,

My linux laptop says:
irq 5: nobody cared!
 [<c0133044>] __report_bad_irq+0x24/0x90
 [<c0133141>] note_interrupt+0x61/0x90
 [<c0132b2b>] __do_IRQ+0x13b/0x150
 [<c0104a33>] do_IRQ+0x23/0x40
 [<c01031fe>] common_interrupt+0x1a/0x20
 [<c0119dee>] __do_softirq+0x2e/0x80
 [<c0119e67>] do_softirq+0x27/0x30
 [<c0119f35>] irq_exit+0x35/0x40
 [<c0104a38>] do_IRQ+0x28/0x40
 [<c01031fe>] common_interrupt+0x1a/0x20
 [<c011d6c0>] del_timer+0x0/0xb0
 [<c02b1c59>] schedule_timeout+0x69/0xc0
 [<c0138b8f>] __get_free_pages+0x1f/0x40
 [<c011df90>] process_timeout+0x0/0x10
 [<c01633e5>] do_select+0x195/0x2f0
 [<c0163090>] __pollwait+0x0/0xc0
 [<c0128cc0>] autoremove_wake_function+0x0/0x50
 [<c016381e>] sys_select+0x2be/0x4b0
 [<c01194fc>] sys_gettimeofday+0x2c/0x70
 [<c010308f>] syscall_call+0x7/0xb
handlers:
[<dc8d35f0>] (usb_hcd_irq+0x0/0x60 [usbcore])
[<dca21690>] (ndis_irq_th+0x0/0xf0 [ndiswrapper])
Disabling IRQ #5

Does anyone care? :-)


Folkert van Heusden

Op zoek naar een IT of Finance baan? Mail me voor de mogelijkheden!
+------------------------------------------------------------------+
|UNIX admin? Then give MultiTail (http://vanheusden.com/multitail/)|
|a try, it brings monitoring logfiles to a different level! See    |
|http://vanheusden.com/multitail/features.html for a feature list. |
+------------------------------------------= www.unixsoftware.nl =-+
Phone: +31-6-41278122, PGP-key: 1F28D8AE

Re: 2.6.11rc4: irq 5, nobody cared

[Rogério Brito]

On Feb 20 2005, Folkert van Heusden wrote:
> My linux laptop says:
> irq 5: nobody cared!
(...)
> Does anyone care? :-)

Well, I'm getting similar stack traces with my system and those are sure
scary, but it seems that my e-mails to the list are simply ignored,
unfortunately.

I am willing to test any patch and configuration (let's call me a "guinea
pig"), but I don't know what I should do. I have, OTOH, reported my problem
many times in the past few days. :-(

I will retry sending my message to the list once again, with the details
(in my case, the message I get is "irq 10: nobody cared!" and it is
regarding my primary HD on my secondary Promise PDC20265 controller).


Thanks for any help, Rogério.

P.S.: I have already bought an 80-pin cable just for this drive in the hope
that the message would go away, but it didn't.
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
  Rogério Brito - rbrito@ime.usp.br - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Re: 2.6.11rc4: irq 5, nobody cared

[Arjan van de Ven]

> [<dca21690>] (ndis_irq_th+0x0/0xf0 [ndiswrapper])
> Disabling IRQ #5
> 
> Does anyone care? :-)

doubt it ... ;)

Re: 2.6.11rc4: irq 5, nobody cared

[Matthias-Christian Ott]

Rogério Brito wrote:

>On Feb 20 2005, Folkert van Heusden wrote:
>  
>
>>My linux laptop says:
>>irq 5: nobody cared!
>>    
>>
>(...)
>  
>
>>Does anyone care? :-)
>>    
>>
>
>Well, I'm getting similar stack traces with my system and those are sure
>scary, but it seems that my e-mails to the list are simply ignored,
>unfortunately.
>
>I am willing to test any patch and configuration (let's call me a "guinea
>pig"), but I don't know what I should do. I have, OTOH, reported my problem
>many times in the past few days. :-(
>
>I will retry sending my message to the list once again, with the details
>(in my case, the message I get is "irq 10: nobody cared!" and it is
>regarding my primary HD on my secondary Promise PDC20265 controller).
>
>
>Thanks for any help, Rogério.
>
>P.S.: I have already bought an 80-pin cable just for this drive in the hope
>that the message would go away, but it didn't.
>  
>
Report it to http://bugzilla.kernel.org/. Maybe you'll get help there. 
But "bugs" are _very_ hardware specific, so just a few people will have 
a similar problem and most of this people are just "normal" users -- not 
Linux Kernel developers. The developer (people who are familiar with the 
kernel code and who are maybe able to fix this problem) aren't able to 
reproduce this error and test code to get it working. So they're maybe 
(without knowing anything about the hardware (maybe it's broken 
hardware?)) not able to say something specific about the hardware -- 
they can just guess.
You see it's very difficult to fix such irq problems because some 
factors can cause such an error.
Maybe contacting specific malinglists (e.g. for "broken" pci cards the 
pci mailinglist, etc.), maintainers or developers would be more 
efficient (cc the lkml) and solve your problem (faster), because this 
people are specialists are this type of hardware (e.g. pci).

What hardware is connect through irq 5?

Matthias-Christian Ott

Re: 2.6.11rc4: irq 5, nobody cared

[Rogério Brito]

On Feb 20 2005, Matthias-Christian Ott wrote:
> Rogério Brito wrote:
> >I am willing to test any patch and configuration (let's call me a
> >"guinea pig"), but I don't know what I should do. I have, OTOH,
> >reported my problem many times in the past few days. :-(
> >
> >I will retry sending my message to the list once again, with the
> >details (in my case, the message I get is "irq 10: nobody cared!"
> >and it is regarding my primary HD on my secondary Promise PDC20265
> >controller).

First of all, Matthias-Christian, thank you very much for your kind
answer.

I have already tried contacting the linux-ide mailing list as a CC to my
earlier messages, but I got no response. I am including some details in
this e-mail. I included Bartlomiej in the CC, as he is listed as general
IDE maintainer in the MAINTAINERS file.

> Report it to http://bugzilla.kernel.org/. Maybe you'll get help there.

Thanks. I will try filing a bug on that system as soon as I get the
reply to create my account there.

(...)
> You see it's very difficult to fix such irq problems because some factors
> can cause such an error.

Yes, I understand that.

> Maybe contacting specific malinglists (e.g. for "broken" pci cards
> the pci mailinglist, etc.), maintainers or developers would be more
> efficient (cc the lkml) and solve your problem (faster), because
> this people are specialists are this type of hardware (e.g. pci).
> 
> What hardware is connect through irq 5?

In my case, my problem is not with irq 5, but with irq 10, as I
mentioned earlier.

The situation is this: I have an Asus A7V motherboard with 2 VIA
vt82c686a controllers and 2 Promise PDC20265 controllers.

I recently bought myself a new DVD recorder and since Alan Cox told
me[*] that the Promise controllers had problems with ATAPI devices, I
decided to arrange my system this way:

/dev/hda: the DVD recorder (VIA controller, master)
/dev/hdc: an old CD recorder (VIA controller, master)
/dev/hde: my first HD (Promise controller, master)
/dev/hdg: my second HD (Promise controller, master)

The Promise controller is able to control the HDs (which now have
exclusive 80-pin cables) at their maximum, but I get the following
stack trace if I have /dev/hdg turned on:

- - - - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - -
ACPI: PCI interrupt 0000:00:11.0[A] -> GSI 10 (level, low) -> IRQ 10
PDC20265: chipset revision 2
PDC20265: 100% native mode on irq 10
PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
    ide2: BM-DMA at 0x7400-0x7407, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0x7408-0x740f, BIOS settings: hdg:pio, hdh:pio
Probing IDE interface ide2...
hde: QUANTUM FIREBALL CX13.0A, ATA DISK drive
ide2 at 0x8800-0x8807,0x8402 on irq 10
Probing IDE interface ide3...
hdg: QUANTUM FIREBALLlct15 30, ATA DISK drive
irq 10: nobody cared!
 [<c0128fc1>] __report_bad_irq+0x31/0x77
 [<c012906b>] note_interrupt+0x4c/0x71
 [<c0128c86>] __do_IRQ+0x93/0xbd
 [<c0104635>] do_IRQ+0x19/0x24
 [<c010335a>] common_interrupt+0x1a/0x20
 [<c011935c>] __do_softirq+0x2c/0x7d
 [<c01193cf>] do_softirq+0x22/0x26
 [<c010463a>] do_IRQ+0x1e/0x24
 [<c010335a>] common_interrupt+0x1a/0x20
 [<c0128d89>] enable_irq+0x88/0x8d
 [<c021edc0>] probe_hwif+0x2da/0x366
 [<c021a137>] ata_attach+0xa3/0xbd
 [<c021ee5c>] probe_hwif_init_with_fixup+0x10/0x74
 [<c0221597>] ide_setup_pci_device+0x72/0x7f
 [<c0216f82>] pdc202xx_init_one+0x15/0x18
 [<c039182e>] ide_scan_pcidev+0x34/0x59
 [<c039186f>] ide_scan_pcibus+0x1c/0x88
 [<c039179f>] probe_for_hwifs+0xb/0xd
 [<c03917e5>] ide_init+0x44/0x59
 [<c037c6ce>] do_initcalls+0x4b/0x99
 [<c0100272>] init+0x0/0xce
 [<c0100299>] init+0x27/0xce
 [<c0101245>] kernel_thread_helper+0x5/0xb
handlers:
[<c021c2a6>] (ide_intr+0x0/0xee)
Disabling IRQ #10
irq 10: nobody cared!
- - - - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - -

This is just an excerpt of the messages. I can provide much more
details if I know what is relevant.

I had already posted some old dmesg logs at my site
<http://www.ime.usp.br/~rbrito/ide-problem/>, but this was before I
got myself a second 80-ribbon cable (I expected that the problem would
go away, but it didn't).

Any other comments are more than welcome.


Thanks in advance, Rogério Brito.

[*] http://infocenter.guardiandigital.com/archive/linux-kernel/2004/Dec/2663.html
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
  Rogério Brito - rbrito@ime.usp.br - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Re: 2.6.11rc4: irq 5, nobody cared

[Matthias-Christian Ott]

Rogério Brito wrote:

>On Feb 20 2005, Matthias-Christian Ott wrote:
>  
>
>>Rogério Brito wrote:
>>    
>>
>>>I am willing to test any patch and configuration (let's call me a
>>>"guinea pig"), but I don't know what I should do. I have, OTOH,
>>>reported my problem many times in the past few days. :-(
>>>
>>>I will retry sending my message to the list once again, with the
>>>details (in my case, the message I get is "irq 10: nobody cared!"
>>>and it is regarding my primary HD on my secondary Promise PDC20265
>>>controller).
>>>      
>>>
>
>First of all, Matthias-Christian, thank you very much for your kind
>answer.
>
>I have already tried contacting the linux-ide mailing list as a CC to my
>earlier messages, but I got no response. I am including some details in
>this e-mail. I included Bartlomiej in the CC, as he is listed as general
>IDE maintainer in the MAINTAINERS file.
>
>  
>
>>Report it to http://bugzilla.kernel.org/. Maybe you'll get help there.
>>    
>>
>
>Thanks. I will try filing a bug on that system as soon as I get the
>reply to create my account there.
>
>(...)
>  
>
>>You see it's very difficult to fix such irq problems because some factors
>>can cause such an error.
>>    
>>
>
>Yes, I understand that.
>
>  
>
>>Maybe contacting specific malinglists (e.g. for "broken" pci cards
>>the pci mailinglist, etc.), maintainers or developers would be more
>>efficient (cc the lkml) and solve your problem (faster), because
>>this people are specialists are this type of hardware (e.g. pci).
>>
>>What hardware is connect through irq 5?
>>    
>>
>
>In my case, my problem is not with irq 5, but with irq 10, as I
>mentioned earlier.
>
>The situation is this: I have an Asus A7V motherboard with 2 VIA
>vt82c686a controllers and 2 Promise PDC20265 controllers.
>
>I recently bought myself a new DVD recorder and since Alan Cox told
>me[*] that the Promise controllers had problems with ATAPI devices, I
>decided to arrange my system this way:
>
>/dev/hda: the DVD recorder (VIA controller, master)
>/dev/hdc: an old CD recorder (VIA controller, master)
>/dev/hde: my first HD (Promise controller, master)
>/dev/hdg: my second HD (Promise controller, master)
>
>The Promise controller is able to control the HDs (which now have
>exclusive 80-pin cables) at their maximum, but I get the following
>stack trace if I have /dev/hdg turned on:
>
>- - - - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - -
>ACPI: PCI interrupt 0000:00:11.0[A] -> GSI 10 (level, low) -> IRQ 10
>PDC20265: chipset revision 2
>PDC20265: 100% native mode on irq 10
>PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
>    ide2: BM-DMA at 0x7400-0x7407, BIOS settings: hde:pio, hdf:pio
>    ide3: BM-DMA at 0x7408-0x740f, BIOS settings: hdg:pio, hdh:pio
>Probing IDE interface ide2...
>hde: QUANTUM FIREBALL CX13.0A, ATA DISK drive
>ide2 at 0x8800-0x8807,0x8402 on irq 10
>Probing IDE interface ide3...
>hdg: QUANTUM FIREBALLlct15 30, ATA DISK drive
>irq 10: nobody cared!
> [<c0128fc1>] __report_bad_irq+0x31/0x77
> [<c012906b>] note_interrupt+0x4c/0x71
> [<c0128c86>] __do_IRQ+0x93/0xbd
> [<c0104635>] do_IRQ+0x19/0x24
> [<c010335a>] common_interrupt+0x1a/0x20
> [<c011935c>] __do_softirq+0x2c/0x7d
> [<c01193cf>] do_softirq+0x22/0x26
> [<c010463a>] do_IRQ+0x1e/0x24
> [<c010335a>] common_interrupt+0x1a/0x20
> [<c0128d89>] enable_irq+0x88/0x8d
> [<c021edc0>] probe_hwif+0x2da/0x366
> [<c021a137>] ata_attach+0xa3/0xbd
> [<c021ee5c>] probe_hwif_init_with_fixup+0x10/0x74
> [<c0221597>] ide_setup_pci_device+0x72/0x7f
> [<c0216f82>] pdc202xx_init_one+0x15/0x18
> [<c039182e>] ide_scan_pcidev+0x34/0x59
> [<c039186f>] ide_scan_pcibus+0x1c/0x88
> [<c039179f>] probe_for_hwifs+0xb/0xd
> [<c03917e5>] ide_init+0x44/0x59
> [<c037c6ce>] do_initcalls+0x4b/0x99
> [<c0100272>] init+0x0/0xce
> [<c0100299>] init+0x27/0xce
> [<c0101245>] kernel_thread_helper+0x5/0xb
>handlers:
>[<c021c2a6>] (ide_intr+0x0/0xee)
>Disabling IRQ #10
>irq 10: nobody cared!
>- - - - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - -
>
>This is just an excerpt of the messages. I can provide much more
>details if I know what is relevant.
>
>I had already posted some old dmesg logs at my site
><http://www.ime.usp.br/~rbrito/ide-problem/>, but this was before I
>got myself a second 80-ribbon cable (I expected that the problem would
>go away, but it didn't).
>
>Any other comments are more than welcome.
>
>
>Thanks in advance, Rogério Brito.
>
>[*] http://infocenter.guardiandigital.com/archive/linux-kernel/2004/Dec/2663.html
>  
>
Hi!
I'm not IDE specialist, but what about operating systems? Did you try a 
Windows or BSD CD (try it with a Windows 2000/XP CD, if you have one, 
else burn a NetBSD or FreeBSD/DragonflyBSD CD -- this is important to 
see if it's a linux bug or acpi bug)? Anyway this is very strange.

Good luck!
Matthias-Christian Ott

Re: 2.6.11rc4: irq 5, nobody cared

[Bartlomiej Zolnierkiewicz]

On Sunday 20 February 2005 19:05, Rogério Brito wrote:
> On Feb 20 2005, Matthias-Christian Ott wrote:
> > Rogério Brito wrote:
> > >I am willing to test any patch and configuration (let's call me a
> > >"guinea pig"), but I don't know what I should do. I have, OTOH,
> > >reported my problem many times in the past few days. :-(
> > >
> > >I will retry sending my message to the list once again, with the
> > >details (in my case, the message I get is "irq 10: nobody cared!"
> > >and it is regarding my primary HD on my secondary Promise PDC20265
> > >controller).
> 
> First of all, Matthias-Christian, thank you very much for your kind
> answer.
> 
> I have already tried contacting the linux-ide mailing list as a CC to my
> earlier messages, but I got no response. I am including some details in
> this e-mail. I included Bartlomiej in the CC, as he is listed as general
> IDE maintainer in the MAINTAINERS file.

Hi,

There is no need to cc: me 3x times,
I'm subscribed to linux-kernel and linux-ide
so I got your mail 5x times...

If I don't reply it means that I'm busy doing other stuff.

Regards,
Bartlomiej

Re: 2.6.11rc4: irq 5, nobody cared

[Jeff Garzik]

Bartlomiej Zolnierkiewicz wrote:
> On Sunday 20 February 2005 19:05, Rogério Brito wrote:
> 
>>On Feb 20 2005, Matthias-Christian Ott wrote:
>>
>>>Rogério Brito wrote:
>>>
>>>>I am willing to test any patch and configuration (let's call me a
>>>>"guinea pig"), but I don't know what I should do. I have, OTOH,
>>>>reported my problem many times in the past few days. :-(
>>>>
>>>>I will retry sending my message to the list once again, with the
>>>>details (in my case, the message I get is "irq 10: nobody cared!"
>>>>and it is regarding my primary HD on my secondary Promise PDC20265
>>>>controller).
>>
>>First of all, Matthias-Christian, thank you very much for your kind
>>answer.
>>
>>I have already tried contacting the linux-ide mailing list as a CC to my
>>earlier messages, but I got no response. I am including some details in
>>this e-mail. I included Bartlomiej in the CC, as he is listed as general
>>IDE maintainer in the MAINTAINERS file.
> 
> 
> Hi,
> 
> There is no need to cc: me 3x times,
> I'm subscribed to linux-kernel and linux-ide
> so I got your mail 5x times...

You should add this to your procmailrc :)

# Nuke duplicate messages
:0 Wh: msgid.lock
| $FORMAIL -D 32768 msgid.cache

	Jeff

Re: 2.6.11rc4: irq 5, nobody cared

[Rogério Brito]

On Feb 21 2005, Bartlomiej Zolnierkiewicz wrote:
> On Sunday 20 February 2005 19:05, Rogério Brito wrote:
> > I have already tried contacting the linux-ide mailing list as a CC to my
> > earlier messages, but I got no response. I am including some details in
> > this e-mail. I included Bartlomiej in the CC, as he is listed as general
> > IDE maintainer in the MAINTAINERS file.
> 
> Hi,

Hi, Bartlomiej.

> There is no need to cc: me 3x times,
> I'm subscribed to linux-kernel and linux-ide
> so I got your mail 5x times...

I'm sorry for this. I didn't know which personal e-mail address was
operational, since I saw many that you used.

> If I don't reply it means that I'm busy doing other stuff.

Ok, thank you for your feedback. I hope that you can find some time to help
me with my system.

I can provide you any information that you want. Just let me know and I
will do my best to give you detailed information.


Thank you very much, Rogério Brito.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
  Rogério Brito - rbrito@ime.usp.br - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Re: 2.6.11rc4: irq 5, nobody cared

[Wichert Akkerman]

Previously Jeff Garzik wrote:
> You should add this to your procmailrc :)
> 
> # Nuke duplicate messages
> :0 Wh: msgid.lock
> | $FORMAIL -D 32768 msgid.cache

That has the nasty side-effect of spreading messages for a single
discussion amongst many different mailboxes depending on which path
happens to be the first to deliver an email to you.

Wichert.

-- 
Wichert Akkerman <wichert@wiggy.net>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.

Re: 2.6.11rc4: irq 5, nobody cared

[Jeff Garzik]

Wichert Akkerman wrote:
> Previously Jeff Garzik wrote:
> 
>>You should add this to your procmailrc :)
>>
>># Nuke duplicate messages
>>:0 Wh: msgid.lock
>>| $FORMAIL -D 32768 msgid.cache
> 
> 
> That has the nasty side-effect of spreading messages for a single
> discussion amongst many different mailboxes depending on which path
> happens to be the first to deliver an email to you.

These are _duplicate_ messages.  The To/CC doesn't vary in my 
experience.  Therefore, sorting on To/CC always guarantees my messages 
go into the correct folder.

Maybe you are thinking of reply-to-munged lists, which eliminate 
duplicates by eliminating custom To/CC lists.

	Jeff

Re: 2.6.11rc4: irq 5, nobody cared

[Wichert Akkerman]

Previously Jeff Garzik wrote:
> These are _duplicate_ messages.  The To/CC doesn't vary in my 
> experience.  Therefore, sorting on To/CC always guarantees my messages 
> go into the correct folder.

It depends highly on how you filter. It do not use To/Cc headers
to choose the mailbox to deliver a message in since that will not work
with things like bounces and aliases. Using headers like List-Id or
X-Mailing-List is reliable, but does not work with the duplicate
filtering you suggested.

It is a matter of choosing your own preference. And ours seem to differ.

Wichert.

-- 
Wichert Akkerman <wichert@wiggy.net>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.

Re: 2.6.11rc4: irq 5, nobody cared

[Bill Davidsen]

Rogério Brito wrote:
> On Feb 20 2005, Folkert van Heusden wrote:
> 
>>My linux laptop says:
>>irq 5: nobody cared!
> 
> (...)
> 
>>Does anyone care? :-)
> 
> 
> Well, I'm getting similar stack traces with my system and those are sure
> scary, but it seems that my e-mails to the list are simply ignored,
> unfortunately.

I posted a similar thing, but the problem is not that you get the 
message. It means your hardware generated an unexpected interrupt. The 
kernel is reporting that fact as it should.

The problem I had (not resolved) is that after the message
   DISABLING IRQ NN
I continued to get interrupts! So the logic to disable the IRQ is not 
working correctly.

as you note, because the hardware is generating the condition, no one 
seems to care, even though there clearly is a problem in the disable 
logic. I found a way to fix my hardware thanks to some pointers I got, 
so I'm running, but I haven't heard that the base problem is fixed.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

Re: 2.6.11rc4: irq 5, nobody cared

[Bill Davidsen]

Wichert Akkerman wrote:
> Previously Jeff Garzik wrote:
> 
>>You should add this to your procmailrc :)
>>
>># Nuke duplicate messages
>>:0 Wh: msgid.lock
>>| $FORMAIL -D 32768 msgid.cache
> 
> 
> That has the nasty side-effect of spreading messages for a single
> discussion amongst many different mailboxes depending on which path
> happens to be the first to deliver an email to you.

It depends on how you process your mail, if you move to folders with 
determanent logic, checking various lists in order, then it always does 
the same thing. If you use the list header it could do what you suggest. 
I personally push a lot of the mailing lists to a news (usenet) server, 
since it allows a single copy of a message to be indexed in multiple 
groups, and some clients will skip what you have seen better than others.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

Re: 2.6.11rc4: irq 5, nobody cared

[Folkert van Heusden]

> >>My linux laptop says:
> >>irq 5: nobody cared!
> >(...)
> >>Does anyone care? :-)
> >Well, I'm getting similar stack traces with my system and those are sure
> >scary, but it seems that my e-mails to the list are simply ignored,
> >unfortunately.
> I posted a similar thing, but the problem is not that you get the 
> message. It means your hardware generated an unexpected interrupt. The 
> kernel is reporting that fact as it should.
> The problem I had (not resolved) is that after the message
>   DISABLING IRQ NN
> I continued to get interrupts! So the logic to disable the IRQ is not 
> working correctly.

In my case, the interrupt should NOT be disabled as my WIFI-interface is
behind it (via ndiswrappers).

> as you note, because the hardware is generating the condition, no one 
> seems to care, even though there clearly is a problem in the disable 
> logic. I found a way to fix my hardware thanks to some pointers I got, 
> so I'm running, but I haven't heard that the base problem is fixed.

Aight.


Folkert van Heusden

Op zoek naar een IT of Finance baan? Mail me voor de mogelijkheden!
+------------------------------------------------------------------+
|UNIX admin? Then give MultiTail (http://vanheusden.com/multitail/)|
|a try, it brings monitoring logfiles to a different level! See    |
|http://vanheusden.com/multitail/features.html for a feature list. |
+------------------------------------------= www.unixsoftware.nl =-+
Phone: +31-6-41278122, PGP-key: 1F28D8AE

Re: 2.6.11rc4: irq 5, nobody cared

[Bill Davidsen]

On Thu, 24 Feb 2005, Folkert van Heusden wrote:

> > >>My linux laptop says:
> > >>irq 5: nobody cared!
> > >(...)
> > >>Does anyone care? :-)
> > >Well, I'm getting similar stack traces with my system and those are sure
> > >scary, but it seems that my e-mails to the list are simply ignored,
> > >unfortunately.
> > I posted a similar thing, but the problem is not that you get the 
> > message. It means your hardware generated an unexpected interrupt. The 
> > kernel is reporting that fact as it should.
> > The problem I had (not resolved) is that after the message
> >   DISABLING IRQ NN
> > I continued to get interrupts! So the logic to disable the IRQ is not 
> > working correctly.
> 
> In my case, the interrupt should NOT be disabled as my WIFI-interface is
> behind it (via ndiswrappers).

Well, that's debatable. The warnings mean that either the WiFi driver
isn't catching them as it should, or that something else is generating the
same (shared) IRQ.

But what bothers me is that the kernel is trying to disable the IRQ and
not doing it. I think that's an issue, since on my hardware that meant the
system did nothing but write wrror messages to the log.

> 
> > as you note, because the hardware is generating the condition, no one 
> > seems to care, even though there clearly is a problem in the disable 
> > logic. I found a way to fix my hardware thanks to some pointers I got, 
> > so I'm running, but I haven't heard that the base problem is fixed.
> 
> Aight.

-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.