From: Manfred Spraul <manfred@colorfullife.com>
To: john@grulic.org.ar
Cc: linux-kernel@vger.kernel.org
Subject: oops followed by "kernel BUG"s
Date: Sun, 25 Feb 2001 14:21:21 +0100 [thread overview]
Message-ID: <3A9906D1.70BDAAD8@colorfullife.com> (raw)
> When I woke today I found I'd gotten the following oops,
>
> kernel: EIP: 0010:[bdput+5/96]
> Code; <_EIP>:
> 0: f0 ff 4b 08 lock decl 0x8(%ebx)
> Call Trace: [clear_inode+194/220]
> [dispose_list+59/84]
>
> kernel: eax: 00020000 ebx: 00020000 ecx: ca58a648 edx: c15ddfa4
^
A single bit error: inode->i_bdev was 00000000, and overnight one bit
changed.
It's a hardware problem - cpu overheating, power spike, overclocked cpu,
bad memory.
--
Manfred
next reply other threads:[~2001-02-25 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 13:21 Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-25 11:37 oops followed by "kernel BUG"s John R Lenton
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=3A9906D1.70BDAAD8@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=john@grulic.org.ar \
--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