Kernel sources cvsupped yesterday.  The sound card is a Yamaha YMF 715
(non-PnP);  worked fine until about the end of April.  Now boot -v
shows:

/kernel: mss_detect - chip revision 0x0a
/kernel: ... try to identify the yamaha
/kernel: mss_detect() - Detected CS4231
/kernel: pcm0 at port 0x530 irq 5 drq 1 flags 0x15 on isa0
/kernel: mss_attach <mss>0 at 0x530 irq 5 dma 1:5 flags 0xa215
/kernel: device combination doesn't support shared irq3
/kernel: intr_connect(irq3) failed, result=-1
/kernel: device combination doesn't support shared irq4
/kernel: intr_connect(irq4) failed, result=-1
/kernel: device combination doesn't support shared irq5
/kernel: intr_connect(irq5) failed, result=-1
/kernel: device combination doesn't support shared irq7
/kernel: intr_connect(irq7) failed, result=-1
/kernel: device combination doesn't support shared irq9
/kernel: intr_connect(irq9) failed, result=-1
/kernel: device combination doesn't support shared irq12
/kernel: intr_connect(irq12) failed, result=-1
/kernel: device combination doesn't support shared irq14
/kernel: intr_connect(irq14) failed, result=-1
/kernel: device combination doesn't support shared irq15
/kernel: intr_connect(irq15) failed, result=-1

The same happens with snd0 instead of pcm.   It looks like it can't
register the interrupt handler - is it now supposed to be registered in
a different way (perhaps via nexus)?

Normal boot (without -v) doesn't show any error messages.  mpg123 starts
normally and just sits there doing nothing:

  UID   PID  PPID CPU PRI NI   VSZ  RSS WCHAN  STAT  TT       TIME
COMMAND
 1001  1159   256  52  -6  0  6464  716 dspwr  S+    p1    0:03.28
mpg123 test.mp3

until I press Ctrl-C, after which the following appears in
/var/log/messages

/kernel: How strange... mss_intr with no reason!
/kernel: tsleep returns 4

Just wondering whether anyone else had the same problem...  

Dean


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

  • pcm still broken in -cu... Dean Lombardo

Reply via email to