Kernel fault from ACPI when using W83627EHG on 2.6.15

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

 



Resolved.

It appears to be a BIOS bug.  The mobo had BIOS version 1.0 installed, and I
updated it to v1.4.  I cannot now repeat the problem, and all runs smoothly.

Should have checked that first really, I guess...

> -----Original Message-----
> From: Jean Delvare [mailto:khali at linux-fr.org]
> Sent: 24 April 2006 07:35
> To: Roger Lucas
> Cc: LM Sensors
> Subject: Re:  Kernel fault from ACPI when using W83627EHG on
> 2.6.15
> 
> Hi Roger,
> 
> > > When starting a new thread, please do NOT use the "reply" function of
> > > your e-mail client on a random post. This confuses users of threading
> > > e-mail clients a lot.
> >
> > I thought that I had started the thread with a new subject line.  Is
> there
> > something else that I am missing that happens behind-the-scenes?
> 
> No, changing the subject line doesn't make a new discussion thread. As
> long as you use "reply", your post will include an "In-Reply-To:"
> header with a reference to the post you are supposedly replying to, and
> most "threading" clients will rely on this information rather than the
> subject line. You really need to use "new" or "compose" to start a new
> thread.
> 
> > I've raised the problem on the mailing list:
> > http://permalink.gmane.org/gmane.linux.acpi.devel/17523
> >
> > I still want to know what is really going on though.  This ACPI area is
> not
> > one I am familiar with, and although I have tried reading the
> documentation,
> > much of it is old and much more seems to indicate that a lot is
> > manufacturer-specific.
> >
> > I have a few work-arounds for this problem, but I'm not comfortable
> using
> > them until I know what is actually going on.  Disabling ACPI completely
> > resolves the problem (but I lose ACPI).  Removing the "thermal" module
> in
> > ACPI stops the kernel dump, but the machine still runs very slowly until
> the
> > over-temperature situation clears.  This may be correct behaviour (e.g.
> the
> > processor is run at a much lower clock speed to help cool it down) but I
> > don't know for sure.   If I just set a very high cpu temperature limit
> (e.g.
> > 95C) then this also "fixes" the problem, but it is really just a hack
> rather
> > than a real solution.
> >
> > Hopefully, the guys on the ACPI mailing list can help.  This doesn't
> seem to
> > be a problem with lm-sensors (as far as I can see).
> 
> Yup, I agree with all you said above.
> 
> --
> Jean Delvare





[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux