From: Dieter Nützel <Dieter.Nuetzel@hamburg.de>
To: "Rik Faith" <rik@valinux.com>
Cc: "Linux Kernel List" <linux-kernel@vger.kernel.org>,
"Dri-devel" <Dri-devel@lists.sourceforge.net>
Subject: 2.4.0.-test10: kernel oops - mount / tdfx.o related
Date: Sun, 5 Nov 2000 00:22:39 +0100 [thread overview]
Message-ID: <00110500223900.07516@SunWave1> (raw)
Hello Rik,
I've got a kernel oops with the 'latest' linux kernel and the DRI.
CD mounting was involved.
ksymoops 2.3.4 on i686 2.4.0-test10. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.0-test10/ (default)
-m /boot/System.map (specified)
Nov 4 18:40:05 SunWave1 kernel: Unable to handle kernel paging request at
virtual address d0c353f3
Nov 4 18:40:05 SunWave1 kernel: d0c353f3
Nov 4 18:40:05 SunWave1 kernel: *pde = 0c291063
Nov 4 18:40:05 SunWave1 kernel: Oops: 0000
Nov 4 18:40:05 SunWave1 kernel: CPU: 0
Nov 4 18:40:05 SunWave1 kernel: EIP: 0010:[<d0c353f3>]
Using defaults from ksymoops -t elf32-i386 -a i386
Nov 4 18:40:05 SunWave1 kernel: EFLAGS: 00010296
Nov 4 18:40:05 SunWave1 kernel: eax: c147a2a8 ebx: cd3c3bd4 ecx:
00000001 edx: c147a280
Nov 4 18:40:05 SunWave1 kernel: esi: cc6e2214 edi: cbc3dd84 ebp:
cd3c3b80 esp: cbc3dd34
Nov 4 18:40:05 SunWave1 kernel: ds: 0018 es: 0018 ss: 0018
Nov 4 18:40:05 SunWave1 kernel: Process mount (pid: 325, stackpage=cbc3d000)
Nov 4 18:40:05 SunWave1 kernel: Stack: cd3c3b80 cbc3dd84 00000000 00000000
00000bb8 00000003 00000002 cc6e2214
Nov 4 18:40:05 SunWave1 kernel: d0c36d20 00000000 00000000 00000000
c147a280 d0c35b12 00000000 cbc3dd84
Nov 4 18:40:05 SunWave1 kernel: 00000000 00000000 00000000 00000003
0000001b 00000003 0000292e d0c2b3e2
Nov 4 18:40:05 SunWave1 kernel: Call Trace: [<d0c36d20>] [<d0c35b12>]
[<d0c2b3e2>] [bread+24/112] [<d0c2b2f8>] [blkdev_get+262/336]
[do_no_page+168/272]
Nov 4 18:40:05 SunWave1 kernel: Code: Bad EIP value.
>>EIP; d0c353f3 <[tdfx].bss.end+3f538/60041a5> <=====
Trace; d0c36d20 <[tdfx].bss.end+40e65/60041a5>
Trace; d0c35b12 <[tdfx].bss.end+3fc57/60041a5>
Trace; d0c2b3e2 <[tdfx].bss.end+35527/60041a5>
Thanks,
Dieter
--
Dieter Nützel
Graduate Student, Computer Science
University of Hamburg
Department of Computer Science
Cognitive Systems Group
Vogt-Kölln-Straße 30
D-22527 Hamburg, Germany
email: nuetzel@kogs.informatik.uni-hamburg.de
@home: Dieter.Nuetzel@hamburg.de
-
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/
reply other threads:[~2000-11-04 23:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=00110500223900.07516@SunWave1 \
--to=dieter.nuetzel@hamburg.de \
--cc=Dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rik@valinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox