mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michel Bouissou <michel@bouissou.net>
To: bjorn.helgaas@hp.com, "Protasevich,
	Natalie" <Natalie.Protasevich@UNISYS.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	liste@jordet.nu, linux-kernel@vger.kernel.org
Subject: VIA KT400 + Kernel 2.6.12 + IO-APIC + uhci_hcd = IRQ trouble
Date: Sun, 17 Jul 2005 19:58:49 +0200	[thread overview]
Message-ID: <200507171958.49770@totor.bouissou.net> (raw)
In-Reply-To: <19D0D50E9B1D0A40A9F0323DBFA04ACCE04C5D@USRV-EXCH4.na.uis.unisys.com>

Hi there,

Natalie Protasevich and Alan Stern have worked a lot on helping me out with a 
VIA KT400 chipset / kernel 2.6.12 / IO-APIC / IRQ problem "irq 21: nobody 
cared!", which so far hasn't found its solution.

Research done with Alan shows that, on my system, the USB 2.0 controller seems 
to generate interrupts on the IRQ line attributed to the USB 1.1 controller, 
which isn't supposed to happen, and puzzles the system, when IO-APIC is 
enabled.

However, this didn't cause problems with 2.4 series kernels.

For the time being, there is no solution (Natalie is still investigating 
this), and it boils down to the following:

- If I boot with USB 2.0 enabled in BIOS, AND IO-APIC enabled in the kernel, 
then it badly breaks.

- If I either disable USB 2.0 in BIOS, or IO-APIC in the kernel, then it's OK.

I found today the thread between Bjorn Helgaas and Mathieu Bérard on LKML, 
where Mathieu reported the same problem, and Bjorn advised him to reverse a 
kernel patch (http://lkml.org/lkml/2005/6/21/243 ).

Mathieu (I don't have his email address, Bjorn, could you be so kind to 
forward this message to him) reports that it apparently solved this problem, 
so I tried to do the same, and reversed the same patch.

At first boot it seems to solve the issue, but when I rebooted again, it broke 
again, so this is not the solution -- the problem is not completely stable, 
sometimes it doesn't happen for some reason unknown to me... But most of the 
times it _does_ happen :-/

So this message is to inform different people who have suffered from this same 
problem, or are working for finding it a fix...

I'll be on travel for the coming week, and may or may not have occasional 
access to my email. (Please copy me on answers, as I'm not subscribed to the 
linux-kernel ML).

Cheers.

-- 
Michel Bouissou <michel@bouissou.net> OpenPGP ID 0xDDE8AC6E

       reply	other threads:[~2005-07-17 17:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <19D0D50E9B1D0A40A9F0323DBFA04ACCE04C5D@USRV-EXCH4.na.uis.unisys.com>
2005-07-17 17:58 ` Michel Bouissou [this message]
2005-07-17 20:36   ` Alan Stern
2005-07-17 21:20     ` Michel Bouissou
2005-07-17 21:51       ` Michel Bouissou
2005-07-18 16:12       ` Alan Stern
2005-07-25 18:06     ` Michel Bouissou
2005-07-25 19:18       ` Alan Stern
2005-07-25 19:31         ` Michel Bouissou
2005-07-25 20:14         ` Michel Bouissou
2005-07-25 20:44           ` Alan Stern
2005-07-25 22:29             ` Michel Bouissou
2005-07-26  1:56               ` Alan Stern
     [not found] ` <200507172022.46975@totor.bouissou.net>
2005-07-19 23:09   ` Mathieu Bérard
2005-07-26  2:13 Protasevich, Natalie

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=200507171958.49770@totor.bouissou.net \
    --to=michel@bouissou.net \
    --cc=Natalie.Protasevich@UNISYS.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liste@jordet.nu \
    --cc=stern@rowland.harvard.edu \
    /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®