[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-current
Subject:    Re: [Solved] FreeBSD 9-Beta3 on X300 2 problems
From:       "crsnet.pl" <crsnet () crsnet ! pl>
Date:       2011-09-30 20:07:16
Message-ID: 26b8cb12f81f4f6af5e14b2dd04b0de9 () i-pi ! pl
[Download RAW message or body]

 On Fri, 30 Sep 2011 09:52:53 +0200, "crsnet.pl" <crsnet@crsnet.pl> 
 wrote:
> On Wed, 28 Sep 2011 19:57:56 +0900, Taku YAMAMOTO
> <taku@tackymt.homeip.net> wrote:
>> On Tue, 27 Sep 2011 13:06:21 +0100
>> Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> wrote:
>>
>>> On Tue, 2011-09-27 at 19:53 +0800, Adrian Chadd wrote:
>>> > Hans,
>>> >
>>> > Why haven't those patches been committed?
>>>
>>> This patch is an absolute hack, and shouldn't be committed as it 
>>> is.
>>>
>>> I would, however, appreciate some help in determining the correct
>>> solution.  The solution may well involve not suspending/resuming 
>>> hpet(4)
>>> or the other timers on the normal DEVICE_SUSPEND()/DEVICE_RESUME() 
>>> path
>>> but instead doing them as the last thing to be suspended, or it may
>>
>> Like the attached patches do?
>>
>>> instead involve reworking the USB code (and potentially other code) 
>>> to
>>> not need to sleep during suspend/resume.  I don't know the right
>>> solution, but would really like to work with somebody who does.
>>>
>>> Please also see the thread "Choosing between DELAY(useconds) and
>>> pause()" on -current.
>>>
>>> Gavin
 Hello.
 After longer testing thouse patches. I must say, they dont resolve my 
 problem in 100%.
 Suspend/Resume on short time (about 2-3 hours, meybye little longer) 
 works fine. But when i suspend it for longer (8-10 hours) system freeze 
 after resume.
 Any another idea why ?

 Best regards, Adrian.

_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread]