[Panic] 6b3 + mdconfig -t malloc + unionfs + screeen

From: McLone (mclone_at_gmail.com)
Date: 09/04/05

  • Next message: Peter Jeremy: "Re: HZ option [Was: Re: custom kernel + if_xl + error]"
    Date: Sun, 4 Sep 2005 22:18:07 +0300
    To: freebsd-current@freebsd.org
    
    

    Hello.

    Today, when trying to make this crappy legacy nVidia driver to work,
    i managed to boot in single-user and i wanted screen(1) too.
    I was afraid kldload nvidia.ko will panic my box, so i was planning
    to do it while [most of] disks were mounted read-only.
    (Yes nvidia.ko v.7xxx paniced it finally)
    So i created following script, which _alone_ paniced my box.

    ...it loads snd_emu10k1 here... i really miss color beastie.
    OK boot -vs
    ...dmesg (verbose) goes here...
    ...enter path name or /bin/sh:
    # fsck -y
    # mount -at ufs -o ro
    # tcsh
    > cat /ramfs.sh
    #!/bin/sh
    swapon -a
    mount -uo rw /
    mkdir /mnt/ramfs 2>&- 1>&-
    mount -o ro -at ufs
    mount -ufo ro -at ufs # just to be sure
    umount /mnt/ramfs 2>&- 1>&-
    mdconfig -d -u 1
    mdconfig -a -t malloc -s 16m -u 1
    bsdlabel -w /dev/md1
    newfs -O 1 -m 0 /dev/md1a
    mount /dev/md1a /mnt/ramfs
    mount_unionfs /mnt/ramfs /var
    chmod 700 /tmp/screens/S-root
    > /ramfs.sh
    ...newfs output goes here, with GEOM messages...
    > pkg_info |grep screen
    screen-4.0.2_1 A multi-screen window manager
    > uname -a
    FreeBSD Droid.local 6.0-BETA3 FreeBSD 6.0-BETA3 #3: Sun Sep 0
    20:49:18 EEST 2005
    root@Droid.local:/usr/src/sys/i386/compile/Droid.debug i386
    > screen
    panic: can't fifo/vnode bypass -1
    KDB: enter: panic
    [thread pid 146 tid 100053 ]
    Stopped ad kdb_enter+0x30: leave
    db> trace
    Tracing pid 146 tid 100057 td 0xc1932af0
    kdb_enter(c07e4ddb,c085bb00,c07dc744,d52c8964,100) at panic+0x30
    panic(c07dc744,ffffffff,c07dc716,11b,c1782d00) at panic+0xd5
    fifo_open(d52c89e4,c1ae3dd0,d52c8bc4,c1a833d0,d52c8a10) at fifo_open+0x660
    VOP_OPEN_APV(c083bba0,d52c89e4,c1932af0,d52c8a54,1) at VOP_OPEN_APV+0xac
    union_open(d52c8a54,d52c8a04,d52c8bc4,0,d52c8b10) at union_open+0x8e
    VOP_OPEN_APV(c1b35240,d52c8a54,267,c1932af0,1) at VOP_OPEN_APV+0xac
    vn_open_cred(d52c8bc4,d52c8cc4,0,c1782d00,4) at vn_open_cred+0x472
    vn_open(d52c8bc4,d52c8cc4,0,4,c08a7018,4) at vn_open+0x33
    kern_open(c1932af0,808e220,0,5,0) at kern_open+0xc8
    open(c1932af0,d52c8d04,c,422,3) at open+0x36
    syscall(bfbf003b,3b,bfbf003b,4,3) at syscall+0x2c0
    Xint0x80_syscall() at Xint0x80_syscall+0x1f
    --- syscall(5, FreeBSD ELF32, open), eip = 0x28172e5f, esp =
    0xbfbfe00c, ebp = 0xbfbfe158 ---
    db> ps
    pid proc uid ppid pgrp flag stat wmesg wchan cmd
    146 c1a4720c 0 145 145 000002 [CPU 0] screen
    145 c1a47000 0 73 145 0004002 [SLP0 pause 0xc1a47034][SLP] screen
    138 c1921418 0 0 0 0000204 [SLP0 mdwait 0xc1a90000][SLP] md1
    73 c1a47418 0 54 73 0004002 [SLP0 pause 0xc1a4744c][SLP] tcsh
    54 c1a47624 0 1 54 0004002 [SLP0 wait 0xc1a47624][SLP] sh
    ...kernel threads here...
    Panic was copied by hand - i have no serial console; but i can set up one.
    Pleace advice me if i provided right information (or You need more).

    The dmesg is on http://mclone.org.ua/~mclone/dmesg.6b3.txt
    (they're from slightly older kernel; i'll reboot and replace ASAP)
    Kernel config is here: http://mclone.org.ua/~mclone/Droid.debug
    Nothing fancy (except verbose load) in /boot/loader.conf,
    and i have only CPUTYPE?=i686 and WITH_OPT_PPRO=yes
    in /etc/make.conf [coupled with various ports defines, that is].

    -- 
    wbr,                        |\      _,,,---,,_           dog bless ya!
    `                       Zzz /,`.-'`'    -.  ;-;;,_
    McLone at GMail dot com    |,4-  ) )-,_. ,\ (  `'-'
      net- and *BSD admin     '---''(_/--'  `-'\_)   ...sorry for translit
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    

  • Next message: Peter Jeremy: "Re: HZ option [Was: Re: custom kernel + if_xl + error]"

    Relevant Pages

    • Problems booting after new motherboard - label /1 not found
      ... I have been using FC4 as a MythTV box for 18 months or so now and all has been well. ... Booting the kernel. ... mount: error 2 mounting ext3 ... The other volume I have is the data volume and is JFS on LVM, this I guess is where the error occurred during mount so is probably not really an issue at the moment, as the boot and root partitions are fine. ...
      (Fedora)
    • Re: Diskless Debian PCs / Network Boot
      ... > Since the client is actually diskless, the boot process stops when the ... > kernel tries to mount a filesystem - that results in a kernel panic as ...
      (Debian-User)
    • odd problem with CDROM drive
      ... installation where the boot kernel detects and mounts the CD. ... it is then able to mount and examine the Knoppix CD. ...
      (Debian-User)
    • Re: 6.1 kernel unable to find /dev ?
      ... you seem to be having disk problems, it may just be due to the disk ... Or there is a bad kernel module in the mix ... Capture the boot output from both the working 6.0 kernel and your ... Mount the filesystems but don't mark them to be ...
      (freebsd-stable)
    • Cant Mount CF-Card on boot of 2.6.15 Kernel on EPIA - VFS: Cannot open root device
      ... Since this device can't boot from CF-Card I boot from network via PXELINUX. ... Now I want to change to kernel 2.6.15.4. ... Kernel panic - not syncinc: VFS: Unable to mount root fs on unknown-block ...
      (Linux-Kernel)