PXE booting issues
I'm currently working on an embedded project which will be built around a BSD (I'm not sure which yet), currently I have an image up and running DragonFly and I'm currently attempting to do the same with FreeBSD for comparison. I'm more or less following the miniBSD tutorials (updating the various file lists and such as I go). The system is being built around 6.2-STABLE but I'm having some issues getting it to PXE boot. On my FreeBSD host I've enabled TFTP, exported the rootfs for the system via NFS, built and installed isc-dhcpd and configured it with the extra options for PXE booting. The client currently gets its IP address from the server successfully, retrieves and loads pxeboot but when it comes to launch the kernel it eventually throws an NFS timeout. I know the export is working because I used NFS to pull the rootfs over to my DragonFly boot host to see what the result was when I booted the same image from a known working boot host (it worked correctly until it hit a problem in the image I will detail in a separate message). I did attempt to rebuild the pxeboot loader, following the standard instructions; set LOADER_TFTP_SUPPORT=YES in /etc/make.conf cd /usr/src/sys/boot make clean && make depend && make It appears to be successful (and the output would support this) but the i386/pxeldr/pxeboot and i386/loader/loader files do not exist, my only guess is that I've not set a make variable I should have, the most confusing part is that the dd command which is the final step in generating pxeboot appears in the output and appears to be successful; == dd if=pxeboot.tmp of=pxeboot obs=2k conv=osync 425+0 records in 107+0 records out == The discrepancy in the records in and the records out is concerning but I would expect the file to exist regardless, I'm currently using the default /boot/pxeboot. Any suggestions as to what might be causing this would be greatly appreciated. Thanks in advance, Morgan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PXE booting issues
> I'm currently working on an embedded project which will be built > around a BSD (I'm not sure which yet), currently I have an image up > and running DragonFly and I'm currently attempting to do the same with > FreeBSD for comparison. > > I'm more or less following the miniBSD tutorials (updating the various > file lists and such as I go). > > The system is being built around 6.2-STABLE but I'm having some issues > getting it to PXE boot. > > On my FreeBSD host I've enabled TFTP, exported the rootfs for the > system via NFS, built and installed isc-dhcpd and configured it with > the extra options for PXE booting. > > The client currently gets its IP address from the server successfully, > retrieves and loads pxeboot but when it comes to launch the kernel it > eventually throws an NFS timeout. > > I know the export is working because I used NFS to pull the rootfs > over to my DragonFly boot host to see what the result was when I > booted the same image from a known working boot host (it worked > correctly until it hit a problem in the image I will detail in a > separate message). > > I did attempt to rebuild the pxeboot loader, following the standard > instructions; > set LOADER_TFTP_SUPPORT=YES in /etc/make.conf > cd /usr/src/sys/boot > make clean && make depend && make > > It appears to be successful (and the output would support this) but > the i386/pxeldr/pxeboot and i386/loader/loader files do not exist, my > only guess is that I've not set a make variable I should have, the > most confusing part is that the dd command which is the final step in > generating pxeboot appears in the output and appears to be successful; > == > dd if=pxeboot.tmp of=pxeboot obs=2k conv=osync > 425+0 records in > 107+0 records out > == > The discrepancy in the records in and the records out is concerning > but I would expect the file to exist regardless, I'm currently using > the default /boot/pxeboot. > > Any suggestions as to what might be causing this would be greatly appreciated. 1- try sniffing (wireshark, not the kind that will get you high :-) and see where it hangs. 2- the dhcp should tell pxeloader where the root is: option root-path "ip:/path" danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [vfs_bio] Re: Fatal trap 12: page fault while in kernel mode (with potential cause)
On Sun, Jun 24, 2007 at 12:30:20AM -0400, Adam McDougall wrote: On Mon, Apr 23, 2007 at 11:55:52AM -0400, Kris Kennaway wrote: On Mon, Apr 23, 2007 at 05:35:47PM +0200, Kai wrote: > On Thu, Apr 19, 2007 at 02:33:29PM +0200, Kai wrote: > > On Wed, Apr 11, 2007 at 12:53:32PM +0200, Kai wrote: > > > > > > Hello all, > > > > > > We're running into regular panics on our webserver after upgrading > > > from 4.x to 6.2-stable: > > > > Hi all, > > To continue this story, a colleague wrote a small program in C that launches > 40 threads to randomly append and write to 10 files on an NFS mounted > filesystem. > > If I keep removing the files on one of the other machines in a while loop, > the first system panics: > > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address = 0x34 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc06bdefa > stack pointer = 0x28:0xeb9f69b8 > frame pointer = 0x28:0xeb9f69c4 > code segment= base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags= interrupt enabled, resume, IOPL = 0 > current process = 73626 (nfscrash) > trap number = 12 > panic: page fault > cpuid = 1 > Uptime: 3h2m14s > > Sounds like a nice denial of service problem. I can hand the program to > developers on request. Please send it to me. Panics are always much easier to get fixed if they come with a test case that developer can use to reproduce it. Kris I have been working on this problem all weekend and I have a strong hunch at this point that it is a result of 1.424 of sys/kern/vfs_bio.c which was between FreeBSD 5.1 and 5.2. This hunch is currently being verified by a system that was cvsupped to code just before 1.424, and it has been running about 7 times longer than the usual time required to crash. I am currently attempting to craft a patch for 6.2 that essentially backs out the change to see if that works, but if this information can help send a FreeBSD developer down the right trail to a proper fix, great. I will follow up with more detailed findings and results tonight or soon. links: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/vfs_bio.c.diff?r1=1.423;r2=1.424 related to 1.424: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/vfs_bio.c.diff?r1=1.420&r2=1.421 Commit emails: http://docs.freebsd.org/cgi/mid.cgi?200311150845.hAF8jawU027349 http://docs.freebsd.org/cgi/mid.cgi?20030445.hAB4jbYw093253 ___ If I turn on invariants, I get the following panic instead, much quicker, and happens with at least as far back as 5.0-RELEASE: panic: bundirty: buffer 0x8e2e95f8 still on queue 1 cpuid = 1 Uptime: 35s Dumping 511 MB (2 chunks) chunk 0: 1MB (153 pages) ... ok chunk 1: 511MB (130816 pages) 496 480 464 448 432 416 400 384 368 352 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16 #0 doadump () at pcpu.h:172 172 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:172 #1 0x8028d699 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0x8028d12b in panic (fmt=0x80443458 "bundirty: buffer %p still on queue %d") at /usr/src/sys/kern/kern_shutdown.c:565 #3 0x802e1e78 in bundirty (bp=0x8e2e95f8) at /usr/src/sys/kern/vfs_bio.c:1055 #4 0x802e3eb1 in brelse (bp=0x8e2e95f8) at /usr/src/sys/kern/vfs_bio.c:1370 #5 0x803550e8 in nfs_writebp (bp=0x8e2e95f8, force=0, td=0x0) at /usr/src/sys/nfsclient/nfs_vnops.c:3005 #6 0x802e5197 in getblk (vp=0xff000c23e5d0, blkno=0, size=14400, slpflag=256, slptimeo=0, flags=0) at buf.h:412 #7 0x80344f13 in nfs_getcacheblk (vp=0xff000c23e5d0, bn=0, size=14400, td=0xff0015b274c0) at /usr/src/sys/nfsclient/nfs_bio.c:1252 #8 0x8034616c in nfs_write (ap=0x0) at /usr/src/sys/nfsclient/nfs_bio.c:1068 #9 0x80405ee4 in VOP_WRITE_APV (vop=0x805a0260, a=0x976bfa10) at vnode_if.c:698 #10 0x80303d2c in vn_write (fp=0xff000f524000, uio=0x976bfb50, active_cred=0x0, flags=0, td=0xff0015b274c0) at vnode_if.h:372 #11 0x802ba2e5 in dofilewrite (td=0xff0015b274c0, fd=3, fp=0xff000f524000, auio=0x976bfb50, offset=0, flags=0) at file.h:253 #12 0x802ba5e1 in kern_writev (td=0xff0015b274c0, fd=3, auio=0x976bfb50) at /usr/src/sys/kern/sys_generic.c:402 #13 0x802ba6da in write (td=0x0, uap=0x0) at /usr/src/sys/kern/sys_generic.c:326 #14 0x803c6db2 in syscall (frame=
Re: Unable to use my USB MP4 player: FreeBSD hangs
"Dominique Goncalves" wrote: > Hi, > > I'm trying to connect my USB MP4 player to transfer some video and > music files, but when I plug the player FreeBSD hangs at this point: You don't say, if, so I'll reccomend: Do turn on power before connectting to FreeBSD Do not rely on player detecting power & turning on. Why: I used to have hell of a problem before with my Clipman mp3 player Problem was devd or usbd created & destroying things while listening to wire one end, & the Clipman mp3 listening to wire & also doing things, eg powering off or destroying /dev entries etc. http://berklix.com/~jhs/~jhs/txt/clipman/ -- Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com HTML mail unseen. Ihr Rauch=mein allergischer Kopfschmerz. Dump cigs 4 snuff. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PXE booting issues
Hi,
> 2- the dhcp should tell pxeloader where the root is:
> option root-path "ip:/path"
And next-server
I have a couple of version 6.2 pxe-clients booting of a 4.11 box without a
problem.
A snippet of my dhcpd.conf:
host gister {
hardware ethernet 00:0e:0c:b4:3a:14;
fixed-address 192.168.4.104;
option root-path "192.168.4.105:/var/nixfs/pxe/gister";
next-server 192.168.4.105;
filename "pxeboot";
}
and the kernel config:
#grep -i bootp /usr/src/sys/i386/conf/GISTER
options BOOTP
options BOOTP_NFSROOT
options BOOTP_NFSV3
options BOOTP_COMPAT
options BOOTP_WIRED_TO=fxp0
Hth.
Kind regards,
Robert
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Upgrading 5.5-STABLE to 6-STABLE
Hi: I bet this is documented /somewhere/, so if the response is in the form of a single URL, I'm cool with that. I'm trying to buildkernel and I'm getting config(8) errors: ERROR: version of config(8) does not match kernel! config version = 500013, version required = 63 What's the process of building from source a new version of FreeBSD? Thanks, -Clint ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading 5.5-STABLE to 6-STABLE
On Sun, Jun 24, 2007 at 12:06:26PM -0700, Clint Olsen wrote: > Hi: > > I bet this is documented /somewhere/, so if the response is in the form > of a single URL, I'm cool with that. I'm trying to buildkernel and I'm > getting config(8) errors: > > ERROR: version of config(8) does not match kernel! > config version = 500013, version required = 63 > > What's the process of building from source a new version of FreeBSD? Read /usr/src/UPDATING (especially the section named "To upgrade in-place from 5.x-stable or higher to 6.x-stable" under "COMMON ITEMS".) It is documented quite clearly there how you are supposed to do it. -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PXE booting issues
On Sun, Jun 24, 2007 at 09:27:42PM +1000, Morgan Reed wrote: > == > dd if=pxeboot.tmp of=pxeboot obs=2k conv=osync > 425+0 records in > 107+0 records out > == > The discrepancy in the records in and the records out is concerning > but I would expect the file to exist regardless, I'm currently using > the default /boot/pxeboot. The default blocksize in dd is 512 -- that is, ibs=512 and obs=512. If you only specify obs, ibs still remains at 512. 2048 / 512 = 4. 107 * 4 == 428, which is about 425; chances are the file isn't *exactly* on a 2047-byte boundary, which explains the "missing 3". If you do "bs=2k", you should see both 107 records in and out. I hope this helps clear up any concern over that part. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PXE booting issues
On 6/25/07, Robert Joosten <[EMAIL PROTECTED]> wrote: And next-server My dhcpd.conf has an appropriate next-server directive, all the configuration (for the network boot) has been duplicated from the functional DragonFly boot server. I have a couple of version 6.2 pxe-clients booting of a 4.11 box without a problem. My FreeBSD boot host is running 6.2-STABLE and the kernel config: #grep -i bootp /usr/src/sys/i386/conf/GISTER options BOOTP options BOOTP_NFSROOT options BOOTP_NFSV3 options BOOTP_COMPAT options BOOTP_WIRED_TO=fxp0 I'm not using the BOOTP options in my kernel, the same image is able to get its kernel on another system so I'm happy it's not the image causing this issue. At Danny's suggestion I've done some sniffing of the virtual interface and discovered that none of the NFS calls from the client are being replied to, yet another host on the same subnet can mount the same filesystem without issue, that said I've just run another trace, and I do notice that the calls when I mount the filesystem on the other host are a mixture of V2 and V3 calls whereas the call from the PXE host is a V2 call (although this is the GETPORT call which is V2 in both cases). Thanks for your time. Morgan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PXE booting issues
On 6/25/07, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: I hope this helps clear up any concern over that part. Thanks for the explanation, that makes sense. Unfortunately it still doesn't explain why the file is not being created, the fact that the dd command is outputting a count for records out suggests to me that it *SHOULD* have been created but even doing a find across my /usr/src/sys/boot doesn't turn it up. Thanks Morgan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
