From: Paul Menzel <paulepanter@users.sourceforge.net>
To: alsa-devel@alsa-project.org
Cc: 619034@bugs.debian.org, 613979@bugs.debian.org, srs@kth.se
Subject: Re: Problems with snd_hda_intel in Linux kernel 2.6.38
Date: Tue, 24 May 2011 12:23:31 +0200 [thread overview]
Message-ID: <1306232611.4255.1.camel@mattotaupa> (raw)
In-Reply-To: <1306087019.5994.20.camel@mattotaupa>
[-- Attachment #1.1: Type: text/plain, Size: 1601 bytes --]
Am Sonntag, den 22.05.2011, 19:56 +0200 schrieb Paul Menzel:
> Am Montag, den 04.04.2011, 11:21 +0200 schrieb Svante Signell:
> > On Mon, 2011-04-04 at 11:12 +0200, Takashi Iwai wrote:
> > > At Mon, 04 Apr 2011 10:42:57 +0200,
> > > Svante Signell wrote:
> > > >
> > > > On Thu, 2011-03-31 at 00:42 +0200, Svante Signell wrote:
> > > > > On Wed, 2011-03-30 at 15:13 +0200, Clemens Ladisch wrote:
> > ...
> > > > Anything happening here with respect to this bug? How can I help
> > > > further? Booting with 2.6.32 all the time does not feel like a good
> > > > solution in long term.
> > >
> > > The point where it Oops implies that the problem isn't in the sound
> > > driver but rather in a breakage in a deeper level, either PCI core,
> > > x86 mm or ACPI/BIOS.
>
> The problem is still present with 2.6.39.
>
> > > Any chance to bisect the kernel?
> >
> > Never done that before. Is there a bisect HOWTO somewhere?
>
> Ben, I am sorry to bother you directly, but there are so many howtos on
> the Web, it would be great if you could point us to an “official” one,
> which has proofed itself. Or maybe you could write up a blog post. ;-)
>
> Anyway I did not find any information here.
>
> $ ls /usr/share/doc/linux-image-2.6.39-1-amd64/
> changelog.Debian.gz copyright
Svante, if you have some time, could you please try to follow the Wiki
page DebianKernel/GitBisect [1] in the Debian Wiki. Unfortunately I will
not have time until the beginning of July.
Thanks,
Paul
[1] http://wiki.debian.org/DebianKernel/GitBisect
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2011-05-24 10:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 10:24 Problems with snd_hda_intel in Linux kernel 2.6.38 Svante Signell
2011-03-29 10:31 ` Takashi Iwai
2011-03-29 10:58 ` Svante Signell
2011-03-29 11:10 ` Paul Menzel
2011-03-29 11:10 ` Takashi Iwai
2011-03-30 10:25 ` Svante Signell
2011-03-30 10:59 ` Takashi Iwai
2011-03-30 11:59 ` Svante Signell
2011-03-30 13:13 ` Clemens Ladisch
2011-03-30 22:42 ` Bug#613979: [alsa-devel] " Svante Signell
2011-04-04 8:42 ` Svante Signell
2011-04-04 9:12 ` Takashi Iwai
2011-04-04 9:21 ` Svante Signell
2011-05-22 17:56 ` Paul Menzel
2011-05-24 10:23 ` Paul Menzel [this message]
2011-07-14 18:27 ` [regression] "BUG: Unable to handle kernel paging request at ffffc90013cd8000" and no sound card recognized Jonathan Nieder
2011-07-14 21:35 ` Bug#619034: " Svante Signell
2011-07-14 22:12 ` Bug#613979: " Paul Menzel
2011-03-29 11:09 ` Problems with snd_hda_intel in Linux kernel 2.6.38 Paul Menzel
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=1306232611.4255.1.camel@mattotaupa \
--to=paulepanter@users.sourceforge.net \
--cc=613979@bugs.debian.org \
--cc=619034@bugs.debian.org \
--cc=alsa-devel@alsa-project.org \
--cc=srs@kth.se \
/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).