Jonathan Nieder wrote: > PICCORO McKAY Lenz wrote: >> but what about squeeze brand 2.6.32, this fails too! > > Actually, we don't care about 2.6.39 at all, except when it is relevant > to fixing 2.6.32 or 3.x.
Ah, sorry, that was less helpful than it should have been. I didn't actually answer your question. I'd suggest working on fixing the bootup in 3.x first, in cooperation with upstream. Afterwards, we would make sure the fix works in 2.6.32.y, too (I called this "backporting the fix", but it has nothing to do with backports.debian.org). Once you are able to reproduce this with a 3.x kernel, please attach * dmesg output from right after bootup when experiencing the bug (you might need to set up a serial console or netconsole or take a photograph of the screen to get this. A photo is fine.) * dmesg and acpidump output from right after bootup when not experiencing the bug (using acpi=off, noapic, or something like that) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
