Hi Henrique, 2012/9/29 Henrique de Moraes Holschuh <h...@debian.org>: > On Fri, 28 Sep 2012, Lionel Gamay wrote: >> I followed you advice but I still get a similar error message, without >> any reference to udev: >> >> "Loading, please wait... >> /init: eval: line 1: array_intel_microcode=: not found >> /init: eval: line 1: array_intel_microcode=: not found >> PANIC: Circular dependancy. Exiting." > > I still wonder WTF is it thinking a variable assignment is a command name? > > Can you give me the output of "dpkg -s busybox", please? And maybe, just in > case, you should "apt-get --reinstall install busybox"...
I use indeed busybox-static but it has no impact on this problem. dpkg -s busybox-static Package: busybox-static Status: install ok installed Priority: extra Section: shells Installed-Size: 1571 Maintainer: Debian Install System Team <debian-b...@lists.debian.org> Architecture: i386 Source: busybox Version: 1:1.20.0-7 Replaces: busybox Conflicts: busybox Description: Standalone rescue shell with tons of builtin utilities BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides minimalist replacements for the most common utilities you would usually find on your desktop system (i.e., ls, cp, mv, mount, tar, etc.). The utilities in BusyBox generally have fewer options than their full-featured GNU cousins; however, the options that are included provide the expected functionality and behave very much like their GNU counterparts. . busybox-static provides you with a statically linked simple stand alone shell that provides all the utilities available in BusyBox. This package is intended to be used as a rescue shell, in the event that you screw up your system. Invoke "busybox sh" and you have a standalone shell ready to save your system from certain destruction. Invoke "busybox", and it will list the available builtin commands. Homepage: http://www.busybox.net > Anyway, please boot the kernel with the broken initramfs with the "debug" > command line parameter. You'll need to set it in the boot loader, add > "debug" to the end of the line with the kernel parameters. > > The nasty thing will be to get the debug file out of the broken system :-( > it is supposed to end up in /run/initramfs/* > > If you're good with shell scripts, maybe you'll find the error right away > :-) Otherwise, try to copy the last 30 or so lines before the PANIC error > message and send it to the bug report. Maybe I can figure it out from > there. here it is: --------------- + log_begin_msg Loading essential drivers + _log_msg Begin: Loading essential drivers ... + [ n = y ] + printf Begin: Loading essential drivers ... Begin: Loading essential drivers ... + load_modules + [ -e /conf/modules ] + cat /conf/modules + read m + [ -z microcode ] + printf %.1s microcode + com=m + [ m = # ] + modprobe microcode + read m + [ n != y ] + log_end_msg + _log_msg done.\n + [ n = y ] + printf done.\n done. + [ -n ] + maybe_break premount + [ = premount ] + [ n != y ] + log_begin_msg Running /scripts/init-premount + _log_msg Begin: Running /scripts/init-premount ... + [ n = y ] + printf Begin: Running /scripts/init-premount ... Begin: Running /scripts/init-premount ... + run_scripts /scripts/init-premount + initdir=/scripts/init-premount + [ ! -d /scripts/init-premount ] + [ -f /scripts/init-premount/ORDER ] + command -v tsort + get_prereqs + set_initlist + unset initlist + [ /scripts/init-premount/intel-microcode = /scripts/init-premount/* ] + [ ! -x /scripts/init-premount/intel-microcode ] + [ -d /scripts/init-premount/intel-microcode ] + sh -n /scripts/init-premount/intel-microcode + initlist= intel-microcode + /scripts/init-premount/intel-microcode prereqs + tmp=udev + eval array_intel-microcode="udev" + array_intel-microcode=udev /init: eval: line 1: array_intel-microcode=udev: not found + reduce_prereqs + unset runlist + set -- intel-microcode + i=1 + [ 1 -ne 0 ] + oldi=1 + reduce_satisfied intel-microcode + render array_intel-microcode + eval echo -n ${array_intel-microcode} + echo -n microcode + deplist=microcode + unset tmpdeplist + [ ! -x /scripts/init-premount/microcode ] + continue + deplist= + eval array_intel-microcode="" + array_intel-microcode= /init: eval: line 1: array_intel-microcode=: not found + render array_intel-microcode + eval echo -n ${array_intel-microcode} + echo -n microcode + count_unsatisfied microcode + set -- microcode + return 1 + cnt=1 + [ 1 -eq 0 ] + [ 1 -eq 1 ] + panic PANIC: Circular dependancy. Exiting. + command -v chvt + chvt 1 + echo PANIC: Circular dependancy. Exiting. PANIC: Circular dependancy. Exiting. + [ -n ] + modprobe -v i8042 + modprobe -v atkbd + modprobe -v ehci-hcd + modprobe -v uhci-hcd + modprobe -v ohci-hcd + modprobe -v usbhid + REASON=PANIC: Circular dependancy. Exiting. PS1=(initramfs) /bin/sh -i --------------- > > Otherwise, if you can get the bug to happen with the _Wheezy kernel_, please > send me the broken initramfs for the wheezy kernel. I should be able to run > that in a VM... I will try this too. Are you talking about 3.2.0-3 debian version ? I have 3.2.0-4 from sid and 3.5-trunk from experimental both installed. > > -- > "One disk to rule them all, One disk to find them. One disk to bring > them all and in the darkness grind them. In the Land of Redmond > where the shadows lie." -- The Silicon Valley Tarot > Henrique Holschuh Regards, Lionel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
