Date: Sat, 15 Jul 2000 14:00:02 -0700 (PDT) From: "Louis A. Mamakos" <louie@TransSys.COM> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/19945: panic: nexus_setup_intr: NULL irq resource with GUS PnP Message-ID: <200007152100.OAA86282@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/19945; it has been noted by GNATS.
From: "Louis A. Mamakos" <louie@TransSys.COM>
To: "Richard Seaman, Jr." <dick@tar.com>
Cc: tanimura@FreeBSD.ORG, FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/19945: panic: nexus_setup_intr: NULL irq resource with GUS PnP
Date: Sat, 15 Jul 2000 16:59:21 -0400
> I discovered the same thing here with my ancient Gus Pnp Pro. Looks like
> the culprit is the newmidi code, recently committed. I can boot
> with the following patch and play mp3's. Don't know if midi works or not.
I made the change you suggested, and loaded the snd_gusc.ko module. It
now doesn't panic, and now I see:
gusc0: <Gravis UltraSound Plug & Play PCM> at port 0x220-0x22f,0x320-0x327,0x32c-0x32f irq 11 drq 5,7 on isa0
gusc1: <Gravis UltraSound Plug & Play OPL> at port 0x38a-0x38b irq 9 drq 1 on isa0
gusc2: <Gravis UltraSound Plug & Play MIDI> at port 0x330-0x331 on isa0
There were no device, so I tried to load snd_pcm.ko, which caused
pcm0: <GUS CS4231> on gusc0
to be emitted on the console. However, the kldload process is hung,
waiting on "swwrt":
UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
0 79430 37865 4 -18 0 176 0 swwrt D+ p1 0:08.69 kldload snd_driver.ko
In this current state, the rest of the machine seems to be running just
fine. I'll try to add back:
device snd
device gusc
in my config, and see what happens at next boot. Currently, /dev/sndstat,
/dev/dsp, etc. don't seem to be present.
> BTW, sound playing doesn't work properly in all cases for me, in any case,
> without hacking the pcm/channel.c code a little. The problem is that DMA
> interrupts don't get generated. I'd be curious to know if you get interrupts
> when playing sounds (assuming the patch fixes things for you). You can test
> this by typing "vmstat -i" before and after playing something. Your card
> should show lots of interrupts (ie. at least hundreds according to Cameron
> Grant). I don't get any, either before or after the newmidi commits. Note,
> if your card has 0 interrupts, it won't even print with vmstat.
I'll give this a try and see what happens. The Gus PnP board was working
reasonably well in 5.0-current a couple of weeks ago (other than this
weird static thing that happens every so often.)
louie
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200007152100.OAA86282>