Re: new panic under -current

2002-01-18 Thread Michael Reifenberger

Hi,
the panic I think is for you Alfred.
The fsck related problems I describe below are for Kirk.

On Mon, 14 Jan 2002, Michael Reifenberger wrote:

 Date: Mon, 14 Jan 2002 23:16:26 +0100 (CET)
 From: Michael Reifenberger root@nihil
 To: Alfred Perlstein [EMAIL PROTECTED]
 Cc: FreeBSD-Current [EMAIL PROTECTED]
 Subject: Re: new panic under -current

 On Mon, 14 Jan 2002, Alfred Perlstein wrote:
 ...
  Can you cvsup and try to reproduce this?
Maybe.
Today I did:
- reducing my mainmem to 64M using hw.physmem=64M
- compiling and cleaning some packages garaphics/[mplayer|ogle] a few times
- starting X + kde
- drinking some coffee
- starting the kde browser
PENG

I somewhat suspect either procfs or linprocfs.
(I see many ?? in the backtrace and they are setup as modules)

My setup regarding this:
/dev - devfs
/proc - procfs
/tmp - md(4)
/compat/linux/dev - devfs
/compat/linux/proc - procfs

Ok, thats one thing.
The second is after reboot I go into singleuser and do:
- `fsck -p` (works OK)
- `mount /usr`
  ...mount pending error: blocks: 243, files 1...
  (Hmm. maybe a leftover from the panic)
- `reboot`
  ...
  syncing 2 2 2 2 2 2 2...
  giving up on 2 buffers
  ...
  (Why?)

After that I have to redo the fsck to get a clean filesystem.
I have this seen only after fsck's and after panics in conjunction
with 'mount pending errors'...
During normal shutdown no 'giving up' messages are occuring.

Any clues?

Bye!

Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS


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...
IdlePTD at phsyical address 0x0040f000
initial pcb at physical address 0x00281d40
panicstr: bwrite: buffer is not busy???
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x80
fault code  = supervisor write, page not present
instruction pointer = 0x8:0xc01a0ef4
stack pointer   = 0x10:0xc9630b84
frame pointer   = 0x10:0xc9630b9c
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 41965 (kdeinit)
trap number = 12
panic: page fault

syncing disks... panic: bwrite: buffer is not busy???
Uptime: 24m47s
pfs_vncache_unload(): 1 entries remaining

dumping to dev ad0s3b, offset 4063232
dump ata0: resetting devices .. done
64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 
35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 
5 4 3 2 1 
---
#0  dumpsys () at ../../../kern/kern_shutdown.c:492
492 if (!dodump)
(kgdb) #0  dumpsys () at ../../../kern/kern_shutdown.c:492
#1  0xc01665e0 in boot (howto=0x104) at ../../../kern/kern_shutdown.c:335
#2  0xc0166a2f in panic (fmt=0xc0238358 bwrite: buffer is not busy???) at 
../../../kern/kern_shutdown.c:634
#3  0xc0196a0f in bwrite (bp=0xc49b9604) at ../../../kern/vfs_bio.c:676
#4  0xc0196fc6 in bawrite (bp=0xc49b9604) at ../../../kern/vfs_bio.c:989
#5  0xc01ddb38 in ffs_fsync (ap=0xc9630a40) at ../../../ufs/ffs/ffs_vnops.c:217
#6  0xc01dc1ba in ffs_sync (mp=0xc1252800, waitfor=0x2, cred=0xc09c7f00, 
td=0xc0256fc4) at vnode_if.h:441
#7  0xc01a3e06 in sync (td=0xc0256fc4, uap=0x0) at ../../../kern/vfs_syscalls.c:669
#8  0xc0166241 in boot (howto=0x100) at ../../../kern/kern_shutdown.c:244
#9  0xc0166a2f in panic (fmt=0xc024b0de %s) at ../../../kern/kern_shutdown.c:634
#10 0xc0217bd0 in trap_fatal (frame=0xc9630b44, eva=0x80) at 
../../../i386/i386/trap.c:842
#11 0xc02178f9 in trap_pfault (frame=0xc9630b44, usermode=0x0, eva=0x80) at 
../../../i386/i386/trap.c:756
#12 0xc0217303 in trap (frame={tf_fs = 0x118, tf_es = 0x100010, tf_ds = 
0xc9670010, tf_edi = 0xc9606004, 
  tf_esi = 0xc9606004, tf_ebp = 0xc9630b9c, tf_isp = 0xc9630b70, tf_ebx = 0x0, 
tf_edx = 0x4, tf_ecx = 0xc9606004, 
  tf_eax = 0x4, tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0xc01a0ef4, tf_cs = 0x8, 
tf_eflags = 0x10282, 
  tf_esp = 0xc15fb0d0, tf_ss = 0xc9671d00}) at ../../../i386/i386/trap.c:426
#13 0xc01a0ef4 in vput (vp=0x0) at machine/atomic.h:144
#14 0xc135f45a in ?? ()
#15 0xc01a0eb7 in vrele (vp=0xc9671d00) at vnode_if.h:654
#16 0xc01aa12c in vn_close (vp=0xc9671d00, flags=0x1, cred=0xc15d5600, td=0xc9606004) 
at ../../../kern/vfs_vnops.c:260
#17 0xc01aaba6 in vn_closefile (fp=0xc157ca80, td=0xc9606004) at 
../../../kern/vfs_vnops.c:730
#18 0xc015106a in fdrop_locked (fp=0xc157ca80, td=0xc9606004) at 
../../../sys/file.h:229
#19 0xc01505b2 in fdrop (fp=0xc157ca80, td=0xc9606004

Re: new panic under -current

2002-01-14 Thread Sheldon Hearn



On Mon, 14 Jan 2002 20:43:11 +0100, Michael Reifenberger wrote:

 syncing disks... panic: bwrite: buffer is not busy???
 Uptime: 4h47m36s

I can get these pretty easily by using modules that are out of sync with
the kernel.

Ciao,
Sheldon.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: new panic under -current

2002-01-14 Thread John Baldwin


On 14-Jan-02 Sheldon Hearn wrote:
 
 
 On Mon, 14 Jan 2002 20:43:11 +0100, Michael Reifenberger wrote:
 
 syncing disks... panic: bwrite: buffer is not busy???
 Uptime: 4h47m36s
 
 I can get these pretty easily by using modules that are out of sync with
 the kernel.

That wasn't his real panic.  If you read teh whole log, a vrele() called from
fdrop_locked() did a vput(0x0), i.e. vput(NULL) which resulted in a page fault
panic.

-- 

John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: new panic under -current

2002-01-14 Thread Sheldon Hearn



On Mon, 14 Jan 2002 12:37:16 PST, John Baldwin wrote:

  I can get these pretty easily by using modules that are out of sync with
  the kernel.
 
 That wasn't his real panic.  If you read teh whole log, a vrele() called from
 fdrop_locked() did a vput(0x0), i.e. vput(NULL) which resulted in a page fault
 panic.

Oops, sorry.

Ciao,
Sheldon.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: new panic under -current

2002-01-14 Thread Alfred Perlstein

* Michael Reifenberger [EMAIL PROTECTED] [020114 11:47] wrote:
 Hi,
 a new panic while surfing under X:

Can you cvsup and try to reproduce this?

-Alfred

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: new panic under -current

2002-01-14 Thread Michael Reifenberger

On Mon, 14 Jan 2002, Alfred Perlstein wrote:
...
 Can you cvsup and try to reproduce this?
Do you have some new -current patches in mind which could affect the problem?
My -current is as of today (with some local patches from bde regarding
slice-handling which shouldn't be related here).
I've seen this type of panic a few times in the past but not reproducable
and somewhat infrequently.
See a previous post of mine with a few backtraces.

Bye!

Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message