Wow, i mounted my phone last nite and nothing that bad happened. Is there any other messages in /var/log/messages?? hbca# dmesg | grep da rum0: need multicast update callback da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: <HTC Android Phone 0100> Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da1 at umass-sim0 bus 0 scbus0 target 0 lun 1 da1: <HTC Android Phone 0100> Removable Direct Access SCSI-2 device da1: 1.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry (da1:umass-sim0:0:0:1): lost device (da1:umass-sim0:0:0:1): removing device entry da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: <HTC Android Phone 0100> Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da1 at umass-sim0 bus 0 scbus0 target 0 lun 1 da1: <HTC Android Phone 0100> Removable Direct Access SCSI-2 device da1: 1.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry (da1:umass-sim0:0:0:1): lost device (da1:umass-sim0:0:0:1): removing device entry hbca# On Wed, 20 Oct 2010, Jung-uk Kim wrote: > On Tuesday 19 October 2010 09:15 pm, Matt wrote: >> My experience with a sleeping freebsd laptop has been shortlived! >> >> Today I rebuilt world using clang & this morning's csup current. >> Clang build went just swimmingly. >> >> Unthinkingly, I closed my laptop lid and put it in my case. >> When I got to my house, it was roasting with fans spinning and >> sleep light flashing. No damage, thankfully. >> >> Low and behold, hw.pci.do_power_resume=0 no longer lets my laptop >> sleep! >> >> I had recently fiddled with powerd, but problem persisted after >> reverting to previous configuration of associated sysctls etc. >> >> Interestingly, sleep bounce now fails with a hard freeze, which it >> never has in the past. >> >> Verbose output shows the wifi then re0 network interfaces going >> from D0->D3 as last living output. >> >> Please note problem persists regardless of user, X running, >> sleep_delay sysctl, do_power_resume, do_power_nodriver, powerd >> running/not running. >> >> Without sleep bounce, problem is characterized by flashing sleep >> light and spinning fans (CPU temperature is high). >> >> No devices added or removed, was sleeping this morning before >> buildworld. Is it worth rebuilding with gcc? Or a content change >> and not a compiler issue? Any major pci changes lately maybe? > > Can you please update source and try again? If it does not work, > please set a new tunable "hw.pci.do_power_suspend=0" and tell me > whether it helps or not. FYI, hw.pci.do_power_resume does not apply > to suspend any more. So, if you want to restore the previous > behaviour, you need both "hw.pci.do_power_resume=0" and > "hw.pci.do_power_suspend=0". However, my hunch tells me that you > only need the latter. > > Also, if possible, I'd like to see 'devinfo -rv', 'pciconf -clv', > 'acpidump -dt', and 'lspci -vvv' output. Note lspci is available via > ports/sysutils/pciutils. > > Thanks, > > Jung-uk Kim > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" >Received on Wed Oct 20 2010 - 15:27:35 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:08 UTC