On Mon, 2005-08-01 at 09:09 +0200, Pavel Machek wrote:
> Hi!
>
> > > If you think it is a linux bug, can you produce small test case doing
> > > just the sigwait, and post it on l-k with big title "sigwait() breaks
> > > when straced, and on suspend"?
> > >
> > > That way it is going to get som
Hi,
>> > If you think it is a linux bug, can you produce small test case
doing
>> > just the sigwait, and post it on l-k with big title "sigwait()
breaks
>> > when straced, and on suspend"?
>> >
>> > That way it is going to get some attetion, and you'll get either
>> > documentation or kernel fixed
Hi!
> > If you think it is a linux bug, can you produce small test case doing
> > just the sigwait, and post it on l-k with big title "sigwait() breaks
> > when straced, and on suspend"?
> >
> > That way it is going to get some attetion, and you'll get either
> > documentation or kernel fixed.
On Sat, 2005-07-30 at 18:30 +0800, Pavel Machek wrote:
> Hi!
>
> > >> One other glitch is that pdnsd (a nameserver caching daemon) has
> crashed
> > >> when the system wakes up from swsusp. It also happens when
> waking up
> > >> from S3, which was working with 2.6.11.4 although not with
> 2.6.
Hi!
> >> One other glitch is that pdnsd (a nameserver caching daemon) has crashed
> >> when the system wakes up from swsusp. It also happens when waking up
> >> from S3, which was working with 2.6.11.4 although not with 2.6.13-rc3.
> >> Many people have said mysql also does not suspend well. Is
>> One other glitch is that pdnsd (a nameserver caching daemon) has crashed
>> when the system wakes up from swsusp. It also happens when waking up
>> from S3, which was working with 2.6.11.4 although not with 2.6.13-rc3.
>> Many people have said mysql also does not suspend well. Is their use of
> Perhaps the patch from Daniel Ritz to free the yenta IRQ on suspend
> (attached) will help?
Alas, when I went to apply it, patch said it was already there, and
sure enough 2.6.13-rc3-mm2 does have it.
One approach is to find out why PCMCIA cannot remove the socket power
when using cardctl eject
> So, in short, problem is that if you leave prism54 card in, even
> with module removed, swsusp hangs, right?
Right, in some circumstances. To narrow them down I spent many hours
rebooting into combinations of runlevels and loaded modules. It is
reproducible even in single-user mode. The vario
On Thursday, 28 of July 2005 23:36, Pavel Machek wrote:
> Hi!
>
> > >>If I don't eject the pcmcia card (usually a prism54 wireless card),
> > >>swsusp begins the process of hibernation, but never gets to the
> > >>writing pages part.
> >
> > > Well, it really may be the firmware loading. Add some
Hi!
> >>If I don't eject the pcmcia card (usually a prism54 wireless card),
> >>swsusp begins the process of hibernation, but never gets to the
> >>writing pages part.
>
> > Well, it really may be the firmware loading. Add some printks to
> > confirm it, then fix it.
>
> I did more tests, this t
>>If I don't eject the pcmcia card (usually a prism54 wireless card),
>>swsusp begins the process of hibernation, but never gets to the
>>writing pages part.
> Well, it really may be the firmware loading. Add some printks to
> confirm it, then fix it.
I did more tests, this time with 2.6.13-rc3-m
Hi!
> swsusp now mostly works on my TP 600X. If I don't eject the pcmcia card
> (usually a prism54 wireless card), swsusp begins the process of
> hibernation, but never gets to the writing pages part. The eth0 somehow
> tries to reload the firmware (as if it's been woken up), and then
> everythi
swsusp now mostly works on my TP 600X. If I don't eject the pcmcia card
(usually a prism54 wireless card), swsusp begins the process of
hibernation, but never gets to the writing pages part. The eth0 somehow
tries to reload the firmware (as if it's been woken up), and then
everything hangs. If I
13 matches
Mail list logo
