Broken Kernel since 2.6.15

[Jerry Williams]

I was running FC4 and I was running fine until the kernel-2.6.16.
I kept my older kernel-2.6.15 and 2.6.14 which worked just fine.
The newer kernels can't seem to find my SATA disks.
[Bug 187641] kernel-2.6.16-1.2069_FC4 SATA panic
[Bug 199034] SATA -> Failed to set xfermode -> Kernel panic
I received an email saying:
> FC4 has now transitioned to the Fedora legacy project, which will
> continue
> to
> release security related updates for the kernel.  As this bug is not
> security
> related, it is unlikely to be fixed in an update for FC4, and has been
> migrated
> to FC5. 
> Please retest with Fedora Core 5. 
> Thank you. 

I decided to upgrade to FC5 since it still had a kernel-2.6.15.
Now my system won't boot.
I also tried the latest kernel-2.6.17, same thing.
I feel like fedora has pulled the plug on my system.

The funny thing is that I can boot from the DVD and go into rescue mode and
it finds the drive just fine.

So my question is what do I have to do to make a cdrom that I can boot from
and find my disk and load everything else from disk?

I tried a grub floppy, and that worked, but only for the kernels that worked
without it.  So it didn't buy me anything.

So I think the cdrom has to have the kernel on it.

[Wojtek.Pilorz]

On Tue, 19 Sep 2006, Jerry Williams wrote:

>  Date: Tue, 19 Sep 2006 00:11:28 -0600
>  From: Jerry Williams <jwilliam(a)xmission.com&gt;
>  Reply-To: For testers of Fedora Core development releases
>      <fedora-test-list(a)redhat.com&gt;
>  To: fedora-test-list(a)redhat.com
>  Subject: Broken Kernel since 2.6.15
>  
>  I was running FC4 and I was running fine until the kernel-2.6.16.
>  I kept my older kernel-2.6.15 and 2.6.14 which worked just fine.
>  The newer kernels can't seem to find my SATA disks.
>  [Bug 187641] kernel-2.6.16-1.2069_FC4 SATA panic
>  [Bug 199034] SATA -> Failed to set xfermode -> Kernel panic
>  I received an email saying:
>  >FC4 has now transitioned to the Fedora legacy project, which will continue
>  >to
>  >release security related updates for the kernel.  As this bug is not
>  >security
>  >related, it is unlikely to be fixed in an update for FC4, and has been
>  >migrated
>  >to FC5.
>  
>  >Please retest with Fedora Core 5.
>  
>  >Thank you.
>  
>  
>  I decided to upgrade to FC5 since it still had a kernel-2.6.15.
>  Now my system won't boot.
>  I also tried the latest kernel-2.6.17, same thing.
>  I feel like fedora has pulled the plug on my system.
>  
>  The funny thing is that I can boot from the DVD and go into rescue mode and
>  it finds the drive just fine.
>  
>  So my question is what do I have to do to make a cdrom that I can boot from
>  and find my disk and load everything else from disk?
>  
>  I tried a grub floppy, and that worked, but only for the kernels that worked
>  without it.  So it didn't buy me anything.
>  
>  So I think the cdrom has to have the kernel on it.
>  
>   
Maybe you could try Centos 4.4 LiveCD. I had rather good experiences with 
it (except that disk performance was poor on one Compaq EVO, about 1/6 of 
normal transfer rate).
It handles LVM2, has growisofs and cdrecord working well.

Best regards,

Wojtek

[Adam Pribyl]

>  I decided to upgrade to FC5 since it still had a kernel-2.6.15.
>  Now my system won't boot.
>  I also tried the latest kernel-2.6.17, same thing.
>  I feel like fedora has pulled the plug on my system.
>
>  The funny thing is that I can boot from the DVD and go into rescue mode and
>  it finds the drive just fine.
>
>  So my question is what do I have to do to make a cdrom that I can boot from
>  and find my disk and load everything else from disk?
>
>  I tried a grub floppy, and that worked, but only for the kernels that worked
>  without it.  So it didn't buy me anything.
>
>  So I think the cdrom has to have the kernel on it. 
You can try to rebuild initrd.

Adam Pribyl

[Mike Chambers]

On Tue, 2006-09-19 at 00:11 -0600, Jerry Williams wrote:

>  I decided to upgrade to FC5 since it still had a kernel-2.6.15.
>  Now my system won't boot.
>  I also tried the latest kernel-2.6.17, same thing.
>  I feel like fedora has pulled the plug on my system. 
Just a quick question, but what file system is installed on your SATA
drives?  ReiserFS?  Ext3? What?

Have you tried a clean install or at least started it, to see if they
are seen then?

-- 
Mike Chambers
Madisonville, KY

"Sex is like air, it's not important unless your not getting any!"

Broken Kernel since 2.6.15 - More Info

[Jerry Williams]

This is what I see when I boot.


Booting 'Fedora Core (2.6.15-1.2054_FC5)' 

root (hd0,0) 
 Filesystem type is ext2fs, partition type 0x83 
kernel /vmlinux-2.6.15-1.2054_FC5 ro root=/dev/V0/L1 acpi=off rhgb quiet 
      [Linux-bzImage, setup=0x1e00, size=0x16eb71] 
initrd /initrd-2.6.15-1.2054_FC5.img 
     [Linux-initrd @ 0x37e3c000, 0x1b312a bytes] 

Uncompressing Linux... Ok, booting the kernel. 
Red Hat nash version 5.0.32 starting 
ata1: failed to set xfermode, disabled 
ata2: failed to set xfermode, disabled 
device-mapper: dm-mirror: Device lookup failure 
device-mapper: reload ioctl failed: No such device or address 

Unable to open /dev/mapper/via_jheaibjjh - unrecognised disk label. 
   Reading all physical volumes.  This may take a while... 
   No volume groups found 
   Unable to find volume group "V0" 
Unable to access resume device (/dev/V0/L0) 
mount: could not find filesystem '/dev/root' 
setuproot: moving /dev failed: No such file or directory 
setuproot: error mounting /proc: No such file or directory 
setuproot: error mounting /sys: No such file or directory 
switchroot: mount failed: No such file or directory 
Kernel panic - not syncing: Attempted to kill init! 



With kernel 2.6.17-1.2187_FC5 the message is pretty much the same except
for:

ata1: failed to set xfermode (err_mask=0x4) 
ata2: failed to set xfermode (err_mask=0x4)

VIA 8237 
libata version 1.20 
sata_via version 1.1 
/dev/V0/L1 / ext3

A couple of people have suggested running mkinitrd and I have upgraded it
and created new initrd file and it does the same thing.

When I boot from the installation DVD in linux rescue mode it load sata_via
And everything is fine.  Just can't boot off the SATA drive.

Just think I am going to have to figure out how to make a boot cdrom and
load the drivers from it.
Only other thing I can think of doing is building kernel with libata and
sata_via as part of the kernel.
Mkinitrd -v says it is loading about 5 modules and looks like it should
work.


-----Original Message-----
From: fedora-test-list-bounces(a)redhat.com
[mailto:[e-mail]] On Behalf Of Jerry Williams
Sent: Tuesday, September 19, 2006 12:11 AM
To: fedora-test-list(a)redhat.com
Subject: Broken Kernel since 2.6.15

I was running FC4 and I was running fine until the kernel-2.6.16.
I kept my older kernel-2.6.15 and 2.6.14 which worked just fine.
The newer kernels can't seem to find my SATA disks.
[Bug 187641] kernel-2.6.16-1.2069_FC4 SATA panic
[Bug 199034] SATA -> Failed to set xfermode -> Kernel panic
I received an email saying:
> FC4 has now transitioned to the Fedora legacy project, which will
> continue
> to
> release security related updates for the kernel.  As this bug is not
> security
> related, it is unlikely to be fixed in an update for FC4, and has been
> migrated
> to FC5. 
> Please retest with Fedora Core 5. 
> Thank you. 

I decided to upgrade to FC5 since it still had a kernel-2.6.15.
Now my system won't boot.
I also tried the latest kernel-2.6.17, same thing.
I feel like fedora has pulled the plug on my system.

The funny thing is that I can boot from the DVD and go into rescue mode and
it finds the drive just fine.

So my question is what do I have to do to make a cdrom that I can boot from
and find my disk and load everything else from disk?

I tried a grub floppy, and that worked, but only for the kernels that worked
without it.  So it didn't buy me anything.

So I think the cdrom has to have the kernel on it.

-- 
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe: 
https://www.redhat.com/mailman/listinfo/fedora-test-list

Broken Kernel since 2.6.15 - More Info

[Michal Jaegermann]

On Tue, Sep 19, 2006 at 10:00:46AM -0600, Jerry Williams wrote:
>  This is what I see when I boot. 
....
>  Red Hat nash version 5.0.32 starting 
>  ata1: failed to set xfermode, disabled 
>  ata2: failed to set xfermode, disabled  
....
>  When I boot from the installation DVD in linux rescue mode it load
> sata_via
>  And everything is fine. 
Smells like for some reasons 'sata_via' module is either missing
from your mkinitrd or not loaded by 'init' script there.
You can unpack your initrd and examine details with

   zcat /path/to/your/initrd | cpio -imd

and there are options to mkinitrd like '--preload'.

The above is a guess but the fact that you can boot from
installation media clearly shows that there is no problem between
kernel and your hardware. Sure, there is a bug somewhere.

But this is truly a wrong list to discuss FC5 problems and it
is quite possible that you can find better help on the right one.

   Michal

Broken Kernel since 2.6.15 - More Info

[Jerry Williams]

Thanks for your suggestions.
Could someone suggest a better list?
I would like to be testing FC6, but I feel I am stuck in the past.
Can't seem to get past this issue and I don't think it is fixed in FC6
either.  
I have submitted bug reports, what else should I do?

-----Original Message-----
From: fedora-test-list-bounces(a)redhat.com
[mailto:[e-mail]] On Behalf Of Michal Jaegermann
Sent: Tuesday, September 19, 2006 10:52 AM
To: For testers of Fedora Core development releases
Subject: Re: Broken Kernel since 2.6.15 - More Info

On Tue, Sep 19, 2006 at 10:00:46AM -0600, Jerry Williams wrote:
>  This is what I see when I boot. 
....
>  Red Hat nash version 5.0.32 starting 
>  ata1: failed to set xfermode, disabled 
>  ata2: failed to set xfermode, disabled  
....
>  When I boot from the installation DVD in linux rescue mode it load
sata_via
>  And everything is fine. 
Smells like for some reasons 'sata_via' module is either missing
from your mkinitrd or not loaded by 'init' script there.
You can unpack your initrd and examine details with

   zcat /path/to/your/initrd | cpio -imd

and there are options to mkinitrd like '--preload'.

The above is a guess but the fact that you can boot from
installation media clearly shows that there is no problem between
kernel and your hardware. Sure, there is a bug somewhere.

But this is truly a wrong list to discuss FC5 problems and it
is quite possible that you can find better help on the right one.

   Michal

-- 
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe: 
https://www.redhat.com/mailman/listinfo/fedora-test-list

Broken Kernel since 2.6.15 - More Info

[Michal Jaegermann]

On Tue, Sep 19, 2006 at 12:09:06PM -0600, Jerry Williams wrote:
>  Thanks for your suggestions.
>  Could someone suggest a better list? 
How about "fedora-list -- For users of Fedora Core releases"?
If you will look at headers of messages from this list it is not
hard to dig from there https://www.redhat.com/mailman/listinfo/ url.
'fedora-list' also has archives.

   Michal

[Kevin Kofler]

>  I was running FC4 and I was running fine until the kernel-2.6.16.
>  I kept my older kernel-2.6.15 and 2.6.14 which worked just fine. 
[snip]
>  I decided to upgrade to FC5 since it still had a kernel-2.6.15.
>  Now my system won't boot. 
The "2.6.15" kernel shipped with FC5 is actually a 2.6.16-rc6-git3, which is 
almost a 2.6.16, so as 2.6.16 didn't work for you, it's no wonder that one 
didn't either.

You'll probably have to track down an old FC4 kernel, or take the one FC4 
shipped with, and hope it's recent enough for FC5's userspace to work with it.

        Kevin Kofler

[Jerry Williams]

I was able to get kernel-2.6.15-1.1833_FC4.i686.rpm to work.
I appear to be using dmraid, but it doesn't make it that far.
I did edit init and comment out the setquiet and it
loads sata_via.ko, but can't seem to find the disks.
But both the working kernel and newer kernels say sata_via.ko is version
1.1.
I did replace mkinitrd (the latest FC5 update is mkinitrd-5.0.32-2),
rebuild initrd and try again.
I have taken initrd apart and it looks fine, and I compared my
initrd from FC4 with the one from FC5 and they are pretty much the same.
init in FC4 had a couple of DM commands that the FC5 doesn't have.
sata_via.ko can't seem to find the disks and the other commands can't
find anything either.
Any suggestions on how to compare the 2.6.15-1.1833_FC4
and the 2.6.15-1.2054_FC5 kernels?
Can I get all the patches that go between and add them one at a time
and see when it breaks?

-----Original Message-----
From: fedora-test-list-bounces(a)redhat.com
[mailto:[e-mail]] On Behalf Of Kevin Kofler
Sent: Wednesday, September 20, 2006 1:29 AM
To: fedora-test-list(a)redhat.com
Subject: Re: Broken Kernel since 2.6.15

>  I was running FC4 and I was running fine until the kernel-2.6.16.
>  I kept my older kernel-2.6.15 and 2.6.14 which worked just fine. 
[snip]
>  I decided to upgrade to FC5 since it still had a kernel-2.6.15.
>  Now my system won't boot. 
The "2.6.15" kernel shipped with FC5 is actually a 2.6.16-rc6-git3, which is

almost a 2.6.16, so as 2.6.16 didn't work for you, it's no wonder that one 
didn't either.

You'll probably have to track down an old FC4 kernel, or take the one FC4 
shipped with, and hope it's recent enough for FC5's userspace to work with
it.

        Kevin Kofler

-- 
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe: 
https://www.redhat.com/mailman/listinfo/fedora-test-list