From: Stephen Clark <stephen.clark@earthlink.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: spontaneous reboots 2.6
Date: Wed, 11 Feb 2004 14:30:51 -0500 [thread overview]
Message-ID: <402A82EB.6010405@earthlink.net> (raw)
Gentle people,
Since 2.6.2-rc1 on Jan 26 thru 2.6.2-mm1 I have had 5 occasions where my
system rebooted, nothing shows up in the system log. I had been using
2.4.20 without ever having had this happen.
Anybody have any ideas or additional information I can provide?
Hardware:
00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333]
00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo
KT266/A/333 AGP]
00:08.0 Multimedia video controller: Brooktree Corporation Bt878 Video
Capture (rev 02)
00:08.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture
(rev 02)
00:09.0 Ethernet controller: Linksys Network Everywhere Fast Ethernet
10/100 model NC100 (rev 11)
00:0a.0 Ethernet controller: Linksys Network Everywhere Fast Ethernet
10/100 model NC100 (rev 11)
00:0b.0 SCSI storage controller: BusLogic BT-946C (BA80C30) [MultiMaster
10] (rev 08)
00:0d.0 Unknown mass storage controller: Promise Technology, Inc. 20265
(rev 02)
00:0e.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus
Master IDE (rev 06)
00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 1b)
00:11.3 USB Controller: VIA Technologies, Inc. USB (rev 1b)
00:11.4 USB Controller: VIA Technologies, Inc. USB (rev 1b)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II]
(rev 70)
01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 RF/SG AGP
reply other threads:[~2004-02-11 19:31 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=402A82EB.6010405@earthlink.net \
--to=stephen.clark@earthlink.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sclark46@earthlink.net \
/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.