help - can't boot 2.6.34

[Dr. Michael J. Chudobiak]

Hi all,

My HP DC7800 with encrypted Intel SSD can boot:

kernel-2.6.33.8-149.fc13.x86_64

but not the 2.6.34 kernels like:

kernel-2.6.34.6-54.fc13.x86_64

The screen goes blank very early in the boot process, before the disk 
passphrase is requested. It happens so fast that I can't read the 
limited text that appears on the screen, and the disks are not mounted 
for logging...

Anyway... maybe this rings a bell for someone?

Removing and re-installing the 2.6.34 kernel doesn't fix anything.

- Mike

[Mogens Kjaer]

On 09/16/2010 02:01 PM, Dr. Michael J. Chudobiak wrote:
> Hi all,
>
> My HP DC7800 with encrypted Intel SSD can boot:
>
> kernel-2.6.33.8-149.fc13.x86_64
>
> but not the 2.6.34 kernels like:
>
> kernel-2.6.34.6-54.fc13.x86_64

Did you ever find a fix for this?

I have a HP DC7800 with the same problem, except that the harddisk isn't 
encrypted.

No messages are displayed, even if rhgb and quiet are removed from the 
boot line.

So I'm still on a 2.6.33 kernel.

Mogens

[Frank Murphy]

On 07/10/10 06:51, Mogens Kjaer wrote:
<snip>
> No messages are displayed, even if rhgb and quiet are removed from the
> boot line.
>
> So I'm still on a 2.6.33 kernel.
>
> Mogens

yum install kernel-debug.
and attempt boot from it.

You may get some relevant info.

[Mogens Kjaer]

On 10/07/2010 09:01 AM, Frank Murphy wrote:
...
> yum install kernel-debug.
> and attempt boot from it.
>
> You may get some relevant info.

Thanks for the suggestion.

The problem is that the monitor goes blank when the crash
occurs.

I had to boot the debug kernel with boot_delay=500 to follow what
goes wrong (alas, I don't have a serial cable any more).

A screen dump before the machine crashes can be seen at:

http://www.lemo.dk/fedora13kernel.jpg

When the call trace finishes, the machine is dead and the monitor blank.

The call trace looks like a warning?

Any more suggestions? agpgart-intel problem?

Mogens

[Mogens Kjaer]

On 10/07/2010 01:31 PM, Mogens Kjaer wrote:
...
> Any more suggestions? agpgart-intel problem?

Google was my friend:

https://bugzilla.redhat.com/show_bug.cgi?id=629203

I'll wait for 2.6.34.7-58

Mogens

[Ranjan Maitra]

On Thu, 7 Oct 2010 00:51:54 -0500 Mogens Kjaer  wrote:
> On 09/16/2010 02:01 PM, Dr. Michael J. Chudobiak wrote:
> > Hi all,
> >
> > My HP DC7800 with encrypted Intel SSD can boot:
> >
> > kernel-2.6.33.8-149.fc13.x86_64
> >
> > but not the 2.6.34 kernels like:
> >
> > kernel-2.6.34.6-54.fc13.x86_64
>
> Did you ever find a fix for this?
>
> I have a HP DC7800 with the same problem, except that the harddisk isn't 
> encrypted.
>
> No messages are displayed, even if rhgb and quiet are removed from the 
> boot line.
>
> So I'm still on a 2.6.33 kernel.
>
> Mogens

I reported this on bugzilla perhaps a month ago, and here is my solution
(not quite):

Go back to the 2.6.33 kernel.

Remove the 2.6.34.6-47 (or intermediate between the 2.6.33 and
2.6.34.7) kernels.

yum update now. The latest kernel (2.6.34-7-56) will be installed via
delta rpms.

Reboot. It worked for me.

For some reason, it appears to me that some mess up was introduced in
the interim last three kernels and it has not gone away yet. The delta
rpms may be the problem but also the solution. This problem and the
observations were reported, but the bug has not been even assigned yet
(certainly actively looked on yet). Bugzilla has become very spotty in
my opinion. It completely depends on who gets assigned the bug and how
committed he/she is to the solution and this is sometimes lacking in
very serious cases as this one.

https://bugzilla.redhat.com/show_bug.cgi?id=632412

Best wishes,
Ranjan
> -- 
> Mogens Kjaer, [e-mail]
> http://www.lemo.dk
> -- 
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

[Mogens Kjaer]

On 10/07/2010 01:59 PM, Ranjan Maitra wrote:
....
> For some reason, it appears to me that some mess up was introduced in
> the interim last three kernels and it has not gone away yet. The delta
> rpms may be the problem but also the solution.

That could be. I have a local fedora mirror so I've disabled delta rpm 
updates. It's faster to download the whole packages than rebuilding.

Mogens

[Jonathan Dieter]

On Thu, 2010-10-07 at 06:59 -0500, Ranjan Maitra wrote:
> The delta rpms may be the problem but also the solution.

The deltarpms are not the problem.  If the deltarpm doesn't build to a
byte-for-byte copy of the original rpm, the signature won't match and
yum will refuse to install it.

Jonathan

[Ranjan Maitra]

On Thu, 7 Oct 2010 07:30:54 -0500 Jonathan Dieter 
wrote:
> On Thu, 2010-10-07 at 06:59 -0500, Ranjan Maitra wrote:
> > The delta rpms may be the problem but also the solution.
>
> The deltarpms are not the problem.  If the deltarpm doesn't build to a
> byte-for-byte copy of the original rpm, the signature won't match and
> yum will refuse to install it.
>
> Jonathan

I don't think the "delta rpms" are a problem in the install. It is
not an issue of the signature matching. Some bug was introduced in the
middle and it seems to have carried on. That is the only explanation I
could come up for my observation that you can not update from the
interim 2.6.34's at all.

Specifically, I went back to 2.6.33.5-122 and removed all the other
more recent kernels -- the last two kernels before 2.6.34-7. Then I installed the latest 2.6.34.7-56.x86_64 from 2.6.33.5-122 and this time, it rebooted fine, no problem.

The problem has cropped up over the last three kernels. If I update from a
lower kernel, there is not a problem, but from these it yields the kernel
panic. So, I believe this bug was introduced in the previous two kernels and has not
gone away. Something there has changed (please consider the changes from the
last three 2.6.34 kernels relative to the ones previous to it, I guess!)

Ranjan