public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hood <jdthood@mail.com>
To: Dave Jones <davej@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sysctl interface to bootflags?
Date: 10 Oct 2001 08:37:23 -0400	[thread overview]
Message-ID: <1002717445.5284.39.camel@thanatos> (raw)
In-Reply-To: <Pine.LNX.4.30.0110100844340.26743-100000@Appserv.suse.de>
In-Reply-To: <Pine.LNX.4.30.0110100844340.26743-100000@Appserv.suse.de>

On Wed, 2001-10-10 at 02:46, Dave Jones wrote:

> Ouch. Can you verify that the CMOS register its changing matches
> with what's listed in the BOOT record ?
> add a printk to bootflag.c to check.

I haven't rebooted since this happened; the error
occurred when I resumed from hibernation.

In any case, I suspect that the BIOS reset whatever
register it was that was incorrectly set.  Here again
is the output of the sbf program that cause the problem.
I ran the "sbf-0.3" version of the program, modified
to ignore the parity error on the value read back from the
register.

root@thanatos:/home/jdthood/src/sbf# ./a.out
BOOT @ 0x07fd0040
CMOS register: 0x33
Read current value := 0x88
Read updated value := 0x89

We need to come to a better understanding of what it's doing
differently from bootflag.c, which writes to the right place.

Regards
Thomas




  reply	other threads:[~2001-10-10 12:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-09  2:56 sysctl interface to bootflags? Thomas Hood
2001-10-10  6:46 ` Dave Jones
2001-10-10 12:37   ` Thomas Hood [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-09  3:29 Thomas Hood
2001-10-09 14:01 Thomas Hood
2001-10-09 14:15 ` Dave Jones
2001-10-09 15:21   ` Thomas Hood
2001-10-09 15:34     ` Dave Jones
2001-10-09 15:50       ` Thomas Hood
2001-10-09 15:52         ` Dave Jones
2001-10-09 15:56           ` Thomas Hood
2001-10-09 16:53             ` Dave Jones
2001-10-09 14:18 ` Alan Cox
2001-10-09 15:35   ` Thomas Hood
2001-10-09 22:48 Thomas Hood
2001-10-10 14:05 ` Dave Jones

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=1002717445.5284.39.camel@thanatos \
    --to=jdthood@mail.com \
    --cc=davej@suse.de \
    --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