http://bugzilla.kernel.org/show_bug.cgi?id=9630
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
------- Comment #10 from [EMAIL PROTECTED] 2008-01-15 14:41 -------
I can't reproduce the bug!
January the 2nd it was still here (when I came back from holydays I
accidentally booted this kernel after an update of the system and the pc was
slow).
I just booted this kernel before the patched one to compare performances, but
it worked flawlessly... both the PNP_MAX_PORT=24 and the original with 8.
During the last days I used only the kernel patched with the first fix
suggested without troubles.
I'm astonished. Since the 2nd of January my Debian SID had about 100 updates,
involving libc6, sysvinit, init scripts and other fundamental packages, perhaps
the problem was a bad dialogue between PNP patched kernel and something else,
but I can't understand what happened...
I tought for some hours before posting this presumed bug, to be sure that this
problem involved only the kernel. I tried the last 2.6.24rc available and it
had the same problem...
I'm sorry for the wasted time and I close this bug.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
