All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: cijoml@volny.cz
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bthid dies via kernel oops in 2.6.5
Date: Mon, 12 Apr 2004 18:47:13 +0200	[thread overview]
Message-ID: <1081788433.8634.2.camel@pegasus> (raw)
In-Reply-To: <200404121822.44231.cijoml@volny.cz>

Hi Michal,

> preempt people told me the same as you :D They told, that this is BT 
> problem :D But they are possibly right, coz kernel oopses too, when I use 
> nonpreempt kernel

I used preempt for a long time now and it works for me, but looking at
the oops this is not a Bluetooth problem. It is the uinput driver that
causes the problem.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-04-12 16:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-12  0:12 [Bluez-users] bthid dies via kernel oops in 2.6.5 Michal Semler (volny.cz)
2004-04-12 13:35 ` Marcel Holtmann
2004-04-12 16:22   ` Michal Semler (volny.cz)
2004-04-12 16:47     ` Marcel Holtmann [this message]
2004-04-12 16:54       ` Michal Semler (volny.cz)
2004-04-12 17:12         ` 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=1081788433.8634.2.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=cijoml@volny.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.