From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: Michael Frank <mhf@linuxmail.org>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.26 intermittent kernel bug on boot.
Date: Sat, 17 Apr 2004 04:37:05 +1000 [thread overview]
Message-ID: <1082140624.19725.82.camel@laptop-linux.wpcb.org.au> (raw)
In-Reply-To: <opr6j9q0d54evsfm@smtp.pacific.net.th>
Hi.
On Sat, 2004-04-17 at 04:02, Michael Frank wrote:
> kernel BUG at slab.c:1238!
That's a really strange oops to see. It's testing that the GFP flags
match the slab's flags. To get an oops there, you'd have to have a
non-dma slab (which makes sense), but you've called the kmem_cache_alloc
routine with a DMA flag. Line 444 of kernel/signal.c clearly doesn't do
that! Could the args be being corrupted while being passed? What does a
backtrace look like?
Nigel
> invalid operand: 0000
>
> CPU: 0
> EIP: 1010:[<c013bf39>] Not tainted
> EFLAGS: 00010002
> EIP is at kmem_cache_alloc+0x31/0xdc [kernel]
> eax: 00000000 ebx: 00000008 ecx: 00000000 edx: 00000001
> esi: 00000000 edi: 0000000b ebp: 00000020 esp: c0407f10
> ds: 1018 es: 1018 ss: 1018
> Process swapper (pid: 0, stackpage=c0407000)
> Stack: 0000000b 00000001 0000000b c040656c c0121f8c 00000000 00000020 c0406000
> 0000000b 0000000b 00000000 c012206d 0000000b 00000001 c040656c 00000282
> 0000000b c0406000 c012211c 0000000b 00000001 c0406000 00000286 c0406000
> Call Trace:
> [<c0121f8c>] send_signal+0x2c/0xf0 [kernel]
> [<c012206d>] deliver_signal+0x1d/0x54 [kernel]
> [<c012211c>] send_sig_info+0x78/0x88 [kernel]
> [<c01221a9>] force_sig_info+0x7d/0x88 [kernel]
> [<c010a5e4>] do_double_fault+0x0/0x64 [kernel]
> [<c01223d5>] force_sig+0x11/0x18 [kernel]
> [<c010a619>] do_double_fault+0x35/0x64 [kernel]
> [<c0109dc4>] error_code+0x34/0x40 [kernel]
>
> Code: 0f 0b d6 04 e0 b7 2b c0 8d 5e 08 9c 5f fa 8b 4e 08 39 d9 75
>
> Entering kdb (current=0xc0406000, pid 0) Oops: invalid operand
> due to oops @ 0xc013bf39
> eax = 0x00000000 ebx = 0x00000008 ecx = 0x00000000 edx = 0x00000001
> esi = 0x00000000 edi = 0x0000000b esp = 0xc0407f10 eip = 0xc013bf39
> ebp = 0x00000020 xss = 0x00001018 xcs = 0x00001010 eflags = 0x00010002
> xds = 0x00001018 xes = 0x00001018 origeax = 0xffffffff ®s = 0xc0407edc
> kdb>
>
> Board did 50K+ boots testing swsusp with 2.4.2[012345]...
>
> It's still sitting in kdb, if you want me lookup something let me know.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Nigel & Michelle Cunningham
C/- Westminster Presbyterian Church Belconnen
61 Templeton Street, Cook, ACT 2614.
+61 (2) 6251 7727(wk); +61 (2) 6254 0216 (home)
Evolution (n): A hypothetical process whereby infinitely improbable events occur
with alarming frequency, order arises from chaos, and no one is given credit.
next prev parent reply other threads:[~2004-04-16 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 18:02 Michael Frank
2004-04-16 18:37 ` Nigel Cunningham [this message]
2004-04-16 19:45 ` Michael Frank
2004-04-19 21:44 ` Marcelo Tosatti
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=1082140624.19725.82.camel@laptop-linux.wpcb.org.au \
--to=ncunningham@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=mhf@linuxmail.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
all inboxes | Powered by JetHome®