public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Dave Sailer <dsailer@paonline.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] kernel bug?
Date: Sat, 23 Oct 2004 19:00:17 +0200	[thread overview]
Message-ID: <1098550817.4866.7.camel@pegasus> (raw)
In-Reply-To: <417A73C5.10907@paonline.com>

Hi Dave,

> I have been getting a kernel bug in bluetooth startup. I'm running 
> gentoo 2.6.8-r7. I have tried a fresh kernel, including a 2.6.8.1 
> version.  Should this be reported as a kernel bug. How do I go about that?
> 
> ------------[ cut here ]------------
> kernel BUG at mm/slab.c:1382!
> invalid operand: 0000 [#1]
> PREEMPT SMP
> Modules linked in: bluetooth nvidia snd_ens1370 snd_ak4531_codec
> CPU:    0
> EIP:    0060:[<c014473d>]    Tainted: P 
> EFLAGS: 00010202   (2.6.8.1)
> EIP is at kmem_cache_create+0x41d/0x5d0
> eax: 0000002b   ebx: dff9a370   ecx: c05e0978   edx: 00000286
> esi: c04c8b48   edi: e08f4664   ebp: dfdb3ce0   esp: df94bf4c
> ds: 007b   es: 007b   ss: 0068
> Process modprobe (pid: 6554, threadinfo=df94a000 task=df284250)
> Stack: c0490fe4 e08f465c 00000020 00002000 df94bf70 dfdb3d38 0000000a 
> c0000000
>        ffffffe0 000000c0 c04e69a0 df94a000 e08f7940 c04e6984 e08ca06f 
> e08f465c
>        00000174 00000020 00002000 00000000 00000000 c01391f8 c05e0828 
> 00000001
> Call Trace:
>  [<e08ca06f>] bt_init+0x6f/0xc0 [bluetooth]
>  [<c01391f8>] sys_init_module+0x158/0x2b0
>  [<c010528b>] syscall_call+0x7/0xb
> Code: 0f 0b 66 05 f8 08 49 c0 8b 0b e9 5b ff ff ff 8b 47 50 c7 04
>  <6>agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
> agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode

this really looks like a kernel bug. Do you tried a 2.6.9 vanilla?

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-10-23 17:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-23 15:07 [Bluez-users] kernel bug? Dave Sailer
2004-10-23 17:00 ` Marcel Holtmann [this message]
     [not found]   ` <007901c4b9fd$76634c20$90a7dcd8@sailers>
2004-10-25  4:03     ` Marcel Holtmann

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=1098550817.4866.7.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=dsailer@paonline.com \
    /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