From: ccrawford@acb.org
To: speakup@braille.uwo.ca
Subject: Re: Kernel bug--machine lockup
Date: Tue, 10 Dec 2002 21:30:16 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0212102129170.1034-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0212101922320.10461-100000@babel.hpcc.noaa.gov>
Is this the twilight zone? I came home and found my linux box off.
Nobody here but the cat. It booted fine, but wierdest thing.
-- charlie Crawford.
On Tue, 10
Dec 2002 jwantz@hpcc.noaa.gov wrote:
> Hi,
> I came home this afternoon and experienced something that I have never
> seen with linux. My computer was completely dead, no speech and
> nonresponsive keys. I thought it was WINDBLOWS!
>
> Here is the pertinent information I obtained when I looked at
> /var/log/messages:
> Dec 10 16:27:00 pcp218693pcs kernel: ------------[ cut here ]------------
> Dec 10 16:27:00 pcp218693pcs kernel: kernel BUG at page_alloc.c:133!
> Dec 10 16:27:00 pcp218693pcs kernel: invalid operand: 0000
> Dec 10 16:27:00 pcp218693pcs kernel: nls_iso8859-1 sr_mod snd-pcm-oss snd-mixer-oss snd-emu10k1-synth snd-emux-synt
> Dec 10 16:27:00 pcp218693pcs kernel: CPU: 0
> Dec 10 16:27:00 pcp218693pcs kernel: EIP: 0010:[<c0136b4c>] Not tainted
> Dec 10 16:27:00 pcp218693pcs kernel: EFLAGS: 00010206
> Dec 10 16:27:00 pcp218693pcs kernel:
> Dec 10 16:27:00 pcp218693pcs kernel: EIP is at __free_pages_ok [kernel] 0x5c (2.4.18-14)
> Dec 10 16:27:00 pcp218693pcs kernel: eax: 00017818 ebx: c1524570 ecx: c1000030 edx: 00000000
> Dec 10 16:27:00 pcp218693pcs kernel: esi: 00000000 edi: 00000000 ebp: 17818067 esp: c56e7de8
> Dec 10 16:27:00 pcp218693pcs kernel: ds: 0018 es: 0018 ss: 0018
> Dec 10 16:27:00 pcp218693pcs kernel: Process sendmail (pid: 31337, stackpage=c56e7000)
> Dec 10 16:27:00 pcp218693pcs kernel: Stack: c02ff4c0 00000002 00000246 00001000 c02ff4c0 00000000 c02ff4c0 c013c580
> Dec 10 16:27:00 pcp218693pcs kernel: d5bfd4b8 00000000 d594c9b4 0000b000 0000c000 17818067 c012bbe0 c1524570
> Dec 10 16:27:00 pcp218693pcs kernel: 00000001 c24ed55c c24ede40 0000000c 40400000 cfc81404 4026e000 00000000
> Dec 10 16:27:00 pcp218693pcs kernel: Call Trace: [<c013c580>] page_remove_rmap [kernel] 0x80 (0xc56e7e04))
> Dec 10 16:27:00 pcp218693pcs kernel: [<c012bbe0>] zap_pte_range [kernel] 0xf0 (0xc56e7e20))
> Dec 10 16:27:00 pcp218693pcs kernel: [<c012a1bb>] do_zap_page_range [kernel] 0x8b (0xc56e7e48))
> Do you think this is worth passing on to the kernel development team? I
> am running Redhat 8.0 kernel 2.4.18-14.
>
> Jim Wantz WB0TFK
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
jwantz
` ccrawford [this message]
` jwantz
` Janina Sajka
` jwantz
` ccrawford
` William F. Acker WB2FLW +1-303-777-8123
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=Pine.LNX.4.44.0212102129170.1034-100000@localhost.localdomain \
--to=ccrawford@acb.org \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).