From: Bill Davidsen <davidsen@tmr.com>
To: Len Brown <len.brown@intel.com>,
Linux Kernel mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Ho ho ho - Linux v2.6.10 (irq18)
Date: Tue, 28 Dec 2004 11:38:08 -0500 [thread overview]
Message-ID: <41D18BF0.2090400@tmr.com> (raw)
In-Reply-To: <1104171962.18174.28.camel@d845pe>
Len Brown wrote:
> On Sat, 2004-12-25 at 21:55, Bill Davidsen wrote:
>
>
>>Alas, It sort-of boots but is terminally slow. I see the log with
>>endless repetitions of "irq 18 nobody cared" and some trace, then
>>"disabling irq 18." Unfortunately it lies, after about 20MB of this I
>>decided it had no real intention of disabling irq 18 and tried to stop
>>it. After ten minutes I had to pull the plug and it's still cleaning
>>filesystems.
>
>
> was irq18 ignored (and disabled) in 2.6.9 on this box?
>
>
Last 2.6 kernel run was 2.6.7, which didn't have any problem with irq18.
I'm going to gather the full set of data on acpi= and pci= options, but
I'm nominally on vacation and spending time with the family instead of
computers. Also, I can't use my Christmas present until I get the FC1
kernel to set the i810/ac97 audio to 4 channels instead of the default
two, so all the people saying "I want to hear it" can't be satisfied.
Priorities this week...
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2004-12-28 16:42 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-24 22:39 Ho ho ho - Linux v2.6.10 Linus Torvalds
2004-12-25 11:11 ` Andrew Walrond
2004-12-25 12:19 ` Alan Cox
2004-12-26 11:30 ` Wichert Akkerman
2004-12-26 13:45 ` R. J. Wysocki
2004-12-26 19:37 ` Pavel Machek
2004-12-26 19:39 ` Pavel Machek
2004-12-26 20:27 ` R. J. Wysocki
2004-12-26 22:10 ` Pavel Machek
2005-01-13 18:09 ` 2.6.10-mm3: swsusp: out of memory on resume (was: Re: Ho ho ho - Linux v2.6.10) Rafael J. Wysocki
2005-01-13 19:59 ` Pavel Machek
2005-01-13 21:22 ` Rafael J. Wysocki
2005-01-14 14:34 ` hugang
2005-01-14 17:25 ` Rafael J. Wysocki
2005-01-15 21:43 ` Rafael J. Wysocki
2005-01-16 21:51 ` Pavel Machek
2005-01-17 14:53 ` Rafael J. Wysocki
2005-01-17 15:22 ` Pavel Machek
2005-01-18 1:44 ` hugang
[not found] ` <200501150042.35377.rjw@sisk.pl>
2005-01-15 1:21 ` hugang
[not found] ` <200501151147.32919.rjw@sisk.pl>
[not found] ` <200501152220.42129.rjw@sisk.pl>
2005-01-16 5:54 ` hugang
2005-01-16 10:07 ` Rafael J. Wysocki
2005-01-16 14:46 ` hugang
2005-01-17 15:48 ` Rafael J. Wysocki
2005-01-17 16:49 ` Rafael J. Wysocki
2004-12-30 9:58 ` Ho ho ho - Linux v2.6.10 Rafael J. Wysocki
2004-12-26 15:45 ` Alan Cox
2004-12-29 12:44 ` Paolo Ciarrocchi
2004-12-26 2:55 ` Bill Davidsen
2004-12-26 3:36 ` Linus Torvalds
[not found] ` <1104171962.18174.28.camel@d845pe>
2004-12-28 16:38 ` Bill Davidsen [this message]
2004-12-26 4:19 ` Alexander E. Patrakov
2004-12-26 5:12 ` [PATCH] parport_pc: don't mix module parameter styles Randy.Dunlap
2004-12-26 20:35 ` Ho ho ho - Linux v2.6.10 Greg Norris
2004-12-27 1:31 ` Dmitry Torokhov
2004-12-28 2:36 ` Greg Norris
2004-12-27 16:10 ` Ho ho ho - Linux v2.6.10 (compile stats) John Cherry
2004-12-28 1:04 ` Ho ho ho - Linux v2.6.10 Håkan Lindqvist
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=41D18BF0.2090400@tmr.com \
--to=davidsen@tmr.com \
--cc=len.brown@intel.com \
--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