From: Svante Signell <srs@kth.se>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Clemens Ladisch <clemens@ladisch.de>,
619034@bugs.debian.org, alsa-devel@alsa-project.org,
613979-submitter@bugs.debian.org, linux-pci@vger.kernel.org
Subject: Bug#619034: [regression] "BUG: Unable to handle kernel paging request at ffffc90013cd8000" and no sound card recognized
Date: Thu, 14 Jul 2011 23:35:22 +0200 [thread overview]
Message-ID: <1310679322.2740.5.camel@x60> (raw)
In-Reply-To: <20110714182702.GA14014@elie>
On Thu, 2011-07-14 at 13:27 -0500, Jonathan Nieder wrote:
> Hi,
>
> Takashi Iwai wrote:
> >>> On Wed, 2011-03-30 at 15:13 +0200, Clemens Ladisch wrote:
> >>>>>>>>> Svante Signell wrote:
>
> >>>>>>>>>> During boot of kernel 2.6.38 (and 2.6.37) udev bugs out:
> >>>>>>>>>> Waiting for /dev to be fully populated
> >>>>>>>>>> BUG: Unable to handle kernel paging request at ffffc90013cd8000
> >>>>>>>>>> axz_probe+ ... [snd_hda_intel]
> >>>>>>>>>> ...lots of output lost...
> >>>>>>>>>> udevadm timeout 180 sec ...
> >>>>>>>>>> udevd[390]: worker [439] failed while handling
> >>>>>>>>>> '/devices/pci0000:80/0000:80:01.0'
> >>>>>>>>>>
> >>>>>>>>>> After the timeout the boot continues! Have not yet tested if sound is
> >>>>>>>>>> functional.
> [...]
> >>>> This is the azx_readw(chip, GCAP) in azx_create(); chip->remap_addr is
> >>>> 0xffffc90011c08000 which does look like a valid pointer, but isn't.
> [...]
> > 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.
> >
> > Any chance to bisect the kernel?
>
> Svante bisected it to v2.6.34-rc1~218^2~27 (x86/pci: Use
> resource_size_t in update_res, 2010-02-10) --- thanks. Which is
> pretty weird, since I think phys_addr_t on an amd64 machine (and hence
> resource_size_t) would be 64 bits, making that commit a no-op.
>
> Svante, more questions (sorry):
>
> - could you try booting b74fd238a9cf and b74fd238a9cf^ again
> (to make sure we haven't hit a heisenbug) and send the
> corresponding full dmesg and .config files?
I am very sorry but I don't have physical access to that box for a month
from now. However, something that might be more interesting is the
output of the second-to last message that was concerning
x86/pci/amd/.... I might get help to find that message in a few days.
next prev parent reply other threads:[~2011-07-14 21:35 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
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 ` Svante Signell [this message]
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=1310679322.2740.5.camel@x60 \
--to=srs@kth.se \
--cc=613979-submitter@bugs.debian.org \
--cc=619034@bugs.debian.org \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=jrnieder@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.