From: Maciej Freudenheim <fahren@student.uci.agh.edu.pl>
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
Date: Tue, 2 Sep 2003 13:04:58 +0200 [thread overview]
Message-ID: <20030902110458.GC3490@piggie> (raw)
In-Reply-To: <20030901153305.GA1429@cliftonlabs.com>
Dale E Martin wrote:
> However, 2.6.0-test4 locks up hard just after loading the PS/2 mouse stuff.
> Unfortunately none the boot messages make it to disk since I don't get far
> enough in the boot process for syslog to turn on.
> CONFIG_ACPI=y
I had exactly the same problems. However, adding pci=noacpi to kernel
boot command line fixes the problem.
Maciej Freudenheim.
-
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/
Dale E Martin wrote:
> However, 2.6.0-test4 locks up hard just after loading the PS/2 mouse stuff.
> Unfortunately none the boot messages make it to disk since I don't get far
> enough in the boot process for syslog to turn on.
> CONFIG_ACPI=y
I had exactly the same problems. However, adding pci=noacpi to kernel
boot command line fixes the problem.
Maciej Freudenheim.
prev parent reply other threads:[~2003-09-02 12:41 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
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 ` Maciej Freudenheim [this message]
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=20030902110458.GC3490@piggie \
--to=fahren@student.uci.agh.edu.pl \
--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