linux-kernel - Re: kernel panic when sending MIDI sequencer events

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5h3bcpsar9.wl%tiwai@suse.de>
Date:	Tue, 25 Jul 2006 22:14:02 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	"Nathan Becker" <nathanbecker@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: kernel panic when sending MIDI sequencer events

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: <ffffffff8038da4d>{rtc_control+56}
> <ffffffff880b3063>{: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.


Takashi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/