2.6.27-rc6-git6: Reported regressions from 2.6.26 - Kernel

This is a discussion on 2.6.27-rc6-git6: Reported regressions from 2.6.26 - Kernel ; This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me ...

Hi,
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.26. Please verify if it still should be listed and let me know
> (either way).

On Sun, Sep 21, 2008 at 08:54:23PM +0200, Rafael J. Wysocki wrote:
> The following bug entry is on the current list of known regressions
> from 2.6.26. Please verify if it still should be listed and let me know
> (either way).

Yes, it still does this with newest kernel
(9824b8f11373b0df806c135a342da9319ef1d893). At last for me.

not sure if it should be;
From over here, I did a bad install
of isight-firmware-tools, causing hal and udev
to clash. After making sure the package was either
using hal or udev, there is no message of disable irq #23.
If its not too much trouble is there a way to verify that this was
the case, i.g. if udev creates a dev, then hal creates the same device
will this cause ehci_hcd to have messages of this kind? If so
then thats what happened, if not then theres something else causing this.

I've asked Joshua for more information. Since he must to use
netdev tree for a while maybe we could wait 'till next merge
window will be closed and check if nmi_watchdog does work.
So the work in progress.