Kernel oops (2.6.24) while booting with battery inserted

Kernel oops (2.6.24) while booting with battery inserted

[Sam Lin]

[-- Attachment #1: Type: text/plain, Size: 235 bytes --]

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 ?

dmesg and dsdt as attachments.

Thanks,
Sam




[-- Attachment #2: dmesg.batt.oops.gz --]
[-- Type: application/x-gzip, Size: 10327 bytes --]

[-- Attachment #3: dsdt.dsl.gz --]
[-- Type: application/x-gzip, Size: 11863 bytes --]

Re: Kernel oops (2.6.24) while booting with battery inserted

[Thomas Renninger]

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?

Can you try:
initcall_debug
parameter and let the machine run into the bug again, pls.

Also send your .config.


  Thomas

Re: Kernel oops (2.6.24) while booting with battery inserted

[Thomas Renninger]

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

Re: Kernel oops (2.6.24) while booting with battery inserted

[Sam Lin]

It's reported as:
http://bugzilla.kernel.org/show_bug.cgi?id=10339

If I load battery.ko lattery it still cause kernel oops and freeze.

Thanks,
Sam

Thomas Renninger 提到:
> 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
>
>
>   

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html