From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Dag Nygren <dag@newtech.fi>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Bug in the sg driver
Date: Mon, 6 Oct 2003 11:20:28 -0700 [thread overview]
Message-ID: <20031006112028.1242199d.rddunlap@osdl.org> (raw)
In-Reply-To: <20031006180636.16530.qmail@dag.newtech.fi>
On Mon, 06 Oct 2003 21:06:36 +0300 Dag Nygren <dag@newtech.fi> wrote:
|
| Hi,
|
| just got back from a customer with major problems
| with a LTO-drive and an Adaptec 19160.
|
| The problems was ones that HP claimed a firmware
| upgrade would fix and even gave a tool for doing this:
| hp_ltt.
|
| Running this the first time would always segfault and trying
| a second time would consistently panic the system.
|
| We traced the segfault to sg_ioctl trying to do something.
| After finding a vague hint with google I tried to boot with
| mem=512M (The machine has 2GB of memory) and voila:
| The update worked without any crashes.
| We don't know yet if the firmware update fixed the original problem,
| but the conclusion is:
|
| sg_ioctl seems to address illegal parts of memory when used with
| kernels where highmem is enabled.
|
| Any sg-driver maintainers out there?
from MAINTAINERS file:
SCSI SG DRIVER
P: Doug Gilbert
M: dgilbert@interlog.com
L: linux-scsi@vger.kernel.org
W: http://www.torque.net/sg
S: Maintained
Any details, like kernel version, oops or panic logs, etc.?
--
~Randy
next parent reply other threads:[~2003-10-06 18:20 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 ` Randy.Dunlap [this message]
2003-10-06 18:47 ` Bug in the sg driver Dag Nygren
2003-10-06 18:52 ` Randy.Dunlap
2003-10-06 19:11 ` Dag Nygren
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=20031006112028.1242199d.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=dag@newtech.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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