Re: [>=2.6.23][BUG] Oops on power disconnection

[Sanjeev Aditya Naga]

Hello Thomas,

On Fri, Apr 4, 2008 at 2:34 AM, Thomas Renninger <trenn@xxxxxxx> wrote:
>
>
>  On Thu, 2008-04-03 at 21:45 +0530, Sanjeev Aditya Naga wrote:
>  > Hello Thomas,
>  >
>  > On Wed, Apr 2, 2008 at 11:42 PM, Thomas Renninger <trenn@xxxxxxx> wrote:
>  > >
>  > > On Wed, 2008-04-02 at 21:43 +0530, Sanjeev Aditya Naga wrote:
>  > >  > Hello Thomas,
>  > >  >
>  > >  > > Hi,
>  > >  > >
>  > >  > >
>  > >  > >  On Wed, 2008-04-02 at 18:38 +0530, Sanjeev Aditya Naga wrote:
>  > >  > >  > Hello Andrew Morton,
>  > >  > >  >
>  > >  > >  > Greetings!
>  > >  > >  >
>  > >  > >  > Thank you for the update. Is there anything I can do
>  > >  > >  > from my side?
>  > >  > >  >
>  > >  > >  > I thought it was a acpi (dsdt) problem. And based on
>  > >  > >  > a tutorial, I have tried to extract, fix, recompile the dsdt
>  > >  > >  > and use it with the kernel. But still I have the same problem.
>  > >  > >  > Let me know if I shall attach the dsdt (original) decompiled
>  > >  > >  > code, if that helps.
>  > >  > >
>  > >  > >  this could be due a general memory corruption problem through ACPICA.
>  > >  > >  If you get different backtraces on reboots even you only modified things
>  > >  > >  that do not have to do with the problem, it's probably that and related
>  > >  > >  to:
>  > >  > >  ïhttp://bugzilla.kernel.org/show_bug.cgi?id=10339
>  > >  > >
>  > >  > >  You might want to try the latest kernel or the patch posted there.
>  > >  >
>  > >  > Thank you for the update.
>  > >  > I have checked the bug and unfortunately its not the
>  > >  > same issue. Things work absolutely fine, when I'm
>  > >  > running on AC power. It even displays the exact
>  > >  > battery (and charging) status to me. It messes up
>  > >  > when suddenly AC power gets disconnected and
>  > >  > switches to battery mode (The time when I get Oops).
>  > >  > The system is still usable after switching to battery
>  > >  > mode and I still get correct battery stats until its
>  > >  > completely discharged. However most of the commands
>  > >  > like kill, poweroff, java doesn't work after the Oops.
>  > >  The bug is not related to battery, but to AML parsing and can therefore
>  > >  affect anything which is ACPI related.
>  > >
>  > >
>  > >  > BTW there is one similarity with the referenced bug.
>  > >  > If I boot the computer without AC Power, it gives the
>  > >  > same Oops and stops during booting itself.
>  > >  >
>  > >  > I shall try the latest kernel once and shall update you.
>  > >  That would be great.
>  > >  If it works, please give the patch there a try, IMO this one should see
>  > >  2.6.2[34].X stable kernels soon.
>  >
>  > I have got the lastest kernel 2.6.25-rc8 today. I observed that
>  > the referenced patch is already in the kernel. However this didn't
>  > solve the problem in question. I get the same Oops on this kernel
>  > as well. Find the latest dmesg along with the Oops:
>  Ok.
>  Maybe best is you document the backtraces/oopses with kernel versions at
>  bugzilla.kernel.org and add dmesg and acpidump.
>  It seems your machine notifies OS that the C-state table changed.
>  AFAIK this is rare and there might be a general bug in the cpuidle layer
>  which I do not know well.
>  Best you add Venkatesh and Shaohua Li <shaohua.li@xxxxxxxxx> to CC of
>  the bug.
>  While the backtrace shows a lot, cpuidle IMO is missing a general debug
>  option like in the cpufreq layer.
>  I couldn't find a single printk in the whole cpuidle/{cpuidle,sysfs}.c
>  files, even on error paths. ïAlso in the cpuidle specific parts of
>  drivers/acpi/processor_idle.c some debug printks may help for future bug
>  reports. It is very hard to guess what happened...

Thank you for the update:

I have just registered a bug at
http://bugzilla.kernel.org/show_bug.cgi?id=10394
as directed by you.

Kind Regards,
Sanjeev
¢éì®&Þ~º&¶¬–+-±éÝ¥Šw®žË±Êâmébžìdz¹Þ)í…æèw*jg¬±¨¶‰šŽŠÝj/êäz¹ÞŠà2ŠÞ¨è­Ú&¢)ß«a¶Úþø®G«éh®æj:+v‰¨Šwè†Ù>Wš±êÞiÛaxPjØm¶ŸÿÃ-»+ƒùdš_