From: Andrew Morton <akpm@osdl.org>
To: "Dale E Martin" <dmartin@cliftonlabs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: repeatable, hard lockup on boot in linux-2.6.0-test4 (more details)
Date: Mon, 1 Sep 2003 12:04:12 -0700 [thread overview]
Message-ID: <20030901120412.2047eeff.akpm@osdl.org> (raw)
In-Reply-To: <20030901182359.GA871@cliftonlabs.com>
"Dale E Martin" <dmartin@cliftonlabs.com> wrote:
>
> I just removed TCQ from my IDE setup, and I still lock up during boot. The
> last message displayed is:
> mice: PS/2 mouse device common for all mice
>
> The numlock comes on, and then I'm locked up hard, for instance, I cannot
> turn off the numlock at this point.
>
> One thing that I would note is that I don't have anything plugged into my
> PS2/2 port since I have a USB mouse. (A Kensington Model# MOSUU B, that
> works fine in 2.4.x, FWIW.) Please advise if there is more debugging that
> I can try.
Are you able to plug any PS/2 devices into the machine, see if that makes a
difference?
Also it would be useful to add the option "initcall_debug" to the kernel
boot command line. Then you will see a bunch of messages of the form
calling initcall 0xNNNNNNNN
Please look up the final address in the System.map file from the 2.6 build.
This will give us an idea of what the machine was trying to do when it
died.
next prev parent reply other threads:[~2003-09-01 19:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 15:33 repeatable, hard lockup on boot in linux-2.6.0-test4 Dale E Martin
2003-09-01 18:23 ` repeatable, hard lockup on boot in linux-2.6.0-test4 (more details) Dale E Martin
2003-09-01 19:04 ` Andrew Morton [this message]
2003-09-01 19:57 ` Dale E Martin
2003-09-01 22:28 ` Andrew Morton
2003-09-02 0:31 ` Dale E Martin
2003-09-02 1:23 ` Andrew Morton
2003-09-02 12:30 ` Dale E Martin
2003-09-02 20:03 ` Andrew Morton
2003-09-02 23:45 ` Chris Wright
2003-09-03 12:41 ` Dale E Martin
2003-09-02 11:04 ` repeatable, hard lockup on boot in linux-2.6.0-test4 Maciej Freudenheim
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=20030901120412.2047eeff.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dmartin@cliftonlabs.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