All of lore.kernel.org
 help / color / mirror / Atom feed
From: jgluckca@netscape.net
To: linux-kernel@vger.kernel.org
Subject: 2.4.19 trashes CMOS
Date: Sat, 31 Aug 2002 14:27:10 -0300	[thread overview]
Message-ID: <3D70FC6E.7060907@netscape.net> (raw)

Hi

I'm really not sure who to send this to since I have no idea when or 
where it happens.

The problem does not happen on version 2.4.18 or any earlier version. I 
checkout the hardware after constantly getting CMOS checksum errors on 
bootup. There is no hardware problem.

My configurations of 2.4.18 and 2.4.19 are identical. They are SMP 
kernels for a dual PIII on a Tyan S1836DLUAN motherboard. I used gcc3.1 
to compile both kernels.
If I boot 2.4.19 and then ask it to reboot (no power off). I do 
"shutdown -r now" the CMOS will be trashed. I've gone back to the 2.4.18 
kernel and the problem is gone.

I'll be happy to look at the problem in detail if someone can tell me 
where to start looking. I'm a professional programmer with experience in 
writing operating systems. I haven't looked at the Linux kernel in any 
detail though.

Please reply to me directly since I don't subscribe to this list.

Thanks

John


                 reply	other threads:[~2002-08-31 17:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3D70FC6E.7060907@netscape.net \
    --to=jgluckca@netscape.net \
    --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 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.