From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 16711] New: Oops with 2.6.36-rc1
Date: Sat, 21 Aug 2010 10:07:31 GMT [thread overview]
Message-ID: <bug-16711-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=16711
Summary: Oops with 2.6.36-rc1
Product: File System
Version: 2.5
Kernel Version: 2.6.36-rc1
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: devnull@plzk.org
CC: akpm@linux-foundation.org, eparis@redhat.com
Regression: Yes
The ubuntu/debian build of 2.6.36-rc1 from [1] doesn't boot on my macbook
v.2.1. It's most likely not an EXT4 bug but I have no idea where to put it and
cc people that probably know better. I am linking to a crappy cellphone shot of
the oops, please see [2].
Unfortunately, due to the kernel-package in ubuntu being broken once again, I
can't build myself, hence no bisecting. All I can say is that 2.6.35-rc2 from
the same ppa works.
Let me know if additional info is needed.
Regards,
Tobias
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.36-rc1-maverick/
[2] http://img841.imageshack.us/img841/6654/imag0030l.jpg
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2010-08-21 10:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 10:07 bugzilla-daemon [this message]
2010-08-21 16:28 ` [Bug 16711] Oops with 2.6.36-rc1 bugzilla-daemon
2010-08-23 10:18 ` bugzilla-daemon
2010-08-24 23:59 ` bugzilla-daemon
2010-08-25 7:52 ` bugzilla-daemon
2010-08-26 9:36 ` bugzilla-daemon
2010-08-26 10:27 ` bugzilla-daemon
2010-08-26 10:30 ` bugzilla-daemon
2010-09-01 8:42 ` bugzilla-daemon
2012-08-13 15:56 ` bugzilla-daemon
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=bug-16711-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/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.