Messages in this thread | | | Date | Wed, 16 Jul 2008 23:57:51 +0200 | From | Frédéric Weisbecker <> | Subject | Re: today's linux-next fails to boot |
| |
Thomas Meyer a écrit : > Am Samstag, den 12.07.2008, 17:03 +0200 schrieb Takashi Iwai: > >> At Fri, 11 Jul 2008 14:12:11 +0300, >> Török Edwin wrote: >> >>> Today's linux-next tree (commit >>> 93847083e4791567931bd17c039cc35881cdad29) fails to boot: >>> [built with gcc-4.2.4-3] >>> >>> BUG: Int 14: CR2 b0049dea >>> EDI 00000082 ESI 00000000 EBP c059be88 ESP c059be5c >>> EBX f000ec62 EDX 0000000e ECX c0595480 EAX f000ec62 >>> err 00000000 EIP c0181ca0 CS 00000060 flg 00010082 >>> Stack: 00000040 c06a2ba0 000080d0 c0595480 c0000f19c c000f180 c0581120 >>> c059bea8 >>> c02bf19b 00000000 00000080 c059beb8 c0000f194 c000f180 0000000a >>> c059beb8 >>> c03a1059 00000000 00000000 c059bed8 c05c4c7c 0009efff 00000000 >>> c04f4df4 >>> >>> I get this as soon as I boot from grub2, strangely the error message is >>> at the bottom of the screen, and I can't see the full message (scrolling >>> won't work). >>> >>> The last kernel I built & booted was 2.6.26-rc8 from Linus's tree. I >>> will try to built&boot 2.6.26-rc9, and then bisect. >>> >>> This happens on 32-bit Dell Inspiron 6400 (Intel Core Duo T2300 @1.66 >>> Ghz CPU), Intel ICH-7 chipset, and a seagate SATA drive. >>> I will provide full hardware details once I bisected the problem. >>> >>> Meanwhile, if somebody has an idea as to what is wrong? >>> >> [Added Ingo to Cc] >> >> I get the boot problem on i386 with 2008-07-11 linux-next tree, too. >> In my case, no error appears on the screen, just staying blank and >> dead. It seems stopping at the very beginning, soon after GRUB, so >> could be the same reason. >> >> The same config worked fine with yesterday's tree (2008-07-10) on the >> same machine. >> Also, today's tree works on x86-64 (but on another machine). >> >> > > I have got the same problem as Edwin TÖRÖK: From next-20080710 to next-20080711 the kernel fails to boot. > EIP seems to be in function kmem_cache_alloc. > > This is also true for next-20080716. > I didn't try the kernels > next-20080711 and < next-20080716. > > Any news on this bug? > Yes a fix has been released: http://article.gmane.org/gmane.linux.kernel.kexec/1882
But I don't know when it will be applied.... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |