From: David Ford <david+cert@blue-labs.org>
To: linux-kernel@vger.kernel.org
Subject: [OOPS] 2.4.19-pre4, oops when dumping scsi data
Date: Mon, 10 Jun 2002 14:56:39 -0400 [thread overview]
Message-ID: <3D04F667.8090701@blue-labs.org> (raw)
# echo "scsi dump #1" > /proc/scsi/scsi
[...] long scsi dump goes here
( 47) 2:0: 4: 0 ( 00:00 0 0 0 ffffffff 0) (0 0 0x 0) ( 0
0 0)
0x00 0x00 0x00000000
( 48) 2:0: 4: 0 ( 00:00 0 0 0 ffffffff 0) (0 0 0x 0) ( 0
0 0)
0x00 0x00 0x00000000
( 49) 2:0: 4: 0 ( 00:00 0 0 0 ffffffff 0) (0 0 0x 0) ( 0
0 0)
0x00 0x00 0x00000000
Dump of pending block device requests
0: <1>Unable to handle kernel NULL pointer dereference at virtual
address 000000
34
printing eip:
c0280280
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c0280280>] Not tainted
EFLAGS: 00010292
eax: 00000000 ebx: 00000000 ecx: 00000000 edx: c03e444a
esi: cbf1147c edi: cbf5d58c ebp: c04df098 esp: c25d9ec4
ds: 0018 es: 0018 ss: 0018
Process bash (pid: 11010, stackpage=c25d9000)
Stack: 00000000 00000000 c58d2005 c03e40a0 c58d2009 0000000d c027f5a9
00000000
c58d200a 00000000 00000000 c4f6ab30 00000000 00000000 00000000
00000002
c4f6ab30 c0113aec c70dc27c c86af9a0 08109168 00000001 00000001
08109168
Call Trace: [<c027f5a9>] [<c0113aec>] [<c01535a8>] [<c0134a50>]
[<c013449f>]
[<c0106deb>]
Code: 8b 43 34 50 8b 4b 20 51 8b 53 1c 52 8b 43 14 50 0f b7 43 10
[...]
>>EIP; c0280280 <scsi_dump_status+220/260> <=====
Trace; c027f5a9 <proc_scsi_gen_write+749/780>
Trace; c0113aec <do_page_fault+2fc/4d7>
Trace; c01535a8 <proc_file_write+28/40>
Trace; c0134a50 <sys_write+e0/110>
Trace; c013449f <filp_close+3f/60>
Trace; c0106deb <system_call+33/38>
reply other threads:[~2002-06-10 18:56 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=3D04F667.8090701@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
all inboxes | Powered by JetHome®