From: Andreas Boman <aboman@nerdfest.org>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.39 "Sleeping function called from illegal context at slab.c:1374"
Date: Tue, 1 Oct 2002 17:59:07 -0400 [thread overview]
Message-ID: <20021001215907.GA8273@midgaard.us> (raw)
In-Reply-To: <3D99EF62.3A3E6932@digeo.com>
* Andrew Morton (akpm@digeo.com) wrote:
> Helge Hafting wrote:
> >
> > ..
> > [<c01146c4>]__might_sleep+0x54/0x60
> > [<c012dca0>]kmalloc+0x4c/0x130
> > [<c010b6b2>]sys_ioperm+0x82/0x11c
> > [<c0106fbb>]syscall_call+0x7/0xb
> >
>
>
> You up to trying this fix?
>
This patch on 2.3.40+xfsfix didnt change anything here, while my trace does look different it seems to be related. I get a similar oops when ide initializes during boot, then when i modprobe ide-scsi it times out, and it seems i get a prompt back, but the box is locked up and doesnt even respond to ping's.
UP athlon, disk on aic7xxx (xfs), ide dvdrom and cdrw on vt82c686b both set to master on separate channels.
.config is avaiable on http://midgaard.us/~aboman/dot.config-2.5
full log up to that point http://midgaard.us/~aboman/messages-40.1
Debug: sleeping function called from illegal context at slab.c:1374
deba1e40 deba1e60 c01333af c03597a5 0000055e dffec000 00000000 00001000
deba1e84 c0131a66 c15070c0 000001d0 00000000 c14cb800 00000246 00000000
00001000 deba1eb0 c0131dab 00001000 00000002 c14cc188 00001000 00001000
Call Trace:
[__kmem_cache_alloc+255/272]__kmem_cache_alloc+0xff/0x110
[get_vm_area+38/256]get_vm_area+0x26/0x100
[__vmalloc+75/304]__vmalloc+0x4b/0x130
[vmalloc+34/48]vmalloc+0x22/0x30
[<e08fe502>]sg_init+0x82/0x130 [sg]
[<e09022c7>].rodata.str1.1+0x23/0x2b0 [sg]
[<e0903be0>]sg_fops+0x0/0x58 [sg]
[<e0903b20>]sg_template+0x0/0x94 [sg]
[scsi_register_device+276/336]scsi_register_device+0x114/0x150
[<e08fec23>]init_sg+0x23/0x60 [sg]
[<e0903b20>]sg_template+0x0/0x94 [sg]
[sys_init_module+1311/1648]sys_init_module+0x51f/0x670
[<e08fc060>]E __insmod_sg_O/lib/modules/2.5.40anb1/kernel/drivers/scsi/sg.o_M3D9A1098_V132392+0x60/0x80 [sg]
[<e0902554>]__ksymtab+0x0/0x28 [sg]
[<e08fc060>]E __insmod_sg_O/lib/modules/2.5.40anb1/kernel/drivers/scsi/sg.o_M3D9A1098_V132392+0x60/0x80 [sg]
[syscall_call+7/11]syscall_call+0x7/0xb
scsi1 : SCSI host adapter emulation for IDE ATAPI devices
scsi_eh_offline_sdevs: Device set offline - notready or command retry failedafter error recovery: host1 channel 0 id 0 lun 0
Vendor: Model: Rev:
Type: Direct-Access ANSI SCSI revision: 00
hda: lost interrupt
next prev parent reply other threads:[~2002-10-01 22:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 11:34 2.4.39 "Sleeping function called from illegal context at slab.c:1374" Helge Hafting
2002-10-01 11:39 ` Jens Axboe
2002-10-01 18:54 ` Andrew Morton
2002-10-01 21:59 ` Andreas Boman [this message]
2002-10-01 22:23 ` Andrew Morton
2002-10-01 23:24 ` Joaquim Fellmann
2002-10-02 16:24 ` Mike Anderson
2002-10-02 18:44 ` Andreas Boman
2002-10-02 19:31 ` Mike Anderson
2002-10-02 21:21 ` Mike Anderson
2002-10-02 23:53 ` Andreas Boman
2002-10-03 17:17 ` Mike Anderson
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=20021001215907.GA8273@midgaard.us \
--to=aboman@nerdfest.org \
--cc=akpm@digeo.com \
--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;
as well as URLs for NNTP newsgroup(s).