Re: sb driver oops in 2.4.0-test8 [BUG found]
Today, in a message to Joachim Achtzehnter, Paul Laufer wrote: > > I already sent Linus a patch. It is not test9-pre1. I have attached it > here for you and others on lkml. Please let me know how it works for > you. Patch applies to test7 through test8, and test9-pre1. Yes, this fixes the problem. Thanks, Joachim -- work: [EMAIL PROTECTED] (http://www.realtimeint.com) private: [EMAIL PROTECTED] (http://www.kraut.bc.ca) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: sb driver oops in 2.4.0-test8 [BUG found]
Today, in a message to Joachim Achtzehnter, Paul Laufer wrote: I already sent Linus a patch. It is not test9-pre1. I have attached it here for you and others on lkml. Please let me know how it works for you. Patch applies to test7 through test8, and test9-pre1. Yes, this fixes the problem. Thanks, Joachim -- work: [EMAIL PROTECTED] (http://www.realtimeint.com) private: [EMAIL PROTECTED] (http://www.kraut.bc.ca) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: sb driver oops in 2.4.0-test8 [BUG found]
Here is some more info about this problem: The trouble is caused by the driver's attempt to find multiple soundblaster cards. Specifying multiple=0 as a module option for sb fixes the problem. Note, however, this quote from the Documentation/Soundblaster file: multiple=0 Set to disable detection of multiple Soundblaster cards. Consider it a bug if this option is needed, and send in a report. So, this is a bug then! The function init_sb in drivers/sound/sb_card.c contains a detection loop from card=0..SB_CARDS_MAX. This doesn't work, however, because the second time around it uses the same module parameters (DMA/IRQ/IO) and hence attempts to detect the exact same card instance. The result is not only that no second card is found, which is ok in my case, but the originally detected card is screwed up as well. I'm not sufficiently familiar with the driver to know what it should do. Could it be that once it can't find a card via isapnp it should bail out from this loop? Joachim -- work: [EMAIL PROTECTED] (http://www.realtimeint.com) private: [EMAIL PROTECTED] (http://www.kraut.bc.ca) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: sb driver oops in 2.4.0-test8 [BUG found]
Here is some more info about this problem: The trouble is caused by the driver's attempt to find multiple soundblaster cards. Specifying multiple=0 as a module option for sb fixes the problem. Note, however, this quote from the Documentation/Soundblaster file: multiple=0 Set to disable detection of multiple Soundblaster cards. Consider it a bug if this option is needed, and send in a report. So, this is a bug then! The function init_sb in drivers/sound/sb_card.c contains a detection loop from card=0..SB_CARDS_MAX. This doesn't work, however, because the second time around it uses the same module parameters (DMA/IRQ/IO) and hence attempts to detect the exact same card instance. The result is not only that no second card is found, which is ok in my case, but the originally detected card is screwed up as well. I'm not sufficiently familiar with the driver to know what it should do. Could it be that once it can't find a card via isapnp it should bail out from this loop? Joachim -- work: [EMAIL PROTECTED] (http://www.realtimeint.com) private: [EMAIL PROTECTED] (http://www.kraut.bc.ca) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
sb driver oops in 2.4.0-test8
Didn't have this problem with 2.4.0-test2, but after upgrading from test2 to test8 the sb driver encounters this error: Sep 12 20:49:52 wizard kernel: SB 3.01 detected OK (220) Sep 12 20:49:52 wizard kernel: SB DSP version is just 3.01 which means that your card is Sep 12 20:49:52 wizard kernel: several years old (8 bit only device) or alternatively the sound driver Sep 12 20:49:52 wizard kernel: is incorrectly configured. Sep 12 20:49:52 wizard kernel: sb: I/O region in use. This is the first sign of trouble. With test2 the message about this being an old SoundBlaster is usually followed by this: Sep 11 23:12:28 wizard kernel: YM3812 and OPL-3 driver Copyright (C) by Hannu Savolainen, Rob Hooft 1993-1996 Here is the rest of the oops with test8: Sep 12 20:49:52 wizard kernel: printing eip: Sep 12 20:49:52 wizard kernel: c681c45d Sep 12 20:49:52 wizard kernel: Oops: Sep 12 20:49:52 wizard kernel: CPU:0 Sep 12 20:49:52 wizard kernel: EIP:0010:[soundcore:unregister_sound_synth +137/884] Sep 12 20:49:52 wizard kernel: EFLAGS: 00010286 Sep 12 20:49:52 wizard kernel: eax: c6829e00 ebx: c118ae60 ecx: edx: Sep 12 20:49:52 wizard kernel: esi: c5f9db40 edi: ebp: esp: c5bd3f08 Sep 12 20:49:52 wizard kernel: ds: 0018 es: 0018 ss: 0018 Sep 12 20:49:52 wizard kernel: Process aumix (pid: 68, stackpage=c5bd3000) Sep 12 20:49:52 wizard kernel: Stack: c5f9db40 c5c4bdc0 c5fa74e0 c5f9db40 c5c4bdc0 c5fa74e0 Sep 12 20:49:52 wizard kernel:72616863 6a616d2d 312d726f c5e70034 ffeb c0128fb5 c5c4bdc0 c5f9db40 Sep 12 20:49:52 wizard kernel:c5f9db40 c5c4bdc0 c01282b0 c5c4bdc0 c5f9db40 0002 0804ddb4 Sep 12 20:49:52 wizard kernel: Call Trace: [chrdev_open+65/84] [dentry_open+192/332] [filp_open+74/84] [sys_open+56/180] [system_call+51/64] Sep 12 20:49:52 wizard kernel: Code: 8b 10 85 d2 74 1d 52 e8 2f 90 8f f9 83 c4 04 85 c0 74 14 8b It seems that subsequently applications that use sound hang for a while and then continue without sound, producing more messages like the above. This is an ancient 8bit original Soundblaster Pro board. But as I said, it works with test2 and earlier kernels. Joachim -- work: [EMAIL PROTECTED] (http://www.realtimeint.com) private: [EMAIL PROTECTED] (http://www.kraut.bc.ca) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
sb driver oops in 2.4.0-test8
Didn't have this problem with 2.4.0-test2, but after upgrading from test2 to test8 the sb driver encounters this error: Sep 12 20:49:52 wizard kernel: SB 3.01 detected OK (220) Sep 12 20:49:52 wizard kernel: SB DSP version is just 3.01 which means that your card is Sep 12 20:49:52 wizard kernel: several years old (8 bit only device) or alternatively the sound driver Sep 12 20:49:52 wizard kernel: is incorrectly configured. Sep 12 20:49:52 wizard kernel: sb: I/O region in use. This is the first sign of trouble. With test2 the message about this being an old SoundBlaster is usually followed by this: Sep 11 23:12:28 wizard kernel: YM3812 and OPL-3 driver Copyright (C) by Hannu Savolainen, Rob Hooft 1993-1996 Here is the rest of the oops with test8: Sep 12 20:49:52 wizard kernel: printing eip: Sep 12 20:49:52 wizard kernel: c681c45d Sep 12 20:49:52 wizard kernel: Oops: Sep 12 20:49:52 wizard kernel: CPU:0 Sep 12 20:49:52 wizard kernel: EIP:0010:[soundcore:unregister_sound_synth +137/884] Sep 12 20:49:52 wizard kernel: EFLAGS: 00010286 Sep 12 20:49:52 wizard kernel: eax: c6829e00 ebx: c118ae60 ecx: edx: Sep 12 20:49:52 wizard kernel: esi: c5f9db40 edi: ebp: esp: c5bd3f08 Sep 12 20:49:52 wizard kernel: ds: 0018 es: 0018 ss: 0018 Sep 12 20:49:52 wizard kernel: Process aumix (pid: 68, stackpage=c5bd3000) Sep 12 20:49:52 wizard kernel: Stack: c5f9db40 c5c4bdc0 c5fa74e0 c5f9db40 c5c4bdc0 c5fa74e0 Sep 12 20:49:52 wizard kernel:72616863 6a616d2d 312d726f c5e70034 ffeb c0128fb5 c5c4bdc0 c5f9db40 Sep 12 20:49:52 wizard kernel:c5f9db40 c5c4bdc0 c01282b0 c5c4bdc0 c5f9db40 0002 0804ddb4 Sep 12 20:49:52 wizard kernel: Call Trace: [chrdev_open+65/84] [dentry_open+192/332] [filp_open+74/84] [sys_open+56/180] [system_call+51/64] Sep 12 20:49:52 wizard kernel: Code: 8b 10 85 d2 74 1d 52 e8 2f 90 8f f9 83 c4 04 85 c0 74 14 8b It seems that subsequently applications that use sound hang for a while and then continue without sound, producing more messages like the above. This is an ancient 8bit original Soundblaster Pro board. But as I said, it works with test2 and earlier kernels. Joachim -- work: [EMAIL PROTECTED] (http://www.realtimeint.com) private: [EMAIL PROTECTED] (http://www.kraut.bc.ca) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
