Your message dated Tue, 02 May 2006 16:17:23 +0200 with message-id <445769F3.80903@aurel32.net> and subject line debian bug #354749 can be closed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: GNU Libc Maintainers <debian-glibc@lists.debian.org>
- Cc: fritsd@wanadoo.nl
- Subject: kernel panic with libc6-2.3.6-2
- From: Frits Daalmans <fritsd@wanadoo.nl>
- Date: Tue, 28 Feb 2006 18:21:16 +0100
- Message-id: <200602281821.17009.fritsd@wanadoo.nl>
Subject: kernel panic with libc6-2.3.6-2 Package: libc6 Version: 2.3.5-13 Severity: critical Justification: breaks the whole system Hello, Each week I try out the progress of Etch, and yesterday I upgraded libc6 (and libc6-amd64) from 2.3.5-13 to 2.3.6-2 * and continued working successfully with no problems* Today I boot my PC resulting in a kernel panic at boot (repeatedly, at the same location, reproducibly). Something about not being able to locate the root device. Since this is on a S-ATA disk on a MSI motherboard with nforce3 chipset that I had serious trouble with in the past (changing the names of its disks from hde5 <-> sda5 and back) I tried both booting with option root=/dev/sda5 and with root=/dev/hde5 to no avail. It took me quite a while to figure out what it was that broke the system. Kernel 2.6.15 failed to boot; in an older kernel 2.6.8 on the same hardware the system booted fine. downgrading libc6 from 2.3.6-2 to 2.3.5-13 solved the problem. I'm really sorry that I can't pinpoint the problem better... good luck!! Frits PS: I've also installed udev 0.084-5, hal 0.5.6-4 and dbus 0.60.5 in case that's of any help.. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-k7 Locale: LANG=nl_NL@euro, LC_CTYPE=nl_NL@euro (charmap=ISO-8859-15) -- no debconf information -- To UNSUBSCRIBE, email to debian-glibc-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
--- End Message ---
--- Begin Message ---
- To: Frits Daalmans <fritsd@wanadoo.nl>, 354749-done@bugs.debian.org
- Subject: Re: debian bug #354749 can be closed
- From: Aurelien Jarno <aurelien@aurel32.net>
- Date: Tue, 02 May 2006 16:17:23 +0200
- Message-id: <445769F3.80903@aurel32.net>
- In-reply-to: <200604301250.30343.fritsd@wanadoo.nl>
- References: <200604301250.30343.fritsd@wanadoo.nl>
Frits Daalmans a écrit :Hello Aurelien,In february I reported bug #354749, that upgrade of libc6 t o2.3.6 made my system unbootable;in the meantime this bug has been tagged unreproducible because I didn't write back. Update: you can close the bug; I am now running libc6 2.3.6-3 without anyOk, closing it with this mail. Aurelien -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' aurel32@debian.org | aurelien@aurel32.net `- people.debian.org/~aurel32 | www.aurel32.net
--- End Message ---