Testing the mainline 2.6.32 kernel on other LX800-based hardware (Artec
ThinCan DBE61C-USB), I notice that everything boots as normal.
It thus appears that some recent changes in the kernel might have
succeeded in exposing BIOS issues on some specific hardware.
I suppose that we could choose to i
Stefan suggested trying mem=nopentium but this did not have any apparent
effect. However raid=noautodetect did. When booting without any
initramfs image, the kernel no longer shows any paging error or
destroyed inode at all.
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initr
Apparently, in all cases, something that touches sysfs does something
nasty, but what?
Instructions on how to locate exactly which part of the initramfs image
payload causes this are welcome.
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/b
The resulting raw dmesg output.
** Attachment added: "dmesg-r_linux_2.6.32-14-generic.txt"
http://launchpadlibrarian.net/39939933/dmesg-r_linux_2.6.32-14-generic.txt
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received
Performing the same test as above (removal of initrd.img and
modification of GRUB's menu.lst) using 2.6.32-14-generic further
confirms that the issue is with something that gets included in the
initramfs image.
The relevant GRUB menu excerpt:
title Ubuntu lucid (development branch), ker
** Attachment added: "dmesg-r_linux_2.6.31-geodelx.txt"
http://launchpadlibrarian.net/39797529/dmesg-r_linux_2.6.31-geodelx.txt
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notification because you are
It seems that we have some progress.
In an attempt to debug this issue, I compared notes with someone on
Fedora for whom the same hardware works. As a test, I used their kernel
2.6.31 config (with a couple of small modifications to build specific
drivers as built-in) as attached to build my own k
Leann? Stefan?
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
I'm wondering if the patch that was used to produce
2.6.32-10.14+bug396286v2 could be added to the Lucid -generic kernel?
While I realize that it's not a proper fix, let's keep in mind that
Lucid is the next LTS and, as such, the last thing we want is a massive
wave of complaints from users of thi
2.6.32-10.14+bug396286v2 boots. dmesg attached.
** Attachment added: "2.6.32-10.14+bug396286v2.txt"
http://launchpadlibrarian.net/37630017/2.6.32-10.14%2Bbug396286v2.txt
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You rece
Uploaded linux-image-2.6.32-10-generic_2.6.32-10.14+bug396286v2_i386.deb
to http://people.canonical.com/~smb/bug396286/
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notification because you are a member of
Tested. Crashes as before.
Could we apply this and your extra debug message patch to something
2.6.32 as well and build test packages with that? It seems that 2.6.31
cannot work with Plymouth and some other novelties found in Lucid, plus
upstream probably wants us to try against the latest and gre
Placed test kernel (2.6.31-17.54 + patch mentioned by hpa in the
upstream bug) to http://people.canonical.com/~smb/bug396286/
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notification because you are a mem
Repeatedly trying to rebuild 2.6.32-9-generic with Peter Anvin's patch
following instructions at
https://help.ubuntu.com/community/Kernel/Compile consistently fails this
way:
CC arch/x86/kernel/alternative.o
CC arch/x86/kernel/i8253.o
CC arch/x86/kernel/pci-nommu.o
CC a
Peter Anvin suggested in the upstream report that enforcing -march=i386
as compiler options might be all that's required to fix this. Could new
test packages be built using the following patch?
http://git.kernel.org/tip/17a2a9b57a9a7d2fd8f97df951b5e63e0bd56ef5
--
[Geode LX] [OLPC] 2.6.31-generic
I'm really wondering what to do about this one since LKML has been
rather uncooperative and yet it already affects those upgrading from
Jaunty to Karmic. However, the real concern is for LTS->LTS+1 upgrades.
Geode support in Hardy is rock-solid, whereas this show-stopper affects
Lucid.
--
[Geode
Added tags for Lucid, since this issue is still unresolved and will blow
up in people's faces when they upgrade from Hardy.
** Tags added: lucid regression-lucid
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this b
** Tags added: karmic
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
** Tags added: regression-release
** Tags removed: regression-potential
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I added the two patches with some comment to the upstream bug report. At
this point I guess it would be interesting to have a second confirmation
with a different (but same model) Geode to rule out a single misbehaving
hardware problem. I heard of others saying they have problems, but were
those th
I'll also add that a Debian developer (dilinger) who is also a member of
the OLPC kernel team would be willing to help, but he cannot do much
until you've attached your diffs to the upstream bug.
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.ne
Just to confirm, this issue still applies to 2.6.32-2-generic.
Stefan, how about attaching all of your your diffs to the upstream bug
and asking the LKML for advice? I think that you and Leann have already
done a fine job of narrowing down the issue and, at this point, the
authors of the upstream
So both (ext3 and ext4) show the corruption messages when running with
v2, but v5 never hits them. For better understanding I am attaching the
diff between v2 and v5. As one can see there is no real change in that.
In __iget there is just a printk added for the case that
inode_check_acl() finds som
** Attachment added: "2.6.31-14-generic_48+bug396286v2_ext3.txt"
http://launchpadlibrarian.net/34705380/2.6.31-14-generic_48%2Bbug396286v2_ext3.txt
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notific
** Attachment added: "2.6.31-14-generic_48+bug396286v2_ext4.txt"
http://launchpadlibrarian.net/34705222/2.6.31-14-generic_48%2Bbug396286v2_ext4.txt
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notific
To make sure the change of the fstab did not have an impact, go back to the v2
version
(which previously showed the corruption) and check whether you find bad acl
messages
now. If not, then it would be most interesting to get back to the old state.
--
[Geode LX] [OLPC] 2.6.31-generic: kernel pa
** Attachment added: "2.6.31-14-generic_48+bug396286v5.txt"
http://launchpadlibrarian.net/34697289/2.6.31-14-generic_48%2Bbug396286v5.txt
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notification becau
As a point of information, I recently changed the fstab entries to state
ext4, to benefit from the slightly faster performance that new features
common to both ext3 and ext4 make possible. In principle, this should
not change anything, since both ext3 and ext4 call the same common
fsattr functions
Somehow those results do not make really sense. In v4, the init code is back to
the place it was before and the only difference between the code that results
in corrupted pointers and this one (which does not show any corruptions at
all), is that there were a few more calls for validating the po
** Attachment added: "2.6.31-14-generic_48+bug396286v4.txt"
http://launchpadlibrarian.net/34619858/2.6.31-14-generic_48%2Bbug396286v4.txt
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notification becau
This actually looks interesting. Maybe some light somewhere? :) Again
the corruption seems not to have happened at all. And this time the
structure was not modified. I only moved the init statements somewhat.
But before getting too existed, could you take a go at v4 (and again
post me the dmesg of
** Attachment added: "2.6.31-14-generic_48+bug396286v3.txt"
http://launchpadlibrarian.net/34595572/2.6.31-14-generic_48%2Bbug396286v3.txt
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notification becau
So the setting of SMP has no effect here and looking at the addresses of
the bad pointers, there seems to be no obvious pattern in those. Neither
the offsets within the inode structure are really showing any suspicious
placements. So one step further, I added some code to immediately check
after th
Sorry, please disregard the previous 48v2 attachment. See this one
instead.
** Attachment added: "2.6.31-14-generic_48+bug396286v2.txt"
http://launchpadlibrarian.net/34451873/2.6.31-14-generic_48%2Bbug396286v2.txt
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
htt
2.6.31-14-generic_48+bug396286v2.txt attached.
** Attachment added: "2.6.31-14-generic_48+bug396286v2.txt"
http://launchpadlibrarian.net/34451515/2.6.31-14-generic_48%2Bbug396286v2.txt
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/
2.6.31-14-generic_48+bug396286v1.txt attached.
** Attachment added: "2.6.31-14-generic_48+bug396286v1.txt"
http://launchpadlibrarian.net/34450612/2.6.31-14-generic_48%2Bbug396286v1.txt
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/
As thie issue seems to vanish when we prod around with the size of the
inode structure, this needs a bit more prodding around. I added two more
test kernels to my peoples page:
2.6.31-14.38*v1: This one is the stock kernel, but with SMP disabled in config
(which removes some code replacement magi
** Tags added: regression-karmic
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
To compare, I tried booting with the stock 47 (46 is no longer
available) and, sure enough, it freezes during boot as the other
unpatched releases before.
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notif
Here's dmesg for 46 v2.
** Attachment added: "dmesg-r_2.6.31-14-generic_46+bug396286v2.txt"
http://launchpadlibrarian.net/33797207/dmesg-r_2.6.31-14-generic_46%2Bbug396286v2.txt
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
That looks somewhat crazy. There is not a single error message in this
dmesg. This is completely unexpected and actually weird. Just because
this is so unbelievable, could you please also try the -14.46 v2 which I
uploaded (and attach the dmesg here). And for the sake of completeness
verify and con
dmesg attached.
** Attachment added: "dmesg-r_2.6.31-14-generic_46+bug396286v1.txt"
http://launchpadlibrarian.net/33728592/dmesg-r_2.6.31-14-generic_46%2Bbug396286v1.txt
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You rec
Grr, wrong build chroot. Ok, on the other hand I'd have been surprised
if there had not been anything gone wrong when doing things quickly in
the evening. Correct architecture uploaded.
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396
Nice, except that Geode really is an i386 architecture, so an amd4
kernel won't be of any use here. :)
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notification because you are a member of Ubuntu
Bugs, whi
New kernel same place. Please try to boot and if it comes up add the
dmesg as usual. Thanks.
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I think this issue is preventing boot on the OLPC XO-1 hardware, however
as the screen never unfreezes it is hard to be certain.
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notification because you are a
** Summary changed:
- 2.6.31-generic: kernel panic near the end of initramfs
+ [Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
--
[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs
https://bugs.launchpad.net/bugs/396286
You received this bug notific
47 matches
Mail list logo
