Package: initramfs-tools
Version: 0.92k
Severity: critical
Justification: breaks the whole system

PowerPC (G4 Macintosh) running sid.
Ran nightly dist-upgrade which updated initramfs-tools.
Now the system crashes with a kernel oops.

I restored the old initrd.img...bak and it now boots OK.

curiously, after gunzip-ing and un-cpio-ing the two initrd.img files,
the only difference is:

greybox:/tmp# diff -r initrd initrd.BAD/
diff -r initrd/conf/initramfs.conf initrd.BAD/conf/initramfs.conf
7,8d6
< # In particular, Debian installer may set MODULES in the file
< # /etc/initramfs-tools/conf.d/driver-policy.
greybox:/tmp#

/var/log/syslog.0 attached (contains the kernel Oops and surrounding stuff)


-- Package-specific info:
-- /proc/cmdline
root=/dev/hda6 ro

-- /proc/filesystems
ext3

-- lsmod
Module Size Used by
radeon 148104 2
drm 79840 3 radeon
rfcomm 38996 2
l2cap 22820 9 rfcomm
bluetooth 58228 4 rfcomm,l2cap
lp 13388 0
parport 40176 1 lp
cpufreq_userspace 6776 0
cpufreq_stats 7908 0
cpufreq_powersave 5280 0
cpufreq_ondemand 10624 0
cpufreq_conservative 10144 0
ipv6 287784 28
dm_snapshot 21344 0
dm_mirror 20640 0
dm_log 13792 1 dm_mirror
dm_mod 60524 3 dm_snapshot,dm_mirror,dm_log
sr_mod 19620 0
snd_powermac 47772 1
sbp2 23116 0
snd_aoa_i2sbus 22820 0
snd_pcm_oss 45248 0
snd_pcm 79876 3 snd_powermac,snd_aoa_i2sbus,snd_pcm_oss
snd_page_alloc 12392 1 snd_pcm
snd_mixer_oss 19360 1 snd_pcm_oss
snd_seq_oss 36756 0
snd_seq_midi 10240 0
snd_rawmidi 26272 1 snd_seq_midi
snd_seq_midi_event 10528 2 snd_seq_oss,snd_seq_midi
snd_seq 57800 5 snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 25508 2 snd_pcm,snd_seq
snd_seq_device 11020 4 snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd 61908 12 snd_powermac,snd_aoa_i2sbus,snd_pcm_oss,snd_pcm,sn d_mixer_oss,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
soundcore 10244 1 snd
snd_aoa_soundbus 9060 1 snd_aoa_i2sbus
uninorth_agp 12008 1
agpgart 37884 2 drm,uninorth_agp
evdev 13728 3
ext3 133704 6
jbd 49204 1 ext3
mbcache 11296 1 ext3
raid1 25600 1
md_mod 88308 2 raid1
sd_mod 28656 4
usbhid 48196 0
hid 45256 1 usbhid
ff_memless 8520 1 usbhid
ide_cd_mod 35812 0
ide_floppy 18784 0
cdrom 40216 2 sr_mod,ide_cd_mod
ide_disk 16448 8
ohci1394 35888 0
sata_sil 11656 2
ieee1394 91584 2 sbp2,ohci1394
libata 160872 1 sata_sil
sungem 32772 0
sungem_phy 14848 1 sungem
scsi_mod 153836 4 sr_mod,sbp2,sd_mod,libata
3c59x 42280 0
i2c_powermac 7552 0

-- /etc/kernel-img.conf
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = yes

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
BOOT=local
DEVICE=eth0
NFSROOT=auto


-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.26-1-powerpc
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages initramfs-tools depends on:
ii cpio 2.9-13 GNU cpio -- a program to manage ar
ii findutils 4.4.0-2 utilities for finding files--find,
ii klibc-utils 1.5.12-2 small utilities built with klibc f
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
ii udev 0.125-6 /dev/ and hotplug management daemo

Versions of packages initramfs-tools recommends:
ii busybox 1:1.10.2-2 Tiny utilities for small and embed

initramfs-tools suggests no packages.

-- no debconf information

severity 499231 normal
tags 499231 moreinfo
stop

On Wed, Sep 17, 2008 at 02:38:04AM -0400, Rick Thomas wrote:
> PowerPC (G4 Macintosh) running sid.
> Ran nightly dist-upgrade which updated initramfs-tools.
> Now the system crashes with a kernel oops.
>
> I restored the old initrd.img...bak and it now boots OK.
>
> curiously, after gunzip-ing and un-cpio-ing the two initrd.img files,
> the only difference is:
>
> greybox:/tmp# diff -r initrd initrd.BAD/
> diff -r initrd/conf/initramfs.conf initrd.BAD/conf/initramfs.conf
> 7,8d6
> < # In particular, Debian installer may set MODULES in the file
> < # /etc/initramfs-tools/conf.d/driver-policy.
> greybox:/tmp#
>
> /var/log/syslog.0 attached (contains the kernel Oops and surrounding stuff)

not attached and aboves change cannot lead to unbootable state,
try to reproduce.

thanks

--
maks



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sep 17, 2008, at 3:31 AM, maximilian attems wrote:


severity 499231 normal
tags 499231 moreinfo
stop

On Wed, Sep 17, 2008 at 02:38:04AM -0400, Rick Thomas wrote:

PowerPC (G4 Macintosh) running sid.
Ran nightly dist-upgrade which updated initramfs-tools.
Now the system crashes with a kernel oops.

I restored the old initrd.img...bak and it now boots OK.

curiously, after gunzip-ing and un-cpio-ing the two initrd.img files,
the only difference is:

greybox:/tmp# diff -r initrd initrd.BAD/
diff -r initrd/conf/initramfs.conf initrd.BAD/conf/initramfs.conf
7,8d6
< # In particular, Debian installer may set MODULES in the file
< # /etc/initramfs-tools/conf.d/driver-policy.
greybox:/tmp#

/var/log/syslog.0 attached (contains the kernel Oops and
surrounding stuff)


not attached and aboves change cannot lead to unbootable state,
try to reproduce.

thanks

--
maks



Ummmm. It was attached. It's definitely there on the CC I sent to
myself. But here it is again.


I know those changes can't cause an unbootable state. That's why I
said "curiously". It's definitely reproducable. If I put the bad
initrd.img back, it dies during the boot sequence repeatably. I have
another system running Sid. I haven't done a dist-upgrade on it
yet. So I'll see what happens there.


For what it's worth, I'm also attaching the dpkg.log file that show
what got updated in the fatal dist-upgrade.

Here are two extracts of the syslog file one (failed) of a boot that
fails using the bad initrd.img, one (succed) of a boot that succeeds
using the good initrd.img.


I've stripped out the date/times and process-ids to make them diff-
able. The diff is interesting.


Rick

On Sep 17, 2008, at 4:02 AM, Rick Thomas wrote:

I have another system running Sid. I haven't done a dist-upgrade
on it yet. So I'll see what happens there.



I did the dist-upgrade on my other G4 running Sid, and the oops
doesn't happen.


Looking at the syslog extracts, it seems that the failing machine
oops-es when it's trying to initialize its Radeon video driver. The
machine that doesn't oops has an ATI Rage video card. The traceback
also mentions radeon. So that's probably where the problem lies.


Do others with Radeon cards have this problem?

Here's the relevant part of "lspci -v" for each of the machines,
incase it's useful:



0000:00:10.0 VGA compatible controller: ATI Technologies Inc Radeon
RV200 QW [Radeon 7500]

Subsystem: ATI Technologies Inc Radeon RV200 QW [Radeon 7500]
Flags: bus master, stepping, 66MHz, medium devsel, latency
255, IRQ 48

Memory at 98000000 (32-bit, prefetchable) [size=128M]
I/O ports at 0400 [size=256]
Memory at 90000000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at f1000000 [size=128K]
Capabilities: [58] AGP version 2.0
Capabilities: [50] Power Management version 2
Kernel driver in use: radeonfb


0000:00:10.0 VGA compatible controller: ATI Technologies Inc Rage 128
PF/PRO AGP 4x TMDS

Flags: bus master, stepping, 66MHz, medium devsel, latency 255, IRQ 48
Memory at 94000000 (32-bit, prefetchable) [size=64M]
I/O ports at 0400 [size=256]
Memory at 90000000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at f1000000 [disabled] [size=128K]
Capabilities: [50] AGP version 2.0
Capabilities: [5c] Power Management version 2
Kernel driver in use: aty128fb


Any help will be appreciated...

Rick



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org