Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 May 1999 20:35:58 -0500 (CDT)
From:      Chris Dillon <cdillon@wolves.k12.mo.us>
To:        freebsd-stable@freebsd.org
Subject:   (again) panic: vinvalbuf: dirty bufs
Message-ID:  <Pine.BSF.4.10.9905272033440.74611-100000@mail.wolves.k12.mo.us>

next in thread | raw e-mail | index | archive | help

Heh... so this turns out to be the second message I send, rather
than the first.  Thats what I get for sending it to myself instead
of to the list.

Ok, I was able this time to get a useful backtrace on the dump (I
couldn't last time due to my own stupidity, forgetting to specify
symbol-file).

Anyway, this very reproducible panic occurs any time I:
dd if=/dev/rda0s1a of=/dev/da1s1a
and then either hit ctrl-C at any time, or just let it finish.

Anytime, anyplace, anywhere.  With or without softupdates.  In
single-user mode or not.  With or without all 256MB of RAM enumerated.
With or without anything but the root partition mounted.  Wether its
read-only or not.  Etc. Etc.

Yes, I know that's the wrong way to copy a filesystem, but that isn't
the point here. :-)

Interestingly enough, doing it the right way, i.e.:
dd if=/dev/rda0s1a of=/dev/rda1s1a
tells me "/dev/rda1s1a: read-only filesystem", which is pure bollocks.
Yes, /dev/rda1s1a does exist and its not trying to write a file into
/dev on a read-only /. :-)

Anyway, here's the output from GDB:

root@cheetah [/var/crash]# gdb -k
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd".
(kgdb) symbol-file /kernel.debug
Reading symbols from /kernel.debug...done.
(kgdb) exec-file kernel.0
(kgdb) core-file vmcore.0
IdlePTD 2613248
initial pcb at 21ee14
panicstr: vinvalbuf: dirty bufs
panic messages:
---
panic: vinvalbuf: dirty bufs

syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up

dumping to dev 20401, offset 581632
dump 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 
---
#0  boot (howto=256) at ../../kern/kern_shutdown.c:285
285			dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0  boot (howto=256) at ../../kern/kern_shutdown.c:285
#1  0xc0140aec in at_shutdown (
    function=0xc01f2da2 <__set_sysctl__kern_sym_sysctl___kern_maxvnodes+226>, 
    arg=0xc35a64c0, queue=-1017486144) at ../../kern/kern_shutdown.c:446
#2  0xc01649d8 in vinvalbuf (vp=0xc35a64c0, flags=1, cred=0xc0864a80, 
    p=0xc35ac700, slpflag=0, slptimeo=0) at ../../kern/vfs_subr.c:599
#3  0xc0171730 in spec_close (ap=0xc3603e84)
    at ../../miscfs/specfs/spec_vnops.c:648
#4  0xc01aa90e in ufsspec_close (ap=0xc3603e84)
    at ../../ufs/ufs/ufs_vnops.c:1872
#5  0xc01aae2d in ufs_vnoperatespec (ap=0xc3603e84)
    at ../../ufs/ufs/ufs_vnops.c:2317
#6  0xc016b320 in vn_close (vp=0xc35a64c0, flags=3, cred=0xc0864a80, 
    p=0xc35ac700) at vnode_if.h:191
#7  0xc016bad9 in vn_closefile (fp=0xc08ccd40, p=0xc35ac700)
    at ../../kern/vfs_vnops.c:559
#8  0xc0139680 in closef (fp=0xc08ccd40, p=0xc35ac700)
    at ../../kern/kern_descrip.c:1065
#9  0xc0139477 in fdfree (p=0xc35ac700) at ../../kern/kern_descrip.c:977
#10 0xc013a963 in exit1 (p=0xc35ac700, rv=256) at ../../kern/kern_exit.c:199
#11 0xc013a7cc in exit1 (p=0xc35ac700, rv=-1017102444)
    at ../../kern/kern_exit.c:104
#12 0xc01cfad3 in syscall (frame={tf_es = 39, tf_ds = 39, 
      tf_edi = -1077944924, tf_esi = 0, tf_ebp = -1077945124, 
---Type <return> to continue, or q <return> to quit---
      tf_isp = -1017102364, tf_ebx = -1, tf_edx = 64, tf_ecx = -66, 
      tf_eax = 1, tf_trapno = 0, tf_err = 2, tf_eip = 134561160, tf_cs = 31, 
      tf_eflags = 582, tf_esp = -1077945140, tf_ss = 39})
    at ../../i386/i386/trap.c:1100
#13 0xc01c6fcc in Xint0x80_syscall ()
#14 0x8049835 in ?? ()
#15 0xbfbfdfdc in ?? ()
#16 0x8048b65 in ?? ()
#17 0x80480e9 in ?? ()
(kgdb) quit


And the dmesg output (boot -v ends up causing much of the first part
of dmesg to be severely truncated, even in /var/run/dmesg.boot, so
here's the non--v version):

Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
	The Regents of the University of California. All rights reserved.
FreeBSD 3.2-STABLE #0: Thu May 27 19:32:28 CDT 1999
    root@cheetah.wolves.k12.mo.us:/usr/src/sys/compile/CHEETAH
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 498830848 Hz
CPU: Pentium III (498.83-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x672  Stepping=2
  Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,<b24>,<b25>>
real memory  = 16777216 (16384K bytes)
avail memory = 14082048 (13752K bytes)
Preloaded elf kernel "kernel" at 0xc0274000.
Probing for devices on PCI bus 0:
chip0: <Host to PCI bridge (vendor=1166 device=0007)> rev 0x04 on pci0.0.0
chip1: <Ross (?) host to PCI bridge> rev 0x02 on pci0.0.1
vga0: <ATI model 4756 graphics accelerator> rev 0x7a on pci0.5.0
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x05 int a irq 12 on pci0.7.0
fxp0: Ethernet address 00:a0:c9:de:9e:be
fxp1: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x05 int a irq 5 on pci0.8.0
fxp1: Ethernet address 00:08:c7:fb:03:1d
fxp2: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x05 int a irq 9 on pci0.9.0
fxp2: Ethernet address 00:08:c7:f3:ee:b8
chip2: <PCI to ISA bridge (vendor=1166 device=0200)> rev 0x4d on pci0.15.0
chip3: <Host to PCI bridge (vendor=1166 device=0007)> rev 0x04 on pci0.17.0
chip4: <Ross (?) host to PCI bridge> rev 0x02 on pci0.17.1
Probing for devices on PCI bus 1:
ncr0: <ncr 53c875 fast20 wide scsi> rev 0x14 int a irq 15 on pci1.4.0
ncr1: <ncr 53c875 fast20 wide scsi> rev 0x14 int b irq 7 on pci1.4.1
fxp3: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x05 int a irq 10 on pci1.6.0
fxp3: Ethernet address 00:08:c7:f3:d4:39
fxp4: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x05 int a irq 11 on pci1.7.0
fxp4: Ethernet address 00:08:c7:f3:cf:2c
fxp5: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x05 int a irq 3 on pci1.8.0
fxp5: Ethernet address 00:50:8b:08:f2:be
chip5: <PCI to PCI bridge (vendor=1011 device=0024)> rev 0x03 on pci1.9.0
Probing for devices on PCI bus 2:
fxp6: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x05 int a irq 12 on pci2.4.0
fxp6: Ethernet address 00:08:c7:07:b2:95
fxp7: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x05 int a irq 12 on pci2.5.0
fxp7: Ethernet address 00:08:c7:07:b2:96
Probing for devices on PCI bus 3:
Probing for PnP devices:
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <16 virtual consoles, flags=0x0>
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
wdc1 not found at 0x170
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
npx0 on motherboard
npx0: INT 16 interface
IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging limited to 100 packets/entry
DUMMYNET initialized (990504)
Waiting 15 seconds for SCSI devices to settle
changing root device to da0s1a
da0 at ncr0 bus 0 target 0 lun 0
da0: <COMPAQ HB00931931 03F1> Fixed Direct Access SCSI-3 device 
da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled
da0: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C)
da2 at ncr0 bus 0 target 2 lun 0
da2: <COMPAQ HB00931931 03F1> Fixed Direct Access SCSI-3 device 
da2: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled
da2: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C)
da1 at ncr0 bus 0 target 1 lun 0
da1: <COMPAQ HB00931931 03F1> Fixed Direct Access SCSI-3 device 
da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled
da1: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C)
WARNING: / was not properly dismounted
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates

uname -a output:
FreeBSD cheetah.wolves.k12.mo.us 3.2-STABLE FreeBSD 3.2-STABLE #0: Thu May 27 19:32:28     root@cheetah.wolves.k12.mo.us:/usr/src/sys/compile/CHEETAH i386

Very recent 3.2-STABLE world and kernel (as of a few hours ago).

If anyone needs me to test any fixes they might have, please tell me
NOW before I put the box into production, and it therefore becomes
unavailable for testing.

The debugging kernel image and appropriate core files are available
upon request (for both this and the other crash I just sent a message 
about).


-- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net
   FreeBSD: The fastest and most stable server OS on the planet.
   For Intel x86 and Alpha architectures (SPARC under development).
   ( http://www.freebsd.org )

   "One should admire Windows users.  It takes a great deal of
    courage to trust Windows with your data."




-- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net
   FreeBSD: The fastest and most stable server OS on the planet.
   For Intel x86 and Alpha architectures (SPARC under development).
   ( http://www.freebsd.org )

   "One should admire Windows users.  It takes a great deal of
    courage to trust Windows with your data."



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9905272033440.74611-100000>