From: Ethan Glasser-Camp <glasse-IL7dBOYR4Vg@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Oops during startup
Date: Tue, 1 Jun 2004 21:35:12 -0400 [thread overview]
Message-ID: <20040602013512.GA570@paladin> (raw)
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
2.6.6 oopses on startup for me. acpi=off seems to work OK.
My Thinkpad T-30 has served me faithfully for about 1.5 years, but was
needing some service so I took it to the shop today. They gave me a
replacement laptop (same model, still a T-30), but when I tried to
boot up, I got a kernel oops. 2.6.5 boots up fine, and so does 2.6.6
when given the boot parameter acpi=off. The machines are basically
identical except for the CD-ROM drive. Might this cause a problem? Or
should I be pointing a finger at the ACPI tables and other firmware?
Since the kernel oopses before it finishes booting up, I can't even
scroll up to the top of it to see what the oops message is. I can copy
the callback if it helps. How can I help to diagnose the problem?
Ethan Glasser-Camp
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2004-06-02 1:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 1:35 Ethan Glasser-Camp [this message]
[not found] ` <20040602013512.GA570-FdgSi869q7U@public.gmane.org>
2004-06-02 2:48 ` Oops during startup Andrew D. Keyser
2004-06-02 6:28 ` David Eriksson
[not found] ` <1086157732.2833.155.camel-+wCu4fnbpeSdFUVPxe8kGA@public.gmane.org>
2004-06-02 16:17 ` Ethan Glasser-Camp
[not found] ` <20040602161747.GA563-FdgSi869q7U@public.gmane.org>
2004-06-08 18:35 ` Ethan Glasser-Camp
-- strict thread matches above, loose matches on Subject: below --
2004-06-02 3:17 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F840483B1C4-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-06-03 3:43 ` Andrew D. Keyser
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=20040602013512.GA570@paladin \
--to=glasse-il7dboyr4vg@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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