From: Dieter Rohlfing <u490248-uKKRHEr75Vc@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Laptop does not reboot
Date: Sun, 29 Feb 2004 17:16:06 +0100 [thread overview]
Message-ID: <40421046.7582AFD3@imail.de> (raw)
In-Reply-To: 3ACA40606221794F80A5670F0AF15F8401CBB6F8@PDSMSX403.ccr.corp.intel.com
Hi Luming,
> I think you need to set up serial console to monitor the kernel message
> of rebooting process to sort out valuable clues.
Here are the last lines from my kernel log:
kernel: unloading PCMCIA Card Services
kernel: Kernel logging (proc) stopped.
kernel: Kernel log daemon terminating.
The last message on the console is 'rebooting system ...'. That's all
and then the lights went off. As far as I can see the shutdown process
comes to a complete end. On booting the next time there's no fsck'ing
because of unproperly unmounting.
> I presume that if acpi=off doesn't work, then acpi is exempt from
> any accusation. :)
Sorry, but I do not agree. Suspending and power management is one side
of ACPI, but ACPI is also used to setup und configure the system. As far
as I noted, the kernel still uses some ACPI information to setup up the
system, even if you have 'acpi=off' on your command line. In the case of
'acpi=off' you definitely have no suspend possibilities.
As Bernd Schubert suggested, I'll give kernel 2.6.x a try. In regards to
PCI kernel 2.2.x had a very 'simple' approach (compared with 2.4.x).
2.4.x makes a better job. But with my Dell I7500 it broke something
(okay, I admit the I7500 has a broken BIOS, too). My only hope is that
2.6.x corrects what 2.4.x didn't achieve.
Dieter
--
Every mail not from this mailing list will be deleted.
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
next prev parent reply other threads:[~2004-02-29 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 2:56 Laptop does not reboot Yu, Luming
2004-02-29 16:16 ` Dieter Rohlfing [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-26 20:41 Dieter Rohlfing
[not found] ` <403E59FF.990E2CD0-uKKRHEr75Vc@public.gmane.org>
2004-02-27 1:09 ` Bernd Schubert
[not found] ` <200402270209.04355.bernd-schubert-S0/GAf8tV78@public.gmane.org>
2004-02-27 8:07 ` Arjen Verweij
2004-02-29 15:53 ` Dieter Rohlfing
2004-03-01 1:04 ` Karol Kozimor
2004-03-05 18:56 ` Dieter Rohlfing
2004-03-02 15:25 ` Dieter Rohlfing
2004-03-04 23:56 ` Dieter Rohlfing
2004-03-06 17:51 ` Dieter Rohlfing
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=40421046.7582AFD3@imail.de \
--to=u490248-ukkrher75vc@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@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