From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030189AbWGYUSO (ORCPT ); Tue, 25 Jul 2006 16:18:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964853AbWGYUSN (ORCPT ); Tue, 25 Jul 2006 16:18:13 -0400 Received: from ns2.suse.de ([195.135.220.15]:33982 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S964852AbWGYUSN (ORCPT ); Tue, 25 Jul 2006 16:18:13 -0400 Date: Tue, 25 Jul 2006 22:18:12 +0200 Message-ID: From: Takashi Iwai To: "Nathan Becker" Cc: linux-kernel@vger.kernel.org Subject: Re: kernel panic when sending MIDI sequencer events In-Reply-To: References: <2151339d0607251301i716f6a01i17b07de5e7905ffc@mail.gmail.com> User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 MULE XEmacs/21.5 (beta25) (eggplant) (+CVS-20060326) (i386-suse-linux) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org At Tue, 25 Jul 2006 22:14:02 +0200, I wrote: > > At Tue, 25 Jul 2006 13:01:49 -0700, > Nathan Becker wrote: > > > > Hi, > > > > I'm getting a kernel panic when a program sends a MIDI sequencer > > event. Seems to happen in all recent kernels I've tested. Currently > > I'm using 2.6.17.7 on an AMD X2 4800+ Nforce4 (Gigabyte K8NXP-SLI) > > system running Slamd64 10.1 in 64-bit mode. I'm using the ALSA sound > > modules for intel8x0 for the motherboard sound chip. I should mention > > that PCM sound works fine, no crashes and sounds OK. If I understand > > correctly, the intel8x0 does not directly support MIDI sound. I guess > > this means I need to install Timidity or something to make MIDI sound > > actually work, but this is of secondary concern. My primary concern > > is that when programs send a MIDI event, it crashes the whole system. > > > > Here is an excerpt from the error message as I've copied it from the console: > > > > Call Trace: {rtc_control+56} > > {:snd_rtctimer:rtctimer_start+28} > > > > ...more stuff like that. Also mentions snd_seq:snd_seq_control_queue+153 > > snd_seq:snd_seq_deliver_single_event+281 > > snd_seq:snd_seq_deliver_event+337 > > snd_seq:queueptr+60 > > snd_seq_client_enqueue_event+119 > > Well, it'd be helpful if you can paste more, at least, what kind of > error it is. Also, please write what you exactly did, how to > reproduce it on other one's system. > > > > Any help would be greatly appreciated. Please cc me directly. > > A possibly simple workaround is to disable CONFIG_SND_RTCTIMER. Oh, also, showing your kernel config is good as a start, too :) Takashi