Re: Here's my most recent crash..

2002-07-24 Thread Anthony Jenkins

Craig Dooley wrote:

>I have the same problem.  heres my debug dump.  It seems to happen to me
>always when sound is playing.  I also get pages of warnings about pcm
>and could sleep with lock.
>
>/usr/src/sys/vm/uma_core.c:1332: could sleep with "pcm0:play:0" locked from 
>/usr/src/sys/dev/sound/pcm/dsp.c:690
>/usr/src/sys/vm/uma_core.c:1332: could sleep with "pcm0:play:0" locked from 
>/usr/src/sys/dev/sound/pcm/dsp.c:713
>/usr/src/sys/vm/uma_core.c:1332: could sleep with "pcm0:play:0" locked from 
>/usr/src/sys/dev/sound/pcm/sound.c:191
>and so on. actually it's flooded dmesg enough that I cant get to any
>useful information without going back a couple message.x's.  buildworld
>and kernel built from yesterdays sources.  
>
I've been looking into trying to fix the pcm code and it seems to be 
riddled with places where locks are held while sleepable memory 
allocations (the umacore.c:1332) are attempted.   I mostly run without 
sound for now until I can get a grasp on where I can get away with not 
locking.  Some locks are created and immediately locked, which to me 
only makes sense if the struct in which the lock exists is entered into 
a list where it's processed by some other KSE (I hope I'm not mangling 
these terms, I've only done Linux kernel work to-date).  Is the pcm code 
maintainer looking into this also?

>>
>>
-- 
Anthony Jenkins
http://www.mindspring.com/~abjenkins/




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



Re: Here's my most recent crash..

2002-07-24 Thread Anthony Jenkins

Alex Zepeda wrote:

[ kdbg output removed]

>The most applicable dmesg output I could find was:
>
>Memory modified after free 0xc215d000(8188)
>panic: Most recently used by none
>
I've gotten this same panic with a kernel+world cvsup'd from Sun Jul 21 
23:43 EDT, just got one a few minutes ago.  I'm in the kernel debugger 
since I haven't been able to get a dump to work since - well ever I 
guess :-/  so I'll echo Alex's offer to entertain any debugger requests. 
 Interesting thing is the apparent page fault I got when I tried 'ps' at 
the "db>" prompt:

lock order 
reversal   
 1st 0xc4758160 process lock (process lock) @ 
/usr/src/sys/kern/kern_exec.c:335   
 2nd 0xc0314880 filelist lock (filelist lock) @ 
/usr/src/sys/kern/kern_descrip.c:
/usr/src/sys/vm/uma_core.c:1332: could sleep with "process lock" locked 
from /usr/src/sys/kern/kern_exec.c:335
J/usr/src/sys/vm/uma_core.c:1332: could sleep with "process lock" locked 
from /usr/src/sys/kern/kern_exec.c:335
/usr/src/sys/vm/uma_core.c:1332: could sleep with "process lock" locked 
from /usr/src/sys/kern/kern_exec.c:335
Memory modified after free 0xc50e3d00(252)
panic: Most recently used by kqueue

cpuid = 0; lapic.id = 0100
Debugger("panic")
Stopped at  Debugger+0x46:  xchgl   %ebx,in_Debugger.0
db> ps
  pid   proc addruid  ppid  pgrp  flag  stat wmesg   wchan   cmd
80562 c4883558 de3fd0000 80533 0 0006002  New

Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id = 0100
fault virtual address   = 0x48
fault code  = supervisor read, page not present
instruction pointer = 0x8:0xc014111b
stack pointer   = 0x10:0xde26fa18
frame pointer   = 0x10:0xde26fa28
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 80561 (sh)
kernel: type 12 trap, code=0
Stopped at  Debugger+0x46:  xchgl   %ebx,in_Debugger.0
db> show locks
exclusive sleep mutex Giant r = 0 (0xc03179e0) locked @ 
/usr/src/sys/kern/kern_fork.c:119
db>  bt
No such command
db> trace
Debugger(c02e10fa) at Debugger+0x46
panic(c02f7408,c02ddda0,c02f73e0,c50e3d00,fc) at panic+0xde
mtrash_ctor(c50e3d00,100,0) at mtrash_ctor+0x4c
uma_zalloc_arg(c082dc00,0,0) at uma_zalloc_arg+0xff
malloc(dc,c0314580,0,c50ffe00,1) at malloc+0x68
fdcopy(c467de40,c50ffe34,0,c02de191,1c9) at fdcopy+0x61
fork1(c467de40,14,de26fce0,c03179e0,0) at fork1+0x6c7
fork(c467de40,de26fd14,0,0,202) at fork+0x2a
syscall(2f,2f,2f,80f23ac,80f23ac) at syscall+0x23c
syscall_with_err_pushed() at syscall_with_err_pushed+0x1b
--- syscall (2, FreeBSD ELF32, fork), eip = 0x8076bb3, esp = 0xbfbff30c, 
ebp = 0xbfbff328 ---
db>

I'm anxious to get something working, at least the dump+gdb/gdb52 
facility, so I can do some type of debugging; it's either that or kill 
the 150 day uptime FreeBSD-4.4 400MHz box and swap the two, but I was 
hoping to debug some SMP on the new box .

-- 
Anthony Jenkins
http://www.mindspring.com/~abjenkins/




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



Re: Here's my most recent crash..

2002-07-24 Thread Craig Dooley

I have the same problem.  heres my debug dump.  It seems to happen to me
always when sound is playing.  I also get pages of warnings about pcm
and could sleep with lock.

/usr/src/sys/vm/uma_core.c:1332: could sleep with "pcm0:play:0" locked from 
/usr/src/sys/dev/sound/pcm/dsp.c:690
/usr/src/sys/vm/uma_core.c:1332: could sleep with "pcm0:play:0" locked from 
/usr/src/sys/dev/sound/pcm/dsp.c:713
/usr/src/sys/vm/uma_core.c:1332: could sleep with "pcm0:play:0" locked from 
/usr/src/sys/dev/sound/pcm/sound.c:191
and so on. actually it's flooded dmesg enough that I cant get to any
useful information without going back a couple message.x's.  buildworld
and kernel built from yesterdays sources.  

dmesg:
Jul 24 18:09:49 filth kernel: FreeBSD 5.0-CURRENT #0: Tue Jul 16 22:17:19 EDT 2002
Jul 24 18:09:50 filth kernel: root@:/usr/obj/usr/src/sys/CUSTOM
Jul 24 18:09:50 filth kernel: Preloaded elf kernel "/boot/kernel/kernel" at 0xc04d3000.
Jul 24 18:09:50 filth kernel: Preloaded elf module "/boot/kernel/acpi.ko" at 
0xc04d30a8.
Jul 24 18:09:50 filth kernel: Timecounter "i8254"  frequency 1193182 Hz
Jul 24 18:09:50 filth kernel: Timecounter "TSC"  frequency 140473 Hz
Jul 24 18:09:50 filth kernel: CPU: AMD Athlon(tm) Processor (1000.04-MHz 686-class CPU)
Jul 24 18:09:50 filth kernel: Origin = "AuthenticAMD"  Id = 0x642 Stepping = 2
Jul 24 18:09:50 filth kernel: Features=0x183f9ff Jul 24 18:09:50 filth kernel: AMD 
Features=0xc044
Jul 24 18:09:50 filth kernel: real memory  = 536805376 (524224K bytes)
Jul 24 18:09:50 filth kernel: avail memory = 515616768 (503532K bytes)
Jul 24 18:09:50 filth kernel: Pentium Pro MTRR support enabled
Jul 24 18:09:50 filth kernel: Using $PIR table, 9 entries at 0xc00fde50
Jul 24 18:09:50 filth kernel: npx0:  on motherboard
Jul 24 18:09:50 filth kernel: npx0: INT 16 interface
Jul 24 18:09:50 filth kernel: acpi0:  on motherboard
Jul 24 18:09:50 filth kernel: acpi0: power button is handled as a fixed feature 
programming model.
Jul 24 18:09:50 filth kernel: Timecounter "ACPI-fast"  frequency 3579545 Hz
Jul 24 18:09:50 filth kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x 
4008-0x400b on acpi0
Jul 24 18:09:50 filth kernel: acpi_cpu0:  on acpi0
Jul 24 18:09:50 filth kernel: acpi_button0:  on acpi0
Jul 24 18:09:50 filth kernel: acpi_button1:  on acpi0
Jul 24 18:09:50 filth kernel: acpi_pcib0:  port 0x6000-0x607f,0 
x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0
Jul 24 18:09:50 filth kernel: pci0:  on acpi_pcib0
Jul 24 18:09:50 filth kernel: pcib1:  at device 1.0 on pci0
Jul 24 18:09:50 filth kernel: pci1:  on pcib1
Jul 24 18:09:50 filth kernel: pci1:  at device 0.0 (no driver attached)
Jul 24 18:09:50 filth kernel: isab0:  at device 7.0 on pci0
Jul 24 18:09:50 filth kernel: isa0:  on isab0
Jul 24 18:09:50 filth kernel: atapci0:  port 0xd00 
0-0xd00f at device 7.1 on pci0
Jul 24 18:09:50 filth kernel: atapci0: Correcting VIA config for southbridge data 
corruption bug
Jul 24 18:09:50 filth kernel: ata0: at 0x1f0 irq 14 on atapci0
Jul 24 18:09:50 filth kernel: ata1: at 0x170 irq 15 on atapci0
Jul 24 18:09:50 filth kernel: uhci0:  port 0xd400-0xd41f 
irq 5 at device 7.2 on pci0
Jul 24 18:09:50 filth kernel: usb0:  on uhci0
Jul 24 18:09:50 filth kernel: usb0: USB revision 1.0
Jul 24 18:09:50 filth kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 
1
Jul 24 18:09:50 filth kernel: uhub0: 2 ports with 2 removable, self powered
Jul 24 18:09:50 filth kernel: uhub0: port error, restarting port 1
Jul 24 18:09:50 filth kernel: uhub0: port error, giving up port 1
Jul 24 18:09:50 filth kernel: ums0: Microsoft Microsoft IntelliMouse Explorer, rev 
1.10/1.07, addr 2, iclass 3/1
Jul 24 18:09:50 filth kernel: ums0: 5 buttons and Z dir.
Jul 24 18:09:50 filth kernel: uhub0: port error, restarting port 2
Jul 24 18:09:50 filth kernel: uhub0: port error, giving up port 2
Jul 24 18:09:50 filth kernel: uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 
1.10/1.10, addr 3
Jul 24 18:09:50 filth kernel: uhub1: 4 ports with 4 removable, self powered
Jul 24 18:09:50 filth kernel: ugen0: Gravis GamePad Pro USB, rev 1.00/2.00, addr 4
Jul 24 18:09:50 filth kernel: uhci1:  port 0xd800-0xd81f 
irq 5 at device 7.3 on pci0
Jul 24 18:09:50 filth kernel: usb1:  on uhci1
Jul 24 18:09:50 filth kernel: usb1: USB revision 1.0
Jul 24 18:09:50 filth kernel: uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00 , 
addr 1
Jul 24 18:09:50 filth kernel: uhub2: 2 ports with 2 removable, self powered
Jul 24 18:09:50 filth kernel: uhub2: port error, restarting port 1
Jul 24 18:09:50 filth kernel: uhub2: port error, giving up port 1
Jul 24 18:09:50 filth kernel: uhub2: port error, restarting port 2
Jul 24 18:09:50 filth kernel: uhub2: port error, giving up port 2
Jul 24 18:09:50 filth kernel: pcm0:  port 0xdc00-0xdc1f irq 5 at 
device 8.0 on pci0
Jul 24 18:09:50 filth kernel: pci0:  at device 9.0 (no driver 
attached)
Jul 24 18:09:50 filth kernel: pci0:  at device 9.1 (no driver attach ed)

Here's my most recent crash..

2002-07-24 Thread Alex Zepeda

My system is down to one cpu (the first slot is appears to have eaten
itself and using it results in interesting smells from the power supply),
but I'm still running a SMP kernel.

Anything else I should probe with gdb?

FreeBSD blarf.homeip.net 5.0-CURRENT FreeBSD 5.0-CURRENT #3: Wed Jul 24 13:13:30 PDT 
2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/ZIPPY_SMP_WITNESS i386


GNU gdb 5.2 (FreeBSD)
Copyright 2002 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-portbld-freebsd5.0"...
IdlePTD at phsyical address 0x0056e000
initial pcb at physical address 0x004564c0
panicstr: bremfree: bp 0xc4209bd4 not locked
panic messages:
---
panic: Most recently used by none

cpuid = 0; lapic.id = 

syncing disks... panic: bremfree: bp 0xc4209bd4 not locked
cpuid = 0; lapic.id = 
Uptime: 3h13m48s
Dumping 127 MB
ata0: resetting devices ..
done
 16 32 48 64 80 96 112
---
#0  doadump () at ../../../kern/kern_shutdown.c:213
213 dumping++;
(kgdb) bt
#0  doadump () at ../../../kern/kern_shutdown.c:213
#1  0xc02220bd in boot (howto=260) at ../../../kern/kern_shutdown.c:345
#2  0xc0ce in poweroff_wait (junk=0xc03b0785, howto=-1004495916)
at ../../../kern/kern_shutdown.c:493
#3  0xc02551d7 in bremfree (bp=0xc03b0785) at ../../../kern/vfs_bio.c:633
#4  0xc025746e in getblk (vp=0xc1b1b000, blkno=196720, size=8192, slpflag=0, 
slptimeo=0) at ../../../kern/vfs_bio.c:2318
#5  0xc02552b7 in breadn (vp=0xc1b1b000, blkno=196720, size=8192, rablkno=0x0, 
rabsize=0x0, cnt=0, cred=0x0, bpp=0x0) at ../../../kern/vfs_bio.c:691
#6  0xc0255286 in bread (vp=0xc1b1b000, blkno=196720, size=8192, cred=0x0, 
bpp=0xc8a5cad0) at ../../../kern/vfs_bio.c:673
#7  0xc02f0894 in ffs_update (vp=0xc1df2a50, waitfor=0)
at ../../../ufs/ffs/ffs_inode.c:102
#8  0xc0301f1a in ffs_fsync (ap=0xc8a5cb48) at ../../../ufs/ffs/ffs_vnops.c:272
#9  0xc02ffee8 in ffs_sync (mp=0xc1b15800, waitfor=2, cred=0xc0bace80, 
td=0xc040f260) at vnode_if.h:463
#10 0xc0263bbe in sync (td=0xc040f260, uap=0x0)
at ../../../kern/vfs_syscalls.c:127
#11 0xc0221d2c in boot (howto=256) at ../../../kern/kern_shutdown.c:254
#12 0xc0ce in poweroff_wait (junk=0xc03cd8e8, howto=-1069754141)
at ../../../kern/kern_shutdown.c:493
#13 0xc032022a in mtrash_ctor (mem=0x100, size=0, arg=0x0)
at ../../../vm/uma_dbg.c:135
#14 0xc0320294 in mtrash_fini (mem=0xc215d000, size=8192)
at ../../../vm/uma_dbg.c:186
#15 0xc031e576 in zone_drain (zone=0xc0bbfcc0) at ../../../vm/uma_core.c:646
#16 0xc031ee8c in zone_foreach (zfunc=0xc031e2e0 )
at ../../../vm/uma_core.c:1167
#17 0xc031fd90 in uma_reclaim () at ../../../vm/uma_core.c:1980
#18 0xc031be72 in vm_pageout_scan (pass=0) at ../../../vm/vm_pageout.c:654
#19 0xc031cbea in vm_pageout () at ../../../vm/vm_pageout.c:1434
#20 0xc021303e in fork_exit (callout=0xc031c9c0 , arg=0x0, 
frame=0xc8a5cd48) at ../../../kern/kern_fork.c:861
(kgdb) quit

The most applicable dmesg output I could find was:

Memory modified after free 0xc215d000(8188)
panic: Most recently used by none

cpuid = 0; lapic.id = 

syncing disks... panic: bremfree: bp 0xc4209bd4 not locked
cpuid = 0; lapic.id = 
Uptime: 3h13m48s
Dumping 127 MB
ata0: resetting devices ..
done
 16 32 48 64 80 96 112


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