All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 16711] Oops with 2.6.36-rc1
Date: Thu, 26 Aug 2010 10:30:30 GMT	[thread overview]
Message-ID: <201008261030.o7QAUUJs016372@demeter1.kernel.org> (raw)
In-Reply-To: <bug-16711-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=16711





--- Comment #8 from Tobias <devnull@plzk.org>  2010-08-26 10:29:21 ---
John,

wrt #5: This is a Macbook 2.1, I replaced RAM and HDD a while back. lscpi
output attached. I have an OSX install on it that it never used, and Ubuntu
10.04. Ubuntu install consists of an unencrypted /boot partition and an
encrypted partition where LVM provides / and /home. 

fdisk -l shows:

/dev/sda1               1          26      204819+  ee  GPT
/dev/sda2   *          26        5248    41943040   af  HFS / HFS+
/dev/sda3            5248        5308      487424   83  Linux
/dev/sda4            5308       60802   445750272   ef  EFI (FAT-12/16/32)

mount:

/dev/mapper/vg-root on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /dev type devtmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
/dev/mapper/vg-home on /home type ext4 (rw)
/dev/sda3 on /boot type ext3 (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc
(rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/tobias/.gvfs type fuse.gvfs-fuse-daemon
(rw,nosuid,nodev,user=tobias)

That said this is a stock setup.

wrt #6: I think I am running into the same issue as described in [1]. People
are saying it is fixed in maverick, so I am hoping for an upgrade or backport
to lucid.
What puzzles me is that the exact issue (trying to build a -git kernel) was
reported to lkml from a maverick user [2], and the thread suggests that there
are kernel patches available to fix this. Now I am unsure where if
kernel-package or source itself are broken.

Please let me know if there are things I can do to be of help (things that
break my setup are no option unfortunately).

[1] https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/58307
[2] http://marc.info/?t=128247993200002&r=1&w=2

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2010-08-26 10:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-21 10:07 [Bug 16711] New: Oops with 2.6.36-rc1 bugzilla-daemon
2010-08-21 16:28 ` [Bug 16711] " 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 [this message]
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=201008261030.o7QAUUJs016372@demeter1.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.