Jonathan Nieder a écrit :
Another thing to try would be booting into an even more minimal
configuration, without loading any modules or mounting the root
filesystem, by passing the parameter break=top on the kernel command
line[1]. It would presumably be necessary to load the appropriate
Jonathan Nieder a écrit :
Denis Laxalde wrote:
Jonathan Nieder a écrit :
Another thing to try would be booting into an even more minimal
configuration, without loading any modules or mounting the root
filesystem, by passing the parameter break=top on the kernel command
line[1
Jonathan Nieder a écrit :
Does unloading (modprobe -r) the e1000e driver before
hibernating help?
No. It does not make any noticeable difference.
--
Denis
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Jonathan Nieder a écrit :
Now that I look more closely, I suspect the dmesg you attached is from
trying to resume after an unsuccessful hibernation. What would be
most useful is to get as much information as possible somehow from the
_unsuccessful_ hibernation, or even better, to trigger a
Jonathan Nieder a écrit :
Then
the machine halted or rebooted (depending on the mode) normally but I'm
not sure what was supposed to happen here. (I mean, I did not expect to
get back to the init shell I was on, since I left the grub cmd line
untouched upon restart...)
It was
Hi,
Le lundi 12 avril 2010 à 01:18 +0100, Ben Hutchings a écrit :
On Sun, 2010-04-11 at 18:23 -0400, Denis Laxalde wrote:
forwarded 575924 https://bugzilla.kernel.org/show_bug.cgi?id=14347
thanks
On Sun, 11 Apr 2010 16:05:57 +0100, Ben Hutchings wrote:
On Sat, 2010-04-10 at 23:05
forwarded 575924 https://bugzilla.kernel.org/show_bug.cgi?id=14347
thanks
On Sun, 11 Apr 2010 16:05:57 +0100, Ben Hutchings wrote:
On Sat, 2010-04-10 at 23:05 -0400, Denis Laxalde wrote:
Hi,
On Sun, 11 Apr 2010 00:28:24 +0100, Ben Hutchings wrote:
The more serious error messages
Hi,
On Sun, 11 Apr 2010 00:28:24 +0100, Ben Hutchings wrote:
The more serious error messages suggest memory corruption. Have you
tested the RAM with memtest86+ yet?
Yes, I've just run a pretty long test with memtest86+ and there was no
error reported.
Denis
--
To UNSUBSCRIBE, email to
Hi,
On Sat, 03 Apr 2010 02:54:01 +0100, Ben Hutchings wrote:
On Tue, 2010-03-30 at 11:40 -0400, Denis Laxalde wrote:
Package: linux-2.6
Version: 2.6.32-10
Severity: important
Boot fails from time to time. A relevant dmesg is attached.
Please let me know if you need more info.
I
Hi,
The upstream report finally lead to a solution. It seems that nvidia
module still rely on /proc/acpi/event to catch acpi events. Since
Debian disabled the deprecated option CONFIG_ACPI_PROC_EVENT, the file
does not exist anymore.
A simple workaround is then to rebuild the kernel with this
Hi,
On Tue, 16 Feb 2010 17:45:01 +0100, maximilian attems wrote:
On Sat, 13 Feb 2010, Denis Laxalde wrote:
It was with package linux-image-2.6.32-trunk-686 (on which
linux-image-2.6-686 still depends).
I just tried with linux-image-2.6.32-2-686 (i.e. 2.6.32-8) and
display switch
Hi,
Le 13 février 2010 à 13:31 +0100, maximilian attems a écrit :
On Tue, 18 Aug 2009, Sjoerd Hardeman wrote:
I have the same situation with a amd64 kernel. After coming back
from holiday and installing the new kernel, I lost the fn-f8 screen
switch thingy.
Sjoerd
please give
Le 13 février 2010 à 19:55 +0100, maximilian attems a écrit :
On Sat, Feb 13, 2010 at 01:08:58PM -0500, Denis Laxalde wrote:
Hi,
please give feedback on 2.6.32, sorry for late reply.
thanks for followup.
This still does not work with 2.6.32.
Let me know if you need more
Package: linux-image-686
Version: 2.6.30+20
Severity: normal
Hi,
I have a Dell Latitude D620 with a Nvidia graphic card GeForce Go 7300
and nvidia drivers (version 185) built using module-assistant.
Since version 2.6.29 (and now 2.6.30) the display switch key
combination (Fn+F8) stopped working
14 matches
Mail list logo
