The patch in 2.6.24.4 and the soon to be 2.6.25 fixes this problem but
only if you build with CONFIG_X86_GENERIC set.
The current Debian build for the 686 kernel does not set this and the
long NOPs will still be there.
This e-mail was sent from a group e-mail system of ARC International Plc. F
Package: initramfs-tools
Version: 0.85h
Severity: normal
You can't use break=??? if you use panic=0. This is because the
maybe_break function calls the panic function to get a shell. It should
be simple to fix by just setting panic=1 inside maybe_break() before
calling panic().
-- Package-specifi
The bug is in this section:
if [ "${NFSROOT#:*}" = "$NFSROOT" ]; then
NFSROOT=${ROOTSERVER}:${NFSROOT}
fi
The :* is the wrong way around so if $NFSROOT=192.168.0.4:/ the :*
pattern won't match (NFSROOT doesn't start with :) and so NFSROOT ge
Package: initramfs-tools
Version: 0.80
Severity: normal
I'm still getting the timeouts on root mount refered to in bug 359926.
With this version of initramfs-tools the retry fails without really
retrying and it enters a loop. After 180s it times out and drops to a
panic shell. IP is configured sin
Package: usplash
Version: 0.3e
Severity: normal
After a usplash timeout (e.g. fsck) I'm left looking at vt8 which
doesn't have much on it and I need to alt-F1 to get to the real console
messages. Does usplash need to switch to vt8? If so can it switch back
on timeout.
-- System Information:
Debia
Package: unionfs-modules-2.6.17-2-686
Version: 1.3+debian-4+2.6.17-2
Severity: normal
Title say it all, I couldn't build without this package.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh lin
Package: usplash
Version: 0.3e
Severity: normal
In the function log_end_msg, line 104 has 'printf "\r"' which is used to
keep the ok/fail message on the same line as the log_begin+msg text.
This confuses the output of bootlogd since it uses its own primitive line
buffer. Replacing the \r with \b
Package: initramfs-tools
Version: 0.77
Severity: important
The new method of creating /dev/null is causing usplash to not work. At
the top of the init script /dev/null is created if it doesn't exist and
then a tmpfs is mounted on top of /dev. This hides the /dev/null and
/dev/console so any script
Package: initramfs-tools
Version: 0.77
Severity: minor
The new mountroot() in scripts/nfs works nicely in that it does retry if
the first mount fails but it always says "Retrying" even though it
should say "Trying" the first time. Very minor bug though.
-- Package-specific info:
-- /proc/cmdline
Package: initramfs-tools
Version: 0.76
Severity: minor
The top part of init has this:
mkdir /sys
mkdir /proc
mkdir /tmp
mkdir -p /var/lock
These can all be put in the initramfs image can't they? Also (not a
bug), I can't figure out how /root gets created, it's not in the image
and there's no "mk
You can consider this bug work-arounded if you use the panic=0 boot
parameter. Getting a timeout would then reboot the machine thus giving a
retry (although a bit slower).
Cheers,
Tim.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTE
Package: usplash
Version: 0.3e
Severity: normal
I have the kbd package installed (it handles bigger fonts than
console-utilities) and its initscript is called
"/etc/init.d/console-screen.kbd.sh". The usplash init.d script is not
going to use this since it's looking for
"/etc/init.d/console-screen.
Package: linux-image-2.6.16
Version: hippo.3
Severity: normal
drivers/media/video/cx88/*.c has this in places:
#define dprintk(level,fmt, arg...) if (debug >= level) ...
I think that >= should be a > so that when debug is set to 0 no messages
are printed by the kernel. At the moment I have n
Package: initramfs-tools
Version: 0.69b
Severity: normal
I created a script called /etc/initramfs-tools/scripts/nfs-bottom/retry-nfs.
There were plenty of hyphens in the path leading to script name so I
didn't think the name would be a problem. Imagine my suprise when I
rebooted and got some crypt
Below is a very hacky script that implements the retry loop. The script
should go in /etc/initramfs-tools/scripts/nfs-bottom/retry. It adds a test
in /conf/param.conf and that script is sourced by the main /init. It needs
to do this since mountroot is only available to /init. The real fix should
be
Package: initramfs-tools
Version: 0.67
Severity: important
For some reason my diskless system seems to fail to boot every other time.
I get time-out messages from nfsroot and then the /init script dumps me
into a debug shell when it can't find /root/sbin/init.
I don't know the cause of the mount
Package: initramfs-tools
Version: 0.60
Severity: minor
/usr/share/initramfs-tools/scripts/functions has a panic() function to spawn an
emergency or debug shell. It does so with this line
FS1='(initramfs) ' /bin/sh /dev/console 2>&1
FS1 should be PS1 if you want to set the prompt.
-- Sy
17 matches
Mail list logo
