From: Adrian Bunk <hidden> Date: 2007-03-30 21:32:14
This email lists some known regressions in Linus' tree compared to 2.6.20.
If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any other way
possibly involved with one or more of these issues.
Due to the huge amount of recipients, please trim the Cc when answering.
Subject : crashes in KDE
References : http://bugzilla.kernel.org/show_bug.cgi?id=8157
Submitter : Oliver Pinter [off-list ref]
Status : unknown
Subject : hung bootup in various drivers
References : http://lkml.org/lkml/2007/3/30/68
Submitter : Ingo Molnar [off-list ref]
Handled-By : Ingo Molnar [off-list ref]
Greg KH [off-list ref]
Kay Sievers [off-list ref]
Status : problem is being discussed
Subject : kernels fail to boot with drives on ATIIXP controller
(ACPI/IRQ related)
References : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229621http://lkml.org/lkml/2007/3/4/257
Submitter : Michal Jaegermann [off-list ref]
Status : unknown
Subject : NCQ problem with ahci and Hitachi drive
References : http://lkml.org/lkml/2007/3/4/178http://lkml.org/lkml/2007/3/9/475http://lkml.org/lkml/2007/2/22/8
Submitter : Mathieu Bérard [off-list ref]
Handled-By : Tejun Heo [off-list ref]
Patch : http://lkml.org/lkml/2007/2/22/8
Status : possible patch available
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, Mar 30, 2007 at 11:32:09PM +0200, Adrian Bunk wrote:
Subject : hung bootup in various drivers
References : http://lkml.org/lkml/2007/3/30/68
Submitter : Ingo Molnar [off-list ref]
Handled-By : Ingo Molnar [off-list ref]
Greg KH [off-list ref]
Kay Sievers [off-list ref]
Status : problem is being discussed
Note, this should probably read:
hung bootup for drivers built into the kernel, that fail their
module_init() call.
A much smaller minority of cases :)
thanks,
greg k-h
I have now even better one with pata_via. A kernel, which for
all practical purposes is 2.6.21-rc5, not only refuses to boot
(and I cannot find some option combination which would allow me to
do so anyway) but simply refuses to read _any_ data from a media.
This included a partitioning information.
Earlier kernel on the same hardware boots without raising any fuss.
Details are collected as
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234650
Michal
I have now even better one with pata_via. A kernel, which for
all practical purposes is 2.6.21-rc5, not only refuses to boot
(and I cannot find some option combination which would allow me to
do so anyway) but simply refuses to read _any_ data from a media.
This included a partitioning information.
Earlier kernel on the same hardware boots without raising any fuss.
Details are collected as
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234650
If I understand this correctly, a plain 2.6.20 kernel is already broken?
Michal
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
I have now even better one with pata_via. A kernel, which for
all practical purposes is 2.6.21-rc5, not only refuses to boot
(and I cannot find some option combination which would allow me to
do so anyway) but simply refuses to read _any_ data from a media.
This included a partitioning information.
Earlier kernel on the same hardware boots without raising any fuss.
Details are collected as
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234650
If I understand this correctly, a plain 2.6.20 kernel is already broken?
You mean that a quoted report talks about 2.6.20-1.3025.fc7 kernel?
These are vagaries of kernel version numbering in Fedora.
Changelogs are not that clear but it appears that
2.6.19-1.2911.6.4.fc6 will be actually closer to 2.6.20.
That kernel from a bug report is really, for all intents and purposes,
2.6.21-rc5 (if I am not misreading something).
I am afraid that I do not have at this moment an easy to way to check
"plain" 2.6.20 on the hardware in question. It appears that the
essential difference is that a working kernel is using and old IDE
driver, and sees the drive - in this case - as /dev/hdc, while the
current one tries to go through libata and chockes uncontrollably.
Michal