From: Dag Nygren <dag@newtech.fi>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Dag Nygren <dag@newtech.fi>,
linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.orgdag@newtech.fi
Subject: Re: Bug in the sg driver
Date: Mon, 06 Oct 2003 22:11:35 +0300 [thread overview]
Message-ID: <20031006191135.19059.qmail@dag.newtech.fi> (raw)
In-Reply-To: Message from "Randy.Dunlap" <rddunlap@osdl.org> of "Mon, 06 Oct 2003 11:52:45 PDT." <20031006115245.17d73f0c.rddunlap@osdl.org>
> | > Any details, like kernel version, oops or panic logs, etc.?
> |
> | Kernel version is 2.4.20 (Redhat 9.0 + newest upgrade)
> |
> | The oops and the panic logs were not written down as the major focus
> | was getting this (production) system up and running, sorry for that
>
> Well, unless someone happens to know something about your exact
> reported problem....
> in general, you will get better help/responses the better your
> problem reports are (IMHO).
Perfectly realize that. Found one report of the exact same problem
on Google. The URL is:
http://groups.google.fi/groups?q=hp_ltt+linux&hl=sv&lr=&ie=UTF-8&selm=zDJq.3O5.
11%40gated-at.bofh.it&rnum=1
The Oops trace for that is:
kernel BUG in header file at line 162
kernel BUG at panic.c:141!
invalid operand: 0000
CPU: 0
EIP: 0010:[__out_of_line_bug+15/36] Tainted: P
EFLAGS: 00010086
eax: 00000026 ebx: f7928a00 ecx: 00000002 edx: 02000000
esi: c3e8207c edi: f79ba1f0 ebp: f79ba1d8 esp: f6fabc68
ds: 0018 es: 0018 ss: 0018
Process hp_ltt (pid: 590, stackpage=f6fab000)
Stack: c026fa80 000000a2 c0202f38 000000a2 f7928a00 c3e8207c f79ba1c0 f79ba1d8
c02c2934 c0132070 00000000 00000000 ffffffff 00000000 0000000e 00000060
00000000 00000002 c0204831 c3e8207c f7928a00 f79ba1c0 0000005a 00000293
Call Trace: [mptscsih_AddSGE+200/832] [__alloc_pages+64/352]
[mptscsih_qcmd+621/1288] [scsi_dispatch_cmd+649/904] [scsi_old_done+0/1500]
[scsi_request_fn+826/892] [__scsi_insert_special+110/128]
[scsi_insert_special_req+26/32] [scsi_do_req+328/368]
[sg_common_write+587/604] [sg_cmd_done_bh+0/912] [sg_new_write+539/576]
[sg_ioctl+616/3004] [journal_dirty_metadata+356/396] [__alloc_pages+64/352]
[do_wp_page+112/668] [handle_mm_fault+135/184] [do_page_fault+380/1178]
[do_page_fault+0/1178] [sys_rt_sigaction+159/324] [sys_ioctl+685/746]
[error_code+52/60] [system_call+51/56]
Code: 0f 0b 8d 00 a6 fa 26 c0 eb fe 8d 74 26 00 8d bc 27 00 00 00
-- Dag
next prev parent reply other threads:[~2003-10-06 19:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031006180636.16530.qmail@dag.newtech.fi>
2003-10-06 18:20 ` Bug in the sg driver Randy.Dunlap
2003-10-06 18:47 ` Dag Nygren
2003-10-06 18:52 ` Randy.Dunlap
2003-10-06 19:11 ` Dag Nygren [this message]
2003-10-06 22:18 ` Randy.Dunlap
2003-10-07 5:47 ` Dag Nygren
2003-10-07 11:56 ` Matthew Wilcox
2003-10-07 12:03 ` Dag Nygren
2003-10-07 12:26 ` Matthew Wilcox
2003-10-07 12:37 ` Douglas Gilbert
2003-10-07 12:50 ` Dag Nygren
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=20031006191135.19059.qmail@dag.newtech.fi \
--to=dag@newtech.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.orgdag \
--cc=rddunlap@osdl.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