mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Nathan Walp <faceprint@faceprint.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: random reboots
Date: Thu, 26 Apr 2001 03:36:43 +0200	[thread overview]
Message-ID: <20010426033643.L1125@ppc.vc.cvut.cz> (raw)
In-Reply-To: <3AE5A762.675581E4@faceprint.com>
In-Reply-To: <3AE5A762.675581E4@faceprint.com>; from faceprint@faceprint.com on Tue, Apr 24, 2001 at 12:18:42PM -0400

On Tue, Apr 24, 2001 at 12:18:42PM -0400, Nathan Walp wrote:
> I upgraded the BIOS on this Asus A7V sometime in the past week, but I
> honestly don't remember when.  From 1005C to 1007.  This was released in
> march, so I assumed it was pretty stable, but it could be the cause. 
> I'm going to go downgrade now, but is this more likely to be a kernel
> bug, or a hardware bug/new bios bug?

No problem here. I'm using 1007 since its release in first half
of March.

Linux version 2.4.3-ac12-amd (root@ppc) (gcc version 3.0 20010402 (Debian prerelease)) #1 Mon Apr 23 02:31:13 CEST 2001
...
Kernel command line: BOOT_IMAGE=Linux ro root=2105 video=matrox:vesa:0x105,fv:85 devfs=nomount
Initializing CPU#0
Detected 1009.013 MHz processor.
...
CPU: AMD Athlon(tm) Processor stepping 02
Enabling fast FPU save and restore... done.
...
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.14)
...

Except that I got 'ide only func: 14' today with my Promise PDC20265
(which looks strange to me - either all Intel, VIA and Promise have
same bug in their UDMA hardware, or there is a bug in Linux IDE 
driver...) (I had to reboot because of kernel somehow believed that
it read some garbage instead of MBR from hdg, so I could not run my 
repartitioning session, as I found no way to invalidate hdg kernel
cache). 
But machine for sure does not spontaneously reboot. And I have 
enabled local apic in kernel configuration. All previous kernels
were built with Debian's 2.95.3-something, ac12 was built with
gcc-3.0, as I wanted to update anyway, and ac12 just gave me a reason.
					Best regards,
						Petr Vandrovec
						vandrove@vc.cvut.cz


  reply	other threads:[~2001-04-26  1:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24 16:18 Nathan Walp
2001-04-26  1:36 ` Petr Vandrovec [this message]
2001-04-26  1:52   ` Nathan Walp
2006-02-13 21:04 Random reboots Ryan Richter
2006-02-13 21:10 ` anders
2006-02-13 21:22   ` Ryan Richter
     [not found]     ` <7c3341450602131332x2fcd7d8co@mail.gmail.com>
2006-02-13 21:39       ` Ryan Richter
2006-02-13 21:49         ` Ryan Richter
2006-02-14  8:54           ` Erik Mouw
2006-02-14 13:29             ` Ryan Richter
2006-02-14 14:47               ` Nick Warne
2006-02-14 22:22               ` Jean Delvare
2006-02-15 14:28                 ` Ryan Richter
2006-02-15 15:11                   ` linux-os (Dick Johnson)
2006-02-15 15:13                     ` Ryan Richter
2006-02-15 15:41                   ` Jean Delvare
2006-02-15 16:00                     ` Ryan Richter
2006-02-15 16:20                       ` Jean Delvare
2006-02-15 16:30                         ` Ryan Richter
2006-02-15 18:46                         ` Ryan Richter
2006-02-27 20:35                         ` Ryan Richter

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=20010426033643.L1125@ppc.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=faceprint@faceprint.com \
    --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

all inboxes | Powered by JetHome®