Older kernels work fine but I can not figure out why the new kernels hang on boot giving the error: Failed to set xfermode. Any ideas? Thanks in advance.

Hello,

Experienced same problem (see https://bugzilla.redhat.com/bugzilla....cgi?id=193492 )

Have you tried adding the following to the boot parameters:
pci=noacpi OR acpi=off

It (temporarly) fixed the problem on my box (equipped VIA VT8237R + SATA discs)

Regards

I tried the kernel args you mention to no avail.
I also have a via + sata. I am getting an error: Can't find /dev/console!!!

Hoy hoy.
Have the same problem. It started with kernel 2.6.16.17. My 2.6.16.16-kernel works just fine. I used the 2.6.16.16-confige file to run "make oldconfig" on the 2.6.16.17-kernel. During boot the output says "ata1: qc timeout (cmd 0xef) ata1: failed to set xfermode, disabled". And then kernel panic. I have reed the changelog-file but I can't figure out waht is new that makes it panic.
(VIA VT8237 and SATA disk)

Hello around,

Also digging through the changelogs from the kernel itself (see http://fedoranews.org/cms/node/958 to find your way around), it seems something happened concerning VIA "quirks" (I don't know what "quirks" stand for exactly), and more precisely INT handling exceptions in regards with some "misbehaving" VIA hardware.

Funny enough, the time I installed FC4 on the same hardware, I experienced problems of the same kind and had to disable ACPI to proceed (it had to do with the "sata_via" driver and INT handling). It somehow got solved later, along with kernel updates.

Maybe a clue for those who know more about those "quirks", INT handling and kernel stuff in general ;-)

Regards