Dell PE2850 freeze on boot with PXE and FreeBSD 7.0 amd64

[Stefan Lambrev]

Hi,

Eric Anderson wrote:
> Stefan Lambrev wrote:
>> Hello,
>>
>> Sorry for cross-posting, but I'm not sure which is the proper mail 
>> list for this.
>>
>> I'm trying to boot latest FreeBSD 7 amd64 snapshot on Dell PE2850 (+2 
>> year old server),
>> but it panic (and freeze) every time on afd.
>> afd in this case should be virtual floppy provided by DRAC (Dell 
>> Remote Access Controller)
>>
>> FreeBSD 7 - i386 boot without a problems, I'll try few other 
>> snapshots (6.2-stable amd64) to be sure that the problem is only in 
>> 7-current amd64
>>
>> Here is result from verbose boot:
After few more test I can say that only FreeBSD 7 amd64 is affected. It 
just panic and freeze while trying to boot on this server.
FreeBSD 6.2-stable amd64/i386 and FreeBSD 7 i386 boot without problems, 
so it seems that there is a regression in FreeBSD 7 amd64.

I hope this can be fixed before 7.0 Release.
>>
>>
> [..snip..]
>> ata2-slave: pio=PIO3 wdma=UNSUPPORTED udma=UNSUPPORTED cable=40 wire
>> ata2-master: pio=PIO3 wdma=UNSUPPORTED udma=UNSUPPORTED cable=40 wire
>> afd0: setting PIO3 on SiI 0680 chip
>> afd0: (no media) <VIRTUALFLOPPY DRIVE Floppy > at ata2-master PIO3
>>
>>
>> Fatal trap 18: integer divide fault while in kernel mode
>> cpuid = 0; apic id = 00
>> instruction pointer     = 0x8:0xffffffff802522f7
>> stack pointer           = 0x10:0xffffffff80f9cba0
>> frame pointer           = 0x10:0xffffffff80f9cc20
>> code segment            = base 0x0, limit 0xfffff, type 0x1b
>>                       = DPL 0, pres 1, long 1, def32 0, gran 1
>> processor eflags        = interrupt enabled, resume, IOPL = 0
>> current process         = 0 (swapper)
>> [thread pid 0 tid 0 ]
>> Stopped at      afd_attach+0x2c7:       divq    %rcx,%eax
>> db>
>>
>>
>> At this point the machine freezes and i cannot trace or whatever.
>>
>> P.S. please include me in CC as I'm not subscribed to both lists.
>>
>
>
> You should be able to disable the virtual floppy on the system, and 
> that should allow it to boot.  That's not a fix, but it could get you 
> going in the mean time.
>
>
> Eric
>
>

-- 

Best Wishes,
Stefan Lambrev
ICQ# 24134177