From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] BIOS Corruption (was : new abituguru driver in mm
Date: Mon, 07 Aug 2006 10:19:09 +0000 [thread overview]
Message-ID: <20060807121909.fef9fe74.khali@linux-fr.org> (raw)
In-Reply-To: <ce9ef0d90608052222j74e9f6fes40cbc5edf5678577@mail.gmail.com>
Hi Sunil, Hans,
> I found an issue with the driver. It seems to have put something in the
> uguru part of BIOS, which makes my BIOS hang when I enter Abit uGuru
> temperature monitor screen in the BIOS. No keys work and only way for me at
> that point is to give it the three finger salute. The peculiar thing I
> noticed was that somehow it modified the shutdown and beep CPU temperatures
> to 245C and 235C while I had them set at 65C and 75C.
>
> As soon as the temp monitor displays 245C in CPU row, it just hangs. The
> next values to be displayed are the enable bit for these temps, I think.
>
> I never used the driver to write anything to BIOS, so how did it end up
> updating those values?
Err, this is bad :(
Hans, see why I was reluctant to having your driver in the kernel tree?
Nothing personal, but that kind of problem is to be expected when
writing a driver without a datasheet :(
What should we do now? Mark the driver broken in the kernel tree?
2.6.18 is just around the corner, and we sure don't want people to
corrupt their BIOS.
Sunil, did you try a complete power-off (with PSU switched off or
unplugged) to see if the default values are back?
--
Jean Delvare
next prev parent reply other threads:[~2006-08-07 10:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 5:22 [lm-sensors] BIOS Corruption (was : new abituguru driver in mm Sunil Kumar
2006-08-07 10:19 ` Jean Delvare [this message]
2006-08-07 16:10 ` Sunil Kumar
2006-08-07 19:34 ` Sergey Vlasov
2006-08-07 20:53 ` Sunil Kumar
2006-08-08 15:25 ` Sergey Vlasov
2006-08-09 18:35 ` Hans de Goede
2006-08-09 20:48 ` Sunil Kumar
2006-08-10 11:57 ` Hans de Goede
2006-08-10 15:48 ` Sunil Kumar
2006-08-11 7:47 ` Jean Delvare
2006-08-11 7:50 ` Hans de Goede
2006-08-11 9:05 ` Jean Delvare
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060807121909.fef9fe74.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.