From: Michel Bouissou <michel@bouissou.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>,
dbrownell@users.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [SOLVED ?] VIA KT400 + Kernel 2.6.12 + IO-APIC + ehci_hcd = IRQ trouble
Date: Tue, 26 Jul 2005 21:44:10 +0200 [thread overview]
Message-ID: <200507262144.10865@totor.bouissou.net> (raw)
In-Reply-To: <200507262139.27150@totor.bouissou.net>
Le Mardi 26 Juillet 2005 21:39, Michel Bouissou a écrit :
> Alas, today it hanged completely 3 times :-(
>
> When I say completely, I mean complete system hang, display frozen,
> keyboard dead (even the Magic SysRQ key doesn't respond), network dead
> (doen't ping back), no visible activity of any kind :-((
>
> ...and of course nothing got logged.
>
> This happened 4 times. The 3 first times, I was running with IO-APIC
> enabled and the system was under high disk activity:
>
> 1/ 1st time, I was copying the complete contents of a loopback-mounted ISO
> image to a directory. The system hanged.
>
> 2/ 2nd time, I tried the same. The system hanged again.
[...]
> Now I'm running with IO-APIC enabled, bus USB 2.0 adn ehci completely
> disabled (both in BIOS and modprobe.conf).
>
> The system hasn't hanged again, but I haven't tried to play with on-disk
> ISO filesystems since...
I just did the same as 1/ and 2/ again, with USB 2.0 disabled, to make my
mind. It didn't hang (otherwise I would need to reboot before writing this
message ;-)
--
Michel Bouissou <michel@bouissou.net> OpenPGP ID 0xDDE8AC6E
next prev parent reply other threads:[~2005-07-26 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 2:13 VIA KT400 + Kernel 2.6.12 + IO-APIC + uhci_hcd " Protasevich, Natalie
2005-07-26 10:48 ` [SOLVED ?] VIA KT400 + Kernel 2.6.12 + IO-APIC + ehci_hcd " Michel Bouissou
2005-07-26 18:54 ` Alan Stern
2005-07-26 19:39 ` Michel Bouissou
2005-07-26 19:44 ` Michel Bouissou [this message]
2005-07-27 17:59 ` Michel Bouissou
2005-07-26 23:37 ` Grant Coady
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=200507262144.10865@totor.bouissou.net \
--to=michel@bouissou.net \
--cc=Natalie.Protasevich@UNISYS.com \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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®