mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chris Li" <lkml@chrisli.org>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: irq 19: nobody cared
Date: Fri, 19 Sep 2008 16:13:21 -0700	[thread overview]
Message-ID: <70318cbf0809191613u19ecc807j8911bc9a4ada50a2@mail.gmail.com> (raw)
In-Reply-To: <20080919233808.64aa7539@lxorguk.ukuu.org.uk>

On Fri, Sep 19, 2008 at 3:38 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>
> It could also be an IRQ being routed wrongly or an incorrect BIOS table
> so that the kernel is looking for the IRQ in the wrong place.
>
> Does booting with the irqpoll option help ?

Yes, booting with irqpoll option does helps with the latest kernel.
There is not such message appear any more. However I do want
the kernel fix this problem. The very same problem prevent me from
installing a FC8 live CD on this slim tower. In that FC8 kernel,
irqpoll does not help. BTW, it was working fine on FC7 kernel.
Upgrade to FC8 complete ruined it.

There are other user dell slim tower user report the same
problem on the Internet. One of the work around mention on the
internet is to change BIOS setting for SATA from "IDE"
mode to "RAID" mode. That tip complete destroy my partition
but  does not work for me any way. FC9 is better, at least
I am able to install with irqpoll.

I was hoping some one else already complain this on the lkml
and get it fixed. Guess not. So I am going my part then.

>> usb 4-2: new full speed USB device using uhci_hcd and address 2
>> irq 19: nobody cared (try booting with the "irqpoll" option)
>
> And does this last one (the irq19) occur immediately when you plug in a
> USB device ?

No,  the USB device is already (cold) plug to the system before the
kernel was booted. That new device message should be the first time the
USB driver detect the those USB device. I just load the kernel and
I did not hotplug any thing. It is the USB keyboard and mouse I think.

Any thing I can do to help to identify the problem?

Chris

  reply	other threads:[~2008-09-19 23:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 20:40 Chris Li
2008-09-19 20:50 ` Yinghai Lu
2008-09-19 21:13   ` Chris Li
2008-09-19 21:57     ` Yinghai Lu
2008-09-19 22:32       ` Chris Li
2008-09-20 21:35         ` Yinghai Lu
2008-09-20 22:04           ` Chris Li
2008-09-20 22:22             ` Yinghai Lu
2008-09-20 23:21               ` Chris Li
2008-09-22 23:30                 ` Chris Li
2008-09-23  1:32                   ` Yinghai Lu
2008-09-23  2:22                     ` Chris Li
2008-09-23  2:34                       ` Yinghai Lu
2008-09-23  5:08                         ` Chris Li
2008-09-19 22:38 ` Alan Cox
2008-09-19 23:13   ` Chris Li [this message]
2008-09-28 22:23     ` Alan Cox
2008-09-21  0:23 ` Dave Airlie
2008-09-21  1:00   ` Chris Li
2008-10-19  4:05 ` Steven Rostedt
2008-10-19  6:34   ` Chris Li
2008-10-19  8:02     ` Justin P. Mattock
2008-10-19  8:17       ` Chris Li
2008-10-19 15:53         ` Justin P. Mattock

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=70318cbf0809191613u19ecc807j8911bc9a4ada50a2@mail.gmail.com \
    --to=lkml@chrisli.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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

all inboxes | Powered by JetHome®