kernel are you using now, and how does it behave?
Thanks for a clear report,
Jonathan
Still testing/unstable, works now. Using 3.2.0-1-amd64.
--
Rares Aioanei
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
On 03/31/2012 04:58 PM, Jonathan Nieder wrote:
Rares Aioanei wrote:
I just dpkg
-i'd the kernel, ran pm-hibernate as root in Fluxbox and it
hibernated, then came up when I started the machine.
Just to check: do you mean you didn't
FYI, the latest kernel from experimental (-rc7) fails to boot in the exact same
manner.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
The error described can be also seen if compiling a vanilla kernel with
the exact config as the Debian one (in my case 2.6.38.6) . I'm writing this
from the same machine running 2.6.38.4 with a custom config and it works fine.
Hope it helps.
--
Rares Aioanei
--
To UNSUBSCRIBE, email
On Tue, 17 May 2011 05:35:24 -0500
Jonathan Nieder jrnie...@gmail.com wrote:
tags 626851 - moreinfo
quit
(cc-ing the bug log)
Rares Aioanei wrote:
I used the exact sequence of commands in building the working kernel and the
non-working kernel; and yes, the disk driver is , of course
On Tue, 17 May 2011 05:55:12 -0500
Jonathan Nieder jrnie...@gmail.com wrote:
Rares Aioanei wrote:
My custom working config is just the Debian config stripped of unnecessary
drivers (wireless, v4l, etc.). I guess I'll get help from my friend diff(1)
and see if I can help further
Package: linux-2.6
Version: 2.6.38-5
Severity: important
I'm not even certain that the kernel is the problem and not
initramfs-tools or something, but since when the update occured (14th of
May) only the kernel was updated (and libuuid-perl) so I will report
this against the kernel. Obviously, no
7 matches
Mail list logo
