Bug#284477: Bug#302001: Merge bugs?
Horms schrieb:
after reading other bug reports regarding symptoms with a crazy clock, I
think the behaviour I described is the same as in #284477 and #298301.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=284477
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298301
Agreed, this mail should merge them.
I had a quick look around, and it seems that most/all of the
reports of this bug are from Debian users. Which could mean
a number of things, but it does make me wonder if it is
caused by one of the patches applied to the Debian Kernel.
btw: It first appeared here when I tried Ubuntu Warty (as you can read
in #302001), so the Ubuntu kernel is (was?) also affected. (I don't know
how much Ubuntu and Debian kernels differ...)
Note also that it happened only after insertion of the uhci_hcd module,
see #302001.
Is there any chance that any of the interested parties could test
a) 2.4.12 from unstable and b) an unpatched kernel from kernel.org?
I'll try an unpatched kernel on an affected machine within the next 10 days.
Are you sure there is an 2.4.12 in unstable? What's special to this
kernel? I also tried kernel-image-2.4.27-2-686 from sarge, where the
problem seemed to be gone - but some of the affected systems where
somehow instable using this kernel (random lockups within 3-6 days).
For me (with kernel 2.6), disabling ACPI_SLEEP and X86_UP_IOAPIC worked
(no BIOS update, no comment-out in pci_link.c). Maybe one of them would
have been enough, but there wasn't enough time to test this..
In the mean time, the best work around seems to be to
commend out the call to acpi_ut_evaluate_object() in
acpi_pci_add_link() in drivers/acpi/pci_link.c.
http://bugzilla.kernel.org/show_bug.cgi?id=4235
But that looks like a solution that will make other things fall apart,
and I am entirely uncomfortable with the idea of applying that fix to
Debain.
Agreed, that's why I first tried the other work arounds.
Martin
--
SULFURCELL Solartechnik GmbH
Martin Stigge
Barbara-McClintock-Str. 11
12489 Berlin
stigge@sulfurcell.de
Reply to: