From: "Condor" <condor@vereya.net>
To: "Mike Fedyk" <mfedyk@matchmail.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.24 may be bug in prints.c:341
Date: Sat, 17 Jan 2004 22:18:25 +0200 [thread overview]
Message-ID: <010801c3dd37$1ff2ee20$8648493e@ixip.net> (raw)
In-Reply-To: 20040117195151.GY1748@srv-lnx2600.matchmail.com
----- Original Message -----
From: "Mike Fedyk" <mfedyk@matchmail.com>
To: "Condor" <condor@vereya.net>
Cc: <linux-kernel@vger.kernel.org>
Sent: Saturday, January 17, 2004 9:51 PM
Subject: Re: 2.4.24 may be bug in prints.c:341
> On Sat, Jan 17, 2004 at 09:42:46PM +0200, Condor wrote:
> > Hello all,
> >
> > 1. My server stop work after trying to access hard drives.
> > 2. My server have kernel panic when trying to access hard drives. I
don't
> > now what is the real problem,
>
> Did you run fsck on the filesystem?
Yes i run, but problem did'nt resolved. The problem is in hard drive, now
disk is gone and may be every thing
is work fine ...
>
> > Jan 16 01:55:19 heaven kernel: kernel BUG at prints.c:341!
> > Jan 16 01:55:19 heaven kernel: invalid operand: 0000
> > Jan 16 01:55:19 heaven kernel: CPU: 1
> > Jan 16 01:55:19 heaven kernel: EIP: 0010:[<c01a3eb8>] Not tainted
> > Jan 16 01:55:19 heaven kernel: EFLAGS: 00010286
> > Jan 16 01:55:19 heaven kernel: eax: 0000004a ebx: eac82800 ecx:
00000000
> > edx: f6febf7c
> > Jan 16 01:55:19 heaven kernel: esi: 00000000 edi: c2849ed4 ebp:
00000002
> > esp: c2849e24
> > Jan 16 01:55:19 heaven kernel: ds: 0018 es: 0018 ss: 0018
> > Jan 16 01:55:19 heaven kernel: Process kupdated (pid: 7,
stackpage=c2849000)
> > Jan 16 01:55:19 heaven kernel: Stack: c0270d4d c0324fc0 c0323560
eac82800
> > c01b33f9 eac82800 c027b9a0 00001295
> > Jan 16 01:55:19 heaven kernel: 00000296 00000001 00000004
eac82800
> > 00000006 c2849ed4 00000000 c01b39e7
> > Jan 16 01:55:19 heaven kernel: c2849ed4 eac82800 00000001
00000006
> > f899d38c 00000000 00000024 00000004
> > Jan 16 01:55:19 heaven kernel: Call Trace: [<c01b33f9>] [<c01b39e7>]
> > [<c01b30e7>] [<c01a0c50>] [<c014785c>]
> > Jan 16 01:55:19 heaven kernel: [<c014684c>] [<c0146c02>] [<c0107652>]
> > [<c0146ac0>] [<c0105000>] [<c01058be>]
> > Jan 16 01:55:19 heaven kernel: [<c0146ac0>]
> > Jan 16 01:55:19 heaven kernel:
> > Jan 16 01:55:19 heaven kernel: Code: 0f 0b 55 01 60 0d 27 c0 85 db 74 0e
0f
> > b7 43 08 89 04 24 e8
>
> You didn't run it through ksymoops...
> -
-
next prev parent reply other threads:[~2004-01-17 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 19:42 2.4.24 may be bug in prints.c:341 Condor
2004-01-17 19:51 ` Mike Fedyk
2004-01-17 20:18 ` Condor [this message]
2004-01-17 20:23 ` Mike Fedyk
2004-01-17 20:31 ` Condor
2004-01-17 21:59 ` Mike Fedyk
2004-01-17 21:22 ` Oleg Drokin
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='010801c3dd37$1ff2ee20$8648493e@ixip.net' \
--to=condor@vereya.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
/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.