On Sun, 27 Aug 2006 14:16:41 +0200
Christian Perrier <[EMAIL PROTECTED]> wrote:
> >
> > If that's not the case and it locks hard, you can try to unload some
> > modules first; the usb and ieee1394 modules for example.
>
>
> I tried unloading all the ieee1394 stuff and as much USB stuff as
> pos
(a mail I forgot to send)
> I think it will be best to send your bug report upstream. But we can
> try to find the problem ourselves first.
>
> Does the the screen just stay black, but for the rest it is OK? Can you
> still ssh into your machine?
OK, I narrowed the problem a little. Even though
> I think it will be best to send your bug report upstream. But we can
> try to find the problem ourselves first.
>
> Does the the screen just stay black, but for the rest it is OK? Can you
> still ssh into your machine?
I finally have been able to check this. The machine is really locked
down.
> I think it will be best to send your bug report upstream. But we can
> try to find the problem ourselves first.
Yep. I agree and this is indeed what I would have done as maintainer..:-)
>
> Does the the screen just stay black, but for the rest it is OK? Can you
> still ssh into your machine?
On Sat, 19 Aug 2006 08:15:27 -0500
Christian Perrier <[EMAIL PROTECTED]> wrote:
> Package: uswsusp
> Severity: normal
>
> When used on my laptop with kernel 2.6.17, s2ram never properly exits
> sleep mode while it works well with 2.6.16 kernels (both are stock
> Debian kernels: linux-image-2.6.16
Package: uswsusp
Severity: normal
When used on my laptop with kernel 2.6.17, s2ram never properly exits
sleep mode while it works well with 2.6.16 kernels (both are stock
Debian kernels: linux-image-2.6.16-2-686 version 2.6.16-17 and
linux-image-2.6.17-1-686 version 2.6.17-5).
[EMAIL PROTECTED]:~
6 matches
Mail list logo
