All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
	marcel@holtmann.org, maxk@qualcomm.com,
	kernel list <linux-kernel@vger.kernel.org>,
	linux-bluetooth@vger.kernel.org
Subject: Re: bluetooth still corrupts memory in 2.6.25-rc6
Date: Thu, 20 Mar 2008 08:05:45 +0100	[thread overview]
Message-ID: <20080320070545.GA17356@elf.ucw.cz> (raw)
In-Reply-To: <a8e1da0803191950s1a656fffq98fbc180069814d9@mail.gmail.com>

Hi!

> >  >>> ...just leave ppp-over-cellphone-over-bluetooth running, and do
> >  >>> s2ram...
> >  >>>
> >  >>> Linux version 2.6.25-rc6 (pavel@amd) (gcc version 4.1.3 20071209 (prerelease) (Debian 4.1.2-18)) #186 SMP Wed Mar 19 00:46:05 CET 2008
> >  >>> BIOS-provided physical RAM map:
> >  >> Pavel, does the "still" from $SUBJ mean, that 2.6.24 is affected too (if
> >  >> this is the same what I hit)?
> >  >
> >  > Hey, I did not do careful analysis. I believe it is the same problem
> >  > that affects 2.6.24, too, yes. But I actually believe it is much older
> >  > than that...
> >
> >  If yes, then I got the crash by using hidp over l2cap with non-hid device
> >  (session->input). I'm not sure if it was connected at all and even if hidd was
> >  running (I tested moving with mouse by cellphone with switching on and off the
> >  daemon, since it needed some little changes).

If you have easy/reproducible way of triggering that crash, yes that
would be useful.

...just leave ppp-over-cellphone-over-bluetooth running, and do
s2ram... takes few tries to reproduce, and you need to set up ppp each
time, so it is quite nasty to debug...

> >  If you, hci fellows, are interested I might send more detailed description of
> >  the crash tomorrow.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
pomozte zachranit klanovicky les:  http://www.ujezdskystrom.info/

      reply	other threads:[~2008-03-20  7:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19  8:21 bluetooth still corrupts memory in 2.6.25-rc6 Pavel Machek
2008-03-19 21:28 ` Rafael J. Wysocki
2008-03-19 21:33   ` Pavel Machek
2008-03-19 23:02 ` Jiri Slaby
2008-03-19 23:06   ` Pavel Machek
2008-03-19 23:26     ` Jiri Slaby
2008-03-20  2:50       ` Dave Young
2008-03-20  7:05         ` Pavel Machek [this message]

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=20080320070545.GA17356@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=hidave.darkstar@gmail.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=maxk@qualcomm.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 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.