Re: BTX failure [Was: Re: pxeboot problems with BETA2]
Am Donnerstag, 25. August 2005 20:06 CEST schrieb John Baldwin: [...] I have no ideay why, but over night I recompiled my PXEROOT system (BETA3 now) and the problem vanished. I can't see any changes in the cvsweb, so I have absolutely no idea what the problem was. Hardware is exactly the same. What have I missed? Maybe you had a corrupted pxeboot binary somehow? I'm quiet sure that this can't be. I played arround with several CFLAG options (-Os, -marchi486 etc.) and with several -DPXELDR_ALWAYS_SERIAL etc. so I'm sure I had tested some dozends of different pxeboot binaries. And I can't imagine that corrupted source file can cause such an error, remember that all these pxeboot binaries worked fine on PIII boxes, just not with the Elan SC520. I'm glad that it works now, but it was really interesting what in the chain of libs/dependend boot/loader stuff was the reason... Thanks for your help, -Harry pgpVgTaiWXS5H.pgp Description: PGP signature
Re: BTX failure [Was: Re: pxeboot problems with BETA2]
On Tuesday 23 August 2005 09:34 am, Emanuel Strobl wrote: Am Mittwoch, 17. August 2005 21:29 CEST schrieb John Baldwin: On Wednesday 17 August 2005 10:43 am, Emanuel Strobl wrote: Am Dienstag, 16. August 2005 19:52 CEST schrieb Brooks Davis: On Tue, Aug 16, 2005 at 02:05:08PM +0200, Emanuel Strobl wrote: Hello, I just wanted to ask if somebody had success with providing pxe boot service under 6-BETA2. I have two clients, one NET4501 wich just reboots after fetching pxeldr via TFTP and a Laptop which just hangs when NFS-loading kernel. I'm about to investigate further, but maybe someone can confirm that in general PXE booting with BETA2 is working... Or not... I'm PXE booting systems with RELENG_6 as of 7/27. I'll probably do an update some time this week. Ok, I read som files and found -DBTX_SERIAL. This gives me the following dump before the box reboots: uilding the boot loader arguments Relocating the loader and the BTX Starting the BTX loader int=0006 err= efl=00010202 eip=00023c21 eax= ebx=000384e0 ecx=000384e0 edx=0001 esi=1000 edi=0029 ebp=00086770 esp=00086758 cs=002b ds=0033 es=0033fs=0033 gs=0033 ss=0033 cs:eip=0f 4f c2 a3 c8 7d 03 00-8d 41 0c c7 41 04 fd 44 ff 55 89 39 c6 44 39 ff-fe 83 c4 0c 5b 5e 5f 5d ss:esp=b4 7d 03 00 29 00 00 00-00 10 00 00 00 00 00 00 83 57 02 00 02 00 00 00-a0 67 08 00 98 1c 02 00 BTX halted Any clue? Regarding cvsweb nothing changed recently, and I had net4501 boxes pxebooting fine with FreeBSD 5.3. Hmm. Int 6 is an invalid opcode exception: I have no ideay why, but over night I recompiled my PXEROOT system (BETA3 now) and the problem vanished. I can't see any changes in the cvsweb, so I have absolutely no idea what the problem was. Hardware is exactly the same. What have I missed? Maybe you had a corrupted pxeboot binary somehow? -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve = http://www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BTX failure [Was: Re: pxeboot problems with BETA2]
Am Mittwoch, 17. August 2005 21:29 CEST schrieb John Baldwin: On Wednesday 17 August 2005 10:43 am, Emanuel Strobl wrote: Am Dienstag, 16. August 2005 19:52 CEST schrieb Brooks Davis: On Tue, Aug 16, 2005 at 02:05:08PM +0200, Emanuel Strobl wrote: Hello, I just wanted to ask if somebody had success with providing pxe boot service under 6-BETA2. I have two clients, one NET4501 wich just reboots after fetching pxeldr via TFTP and a Laptop which just hangs when NFS-loading kernel. I'm about to investigate further, but maybe someone can confirm that in general PXE booting with BETA2 is working... Or not... I'm PXE booting systems with RELENG_6 as of 7/27. I'll probably do an update some time this week. Ok, I read som files and found -DBTX_SERIAL. This gives me the following dump before the box reboots: uilding the boot loader arguments Relocating the loader and the BTX Starting the BTX loader int=0006 err= efl=00010202 eip=00023c21 eax= ebx=000384e0 ecx=000384e0 edx=0001 esi=1000 edi=0029 ebp=00086770 esp=00086758 cs=002b ds=0033 es=0033fs=0033 gs=0033 ss=0033 cs:eip=0f 4f c2 a3 c8 7d 03 00-8d 41 0c c7 41 04 fd 44 ff 55 89 39 c6 44 39 ff-fe 83 c4 0c 5b 5e 5f 5d ss:esp=b4 7d 03 00 29 00 00 00-00 10 00 00 00 00 00 00 83 57 02 00 02 00 00 00-a0 67 08 00 98 1c 02 00 BTX halted Any clue? Regarding cvsweb nothing changed recently, and I had net4501 boxes pxebooting fine with FreeBSD 5.3. Hmm. Int 6 is an invalid opcode exception: I have no ideay why, but over night I recompiled my PXEROOT system (BETA3 now) and the problem vanished. I can't see any changes in the cvsweb, so I have absolutely no idea what the problem was. Hardware is exactly the same. What have I missed? Thanks, -Harry 0F4FC2cmovg eax,edx 0003 A3C87D0300mov [0x37dc8],eax 0008 8D410Clea eax,[ecx+0xc] 000B C74104FD44FF55mov dword [ecx+0x4],0x55ff44fd 0012 8939 mov [ecx],edi 0014 C64439FFFEmov byte [ecx+edi-0x1],0xfe 0019 83C40Cadd esp,byte +0xc 001C 5Bpop ebx 001D 5Epop esi 001E 5Fpop edi 001F 5Dpop ebp I'm guessing that there's been a stack overflow or some such. Your eip is in the loader. You can try using the loader.sym from your loader binary to look up that eip address. In the loader here on my laptop it's in the write function: % nm /usr/obj/usr/src/sys/boot/i386/loader/loader.sym | sort ... 00023b9c T readdirfd 00023c14 T write 00023d18 T lseek If you want to be able to use gdb, then rebuild libstand with debugging (make DEBUG_FLAGS=-g) and rebuild all of /sys/boot with debugging (make DEBUG_FLAGS=-g). You can then use /usr/obj/usr/src/sys/boot/i386/pxeldr/pxeboot for your pxeboot and you can run gdb on /usr/obj/usr/src/sys/boot/i386/loader/loader.sym and you can do listings of the addresses for eip, etc. pgpj0zK68sjPU.pgp Description: PGP signature
Re: BTX failure [Was: Re: pxeboot problems with BETA2]
On Wednesday 17 August 2005 10:43 am, Emanuel Strobl wrote: Am Dienstag, 16. August 2005 19:52 CEST schrieb Brooks Davis: On Tue, Aug 16, 2005 at 02:05:08PM +0200, Emanuel Strobl wrote: Hello, I just wanted to ask if somebody had success with providing pxe boot service under 6-BETA2. I have two clients, one NET4501 wich just reboots after fetching pxeldr via TFTP and a Laptop which just hangs when NFS-loading kernel. I'm about to investigate further, but maybe someone can confirm that in general PXE booting with BETA2 is working... Or not... I'm PXE booting systems with RELENG_6 as of 7/27. I'll probably do an update some time this week. Ok, I read som files and found -DBTX_SERIAL. This gives me the following dump before the box reboots: uilding the boot loader arguments Relocating the loader and the BTX Starting the BTX loader int=0006 err= efl=00010202 eip=00023c21 eax= ebx=000384e0 ecx=000384e0 edx=0001 esi=1000 edi=0029 ebp=00086770 esp=00086758 cs=002b ds=0033 es=0033fs=0033 gs=0033 ss=0033 cs:eip=0f 4f c2 a3 c8 7d 03 00-8d 41 0c c7 41 04 fd 44 ff 55 89 39 c6 44 39 ff-fe 83 c4 0c 5b 5e 5f 5d ss:esp=b4 7d 03 00 29 00 00 00-00 10 00 00 00 00 00 00 83 57 02 00 02 00 00 00-a0 67 08 00 98 1c 02 00 BTX halted Any clue? Regarding cvsweb nothing changed recently, and I had net4501 boxes pxebooting fine with FreeBSD 5.3. Hmm. Int 6 is an invalid opcode exception: 0F4FC2cmovg eax,edx 0003 A3C87D0300mov [0x37dc8],eax 0008 8D410Clea eax,[ecx+0xc] 000B C74104FD44FF55mov dword [ecx+0x4],0x55ff44fd 0012 8939 mov [ecx],edi 0014 C64439FFFEmov byte [ecx+edi-0x1],0xfe 0019 83C40Cadd esp,byte +0xc 001C 5Bpop ebx 001D 5Epop esi 001E 5Fpop edi 001F 5Dpop ebp I'm guessing that there's been a stack overflow or some such. Your eip is in the loader. You can try using the loader.sym from your loader binary to look up that eip address. In the loader here on my laptop it's in the write function: % nm /usr/obj/usr/src/sys/boot/i386/loader/loader.sym | sort ... 00023b9c T readdirfd 00023c14 T write 00023d18 T lseek If you want to be able to use gdb, then rebuild libstand with debugging (make DEBUG_FLAGS=-g) and rebuild all of /sys/boot with debugging (make DEBUG_FLAGS=-g). You can then use /usr/obj/usr/src/sys/boot/i386/pxeldr/pxeboot for your pxeboot and you can run gdb on /usr/obj/usr/src/sys/boot/i386/loader/loader.sym and you can do listings of the addresses for eip, etc. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve = http://www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BTX failure [Was: Re: pxeboot problems with BETA2]
Am Mittwoch, 17. August 2005 21:29 CEST schrieb John Baldwin: On Wednesday 17 August 2005 10:43 am, Emanuel Strobl wrote: [*schnip*] Relocating the loader and the BTX Starting the BTX loader int=0006 err= efl=00010202 eip=00023c21 eax= ebx=000384e0 ecx=000384e0 edx=0001 esi=1000 edi=0029 ebp=00086770 esp=00086758 cs=002b ds=0033 es=0033fs=0033 gs=0033 ss=0033 cs:eip=0f 4f c2 a3 c8 7d 03 00-8d 41 0c c7 41 04 fd 44 ff 55 89 39 c6 44 39 ff-fe 83 c4 0c 5b 5e 5f 5d ss:esp=b4 7d 03 00 29 00 00 00-00 10 00 00 00 00 00 00 83 57 02 00 02 00 00 00-a0 67 08 00 98 1c 02 00 BTX halted Any clue? Regarding cvsweb nothing changed recently, and I had net4501 boxes pxebooting fine with FreeBSD 5.3. Hmm. Int 6 is an invalid opcode exception: 0F4FC2cmovg eax,edx 0003 A3C87D0300mov [0x37dc8],eax 0008 8D410Clea eax,[ecx+0xc] 000B C74104FD44FF55mov dword [ecx+0x4],0x55ff44fd 0012 8939 mov [ecx],edi 0014 C64439FFFEmov byte [ecx+edi-0x1],0xfe 0019 83C40Cadd esp,byte +0xc 001C 5Bpop ebx 001D 5Epop esi 001E 5Fpop edi 001F 5Dpop ebp I'm guessing that there's been a stack overflow or some such. Your eip is in the loader. You can try using the loader.sym from your loader binary to look up that eip address. In the loader here on my laptop it's in the write function: Thanks for your attention! It's late here, I'll try to understand and see what I can do tomorrow. Just for info, simply copying pxeboot from a 5.3-release (also real verified with 5.2.1 no 5.4 so far) DVD works. Bisides that I need sio support in pxeldr so I have to compile it my own. And of course I'd love to have the new comspeed config option :) % nm /usr/obj/usr/src/sys/boot/i386/loader/loader.sym | sort ... 00023b9c T readdirfd 00023c14 T write 00023d18 T lseek If you want to be able to use gdb, then rebuild libstand with debugging (make DEBUG_FLAGS=-g) and rebuild all of /sys/boot with debugging (make DEBUG_FLAGS=-g). You can then use /usr/obj/usr/src/sys/boot/i386/pxeldr/pxeboot for your pxeboot and you can run gdb on /usr/obj/usr/src/sys/boot/i386/loader/loader.sym and you can do listings of the addresses for eip, etc. Expect to here from me the next 48 hours, tommorow I'm too busy as I could just see :( Thanks again, -Harry pgpzBtA0HvYVp.pgp Description: PGP signature
