From: Douglas Gilbert <dougg@torque.net>
To: linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Dave Jones <davej@suse.de>
Subject: [PATCH] 2.5.9-dj1 sd_init() fails at boot
Date: Tue, 23 Apr 2002 21:56:59 -0400 [thread overview]
Message-ID: <3CC610EB.C8A287C8@torque.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 819 bytes --]
With both lk 2.5.8-dj1 and lk 2.5.9-dj1 the
scsi disk driver (sd) fails in sd_init()
with OOM causing the scsi disk holding my
root fs not to be found. The kmalloc(,GFP_ATOMIC)
for the array of "struct hd_struct" returns NULL.
Strange that my Athlon 1.2 GHz box with 512 MB of
ram should get an OOM error at that point.
Pete Zaitcev came across similar problems in the
2.4 series which he has addressed by changing the
kmalloc() to vmalloc().
Rather than a minimal patch, the attachment uses
vmalloc() and does a cleanup of the sd driver that was
presented in an earlier post:
http://marc.theaimsgroup.com/?l=linux-scsi&m=101798201714399&w=2
As noted in that post, the attachment also fixes an
oops resulting from this sequence (when sd is a module):
$ modprobe sd_mod; rmmod sd_mod; modprobe sd_mod
Doug Gilbert
[-- Attachment #2: sd203_259dj1.diff.gz --]
[-- Type: application/x-gzip, Size: 14498 bytes --]
reply other threads:[~2002-04-24 2:06 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=3CC610EB.C8A287C8@torque.net \
--to=dougg@torque.net \
--cc=davej@suse.de \
--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