From: Ken Brownfield <ken@irridia.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: I/O APIC fixed in 2.4.19-pre3 & 2.5.6 (was Re: Linux 2.4.19-pre3)
Date: Tue, 19 Mar 2002 18:34:20 -0600 [thread overview]
Message-ID: <20020319183420.A15811@asooo.flowerfire.com> (raw)
In-Reply-To: <20020318204106.A24611@asooo.flowerfire.com> <Pine.LNX.3.96.1020319111636.1772A-100000@gatekeeper.tmr.com>
If noapic doesn't fix your problem, the I/O APIC patch won't help
unfortunately, AFAIK. Are these solid system-wide lockups not
attributable to a binary-only X driver? ;)
--
Ken.
ken@irridia.com
On Tue, Mar 19, 2002 at 11:22:44AM -0500, Bill Davidsen wrote:
| Any chance this will cure the lockups on a Dell Latitude C600 every time
| you exit X? I've disabled both the IO-APIC and APIC-uni, which was
| supposed to fix the problem but didn't. Dare I hope that the disable
| wasn't enough?
|
| A quick google tells me other people have the same problem, but I
| haven't seen a working solution yet. Nice machine other than needing to be
| rebooted after every use of X :-(
|
| --
| bill davidsen <davidsen@tmr.com>
| CTO, TMR Associates, Inc
| Doing interesting things with little computers since 1979.
|
| -
| To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
| the body of a message to majordomo@vger.kernel.org
| More majordomo info at http://vger.kernel.org/majordomo-info.html
| Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-03-20 0:35 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-11 21:08 Linux 2.4.19-pre3 Marcelo Tosatti
2002-03-11 22:40 ` Eyal Lebedinsky
2002-03-11 23:03 ` Alan Cox
2002-03-11 22:55 ` Stephan von Krawczynski
2002-03-12 1:50 ` Mike Fedyk
2002-03-12 11:06 ` Stephan von Krawczynski
2002-03-12 21:59 ` Paul Mackerras
2002-03-11 23:04 ` Eyal Lebedinsky
2002-03-11 23:14 ` Keith Owens
2002-03-12 15:49 ` DevilKin
2002-03-21 12:06 ` [patch] Don't offer CONFIG_INDYDOG on non-ip22 machines Adrian Bunk
2002-03-22 21:13 ` Marcelo Tosatti
2002-03-11 23:21 ` Linux 2.4.19-pre3 Eyal Lebedinsky
2002-03-12 1:40 ` Takeo Saito
2002-03-12 0:04 ` J.A. Magallon
2002-03-12 0:37 ` Ken Brownfield
2002-03-19 2:41 ` I/O APIC fixed in 2.4.19-pre3 & 2.5.6 (was Re: Linux 2.4.19-pre3) Ken Brownfield
2002-03-19 16:22 ` Bill Davidsen
2002-03-20 0:34 ` Ken Brownfield [this message]
2002-03-20 4:36 ` Bill Davidsen
2002-03-12 10:35 ` Linux 2.4.19-pre3 Gerd Knorr
2002-03-12 17:24 ` Trond Myklebust
2002-03-12 17:47 ` Gerd Knorr
2002-03-12 13:01 ` Karsten Weiss
2002-03-12 13:17 ` Jens Axboe
2002-03-12 13:37 ` Alan Cox
2002-03-12 13:46 ` Jens Axboe
2002-03-12 19:02 ` Marcelo Tosatti
2002-03-13 8:09 ` Jens Axboe
2002-03-13 9:00 ` Andre Hedrick
2002-03-13 9:27 ` Jens Axboe
2002-03-13 9:33 ` Andre Hedrick
2002-03-13 17:32 ` Andre Hedrick
2002-03-13 17:40 ` Jens Axboe
2002-03-13 18:52 ` Andre Hedrick
2002-03-14 4:41 ` Marcelo Tosatti
2002-03-14 6:28 ` Andre Hedrick
2002-03-14 3:32 ` Michal Jaegermann
2002-03-12 14:47 ` J.A. Magallon
2002-03-12 13:31 ` Jurgen Philippaerts
2002-03-12 15:43 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2002-03-20 2:40 I/O APIC fixed in 2.4.19-pre3 & 2.5.6 (was Re: Linux 2.4.19-pre3) PlasmaJohn
2002-03-20 4:30 ` Bill Davidsen
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=20020319183420.A15811@asooo.flowerfire.com \
--to=ken@irridia.com \
--cc=davidsen@tmr.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