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: >> >> > [..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 > > Yes this is workaround and seems to work for 7-current. I checked 6.2-stable amd64 latest snapshot and it boots without a problem (with enabled virtual devices). What is more weird, I tried to tell the kernel to not probe afd and acd1 by escaping to boot prompt and typing: set hint.afd.0.disable="1" set hint.acd.1.disable="1" boot -vDh but both devices are again detected and probed followed by kernel panic. Is this supposed to work, or I made a mistake somewhere? -- Best Wishes, Stefan Lambrev ICQ# 24134177Received on Tue Jul 03 2007 - 12:35:49 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:13 UTC