On 26.11.2011 14:30, Jonathan Nieder wrote:
hu...@online.de wrote:
Loading all other modules except radeon works fine, loading radeon causes a
system hangup on suspend to disk.
Loading the radeon module also gives the following error messages:
[ 270.715016] radeon_cp: Failed to load firmware
On 25.11.2011 21:49, Jonathan Nieder wrote:
hu...@online.de wrote:
When entering swapon -a the message swapon: /etc/fstab : No such file or
directory was shown, so I used swapon /dev/sda5 instead.
Thanks.
Unfortunately I was not able to identify the culprit , after loading all
modules step
On 24.11.2011 21:02, Jonathan Nieder wrote:
hu...@online.de wrote:
So the problem module should be one of the remaining 60 modules attached as
lsmod21.txt .
But now I do not know how to unload them cause I always get the message
module is in use - even when system is started in recovery mode
Hi,
after a system upgrade to the current state of Debian Testing - which
included an upgrade
of the linux-image-2.6.32-5-amd64 package to the version 2.6.32.28 - a
kernel failure occured.
The failure message has been sent to kerneloops.com and is also shown below.
Don't know if this has to
The problem not exists in the one and only 2.6.31 kernel
linux-image-2.6.31-1-amd64_2.6.31-1_amd64.deb
and comes up in the first 2.6.32 kernel
linux-image-2.6.32-1-amd64_2.6.32-6_amd64.deb .
I have also filed a bug report to bugzilla.kernel.org, bug id is 22022 .
Thanks and regards
The problem also exists with linux-image-2.6.36-rc6-amd64 and
xserver.xorg 7.5+8 .
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cd11e53.8070...@online.de
As expected, the problem also exists with linux-image-2.6.36-trunk-amd64 .
But before putting something into bugzilla I'd like to tell you about
another
interesting detection I made now during testing:
For 6 times in follow the system showed the following absolute constant
behavior:
After
Sometimes there existed different additional processes like these after
the first Suspend-To-RAM, but the result was the same: hanging second
Suspend-To-RAM
root 2932 2 0 11:33 ?00:00:00 [kworker/u:1]
root 2933 2 0 11:33 ?00:00:00 [kworker/u:2]
root 2934
I downloaded three versions of the 2.6.30 kernel from snapshot.debian.org
and installed them on my notebook - without doing any other changes to
the system.
And the Suspend-To-RAM of all of the three 2.6.30 kernels worked
perfectly well !
So from my point of view the problem started
The problem also exists in 2.6.32-27 version of
linux-image-2.6.32-5-amd64 package.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cd01f8a.7040...@online.de
I remember another item:
At the time when the Suspend-To-RAM worked fine the login window always
occurred in front
of an empty clean black background.
But now the background behind the login window has a strange colored
look and seems to be
a shattered and unrecognizable picture - maybe taken
What I forgot to mention:
I tried the new Kubuntu 10.10 with kernel 2.6.35 and the bug there also
exists.
Immediately after the installation without any configuration I tried the
Suspend-To-RAM
5 times and it seemed to work fine.
After doing some configurations (e.g. mounting two additional
What I also forgot and remember now:
After installing and configuring Kubuntu 10.10, later on I did also a
small system update where roundabout 20 packages were replaced
by newer versions - and one of them was the linux kernel.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
13 matches
Mail list logo
