Hi David, David Coppa wrote on Tue, Sep 09, 2014 at 07:44:47PM +0200: > On Tue, Sep 9, 2014 at 7:27 PM, Ingo Schwarze <schwa...@usta.de> wrote:
>> i'm sorry to say it makes no difference for me (i'm not opposed to the >> diff, though). >> >> On my laptop, building ports works fine, running firefox works fine, >> but whenever i surf the web with firefox while building ports, >> the machine locks up hard. Sometimes, the lockup already happens >> when merely starting firefox while building ports. Often, it >> happens not when requesting a new URI, but when merely scrolling >> within the page in firefox. >> >> After the lockup, CapsLk and NmLk still toggle the respective LEDs, >> Fn-PgUp still switches on and off the torch, but nothing else has >> any effect, not even Ctrl-Alt-Esc, Ctrl-Alt-Delete, Ctrl-Alt-Backspace >> or Ctrl-Alt-F1. >> >> Unfortunately, i cannot break into ddb because i don't have a >> docking station, hence no serial console, and when going to the >> PC virtual console (Ctrl-Alt-F1), setting export DISPLAY=:0, >> and starting firefox from the console, i was unable to get any >> lockup. Apparently, it only happens when X (or whatever) is >> actually painting something onto the screen. >> >> Whether i run with the defaults or with apm -A doesn't appear to >> make a difference. > I'm a bit confused... Is this hang happening without apmd running? Yes. That doesn't make a difference, either. Usually, i run with apmd in default mode: ischwarze@isnote $ grep apm /etc/rc.conf.local apmd_flags="" But with apmd_flags="-A" or apmd_flags=NO the hangs happen in exactly the same way. Yours, Ingo
