From: Thomas Renninger <trenn@suse.de>
To: Sam Lin <itrs.lin@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Kernel oops (2.6.24) while booting with battery inserted
Date: Thu, 27 Mar 2008 16:21:11 +0100 [thread overview]
Message-ID: <1206631271.19236.86.camel@queen.suse.de> (raw)
In-Reply-To: <1206630454.19236.79.camel@queen.suse.de>
On Thu, 2008-03-27 at 16:07 +0100, Thomas Renninger wrote:
> On Thu, 2008-03-27 at 13:59 +0800, Sam Lin wrote:
> > Hi List,
> >
> > I encountered kernel oops (Ubuntu 2.6.24-12) while booting with battery
> > inserted.
> > Some workaround are acpi=off, avoiding loading battery.ko or putting
> > battery away.
> >
> > Any idea ?
> Why do you need:
> acpi_fake_ecdt
> parameter? This does not even exist (anymore? I searched 2.6.25).
>
> > dmesg and dsdt as attachments.
>
> I expect removing the line:
> acpi_bus_generate_netlink_event(device->pnp.device_class,
> device->dev.bus_id, event,
> acpi_battery_present(battery));
> in battery.c makes the machine work or at least go a bit further?
>
> Could it be that you compiled in ACPI modules and that:
> fs_initcall(acpi_event_init);
> in drivers/acpi/event.c
> has not been called and initialized the netlink acpi stuff, but battery
> has already tried to send an event?
acpi_event_init should have been called already...
I still think it has to do with the netlink event.
As it is rather early, maybe because of that.
Does it work for you if you load the battery module later?
Can you open a bugreport on bugzilla.kernel.org, add .config and
dmesg/acpidump you already sent and add me to CC.
Thanks,
Thomas
next prev parent reply other threads:[~2008-03-27 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 5:59 Kernel oops (2.6.24) while booting with battery inserted Sam Lin
2008-03-27 15:07 ` Thomas Renninger
2008-03-27 15:21 ` Thomas Renninger [this message]
2008-03-27 16:02 ` Sam Lin
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=1206631271.19236.86.camel@queen.suse.de \
--to=trenn@suse.de \
--cc=itrs.lin@gmail.com \
--cc=linux-acpi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.