From: jdthood@home.dhs.org (Thomas Hood)
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PnPBIOS 2.4.9-ac1[56] Vaio fix
Date: Tue, 2 Oct 2001 09:37:50 -0400 (EDT) [thread overview]
Message-ID: <20011002133751.074DA10E6@thanatos.toad.net> (raw)
>> However, if is_sony_vaio_laptop is 0 at pnpbios init
>> time then if you look in /proc/bus/pnp you'll see numerical
>> entries there.
>
>Yes:
># cd /proc/bus/pnp/
># ls
>00 01 02 03 04 05 06 07 08 09 0b 0c 0d 0e boot devices
># ls boot
>00 01 02 03 04 05 06 07 08 09 0b 0c 0d 0e
>
>> Want to crash your machine? Just read from
>> them. (The numerically named entries in /proc/bus/pnp/boot
>> should be okay to read and write, though.)
>
>It doesn't crash. I did a "cat /proc/bus/pnp/0* > /dev/null"
>and the laptop is still alive.
Well! That's interesting. Reading from those files
induces the same calls to the PnP BIOS that crashed
your system before. A mystery. Perhaps there's a way
to use the "current" config of your PnP BIOS after all---
so long as you avoid the particular [sequences of] calls that
cause crashes. You'll have to experiment with this yourself.
In the meantime, though, it's safest to disable use of
the "current" config entirely on Sony Vaio Laptops. I'll
test your patch now.
--
Thomas Hood
(Don't reply to the From: address but to jdthood_AT_yahoo.co.uk)
next reply other threads:[~2001-10-02 13:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 13:37 Thomas Hood [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-02 15:15 [PATCH] PnPBIOS 2.4.9-ac1[56] Vaio fix Thomas Hood
2001-10-02 1:54 Thomas Hood
2001-10-01 12:54 Thomas Hood
2001-10-01 13:41 ` Stelian Pop
2001-10-01 19:21 ` J.D. Hood
2001-10-02 8:35 ` Stelian Pop
2001-10-01 13:44 ` Alan Cox
2001-09-30 17:46 Thomas Hood
2001-10-01 10:04 ` Stelian Pop
2001-10-01 13:50 ` St?phane List
2001-09-29 0:29 Thomas Hood
2001-09-29 0:28 Thomas Hood
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=20011002133751.074DA10E6@thanatos.toad.net \
--to=jdthood@home.dhs.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox