public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	maxk@qualcomm.com, bluez-devel@lists.sourceforge.net
Subject: Re: bluetooth oops during resume from ram
Date: Sun, 17 Sep 2006 18:52:59 +0200	[thread overview]
Message-ID: <1158511979.24941.1.camel@localhost> (raw)
In-Reply-To: <20060917140952.GA3349@elf.ucw.cz>

Hi Pavel,

> If I suspend-to-RAM with usb active on thinkpad x60, I get an
> oops. Machine works okay after that, but...
> 
> it seems bluetooth is scribbling over more memory than was allocated
> (?)

not that I am aware of. Is this a plain 2.6.18-rc6 or did you apply
additional patches that might have caused this behavior?

Regards

Marcel



  reply	other threads:[~2006-09-17 16:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-17 14:09 bluetooth oops during resume from ram Pavel Machek
2006-09-17 16:52 ` Marcel Holtmann [this message]
2006-09-17 19:36   ` Pavel Machek
2006-09-18  6:20     ` Marcel Holtmann
2006-09-20 12:00       ` Pavel Machek

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=1158511979.24941.1.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxk@qualcomm.com \
    --cc=pavel@ucw.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox