Hello,
I sent this to nahant-list earlier but thought some folks on here might
have run into my problem. Thanks for any help with this issue.
/Brian/
--
Brian Long | | |
IT Data Center Systems | .|||. .|||.
Cisco Linux Developer | ..:|||||||:...:|||||||:..
Phone: (919) 392-7363 | C i s c o S y s t e m s
--- Begin Message ---
- Subject: UP Kernel oops on EM64T with long command-line
- From: Brian Long <brilong@xxxxxxxxx>
- Date: Tue, 13 Dec 2005 11:25:12 -0500
- Reply-to: "Red Hat Enterprise Linux 4 (Nahant) Discussion List" <nahant-list@xxxxxxxxxx>
Has anyone run into a problem where certain servers will cause the
kernel to oops if the kernel is passed a large command-line? For
example, in our pxe configuration, we have an append line as follows:
append initrd=pxe-tftp.esl.cisco.com::images/releases/5.00b4-4/x86_64/initrd.img ks=http://wwwin-kickstart-dev/cgi-bin/pxe/getkscfg?macaddr=00:12:79:3d:f7:d8 ramdisk_size=8192 ksdevice=00:12:79:3d:f7:d8 nostorage
This is 207 characters and it works fine on all our desktops, our
Opteron-based V20z and V40z's, but it does not work on HP DL360 G4 or
DL380 G4 EM64T-based servers when trying to kickstart the RHEL 4 U2
x86_64 image (or U1 either). The i386 image installs fine with this
long append statement.
The details are located in this Bugzilla:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=175616
Any ideas on how I might resolve this? I've tried reducing the append
line by using filesytem symlinks on our web server (replace
images/releases with i/r), but I still end up with ~180 characters. The
problem goes away at 176 characters or less. :(
BTW, what is the default ramdisk_size?
Thanks for any help with this issue.
/Brian/
--
Brian Long | | |
IT Data Center Systems | .|||. .|||.
Cisco Linux Developer | ..:|||||||:...:|||||||:..
Phone: (919) 392-7363 | C i s c o S y s t e m s
--
nahant-list mailing list
nahant-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/nahant-list
--- End Message ---
