On 12/9/09, Corentin Chary <corentin.ch...@gmail.com> wrote: > On Wed, Dec 9, 2009 at 12:54 PM, Alan Jenkins > <sourcejedi.l...@googlemail.com> wrote: >> Hi Corentin >> >> It looks like it's not just my 701 which has problems with SHE. Given >> that Asus don't support it on the pre-installed OS, I think we should >> disable it for the 701. >> >> <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559578>. >> >> Thanks >> Alan >> > > But if I remember correctly, it worked fine on my 701 (only two modes, > but no freeze). > To trigger the bug, I have to "echo 0 >/sys/devices/platform/eeepc/cpufv" ?
Reportedly <http://groups.google.com/group/linux.debian.bugs.dist/msg/9805f22bc6b8bbda>. Another report says it happens only when booting in "single user mode", and not every time. I can't reproduce it myself, even though it's happened to me in the past, both from writing to that file manually, and from the default configuration of eeepc-acpi-scripts. I _can_ still reproduce the strange hissing noise in "performance" mode. If I repeatedly plug and unplug the power adaptor with eeepc-acpi-scripts installed (triggering the switch between "performance" and "normal"), I see various kernel messages. These are the kernel init messages for the webcam and cardreader, suggesting that they are disappearing and re-appearing. I wasn't able to reproduce it without eeepc-acpi-scripts (either by plugging / unplugging repeatedly, or by toggling the value of cpufv in a scripted loop, or by both at the same time). > I don't have my 701 right now, so I can't test, is there anything in > dmesg or is it only a bad hardware freeze ? Apparently it's just a freeze: "Indeed it sounds like 559578, and before proceeding further, though garbled, I have compared the blurred lines to a regular boot, and it turns out the final words before freezing are: Wed Dec 9 09:34:02 2009: Loading EeePC support modules...done. Wed Dec 9 09:34:02 2009: Setting super hybrid engine according to configuration...(AC)...done." <http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/d3f0716684bbadd8> > Anyway, if we disable it for 701, how can we detect that this is a 701 > ? using dmi matching ? when only 2 modes are available ? > Thanks, I would use a DMI match (product name "701"). Hopefully that is distinct from the 701SD, which is marketed with SHE. I know the "900A" has a distinct product name, so it seems likely. Thanks Alan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
