From: Wichert Akkerman <wichert@wiggy.net>
To: linux-kernel@vger.kernel.org
Subject: [2.5.41] sleeping function called from illegal context at mm/slab.c:1374
Date: Tue, 8 Oct 2002 00:06:49 +0200 [thread overview]
Message-ID: <20021007220649.GF14953@wiggy.net> (raw)
I seem to have hit a debug trigger while booting in 2.5.41. The
calltrace suggests it is an IDE problem:
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x0860-0x0867, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x0868-0x086f, BIOS settings: hdc:pio, hdd:pio
hda: FUJITSU MHJ2181AT, ATA DISK drive
Debug: sleeping function called from illegal context at mm/slab.c:1374
Call Trace:
[<c01138f4>] __might_sleep+0x54/0x60
[<c012e1d3>] kmem_cache_alloc+0x23/0xd0
[<c01f8b50>] blk_init_free_list+0x4c/0xd0
[<c0108998>] request_irq+0x8c/0xa8
[<c01f8be0>] blk_init_queue+0xc/0xd4
[<c01fd7f0>] ide_init_queue+0x28/0x68
[<c0203a20>] do_ide_request+0x0/0x18
[<c01fdaad>] init_irq+0x27d/0x334
[<c01fde06>] hwif_init+0x112/0x258
[<c01fd71c>] probe_hwif_init+0x1c/0x6c
[<c0209b4d>] ide_setup_pci_device+0x3d/0x68
[<c01fc77f>] piix_init_one+0x37/0x40
[<c010508b>] init+0x33/0x188
[<c0105058>] init+0x0/0x188
[<c01054a9>] kernel_thread_helper+0x5/0xc
--
_________________________________________________________________
/wichert@wiggy.net This space intentionally left occupied \
| wichert@deephackmode.org http://www.wiggy.net/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
next reply other threads:[~2002-10-07 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 22:06 Wichert Akkerman [this message]
2002-10-07 22:21 ` [2.5.41] sleeping function called from illegal context at mm/slab.c:1374 Robert Love
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=20021007220649.GF14953@wiggy.net \
--to=wichert@wiggy.net \
--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