On 11/07/12 00:12, Jonathan Nieder wrote:
Eugen Dedu wrote:
No problem for me, I am glad that it works on 3.4! So if you
prefer, you can close this bug.
I'd rather get it fixed in 3.2.y since we will be maintaining that for
a while. Would you be interested in pursuing that (by testing it
On 10/07/12 05:33, Jonathan Nieder wrote:
Eugen Dedu wrote:
First, note that I have indeed a problem with the battery, since the
icon of gnome is not working properly: it shows an empty battery,
whice it is fully loaded, or viceversa.
Is this more reproducible than the resume failures?
On 10/07/12 05:31, Jonathan Nieder wrote:
Eugen Dedu wrote:
Making a git bissect inside these versions will take me ages,
especially that the freeze is not easily reproducible and it is
difficult during a test to be sure that the freeze does NOT appear.
Fair enough. When's the last time it
Eugen Dedu wrote:
No problem for me, I am glad that it works on 3.4! So if you
prefer, you can close this bug.
I'd rather get it fixed in 3.2.y since we will be maintaining that for
a while. Would you be interested in pursuing that (by testing it and
contacting upstream and cc-ing us when it
clone 677016 -1
retitle -1 Dell Latitude E6500: battery charging state is inaccurate
# cosmetic
severity -1 minor
quit
Eugen Dedu wrote:
This is 100% reproducible. For ex., right now I have 2 horizontal
lines instead of 3, and my battery is 87% charged. Moreover, it is
charging, but the
On 07/07/12 07:54, Jonathan Nieder wrote:
Eugen Dedu wrote:
On 07/07/12 04:49, Jonathan Nieder wrote:
Does that mean 2.6.38 works fine? (If you'd like to test this,
historical precompiled kernels are available from
http://snapshot.debian.org/, source package linux-2.6.)
I think that it
Eugen Dedu wrote:
Making a git bissect inside these versions will take me ages,
especially that the freeze is not easily reproducible and it is
difficult during a test to be sure that the freeze does NOT appear.
Fair enough. When's the last time it happened? Is the error always
Eugen Dedu wrote:
First, note that I have indeed a problem with the battery, since the
icon of gnome is not working properly: it shows an empty battery,
whice it is fully loaded, or viceversa.
Is this more reproducible than the resume failures?
--
To UNSUBSCRIBE, email to
On 22/06/12 19:27, Eugen Dedu wrote:
On 22/06/12 19:10, Jonathan Nieder wrote:
Eugen Dedu wrote:
On 22/06/12 18:29, Jonathan Nieder wrote:
But I suspect this is an ACPI support bug elsewhere (effect of lid
switch). Can you easily reproduce it by opening and closing the lid
a bunch of times?
Hi,
Eugen Dedu wrote:
In fact, I have been having freezes at suspend since 3.0 or 2.6.39,
while before suspend was working perfectly.
Does that mean 2.6.38 works fine? (If you'd like to test this,
historical precompiled kernels are available from
http://snapshot.debian.org/, source package
On 07/07/12 04:49, Jonathan Nieder wrote:
Hi,
Eugen Dedu wrote:
In fact, I have been having freezes at suspend since 3.0 or 2.6.39,
while before suspend was working perfectly.
Does that mean 2.6.38 works fine? (If you'd like to test this,
historical precompiled kernels are available from
Eugen Dedu wrote:
On 07/07/12 04:49, Jonathan Nieder wrote:
Does that mean 2.6.38 works fine? (If you'd like to test this,
historical precompiled kernels are available from
http://snapshot.debian.org/, source package linux-2.6.)
I think that it worked fine. Do you want me to test it?
I
On 12/06/12 06:02, Jonathan Nieder wrote:
Eugen Dedu wrote:
Here it is: another freeze during resume, with kernel 3.3 too.
Thanks for the quick feedback. (As a reminder to myself, the message
is
BUG: unable to handle kernel paging request at fff(lens flare)
IP:
Eugen Dedu wrote:
# echo reboot /sys/power/disk
# echo disk /sys/power/state
[screen got black for ~2 secs, it shows Cannot find swap device,
try swapon -a.\nCannot get swap writer - which is normal since I do
not have one - and afterwards comes back]
bash: echo: write error: No such
On 22/06/12 17:42, Jonathan Nieder wrote:
Eugen Dedu wrote:
# echo reboot /sys/power/disk
# echo disk /sys/power/state
[screen got black for ~2 secs, it shows Cannot find swap device,
try swapon -a.\nCannot get swap writer - which is normal since I do
not have one - and afterwards comes
Eugen Dedu wrote:
On 22/06/12 17:42, Jonathan Nieder wrote:
Hm. What tool do you normally use to suspend to RAM?
Just closing the monitor lid on the laptop.
If you explicitly run pm-suspend, does it produce the same bad
behavior?
--
To UNSUBSCRIBE, email to
On 22/06/12 17:48, Jonathan Nieder wrote:
Eugen Dedu wrote:
On 22/06/12 17:42, Jonathan Nieder wrote:
Hm. What tool do you normally use to suspend to RAM?
Just closing the monitor lid on the laptop.
If you explicitly run pm-suspend, does it produce the same bad
behavior?
Just tested
On 22/06/12 18:29, Jonathan Nieder wrote:
Eugen Dedu wrote:
As I said in the first e-mail, the freeze appears each 1-20 suspend
actions. I wonder if I am not unlucky during these tests.
That's possible. The only way I would know to test is to make a
habit of using pm-suspend instead of
Eugen Dedu wrote:
On 22/06/12 18:29, Jonathan Nieder wrote:
But I suspect this is an ACPI support bug elsewhere (effect of lid
switch). Can you easily reproduce it by opening and closing the lid
a bunch of times?
Well, closing and reopening for about 20 times does not trigger the
bug.
On 22/06/12 19:10, Jonathan Nieder wrote:
Eugen Dedu wrote:
On 22/06/12 18:29, Jonathan Nieder wrote:
But I suspect this is an ACPI support bug elsewhere (effect of lid
switch). Can you easily reproduce it by opening and closing the lid
a bunch of times?
Well, closing and reopening for
Eugen Dedu wrote:
Here it is: another freeze during resume, with kernel 3.3 too.
Thanks for the quick feedback. (As a reminder to myself, the message
is
BUG: unable to handle kernel paging request at fff(lens flare)
IP: [810514c7] kthread_data+0x7/0xc
PGD
Hi,
Eugen Dedu wrote:
Very often (each 2-10 times) kernel freezes with an error message upon
resuming from suspend to ram. Here is the message:
kobject_add_internal failed for BATO with -EEXIST, don't try to
register things with the same name in the same directory
Please attach a log or
On 11/06/12 13:31, Jonathan Nieder wrote:
Hi,
Eugen Dedu wrote:
Very often (each 2-10 times) kernel freezes with an error message upon
resuming from suspend to ram. Here is the message:
kobject_add_internal failed for BATO with -EEXIST, don't try to
register things with the same name in the
23 matches
Mail list logo