While using amd64 livecd's 2007.0 and 2008.0b1 I have several kernel oopses that don't happen while I'm running a completely built system. It might be a kernel misconfiguration for my system. Motherboard: Gigabyte GA-MA69VM-S2 CPU: AMD X2 6400+ Memory: 2GB (2x1GB) 800MHz DDR2, Corsair, which tests OK with memtest86 GPU: ATI RV370 Reproducible: Always Steps to Reproduce: 1.start computer using livcd 2007.0 or 2008.0b1 2.do something processor intensive (emerge kdepim will always oops, emerge --sync oops-es during portage cache update) 3.Oops Actual Results: >>> Updating Portage cache: 39%Unable to handle kernel paging request at ffff81003ba0029d RIP: [<ffffffff8018132f>] PGD 8063 PUD 9063 PMD c7c800003ba001e3 BAD Oops: 000b [1] SMP CPU 0 (full backtrace in attachment) Expected Results: No Oopses Motherboard: Gigabyte GA-MA6VM-S2 CPU: AMD X2 6400+ Memory: Corsair DDR2 800MHz ATI RV370 (X300, PCIE) Happens whether I use swap or not.
Created attachment 149057 [details] Example of an oops that occurs with livecd's 2007 and 2008
Created attachment 149258 [details] .config of kernel that doesn't have kernel paging errors on my system
I was able to install using the 2008.0 beta CD by using a stage3 image and just emerging vanilla-sources (computer would have kernel paging problems while installing gentoo-sources) and grub so I could boot into a minimal system. The kernel that I built myself (.config attached) didn't have a problem and made it possible to finish installing the system.
So are you doing a 32-bit or 64-bit install? You've not specified which media you used, so we have no idea.
I'm installing a 64 bit environment, otherwise I'd have used the x86 livecd and not the amd64 one as I mentioned in the first line of the bug report description. The machine is rock solid with my own kernel (both vanilla- and gentoo-sources). I have both cores working on foldingathome work units and in the mean time I'm emerging a lot of stuff to complete the system. I can use Juniper 32 bit VPN java stuff, other emulated 32 bit stuff and the machine just won't flinch. I would be happy to build a kernel with the .config that is used in the amd64 livecd to see if I can reproduce these kernel paging problems with it.
Why isn't kernel debug enabled on distribution media? It does not slow down the machine when enabled decently. The CONFIG_DEBUG_KERNEL add several variables otherwise not present in .config, so best is to enable it through 'make menuconfig'. Anyway, here is what I propose for future kernels on distribution media. CONFIG_DEBUG_KERNEL=y CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_INFO=y CONFIG_FRAME_POINTER=y
The oops.tx you would have to resolve using the System.map file, hopefully located in /boot partition using ksymoops(1) utility. Am not sure if it is available on the Live CD/DVD media.
The kernel debug options sound like a good idea. On installation media speed is probably not that much of an issue and once the system is up and running people can decide for themselves how fast they want their kernel to be. I won't have much time in the near future to tinker with it but I will play with it some more.
These few options are really below a 1%, really nobody will realize. ;-)
OK, I added the debugging options and they'll show up in 2008.0 Beta 2. Of course, we've also updated to the 2.6.24 kernel and made quite a few kernel config changes, so this might be fixed, anyway.
I have just finished playing around with the 2008 beta2 amd64 minimal install livecd. I have compiled kdepim, kdelibs and openoffice-2.4 from source without any problems. It looks to me like this livecd problem has been solved by upgrading the kernel to 2.6.24-gentoo-r5.
