LTSP clients kernel panic on boot when active nic isn't eth0
Bug #365380 reported by
Kenneth Finnegan
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ltsp (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Upgraded my LTSP server from Hardy to Jaunty with a clean install. I can boot my laptop as a client no problem, but one of my other desktops fails. It worked fine with Hardy.
It gets an IP address, downloads a kernel image, and then sits at the boot splash screen as the bar bounces back and forth, then the screen goes blank and it displays:
[ 63.564633] Kernel panic - not syncing: Attempted to kill init!
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelMo
Package: ltsp-server 5.1.65-0ubuntu2
PackageArchitec
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
SourcePackage: ltsp
Uname: Linux 2.6.28-11-generic i686
summary: |
- Some LTSP clients kernel panic on boot + LTSP clients kernel panic on boot when active nic isn't eth0 |
Changed in ltsp (Ubuntu): | |
status: | New → Incomplete |
To post a comment you must log in.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Can you try booting the thin client without the splash and quiet options tftpboot/ ltsp/i386/ pxelinux. cfg/default
(you can change that in /var/lib/
on the server), that should give you a bit more information on what went
wrong.
I'm especially looking at an error from either ipconfig (network
configuration) or nbd (connection to the network harddisk).
Is the problem happening with similar network cards ? Do these thin
clients only have one network card or two ?
Thanks enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkn v+VwACgkQjxyfqk jBhuw46gCfe3cD/ fTGsmGxvtpcOi1W mUjE Hw7FOmCgSFp6i35 4Bw
rC4An174NeNgw/
=sm7e
-----END PGP SIGNATURE-----