Hotplugging a firewire (ieee1394) harddisk in my AMD64 system caused a kernel panic (in interrupt handler, no sync.) I was running gentoo-sources-2.6.12-r9 or 2.6.12-r10 at the time. Last logmessages before the crash: Nov 2 00:34:03 compare ieee1394: sbp2: Error logging into SBP-2 device - login timed-out Nov 2 00:34:03 compare sbp2: probe of 0050770e00071002-0 failed with error -16 Nov 2 00:34:03 compare ieee1394: unsolicited response packet received - no tlabel match Nov 2 00:34:03 compare scsi3 : SCSI emulation for IEEE-1394 SBP-2 Devices Nov 2 00:34:19 compare ieee1394: unsolicited response packet received - no tlabel match Nov 2 00:34:22 compare ieee1394: unsolicited response packet received - no tlabel match Nov 2 00:34:23 compare ieee1394: unsolicited response packet received - no tlabel match Nov 2 00:34:24 compare ieee1394: sbp2: Error logging into SBP-2 device - login timed-out Nov 2 00:34:24 compare sbp2: probe of 0050770e00071002-0 failed with error -16 Nov 2 00:34:25 compare ieee1394: unsolicited response packet received - no tlabel match Nov 2 00:34:25 compare scsi4 : SCSI emulation for IEEE-1394 SBP-2 Devices Nov 2 00:34:32 compare ieee1394: unsolicited response packet received - no tlabel match Nov 2 00:34:40 compare ieee1394: unsolicited response packet received - no tlabel match Hardware information: Motherboard: Gigabyte K8NNXP, NForce3-130 chipset FireWire controller: Texas Instruments TSB82AA2 IEEE-1394b Link Layer Controller (rev 01) emerge info: Portage 2.0.51.22-r3 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r2, 2.6.12-gentoo-r10 x86_64) ================================================================= System uname: 2.6.12-gentoo-r10 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5-r2, 2.4.2 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-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://ftp.snt.utwente.nl/pub/os/linux/gentoo ftp://194.117.143.71/mirrors/gentoo http://194.117.143.70" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X alsa ansi arts avi berkdb bitmap-fonts bonobo cdr clisp crypt cups curl doc dvd dvdr eds emboss encode esd fam flac foomaticdb fortran gcl gd gdbm gif gnome gpm gstreamer gtk gtk2 gtkhtml guile imagemagick imlib ipv6 java jpeg kde ldap libwww lm-sensors lzw lzw-tiff mad mikmod motif mozilla mp3 mpeg mysql ncurses nls ogg oggvorbis opengl pam pda pdflib perl png postgres python qt quicktime readline ruby samba sdl speex spell ssl tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts unicode usb userlocales vorbis xine xml xml2 xmms xpm xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS
Reopen if you are able to reproduce the problem with latest gentoo-sources/vanilla sources.
Please allow a few weeks till I get the 2.6.13 or 2.6.14 to boot into a working system.
Well, the 2.6.13 boot went better after installing some udev stuff and I couldn't reproduce the 2.6.12 kernel panic. The firewire harddisk doesn't want to become friends with Gentoo though. (lot's of syslogging, not recognised as harddisk.)
(In reply to comment #3) > Well, the 2.6.13 boot went better after installing some udev stuff and I > couldn't reproduce the 2.6.12 kernel panic. Closing then.
