Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: syslinux: users

kernel stops booting process

 

 

syslinux users RSS feed   Index | Next | Previous | View Threaded


o.klein at comdivision

Oct 20, 2007, 8:19 AM

Post #1 of 2 (1557 views)
Permalink
kernel stops booting process

Hi



I have a problem with our pxelinux server, the server works for month without any problems. We use syslinux-3.51 version on an FC2 with in.tftp. Today I want to install a new server, but it fails after loading the kernel and booting stopped with this message



ide-floppy driver 0.99.newide
usbcore: registered new driver libusual
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
PNP: PS/2 controller doesn't have AUX irq; using default 12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
md:md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
ACPI: (supports<6>Time: tsc clocksource has been installed.
S0 S1 S4 S5)
Freeing unused kernel memory: 240k freed Write protecting the kernel read-only data: 370k



I tested this with different OS like Fedora Core 6 and CentOS-5, both stopped at same time. OpenSUSE stopped after scan the network interface. I have no idea why this happens...in the installserver log I found this



Oct 19 11:35:45 srv1 dhcpd: DHCPOFFER on XXX.XXX.201.226 to 00:30:48:85:35:32 via eth1 Oct 19 11:35:45 srv1 dhcpd: DHCPREQUEST for XXX.XX.201.226 (XXX.XX201.195) from 00:30:48:85:35:32 via eth1 Oct 19 11:35:45 srv1 dhcpd: DHCPACK on XXX.XX.201.226 to 00:30:48:85:35:32 via eth1 Oct 19 11:38:09 srv1 dhcpd: DHCPOFFER on XXX.XX201.226 to 00:30:48:85:35:32 via eth1 Oct 19 11:38:11 srv1 dhcpd: DHCPREQUEST for XXX.XX.201.226 (XXX.XX201.195) from 00:30:48:85:35:32 via eth1 Oct 19 11:38:11 srv1 dhcpd: DHCPACK on XXX.XX.201.226 to 00:30:48:85:35:32 via eth1 Oct 19 09:38:11 srv1 in.tftpd[20811]: RRQ from XXX.XX.201.226 filename pxelinux.0 Oct 19 09:38:11 srv1 in.tftpd[20812]: RRQ from XXX.XX201.226 filename pxelinux.0 Oct 19 09:38:11 srv1 in.tftpd[20813]: RRQ from XXX.XX.201.226 filename pxelinux.cfg/64837263-8462-7493-1212-003048853532

Oct 19 09:38:11 srv1 in.tftpd[20813]: sending NAK (1, File not found) to XXX.XX201.226 Oct 19 09:38:11 srv1 in.tftpd[20814]: RRQ from XXX.XX.201.226 filename pxelinux.cfg/01-00-30-48-85-35-32 Oct 19 09:38:11 srv1 in.tftpd[20814]: sending NAK (1, File not found) to XXX.XX201.226 Oct 19 09:38:11 srv1 in.tftpd[20815]: RRQ from XXX.XX.201.226 filename pxelinux.cfg/D9ABC9E2 Oct 19 09:38:11 srv1 in.tftpd[20815]: sending NAK (1, File not found) to XXX.XX201.226 Oct 19 09:38:11 srv1 in.tftpd[20816]: RRQ from XXX.XX.201.226 filename pxelinux.cfg/D9ABC9E Oct 19 09:38:11 srv1 in.tftpd[20816]: sending NAK (1, File not found) to XXX.XX201.226 Oct 19 09:38:11 srv1 in.tftpd[20817]: RRQ from XXX.XX.201.226 filename pxelinux.cfg/D9ABC9 Oct 19 09:38:11 srv1 in.tftpd[20817]: sending NAK (1, File not found) to XXX.XX201.226 Oct 19 09:38:11 srv1 in.tftpd[20818]: RRQ from XXX.XX.201.226 filename pxelinux.cfg/D9ABC Oct 19 09:38:11 srv1 in.tftpd[20818]: sending NAK (1, File not found) to XXX.XX201.226 Oct 19 09:38:11 srv1 in.tftpd[20819]: RRQ from XXX.XX.201.226 filename pxelinux.cfg/D9AB Oct 19 09:38:11 srv1 in.tftpd[20819]: sending NAK (1, File not found) to XXX.XX201.226 Oct 19 09:38:11 srv1 in.tftpd[20820]: RRQ from XXX.XX.201.226 filename pxelinux.cfg/D9A Oct 19 09:38:11 srv1 in.tftpd[20820]: sending NAK (1, File not found) to XXX.XX201.226 Oct 19 09:38:11 srv1 in.tftpd[20821]: RRQ from XXX.XX.201.226 filename pxelinux.cfg/D9 Oct 19 09:38:11 srv1 in.tftpd[20821]: sending NAK (1, File not found) to XXX.XX201.226 Oct 19 09:38:11 srv1 in.tftpd[20822]: RRQ from XXX.XX.201.226 filename pxelinux.cfg/D Oct 19 09:38:11 srv1 in.tftpd[20822]: sending NAK (1, File not found) to XXX.XX201.226 Oct 19 09:38:11 srv1 in.tftpd[20823]: RRQ from XXX.XX.201.226 filename pxelinux.cfg/default Oct 19 09:38:11 srv1 in.tftpd[20824]: RRQ from XXX.XX.201.226 filename vesamenu.c32 Oct 19 09:38:12 srv1 in.tftpd[20825]: RRQ from XXX.XX.201.226 filename pxelinux.cfg/default Oct 19 09:38:17 srv1 in.tftpd[20826]: RRQ from XXX.XX.201.226 filename centos-5/i386/vmlinuz Oct 19 09:38:19 srv1 in.tftpd[20827]: RRQ from XXX.XX.201.226 filename /centos-5/i386/initrd.img

You see vmlinuz and initrd.img were loaded but fails with kernel freece message

So any ideas what goes wrong here? THX FOR HELP IN ADVANCE!



Mit freundlichem Gruß / Best regards



Oliver Klein


_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX [at] zytor
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.


stappers at stappers

Oct 21, 2007, 7:55 AM

Post #2 of 2 (1336 views)
Permalink
Re: kernel stops booting process [In reply to]

Op 20-10-2007 om 17:19 schreef Oliver Klein:
>
> Oct 19 09:38:11 srv1 in.tftpd[20823]: RRQ from XXX.XX.201.226 filename pxelinux.cfg/default
> Oct 19 09:38:11 srv1 in.tftpd[20824]: RRQ from XXX.XX.201.226 filename vesamenu.c32
> Oct 19 09:38:12 srv1 in.tftpd[20825]: RRQ from XXX.XX.201.226 filename pxelinux.cfg/default
> Oct 19 09:38:17 srv1 in.tftpd[20826]: RRQ from XXX.XX.201.226 filename centos-5/i386/vmlinuz
> Oct 19 09:38:19 srv1 in.tftpd[20827]: RRQ from XXX.XX.201.226 filename /centos-5/i386/initrd.img

I would have expect

| Oct 19 09:38:19 srv1 in.tftpd[20827]: RRQ from XXX.XX.201.226 filename centos-5/i386/initrd.img

(no slash prefixed to centos)



> So any ideas what goes wrong here?

As I see it, does the new hardware not boot with the very same setup
as previous hardware did.
And it is indeed interresting to known why the new computer doesn't boot
the same way as other computers did.
First thing I would do, is netbooting an "old" computer to check the
server side setup.



I hope that this posting did help.


Cheers
Geert Stappers

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX [at] zytor
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

syslinux users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.