From: David Ford <david+cert@blue-labs.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [OOPS] 2.5.62, bootup, do_add_mount
Date: Fri, 21 Feb 2003 23:47:38 -0500 [thread overview]
Message-ID: <3E5700EA.9070905@blue-labs.org> (raw)
Pentium II, kernel compiled with gcc 2.95.3
[...]
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
BIOS EDD facility v0.09 2003-Jan-22, 3 devices found
ACPI: (supports S0 S1 S4 S5)
Started krxiod 12
Started krxsecd 13
(filter_get_filter_fs,l. 234): ops at c05d4918
(fs/intermezzo/super.c:presto_get_sb,l. 253 1): Presto: unrecognized fs
type or cache type
Unable to handle kernel NULL pointer dereference at virtual address 0000003c
printing eip:
c016a6a4
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0060:[<c016a6a4>] Not tainted
EFLAGS: 00010217
EIP is at do_kern_mount+0x58/0xa8
eax: 00000000 ebx: c3fe9720 ecx: c3f55000 edx: c3f55010
esi: 00000000 edi: c05124a0 ebp: c3fcbee0 esp: c3fcbed4
ds: 007b es: 007b ss: 0068
Process swapper (pid: 1, threadinfo=c3fca000 task=c3fc8000)
Stack: 00008001 c3fca000 c3e2800a c3fcbf04 c0186546 c3e28000 00008001
c11ff000
00000000 00008001 00000000 c3fcbf38 c3fcbf54 c018683d c3fcbf38
c3e28000
00008001 00000000 c11ff000 00000000 c3fca000 00000001 c3e29000
c11ff000
Call Trace:
[<c0186546>] do_add_mount+0x62/0x150
[<c018683d>] do_mount+0x139/0x150
[<c018718e>] sys_mount+0x136/0x224
[<c010545e>] prepare_namespace+0xfe/0x140
[<c01051a5>] init+0xcd/0x288
[<c01050d8>] init+0x0/0x288
[<c0107211>] kernel_thread_helper+0x5/0xc
Code: 8b 46 3c 85 c0 74 06 ff 00 80 48 04 08 89 43 10 8b 46 3c 89
<0>Kernel panic: Attempted to kill init!
--
I may have the information you need and I may choose only HTML. It's up to you. Disclaimer: I am not responsible for any email that you send me nor am I bound to any obligation to deal with any received email in any given fashion. If you send me spam or a virus, I may in whole or part send you 50,000 return copies of it. I may also publically announce any and all emails and post them to message boards, news sites, and even parody sites. I may also mark them up, cut and paste, print, and staple them to telephone poles for the enjoyment of people without internet access. This is not a confidential medium and your assumption that your email can or will be handled confidentially is akin to baring your backside, burying your head in the ground, and thinking nobody can see you butt nekkid and in plain view for miles away. Don't be a cluebert, buy one from K-mart today.
When it absolutely, positively, has to be destroyed overnight.
AIR FORCE
next reply other threads:[~2003-02-22 4:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-22 4:47 David Ford [this message]
2003-02-25 8:03 ` [OOPS] 2.5.62, bootup, do_add_mount Maneesh Soni
2003-02-25 8:04 ` Andrew Morton
2003-02-25 9:47 ` Maneesh Soni
2003-02-25 20:06 ` Peter Braam
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=3E5700EA.9070905@blue-labs.org \
--to=david+cert@blue-labs.org \
--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