Bug 105414 - udevstart from udev-068 triggers a kernel panic
|
Bug#:
105414
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: HPPA
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: critical
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: hppa@gentoo.org
|
Reported By: jer@gentoo.org
|
|
Component: Core system
|
|
|
URL:
|
|
Summary: udevstart from udev-068 triggers a kernel panic
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2005-09-09 11:39 0000
|
After merging sys-fs/udev-068, running udevstart on a B160L during the same
'boot session' caused a kernel panic ("not syncing") without any other error
mentioned.
A reboot did not help at all, probably for the same reason (udevstart causing a
kernel panic), this time while init was minding the contents of /dev.
A reboot with the gentoo=nodevfs did give some warnings, but at least allowed me
to safely remerge udev-058. The problem didn't occur again after that, and
running udevstart 'manually' didn't give any problems with 058.
Reproducible: Always
Steps to Reproduce:
1. Upgrade to (oddly marked stable for HPPA) sys-fs/udev-068.
2. Reboot or run udevstart.
Actual Results:
Panic!
Expected Results:
No panic.
Gentoo Base System version 1.6.13
Portage 2.0.52-r1 (default-linux/hppa/2005.0, gcc-3.3.5, glibc-2.3.4.20040808-
r1, 2.6.12.4-pa2-JeR parisc)
=================================================================
System uname: 2.6.12.4-pa2-JeR parisc PA7300LC (PCX-L2)
ccache version 2.3 [disabled]
dev-lang/python: 2.2.3-r6, 2.3.5
sys-apps/sandbox: 1.2.12
sys-devel/autoconf: 2.13, 2.59-r6
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6
sys-devel/binutils: 2.15.92.0.2-r10
sys-devel/libtool: 1.5.18-r1
virtual/os-headers: 2.6.11-r2
ACCEPT_KEYWORDS="hppa"
AUTOCLEAN="yes"
CBUILD="hppa1.1-unknown-linux-gnu"
CFLAGS="-O3 -pipe -mschedule=7100LC -march=1.1"
CHOST="hppa1.1-unknown-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/
config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/ssh /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -pipe -mschedule=7100LC -march=1.1"
DISTDIR="/keeps/gentoo/portage/distfiles"
FEATURES="autoconfig confcache distlocks notitles parallel-fetch sandbox sfperms
strict"
GENTOO_MIRRORS="http://ftp.easynet.nl/mirror/gentoo/ http://ftp.snt.utwente.nl/
pub/os/linux/gentoo ftp://mirror.scarlet-internet.nl/pub/gentoo ftp://mirror.
nutsmaas.nl/gentoo/"
LC_ALL="en_US.UTF-8"
MAKEOPTS="-j2"
PKGDIR="/keeps/gentoo/packages-hpvis"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/keeps/gentoo/portage"
PORTDIR_OVERLAY="/keeps/gentoo/local"
SYNC="rsync://10.0.0.153/gentoo-portage"
USE="hppa aalib apache2 bash-completion berkdb bitmap-fonts c++ crypt cups curl
elf esd fam fbcon foomaticdb fortran gd gdbm gimpprint gpm imagemagick imlib
ipv6 jpeg libwww mad mikmod ncurses nls offensive ogg pam pdflib perl pic png
python readline snmp spell ssl svg tcpd threads tiff truetype truetype-fonts
type1-fonts unicode userlocales vorbis xml2 zlib userland_GNU kernel_linux
elibc_glibc"
Unset: ASFLAGS, CTARGET, LANG, LDFLAGS, LINGUAS
can you try a few diff kernels to see if any work ?
(In reply to comment #1)
> can you try a few diff kernels to see if any work ?
I'll try hppa-sources-2.6.13_p1 (~hppa) as it is newer than my current (very
stable) 2.6.12.4-pa2 (hppa).
hppa-sources-2.6.13_p1 went exactly the same: doing 'udevstart' caused a kernel
panic, and rebooting caused a kernel panic. Then rebooting with gentoo=noudev
(as earlier -- consider this a correction of my earlier report of using
gentoo=nodevfs) brought the system up properly.
(In reply to comment #3)
> Then rebooting with gentoo=noudev
> (as earlier -- consider this a correction of my earlier report of using
> gentoo=nodevfs) brought the system up properly.
Addendum: Then running udevstart again does *not* trigger a kernel panic.
Created an attachment (id=70436) [details]
What netconsole managed to send...
This dmesg log (if you will) was triggered after an upgrade to
sys-fs/udev-068-r1 (current stable for hppa) by a subsequent run of
'udevstart'.
This is caused by "vol_id --export /dev/.tmp-43-0" which udevstart uses to
populate /dev. When it reads the block device 43 0, there is a kernel panic.
If you set CONFIG_BLK_DEV_NBD=n, the problem goes away.
This is then a kernel problem. I'll forward this issue to pa kernel guys.