Re: PATCH - MIDI on ice1724 - real-time kernel problem SOLVED(?)

From: Pavel Hofman <pavel.hofman@insite.cz>
To: "Martin Krüger" <m_a_krueger@gmx.de>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: PATCH - MIDI on ice1724 - real-time kernel problem SOLVED(?)
Date: Thu, 29 May 2008 18:14:10 +0200	[thread overview]
Message-ID: <483ED652.6020805@insite.cz> (raw)
In-Reply-To: <20080529140349.115520@gmx.net>

Martin Krüger wrote:
> Pavel Hofman schrieb:
>> Hi Martin,
>>
...............
> 
> Hi Pavel,
> 
> now i'm confused. I just compiled the current daily snapshot with
> "./configure --with-isapnp=no --with-sequencer=yes --with-oss=no 
> --with-debug=verbose --with-cards=ice1724".
> 
> That should give as much debug messages as i need, as i understood. I 
> get only one Message, telling me that ice1724 is using the defined 
> eeprom. After using the midi output port, there is no more message in 
> any log at all.

That is OK, it means the loop-detection code does not kick in, i.e. 
there is no problem with clearing interrupt status bits.

> 
> Due to this, it is really hard to understand the problem, for me it 
> looks like a complete freeze. If i would get "just" a heavy overload, 
> the numlock should still react within 10 minutes, and the cpu cooler 
> should be louder. Both of this should also happen during an irq flood, 
> if i understood that right.

My IRQ flood loaded the PC heavily, but I could still switch windows and 
move mouse around, with long delays. Yours looks like a real freeze.

> 
> Do you have any idea how to find out whats happening there? 

I just add debug printk's to major code points all the way down to 
bottom functions. It takes many compiling and rebooting (after freezes). 
  Unfortunately I do not know of any other way to hunt the bug down.

Good luck,

Pavel.

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel