From: ssd@nevets.oau.org (Steven S. Dick)
To: linux-kernel@vger.kernel.org
Subject: 2.4.0-test11 (pre1, final) OOPS during boot/modprobe
Date: Sat, 25 Nov 2000 06:10:54 -0500 (EST) [thread overview]
Message-ID: <m13zdEM-000QAFC@nevets.oau.org> (raw)
2.4.0-test11-pre1 seems to have broken something.
I have no problems with test10, but test11-pre1 gives three oops
messages during boot. test11-final gives the exact same OOPS messages...
Of the three, only the first one decodes to anything useful:
Unable to handle kernel paging request at virtual address c86bd1e0
printing eip:
c4890060
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[nfsd:__insmod_nfsd_O/lib/modules/2.4.0-test11/kernel/fs/nfsd/nfs+-12192/80]
EFLAGS: 00010a82
eax: c4890050 ebx: c3fcb400 ecx: c489101c edx: ffffffff
esi: c4891160 edi: c4891160 ebp: c48912d4 esp: c36fbee8
ds: 0018 es: 0018 ss: 0018
Process modprobe (pid: 201, stackpage=c36fb000)
Stack: c01b74fc c3fcb400 c489101c c3fcb400 00000000 c01b7554 c4891160 c3fcb400
c4890000 c489098c 00000001 c4890996 c4891160 c0117d2d c36fa000 08065490
08061760 bfffe164 00000001 c488d000 c488d000 c36fbf60 0000004c c48912c0
Call Trace: [pci_announce_device+44/64] [nfsd:__insmod_nfsd_O/lib/modules/2.4.0-test11/kernel/fs/nfsd/nfs+-8164/80] [pci_register_driver+68/92] [nfsd:__insmod_nfsd_O/lib/modules/2.4.0-test11/kernel/fs/nfsd/nfs+-7840/80] [nfsd:__insmod_nfsd_O/lib/modules/2.4.0-test11/kernel/fs/nfsd/nfs+-12288/80] [nfsd:__insmod_nfsd_O/lib/modules/2.4.0-test11/kernel/fs/nfsd/nfs+-9844/80] [nfsd:__insmod_nfsd_O/lib/modules/2.4.0-test11/kernel/fs/nfsd/nfs+-9834/80]
[nfsd:__insmod_nfsd_O/lib/modules/2.4.0-test11/kernel/fs/nfsd/nfs+-7840/80] [sys_init_module+1409/1568] [nfsd:__insmod_nfsd_O/lib/modules/2.4.0-test11/kernel/fs/nfsd/nfs+-24576/80] [nfsd:__insmod_nfsd_O/lib/modules/2.4.0-test11/kernel/fs/nfsd/nfs+-24576/80] [nfsd:__insmod_nfsd_O/lib/modules/2.4.0-test11/kernel/fs/nfsd/nfs+-7488/80] [nfsd:__insmod_nfsd_O/lib/modules/2.4.0-test11/kernel/fs/nfsd/nfs+-24576/80] [nfsd:__insmod_nfsd_O/lib/modules/2.4.0-test11/kernel/fs/nfsd/nfs+-12192/80] [system_call+51/64]
Code: 12 89 c4 c1 e2 03 89 44 24 18 89 54 24 1c 40 8b 8a c8 0f 89
The addresses are different, but the stack trace is identical,
between test-11(pre1) and test11(final).
I think the oops's each correspond to a modprobe.
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-25 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-25 11:10 Steven S. Dick [this message]
2000-11-25 12:05 ` Keith Owens
2000-11-25 12:27 ` Russell King
2000-11-25 12:36 ` Keith Owens
2000-11-25 16:21 ` Steven S. Dick
2000-11-25 17:03 ` Keith Owens
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=m13zdEM-000QAFC@nevets.oau.org \
--to=ssd@nevets.oau.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
all inboxes | Powered by JetHome®