Bug#677016: resume failure: kobject_add_internal failed for BAT0 with -EEXIST

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 testi

Bug#677016: resume failure: kobject_add_internal failed for BAT0 with -EEXIST

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 ti

Bug#677016: resume failure: kobject_add_internal failed for BAT0 with -EEXIST

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

Bug#677016: resume failure: kobject_add_internal failed for BAT0 with -EEXIST

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 th

Bug#677016: resume failure: kobject_add_internal failed for BAT0 with -EEXIST

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

Bug#677016: resume failure: kobject_add_internal failed for BAT0 with -EEXIST

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

Bug#677016: resume failure: kobject_add_internal failed for BAT0 with -EEXIST

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

Bug#677016: resume failure: kobject_add_internal failed for BAT0 with -EEXIST

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&q

Bug#677016: resume failure: kobject_add_internal failed for BAT0 with -EEXIST

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? J

Bug#677016: resume failure: kobject_add_internal failed for BAT0 with -EEXIST

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

Bug#677016: resume failure: kobject_add_internal failed for BAT0 with -EEXIST

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

Bug#677016: resume failure: kobject_add_internal failed for BAT0 with -EEXIST

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 i

Bug#677016: linux-image-3.3.0-trunk-amd64: Freeze with error message upon resume

efore suspend was working perfectly. Thank you, Eugen Dedu http://eugen.dedu.free.fr -- Package-specific info: ** Version: Linux version 3.3.0-trunk-amd64 (Debian 3.3.6-1~experimental.1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Fri May 18 14:52:13 UTC

Bug#613909: Suggests grub instead of grub-pc

Package: linux-image-2.6.37-1-amd64 Version: 2.6.37-1 Severity: minor This package suggests grub instead of grub-pc. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) -- To UNSUBSCRIBE, email to debian-kernel-

Bug#572283: linux-image-2.6.33-2-amd64: Installation error

severity 572283 normal thanks Ben Hutchings wrote: > On Wed, 2010-03-03 at 01:30 +0100, Eugen Dedu wrote: >> severity 572283 critical >> thanks >> >> Ben Hutchings wrote: >>> On Wed, 2010-03-03 at 01:15 +0100, Eugen Dedu wrote: >>> [...] >>

Bug#572283: linux-image-2.6.33-2-amd64: Installation error

severity 572283 critical thanks Ben Hutchings wrote: > On Wed, 2010-03-03 at 01:15 +0100, Eugen Dedu wrote: > [...] >> Thanks for the fast help. >> >> I have just executed 'dpkg -P linux-base'. So it is now safe to reboot >> computer (after having issued

Bug#572283: linux-image-2.6.33-2-amd64: Installation error

Ben Hutchings wrote: > On Tue, Mar 02, 2010 at 11:16:43PM +0100, Eugen Dedu wrote: >> Subject: linux-image-2.6.33-2-amd64: Installation error >> Package: linux-2.6 >> Version: 2.6.33-1~experimental.2 >> Severity: normal > > Thanks for testing! > >> *

Bug#572283: linux-image-2.6.33-2-amd64: Installation error

Subject: linux-image-2.6.33-2-amd64: Installation error Package: linux-2.6 Version: 2.6.33-1~experimental.2 Severity: normal *** Please type your report below this line *** I use 2.6.32. When installing 2.6.33 I receive (I really hope that the system will be usable after that, since it modified s

Bug#518425: linux-image-2.6.28-1-amd64: Boot failure on MacBook Pro

Subject: linux-image-2.6.28-1-amd64: Boot failure on MacBook Pro Package: linux-image-2.6.28-1-amd64 Version: 2.6.28-1 Severity: grave Justification: renders package unusable 2.6.28-1 stops at: [...] [0.3...] RAMDISK: Couldn't find valid Ram disk image starting at 0 List of all partitions: No fil

Bug#517193: linux-image-2.6.28-1-amd64 fails to boot on amd64

Ben Hutchings wrote: Can you confirm whether this boot failure matches the bug filed upstream as ? That bug has not yet been fixed in a stable release but is believed to be fixed in Linux 2.6.29. For me, it's not the same bug. It stops at: [..

Bug#509927: closed by Bastian Blank (Re: Bug#509927: linux-2.6: Package new release)

: Bastian Blank Date: Sun, 28 Dec 2008 11:42:48 +0100 To: 509927-d...@bugs.debian.org To: 509927-d...@bugs.debian.org On Sat, Dec 27, 2008 at 08:28:39PM +0100, Eugen Dedu wrote: Any plan to package 2.6.27 or .28? Personally, I need it for ath9k and newer ath5k (two laptops). Yes. They will be

Bug#509927: linux-2.6: Package new release

Subject: linux-2.6: Package new release Package: linux-2.6 Severity: wishlist *** Please type your report below this line *** Hi, Any plan to package 2.6.27 or .28? Personally, I need it for ath9k and newer ath5k (two laptops). Cheers, Eugen -- System Information: Debian Release: 5.0 APT p

Bug#479101: Bug#479607: With lilo 22.8-5 still can't boot on macbookpro

MB: -rw-r--r-- 1 root root 6998498 2008-05-16 10:11 initrd.img-2.6.25-2-amd64 I put a few days ago this image as the default one and run lilo: no warning was issued about the size, still rebooting the computer does not work. So I reopen this bug. Cheers, -- Eugen Dedu -- To UNSUBSCRIB

Bug#479101: linux-image-2.6.25-1-amd64: Kernel panic: Unable to mount root

maximilian attems wrote: On Sat, May 03, 2008 at 11:45:42PM +0200, Eugen Dedu wrote: I typed Linux break=X at boot prompt, with X=mount, premount, modules and top. In all the cases, it does NOT stop before the panic. I do not have any console. just quickly online, maybe you posted it

Bug#479101: linux-image-2.6.25-1-amd64: Kernel panic: Unable to mount root

maximilian attems wrote: On Sat, May 03, 2008 at 11:45:42PM +0200, Eugen Dedu wrote: I typed Linux break=X at boot prompt, with X=mount, premount, modules and top. In all the cases, it does NOT stop before the panic. I do not have any console. just quickly online, maybe you posted it

Bug#479101: linux-image-2.6.25-1-amd64: Kernel panic: Unable to mount root

maximilian attems wrote: On Sat, May 03, 2008 at 11:54:35AM +0200, Eugen Dedu wrote: maximilian attems wrote: On Sat, May 03, 2008 at 10:01:20AM +0200, Eugen Dedu wrote: maximilian attems wrote: On Fri, May 02, 2008 at 09:03:28PM +0200, Eugen Dedu wrote: Subject: linux-image-2.6.25-1-amd64

Bug#479101: linux-image-2.6.25-1-amd64: Kernel panic: Unable to mount root

maximilian attems wrote: On Sat, May 03, 2008 at 10:01:20AM +0200, Eugen Dedu wrote: maximilian attems wrote: On Fri, May 02, 2008 at 09:03:28PM +0200, Eugen Dedu wrote: Subject: linux-image-2.6.25-1-amd64: Kernel panic: Unable to mount root Package: linux-image-2.6.25-1-amd64 Version: 2.6.25

Bug#479101: linux-image-2.6.25-1-amd64: Kernel panic: Unable to mount root

maximilian attems wrote: On Fri, May 02, 2008 at 09:03:28PM +0200, Eugen Dedu wrote: Subject: linux-image-2.6.25-1-amd64: Kernel panic: Unable to mount root Package: linux-image-2.6.25-1-amd64 Version: 2.6.25-1 Severity: normal *** Please type your report below this line *** Hi, The new

Bug#479101: linux-image-2.6.25-1-amd64: Kernel panic: Unable to mount root

ernel/drivers/virtio/virtio.ko ./lib/modules/2.6.25-1-amd64/kernel/drivers/parport ./lib/modules/2.6.25-1-amd64/kernel/drivers/parport/parport.ko ./lib/libsplashycnf.so.1 I have reiserfs. I have reiserfs. Best regards, Eugen Dedu -- Package-specific info: -- System Information: Debian Rele

Bug#451085: linux-image-2.6.22-3-amd64: Does not boot

maximilian attems wrote: tags 451085 moreinfo severity 451085 normal stop On Tue, Nov 13, 2007 at 09:50:23AM +0100, Eugen Dedu wrote: Hi, The new linux-image-2.6.22-3-amd64 (2.6.22-6) does not boot on my system, it stops after "Booting linux..[ENTER]". Best regards, Eugen Ded

Bug#451085: linux-image-2.6.22-3-amd64: Does not boot

Package: linux-image-2.6.22-3-amd64 Version: 2.6.22-6 Severity: critical Justification: breaks the whole system Hi, The new linux-image-2.6.22-3-amd64 (2.6.22-6) does not boot on my system, it stops after "Booting linux..[ENTER]". Best regards, Eugen Dedu -- Package-specific info:

Bug#305557: We believe this is fixed in 2.6.15-2. ...

Sven Luther wrote: tags 305557 + moreinfo thanks Hi, ... It would be nice if you could confirm this bug is still present in 2.6.15-2 or not. Friendly, Sven Luther It still exists with 2.6.15-2. Steps to reproduce: After booting: snoopy:~$ iwconfig eth2 eth2 IEEE 802.11-DS ESSID:"U

Bug#305557: kernel-image-2.6.11-powerpc: Resumes does not restore the previous essid of wireless card.

Package: kernel-image-2.6.11-powerpc Version: 2.6.11-1 Severity: normal *** Please type your report below this line *** I use a CardBus wireless card (Cisco 350 Series). After resumes (from sleeping) the network card is connected to an essid called "tsunami". This essid is non existent at my home

Bug#267029: kernel-image-2.6.8-powerpc: Invalid link in /lib/modules/2.6.8-powerpc/

Sven Luther wrote: On Fri, Aug 20, 2004 at 12:07:57PM +0200, Eugen Dedu wrote: Package: kernel-image-2.6.8-powerpc Version: 2.6.8-1 Severity: minor /lib/modules/2.6.8-powerpc/ contains a invalid symbolic link source to /home/hch/kernel-patch-powerpc-2.6.8/tmp/kernel-source-2.6.8-powerpc This is

Bug#267029: kernel-image-2.6.8-powerpc: Invalid link in /lib/modules/2.6.8-powerpc/

Package: kernel-image-2.6.8-powerpc Version: 2.6.8-1 Severity: minor /lib/modules/2.6.8-powerpc/ contains a invalid symbolic link source to /home/hch/kernel-patch-powerpc-2.6.8/tmp/kernel-source-2.6.8-powerpc -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 't