Prev: swiotlb v0.6: seperation of physical/virtual address translation
Next: PATCH: 2.4.37.9 MTU change for TUN/TAP interfaces
From: Eric Miao on 8 Apr 2010 08:10 2010/4/8 Pavel Machek <pavel(a)ucw.cz>: > >> >> > > > > I tried compiling 2.6.34-rc1, and it does not boot :-(. It does not >> >> > > > > seem to even reset the framebuffer (I'm using kexec -- so it stays >> >> > > > > stuck on on previous screen). >> >> > > >> >> > > Tried again with -rc2 and -rc3, and neither boots :-(. I did not have >> >> > > time to set up serial console, yet :-(. Any ideas? >> >> > >> >> > I created a Bugzilla entry at >> >> > https://bugzilla.kernel.org/show_bug.cgi?id=15712 >> >> > for your bug report, please add your address to the CC list in there, >> >> > thanks! >> >> > >> >> Pavel, you broke it ... and here you say something about sane arm maintainers >> >> ;-) >> > >> > ? You know which patch causes it ? >> >> Just have some time to try this out on my corgi, and the kernel runs >> happily. >> >> Pavel, >> >> Which exact model are you running your kernel? > > It is Zaurus SL-C3000 (aka spitz). I'm using kexec, but that used to > work. Should I try minimal config? I'm using kexec as well, but on corgi. My akita is not on hands these days, otherwise I can give it a try. I guess there is nothing fundamentally wrong, so yes, I think it's feasible to try minimal config. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |