Re: pcm0 + rl0 in the same irq causes panic

Hello,

Here is a backtrace of the panic:

blackpearl# kgdb kernel.debug /var/crash/vmcore.0
kgdb: kvm_nlist(_stopped_cpus):
kgdb: kvm_nlist(_stoppcbs):
[GDB will not be able to debug user-mode threads:
/usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 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-marcel-freebsd".

Unread portion of the kernel message buffer:
pcm0: PCMDIR_PLAY: Stream setup nid=2 fmt=0x00000011
<2>NMI ISA b0, EISA ff
<2>RAM parity error, likely hardware failure.

Fatal trap 19: non-maskable interrupt trap while in kernel mode
instruction pointer     = 0x20:0xc5798eaa
stack pointer           = 0x28:0xe50e6b70
frame pointer           = 0x28:0xe50e6bc4
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, IOPL = 0
current process         = 1211 (artsd)
trap number             = 19
panic: non-maskable interrupt trap
Uptime: 1h31m2s
Dumping 1014 MB (2 chunks)
  chunk 0: 1MB (159 pages) ... ok
  chunk 1: 1014MB (259456 pages) 998 982 966 950 934 918 902 886 870
854 838 822 806 790 774 758 742 726 710 694 678 662 646 630 614 598
582 566 550 534 518 502 486 470 454 438 422 406 390 374 358 342 326
310 294 278 262 246 230 214 198 182 166 150 134 118 102 86 70 54 38 22
6

#0  doadump () at pcpu.h:165
165             __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) where
#0  doadump () at pcpu.h:165
#1  0xc05f34cc in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2  0xc05f3819 in panic (fmt=0xc0816cc2 "%s") at
/usr/src/sys/kern/kern_shutdown.c:565
#3  0xc07d78cc in trap_fatal (frame=0xe50e6b30, eva=0) at
/usr/src/sys/i386/i386/trap.c:837
#4  0xc07d72d2 in trap (frame=
      {tf_fs = -452067320, tf_es = 40, tf_ds = -993853400, tf_edi = 0,
tf_esi = 0, tf_ebp = -452039740, tf_isp = -452039844, tf_ebx =
1039527936, tf_edx = -994638720, tf_ecx = -988999680, tf_eax = 2,
tf_trapno = 19, tf_err = 0, tf_eip = -981889366, tf_cs = 32, tf_eflags
= 2097811, tf_esp = -982862592, tf_ss = 0}) at
/usr/src/sys/i386/i386/trap.c:632
#5  0xc07c26ca in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#6  0xc5798eaa in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb)


On 10/1/06, Alexandre Vieira <nullpt_at_gmail.com> wrote:
> Hello,
>
> I've tried to run artsd on the console and whenever I have snd_hda
> loaded it panics.
>
> arts-1.5.4,1        Audio system for the KDE integrated X11 desktop
>
> FreeBSD blackpearl.mshome.net 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE
> #1: Sun Oct  1 01:01:24 WEST 2006
> alex_at_blackpearl:/usr/obj/usr/src/sys/blackpearl  i386
>
>
> On 10/1/06, Ariff Abdullah <ariff_at_freebsd.org> wrote:
> > On Sun, 01 Oct 2006 17:03:43 -0400
> > Michael Butler <imb_at_protected-networks.net> wrote:
> > >
> > > Ariff Abdullah wrote:
> > > > Try running artsd while in console and see whether its panicking.
> > > > Then, play simple .wav file using artsplay.
> > >
> > > Simply starting artsd is enough to kill my laptop yet I can use
> > > mpg123 in a konsole window w/o issue,
> > >
> >
> > I cannot reproduce this panic running artsd. artsplay, artsdsp both
> > running fine.
> >
> > I'm using artsd package from
> >
> ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.2-BETA1/packages/audio/arts-1.5.4,1.tbz
> >
> >
> > I guess it is time for both of you to send us panic backtrace.
> >
> >
> >
> > --
> > Ariff Abdullah
> > FreeBSD
> >
> > ... Recording in stereo is obviously too advanced
> >     and confusing for us idiot ***** users :P ........
> >
> >
>
>
> --
> Alexandre Vieira - nullpt_at_gmail.com
>


-- 
Alexandre Vieira - nullpt_at_gmail.com