[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#677016: resume failure: kobject_add_internal failed for BAT0 with -EEXIST



Eugen Dedu wrote:

> Here it is: another freeze during resume, with kernel 3.3 too.

Thanks for the quick feedback.  (As a reminder to myself, the message
is

	BUG: unable to handle kernel paging request at fffffff(lens flare)
	IP: [<ffffffff810514c7>] kthread_data+0x7/0xc
	PGD 1607067 PUD 1608067 PMD 0
	Oops: 0000 [#2] SMP
	CPU 0
[...]
	Code: 3f 48 c1 e5 03 48 c1 e0 06 48 8d b0 50 54 40 81 29 ee e8 62 c0 00 00 81 4b 14 00 00 00 04 41 59 5b 5d c3 48 8b 87 a0 02 00 00 <48> 8b 40 f8 c8 48 3b 3d 95 43 72 00 75 08 0f bf 87 6a 06 00 00
[...]
	Fixing recursive fault but reboot is needed!

Call trace involves trying to handle a page fault in
led_trigger_unregister, called by power_supply_unregister, called by
acpi_battery_notify.  The first oops looks similar but scrolled off
the screen.  This is a 3.3.y kernel with virtualbox modules loaded.)

Ideas for moving forward:

 - please attach:
   - full "dmesg" output from a normal boot
   - "acpidump" output
 - see Documentation/power/basic-pm-debugging.txt from [1] or the
   kernel-doc-3.2 package.  Does suspend-to-disk work?  Do pm_test
   modes work?  Are any warnings shown at suspend time that can be
   captured using a serial console or netconsole with
   no_console_suspend?  Does unloading the "battery" module before
   suspend avoid trouble?

Hope that helps,
Jonathan

[1] http://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt



Reply to: