Comment 28 for bug 26859

(In reply to comment #27)
> Kernel Testing – First Report
>

>
> 2.Testing of Kernel Image
> Attempts to boot the /6 kernel image all reach the same point – grub selection
> completes, the screen is replaced with the default ubuntu wallpaper with the
> horizontal loading bar and the message “loading modules” and the system then
> hangs. Waiting for 5 minutes confirms system hang at that point.
>
> 3.Testing of Safe Mode Kernel Image
> Attempting to boot into the new Kernel in safe mode result in a similar
> end-point. However, after a brief delay the screen clears and the text-mode of a
> dump starts to scroll rapidly up the screen. This continues indefinitely [core
> dump maybe?] until I use the escape key to interrupt, where I get the following
> message displayed on my screen:-
>
> Kernel panic – not syncing – Aieee!!!
>
> [ 89.757625] Code: 80 3f 00 7e f9 e9 1d fd ff ff f3 90 80 3f 00 7e f9 e9 4a fd
> [ 89.757795] console shuts up...
>
>
> At which point I assume that this kernel [even though it is No. 6] has the sync
> problem that I observed in /var/log/messages when I reported this error initially.

SCORE! number 6 is just a rebuild of 2.6.12-9. *shrug*

> 4.Addenda relating to new Kernel Images
> To give maximum validity to test results, I decided to perform all these tests
> on a new, fresh, “vanilla” build. After the initial boot of the machine the
> “Update Manager” in GNOME reported new packages for downloading. The first time
> I saw this I accepted automatically without checking first. Turns out that there
> is a new kernel being shipped, 2.6.12.16.1. For what it's worth, this hangs my
> machine just as efficiently as all the rest!

don't mind it. that's only a meta package.

>
> 5.Final thought.
> I haven't tried this yet... but it so happens that I do have the i386 DVD for
> ubuntu 5.10 which I downloaded at the same time as my 64-bit version. Since I
> can't do anything useful with your test kernels [sorry, Fabio! I am happy to
> take your suggestions/directions on how best to proceed] I might just wipe away
> this 64-bit build and try a 32-bit version instead...
>
> Awaiting next instruction...

I guess the next step is to see why the build environment is making such a mess.

At this point given that number 6 is a rebuild of 2.6.12-9, i can't see any
reason why it should hang that way.

For now i will need to return from holidays, get access again to the build farm
and start poking bit by bit what hell is going on.

Thanks a lot for your tests
Fabio