Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	perex@suse.cz, alsa-devel@alsa-project.org,
	Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [1/2] 2.6.21-rc7: known regressions
Date: Mon, 16 Apr 2007 17:44:57 -0400	[thread overview]
Message-ID: <4623EE59.7090005@redhat.com> (raw)
In-Reply-To: <20070416003714.GL3691@stusta.de>

Adrian Bunk wrote:

> This email lists some known regressions in Linus' tree compared to 2.6.20.
> 
> Subject    : snd_intel8x0: divide error: 0000
> References : http://lkml.org/lkml/2007/3/5/252
> Submitter  : Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
> Status     : unknown
> 

Oops is in sound/pci/intel8x0.c::snd_intel8x0_update(), part of
the interrupt handler:

Line 751:

        ichdev->position += step * ichdev->fragsize1;
        if (! chip->in_measurement)
                ichdev->position %= ichdev->size;

ichdev->size is 0. Interrupt happened upon request_irq().

Does chip->in_measurement need to be reset because this is a
crashdump kernel?

  reply	other threads:[~2007-04-16 21:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0704151659570.5473@woody.linux-foundation.org>
2007-04-16  0:37 ` [1/2] 2.6.21-rc7: known regressions Adrian Bunk
2007-04-16 21:44   ` Chuck Ebbert [this message]
2007-04-17  0:14   ` Brandeburg, Jesse
2007-04-17  0:32     ` Dave Jones
2007-04-17  0:41       ` Jeff Garzik
2007-04-23 21:48 ` [1/3] 2.6.21-rc7: known regressions (v2) Adrian Bunk
2007-04-23 22:18   ` Greg KH
2007-04-24  9:32     ` Wolfgang Erig
2007-04-25  0:14       ` Greg KH
2007-04-25 23:40 ` 2.6.21-rc7: known regressions with patches Adrian Bunk

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=4623EE59.7090005@redhat.com \
    --to=cebbert@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=perex@suse.cz \
    /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