linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nils Rennebarth <nils.rennebarth@packetalarm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: e100 in 2.6.15 fails unless irqpoll ist used
Date: Mon, 16 Jan 2006 10:59:50 +0100	[thread overview]
Message-ID: <43CB6E96.6030907@packetalarm.com> (raw)
In-Reply-To: <20060111102536.5d91fd92.akpm@osdl.org>

Andrew Morton wrote:
> Nils Rennebarth <nils.rennebarth@packetalarm.com> wrote:
> 
>>An upgrade from 2.6.14.3 to 2.6.15 on my testmachine disabled my network cards: 
>> no packets are sent or received.
>>
>> There is the following in dmesg:
>>
>> usbcore: registered new driver usbfs
>> usbcore: registered new driver hub
>> USB Universal Host Controller Interface driver v2.3
>> irq 11: nobody cared (try booting with the "irqpoll" option)
>>   [<c012ae21>] __report_bad_irq+0x31/0x77
>>   [<c012aef4>] note_interrupt+0x75/0x99
>>   [<c012a9f0>] __do_IRQ+0x65/0x91
>> ...
>>
>> Rebooting with irqpoll will make the network cards work. The above message will 
>> appeare nonetheless.
> 
> 
> This means that your IRQ routing broke and the card's interrupt requests
> are not getting through.
> 
> This is likely to be an ACPI regression.  Please raise a report at
> bugzilla.kernel.org, generate full `dmesg -s 1000000' output for both
> 2.6.14.3 and for 2.6.15 and attach them to the report, thanks.
Thanks for your fast reply.

As I do not have access to my work machine from home I could only answer today, 
and try what I might, I am not able to reproduce the mentioned behaviour any more.

The first thing I tried last Wednesday was to pull out an unused Adaptec 
AHA-2940U SCSI controller which happened to be in the machine for testing 
purposes only.

This "fixed" the network cards as well and now reinserting the SCSI adapter does 
not break them again, neither can I reproduce the "nobody cared" message. 
Unfortunately I also overwrote the saved dmesg from a boot where the network 
cards *did* break.

So the only thing I have is a dmesg (which I cannot reproduce) where irqpoll 
seems to have fixed the problem, and apart form the missing "nobody cares" plus 
the backtrace, it differs from the current one in the order the hardware is 
detected.

I'll be more cautious to save useful information if said behaviour raises its 
ugly head again, but for now, thanks and sorry for the noise.


-- 

Mit freundlichen Grüßen / with kind regards

Nils Rennebarth
--
VarySys Technologies GmbH & Co. KG
Moenchhaldenstraße 28
70191 Stuttgart
Germany
Tel +49 711 2501198
Fax +49 711 2501197
mailto:Nils.Rennebarth@packetalarm.com
http://www.packetalarm.com

Download the free software trial version of PacketAlarm now
http://www.packetalarm.com/download/

      reply	other threads:[~2006-01-16 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11 13:57 e100 in 2.6.15 fails unless irqpoll ist used Nils Rennebarth
2006-01-11 18:25 ` Andrew Morton
2006-01-16  9:59   ` Nils Rennebarth [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43CB6E96.6030907@packetalarm.com \
    --to=nils.rennebarth@packetalarm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).