linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Pockele <chrisp@newmail.net>
To: Samium Gromoff <_deepfire@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sound crashes in 2.4
Date: Fri, 24 Aug 2001 20:17:26 +0200	[thread overview]
Message-ID: <3B869A36.3E035F6D@newmail.net> (raw)
In-Reply-To: <E15aFMJ-0007GS-00@f8.mail.ru>

Samium Gromoff wrote:
> 
> > Both 2.4.8 and 2.4.9 have this problem (these are the ones I tried).
> > Btw on 2.2.x i get DMA (output) timeout errors (and broken sound).
> 
>   just to clarify: does 2.4.7 hangs?
>   (for me it doesnt, but everything >= 2.4.8 does)
> 
After i read in this list that some people do not experience
this problem in 2.4.7, I decided to give it a try.

2.4.7 crashes too, but behaves differently:

invalid operand: 0000
CPU:	0
EIP:	0010:[<c01f5ea0>]
EFLAGS:	00010046
eax: 00000000	ebx: c0248000	ecx: c086a260	edx: c086a260
esi: c0105170	edi: ffffe000	ebp: 0008e000	esp: c0249fd0
ds: 0018   es: 0018    ss: 0018
Process swapper (pid: 0, stackpage=c0249000)
Stack: c0105193 00000010 00000246 c01051f8 00001000 0009b800 c0105000
c0105027
       c024a84e 00000000 c025c340 c0100197
Call Trace: [<c0105193>] [<c01051f8>] [<c0105000>] [c0105027>]

Code: ff e9 46 ff ff ff 90 90 90 90 90 90 90 90 90 90 68 0a ff ff
Kernel panic: Attempted to kill the idle task!
In idle task - not syncing

(This was the 2nd time i tried it out ; the 1st time
it Oopsed (0002) but i don't have that message anymore)

  reply	other threads:[~2001-08-24 18:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-24 11:42 sound crashes in 2.4 Samium Gromoff
2001-08-24 18:17 ` Chris Pockele [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-24 12:49 Samium Gromoff
     [not found] <no.id>
2001-08-20 16:33 ` Alan Cox
2001-08-20 19:24   ` Chris Pockele
2001-08-20 23:08     ` Frank Davis
2001-08-24 11:01       ` Chris Pockele
2001-08-20 16:17 Chris Pockele

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3B869A36.3E035F6D@newmail.net \
    --to=chrisp@newmail.net \
    --cc=_deepfire@mail.ru \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).