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

[Eugen Dedu <Eugen.Dedu@pu-pm.univ-fcomte.fr>]

On 10/07/12 05:31, Jonathan Nieder wrote:
> Eugen Dedu wrote:
>
> > Making a git bissect inside these versions will take me ages,
> > especially that the freeze is not easily reproducible and it is
> > difficult during a test to be sure that the freeze does NOT appear.
>
> Fair enough.  When's the last time it happened?  Is the error always
> "kobject_add_internal failed for BAT0 with -EEXIST"?

It appeared last time two weeks ago, when I was still using 3.3.  Since 
then I have been using 3.4, and no problem so far.

There were two errors:
- "kobject_add_internal failed for BAT0 with -EEXIST" and no other message
- the error with the recursivity, the acpi function and so on (the image 
I posted).

But probably they are related, since BAT0 (battery 0) is surely to acpi.

> I tried searching the web for that message but you seem to be the only
> one getting it in this circumstance. :)  Alas.
>
> If you can still reproduce it occasionally with some kernel, please
> report the symptoms to linux-acpi@vger.kernel.org, cc-ing either me or
> this bug log so we can track it.  Be sure to mention:
>
>   - precise steps to reproduce, expected result, actual result, and
>     how the difference indicates a bug (should be simple enough)
>   - how reproducible it is
>   - which kernels you have tested and what happened with each
>   - full "dmesg" output from booting an affected kernel, as an
>     attachment or link
>   - acpidump output, as an attachment or link
>   - any other weird symptoms or workarounds
>
> Hopefully someone there can suggest a way to figure out what is
> happening, for example by applying some patch or enabling some
> debugging feature to be ready for when it happens next.
>
> Thanks again for a clear report, and sorry I have no better advice.

No problem for me, I am glad that it works on 3.4!  So if you prefer, 
you can close this bug.

--
Eugen