From: Andrew Morton <akpm@osdl.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
marcel@holtmann.org, maxk@qualcomm.com,
bluez-devel@lists.sourceforge.net
Subject: Re: ext3-related crash in 2.6.20-rc1
Date: Sat, 23 Dec 2006 17:12:28 -0800 [thread overview]
Message-ID: <20061223171228.120ac8a6.akpm@osdl.org> (raw)
In-Reply-To: <20061223234305.GA1809@elf.ucw.cz>
On Sun, 24 Dec 2006 00:43:05 +0100
Pavel Machek <pavel@ucw.cz> wrote:
> Hi!
>
> I got this nasty oops while playing with debugger. Not sure if that is
> related; it also might be something with bluetooth; I already know it
> corrupts memory during suspend, perhaps it corrupts memory in some
> error path?
>
>
>
> Pavel
>
>
> l2cap_recv_acldata: Unexpected continuation frame (len 0)
> l2cap_recv_acldata: Unexpected continuation frame (len 0)
> l2cap_recv_acldata: Unexpected continuation frame (len 0)
> l2cap_recv_acldata: Unexpected continuation frame (len 0)
> l2cap_recv_acldata: Unexpected continuation frame (len 0)
> l2cap_recv_acldata: Unexpected continuation frame (len 0)
> l2cap_recv_acldata: Unexpected continuation frame (len 0)
> PM: Removing info for bluetooth:acl00803715A329
> e1000: eth0: e1000_watchdog: NIC Link is Down
> e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
> e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO
> e1000: eth0: e1000_watchdog: NIC Link is Down
> e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
> e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO
> ------------[ cut here ]------------
> kernel BUG at fs/buffer.c:1235!
get thee to fs/buffer.c:1235. You'll see that someone somewhere forgot to
reenable local interrupts.
Were you using gdb at the time? A fix for something like that was merged
into mainline yesterday.
The slab errors which you're reporting in later emails will almost surely
be unrelated to this.
next parent reply other threads:[~2006-12-24 1:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061223234305.GA1809@elf.ucw.cz>
2006-12-24 1:12 ` Andrew Morton [this message]
[not found] ` <20061223235501.GA1740@elf.ucw.cz>
2006-12-24 1:18 ` bluetooth memory corruption (was Re: ext3-related crash in 2.6.20-rc1) Andrew Morton
2006-12-24 23:24 ` Pavel Machek
[not found] ` <20061224000150.GA1812@elf.ucw.cz>
[not found] ` <20061224000605.GA1768@elf.ucw.cz>
[not found] ` <20061224000753.GA1811@elf.ucw.cz>
[not found] ` <458DD459.2030209@gmail.com>
[not found] ` <458E69CB.6000107@gmail.com>
2006-12-24 12:22 ` ptrace() memory corruption? Andrew Morton
2006-12-24 13:44 ` Jiri Slaby
2006-12-24 14:39 ` [Bluez-devel] bluetooth memory corruption (was Re: ext3-related crash in 2.6.20-rc1) Marcel Holtmann
2006-12-24 23:36 ` Pavel Machek
[not found] ` <20061224234357.GA1817@elf.ucw.cz>
[not found] ` <20061228084251.GB3955@ucw.cz>
2006-12-28 10:40 ` 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=20061223171228.120ac8a6.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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