DragonFly installation experience / suggestions

[Michael Neumann]

Sepherosa Ziehau wrote:
On 8/10/07, Michael Neumann <mneumann at ntecs.de> wrote:
Hey,

Once again I changed from FreeBSD to DragonFly :)

Here's a list of a few problems I encountered and what I think
could be improved:
* After installation, my laptop BIOS hung up. I had to manually
   intercept the installation process and issue "fdisk -BIC". The "-C"
   option seems to be important here. This wasn't neccessary on
   NetBSD/FreeBSD. The -C option does not exist in FreeBSD's fdisk, maybe
   there do it more intelligently?
* "kldload if_ipw" led to a kernel panic, whereas if_ipw_load="YES" in
Can you give me more information about this panic?  Things like back trace...
#0  dumpsys () at thread.h:83
#1  0xc02ef8ab in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:371
#2  0xc02f0034 in panic (fmt=0xc05677c5 "from debugger") at
/usr/src/sys/kern/kern_shutdown.c:796
#3  0xc0166c6a in db_panic (addr=-1068458059, have_addr=0, count=-1,
modif=0xd2bcd8cc "")
    at /usr/src/sys/ddb/db_command.c:447
#4  0xc0166bff in db_command (last_cmdp=0xc063a9b0, cmd_table=0x0,
aux_cmd_tablep=0xc05c4194,
    aux_cmd_tablep_end=0xc05c41b0) at /usr/src/sys/ddb/db_command.c:343
#5  0xc0166cdf in db_command_loop () at
/usr/src/sys/ddb/db_command.c:469
#6  0xc0169874 in db_trap (type=3, code=0) at
/usr/src/sys/ddb/db_trap.c:71
#7  0xc0509c58 in kdb_trap (type=3, code=0, regs=0xd2bcd9f0)
    at /usr/src/sys/platform/pc32/i386/db_interface.c:148
#8  0xc051cad0 in trap (frame=0xd2bcd9f0) at
/usr/src/sys/platform/pc32/i386/trap.c:804
#9  0xc050aca6 in calltrap () at
/usr/src/sys/platform/pc32/i386/exception.s:783
#10 0xc0509fb5 in Debugger (msg=0x12 <Address 0x12 out of bounds>) at
cpufunc.h:73
#11 0xc02f002c in panic (fmt=0xc05aa1c0 "resource_list_release: resource
entry is not busy")
    at /usr/src/sys/kern/kern_shutdown.c:794
#12 0xc03028c3 in resource_list_release (rl=0x12, bus=0xcb2cb9d0,
child=0xcb2cbaf0, type=3, rid=16,
    res=0xcb28ce68) at /usr/src/sys/kern/subr_bus.c:1832
#13 0xc045e920 in pci_release_resource (dev=0x0, child=0xcb2cbaf0,
type=0, rid=0, r=0x0)
    at /usr/src/sys/bus/pci/pci.c:1932
#14 0xc0303cb7 in bus_release_resource (dev=0x0, type=3, rid=16,
r=0xcb28ce68) at bus_if.h:131
#15 0xc0172c3f in cbb_pci_attach (brdev=0xcb2cbaf0) at
/usr/src/sys/dev/pccard/pccbb/pccbb_pci.c:438
#16 0xc03017df in device_doattach (dev=0xcb2cbaf0) at device_if.h:39
#17 0xc03016f3 in device_probe_and_attach (dev=0xcb2cbaf0) at
/usr/src/sys/kern/subr_bus.c:1114
#18 0xc030306f in bus_generic_driver_added (dev=0xcb2cb9d0,
driver=0xd2c2a1b8)
    at /usr/src/sys/kern/subr_bus.c:2095
#19 0xc0300561 in devclass_add_driver (dc=0xc1641038, driver=0xd2c2a1b8)
at bus_if.h:71
#20 0xc0304556 in driver_module_handler (mod=0xcb28cbc8,
what=-758996552, arg=0xd2c2a1d0)
    at /usr/src/sys/kern/subr_bus.c:2636
#21 0xc02d1e38 in module_register_init (arg=0xd2c2a1e4) at
/usr/src/sys/kern/kern_module.c:110
#22 0xc02d24c4 in linker_file_sysinit (lf=0xd2ad3cd8) at
/usr/src/sys/kern/kern_linker.c:157
#23 0xc02d2779 in linker_load_file (filename=0xcb2e4c00 "if_ipw",
result=0xd2bcdcac)
    at /usr/src/sys/kern/kern_linker.c:286
#24 0xc02d30b8 in sys_kldload (uap=0xd2bcdcf8) at
/usr/src/sys/kern/kern_linker.c:744
#25 0xc051d430 in syscall2 (frame=0xd2bcdd40) at
/usr/src/sys/platform/pc32/i386/trap.c:1340
#26 0xc050ad45 in Xint0x80_syscall () at
/usr/src/sys/platform/pc32/i386/exception.s:872
#27 0x080487b8 in ?? ()
#28 0xbfbffb4c in ?? ()
#29 0x0000002f in ?? ()
#30 0x00000000 in ?? ()
#31 0x00000000 in ?? ()
#32 0x00000000 in ?? ()
#33 0x00000000 in ?? ()
#34 0x1a5cb000 in ?? ()
#35 0x0000000d in ?? ()
#36 0xc0652878 in intr_info_ary ()
#37 0xd2bcd8a0 in ?? ()
#38 0xd2bcd888 in ?? ()
#39 0xc8016e00 in ?? ()
#40 0xc02f7572 in lwkt_preempt (ntd=0xbfbffbd8, critpri=Cannot access
memory at address 0xbfbffb9c
) at /usr/src/sys/kern/lwkt_thread.c:882
Previous frame inner to this frame (corrupt stack?)
Do you need anything else?

Regards,

  Michael