Re: Several problems on a toshiba S3000-X11

Bob McElrath
2002-09-30T16:33:24Z

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

?ric Brunet [ebrunet-l5PIGlIYzrxGWvitb5QawA@public.gmane.org] wrote:
> On Fri, Sep 27, 2002 at 05:45:42PM +0200, Ducrot Bruno wrote:
> > > When I read the battery state for the first couple of times, the
> > > /proc/acpi files claim that I have two batteries present, and that both
> > > batteries have a charge of 2040 mAh (capacity is 4000 mAh). After a
> > > couple of readings, I have the truth (only one battery and whatever
> > > capacity I have left.) That's annoying, and it didn't happen with my
> > > previous kernel. I don't now if it comes from the patched DSDT or from
> > > the new version of the acpi patch.
> >
> > This is a trouble with the original AML, and I have not corrected it.
> >
> Are you sure ? Bob McElrath and I never had this problem with the
> original DSDT; it appeared when I used your hand-tuned version. It looks
> that the problem lies into your correction...

Also note that I am using a Compal DSDT. You guys probably have Toshiba
DSDT's. My native DSDT correctly reports battery status. (although
when plugged in with a full battery it says 'charging state: unknown')
But discharge reporting works fine.

> > Only the restore should be made. Actually, the
> It is noted, I will try that. But I hope that it will go mainstream in a
> future version.
> >
> > > So the computer shuts down, without warning, while it is not particulary
> > > hot, with nothing written in the logs, while the user was just using vim
> > > in a xterm, at irregular times, and it can happen two or three times in
> > > an afternoon.
> > >
> >
> > Yes, I have this trouble with some version of ACPI now. I think that I need
> > to incorporate now more smoothly with ACPI (that is, I need to use
> > the function acpi_ec_read() etc. instead of providing them in the module,
> > and so I avoid some possible races..)
>
> So you confirm that it is ACPI related ? Do you think I can get rid of
> that problem by disabling parts of ACPI ? (I guess I could boot with no
> acpi at all, but that means no battery readings, no software shutdown and
> no S1. That would be a sad world...)

Once upon a time I was able to keep my computer up and running for over
a week by using acpi=noacpi on the kernel's command line. This was
sometime in July (probably with the July ACPI code). I have tried it
since then and been unable to reproduce this behavior. (I unwisely
nuked that kernel)

However, as my computer normally stays up for ~1 day on average
(sometimes two), I could believe a statistical fluctuation that stayed
up for a week. ;)

Cheers,
-- Bob

Bob McElrath (rsmcelrath-9geRo0GdX4mkVGS65fRQmodd74u8MsAO@public.gmane.org)
Univ. of Wisconsin at Madison, Department of Physics

"The purpose of separation of church and state is to keep forever from
these shores the ceaseless strife that has soaked the soil of Europe in
blood for centuries." -- James Madison