From: Alnie <alnieb@yahoo.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Issues w/ Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG
Date: Wed, 25 Feb 2015 00:21:15 -0800 [thread overview]
Message-ID: <54ED85FB.9060601@yahoo.com> (raw)
In-Reply-To: <s5hh9ua5sbb.wl-tiwai@suse.de>
On 02/25/2015 12:06 AM, Takashi Iwai wrote:
> At Tue, 24 Feb 2015 23:55:25 -0800,
> Alnie wrote:
>>
>> [ 2619.199658] pciehp 0000:00:1c.3:pcie04: Card not present on Slot(3)
>> [ 2619.199666] pciehp 0000:00:1c.3:pcie04: slot(3): Link Down event
>> [ 2619.199674] pciehp 0000:00:1c.3:pcie04: Link Down event ignored on
>> slot(3): already powering off
>> [ 2619.199911] pci_bus 0000:06: busn_res: [bus 06-0c] is released
>> [ 2620.757928] pciehp 0000:00:1c.3:pcie04: Card present on Slot(3)
>> [ 2620.767950] pciehp 0000:00:1c.3:pcie04: slot(3): Link Up event
>> [ 2620.767985] pciehp 0000:00:1c.3:pcie04: Link Up event ignored on
>> slot(3): already powering on
>
> pciehp reacted power off and on here, and...
>
>> [ 2620.876160] pci 0000:05:00.0: [1102:7006] type 01 class 0x060400
>> [ 2620.876426] pci 0000:05:00.0: supports D1 D2
>> [ 2620.876719] pci 0000:05:00.0: bridge configuration invalid ([bus
>> 00-00]), reconfiguring
>> [ 2620.876928] pci_bus 0000:06: busn_res: can not insert [bus 06-ff]
>> under [bus 05-0c] (conflicts with (null) [bus 05-0c])
>
> .... and something failed here for the PCI bridge device.
>
>> [ 2620.876967] pci 0000:06:00.0: [1102:0009] type 00 class 0x040300
>> [ 2620.877013] pci 0000:06:00.0: reg 0x10: [mem 0x00000000-0x00003fff]
>> [ 2620.877203] pci 0000:06:00.0: supports D1 D2
>> [ 2620.877443] pci 0000:05:00.0: PCI bridge to [bus 06-ff]
>> [ 2620.877462] pci 0000:05:00.0: bridge window [io 0x0000-0x0fff]
>> [ 2620.877474] pci 0000:05:00.0: bridge window [mem 0x00000000-0x000fffff]
>> [ 2620.877492] pci 0000:05:00.0: bridge window [mem
>> 0x00000000-0x000fffff 64bit pref]
>> [ 2620.877500] pci_bus 0000:06: busn_res: [bus 06-ff] end is updated to 06
>> [ 2620.877559] pci 0000:05:00.0: BAR 14: assigned [mem
>> 0xf4300000-0xf43fffff]
>> [ 2620.877568] pci 0000:05:00.0: BAR 15: assigned [mem
>> 0xf4000000-0xf40fffff 64bit pref]
>> [ 2620.877574] pci 0000:05:00.0: BAR 13: assigned [io 0x2000-0x2fff]
>> [ 2620.877582] pci 0000:06:00.0: BAR 0: assigned [mem 0xf4300000-0xf4303fff]
>> [ 2620.877595] pci 0000:05:00.0: PCI bridge to [bus 06]
>> [ 2620.877603] pci 0000:05:00.0: bridge window [io 0x2000-0x2fff]
>> [ 2620.877618] pci 0000:05:00.0: bridge window [mem 0xf4300000-0xf43fffff]
>> [ 2620.877630] pci 0000:05:00.0: bridge window [mem
>> 0xf4000000-0xf40fffff 64bit pref]
>> [ 2620.877647] pcieport 0000:00:1c.3: PCI bridge to [bus 05-0c]
>> [ 2620.877655] pcieport 0000:00:1c.3: bridge window [io 0x2000-0x2fff]
>> [ 2620.877667] pcieport 0000:00:1c.3: bridge window [mem
>> 0xf4300000-0xf7efffff]
>> [ 2620.877677] pcieport 0000:00:1c.3: bridge window [mem
>> 0xf4000000-0xf40fffff 64bit pref]
>> [ 2620.877990] pci 0000:05:00.0: enabling device (0000 -> 0003)
>> [ 2620.878013] snd_hda_intel 0000:06:00.0: enabling device (0000 -> 0002)
>> [ 2620.882747] azx_single_wait_for_response: 108 callbacks suppressed
>> [ 2620.882753] snd_hda_intel 0000:06:00.0: Codec #1 probe error;
>> disabling it...
>> [ 2620.887052] snd_hda_intel 0000:06:00.0: no AFG or MFG node found
>> [ 2620.887058] snd_hda_intel 0000:06:00.0: no codecs initialized
>
> What if you once unload snd-hda-intel module and reload again while
> keeping the card plugged? I guess it still doesn't work, but just to
> be sure...
>
> Overall, this look more like a problem of PCI core stuff. Better to
> toss the issue to PCI people.
>
>
> Takashi
>
I did alsa force-reload and the same error comes up. Do you know of a
good starting point for presenting PCI issues?
next prev parent reply other threads:[~2015-02-25 8:21 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54E10F0C.7070802@yahoo.com>
2015-02-15 21:33 ` Issues w/ Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG Alnie
2015-02-16 16:05 ` Takashi Iwai
2015-02-16 19:03 ` Alnie
2015-02-16 19:52 ` Takashi Iwai
2015-02-22 20:47 ` Alnie
2015-02-22 20:55 ` Alnie
2015-02-24 15:37 ` Takashi Iwai
2015-02-24 18:14 ` Alnie
2015-02-24 19:52 ` Takashi Iwai
2015-02-24 20:10 ` Alnie
2015-02-24 20:39 ` Takashi Iwai
2015-02-24 21:30 ` Alnie
2015-02-25 4:37 ` Alnie
2015-02-25 6:28 ` Takashi Iwai
2015-02-25 6:51 ` Alnie
2015-02-25 7:06 ` Takashi Iwai
2015-02-25 7:32 ` Alnie
2015-02-25 7:48 ` Takashi Iwai
2015-02-25 8:01 ` Alnie
[not found] ` <54ED7FED.9080600@yahoo.com>
2015-02-25 8:06 ` Takashi Iwai
2015-02-25 8:21 ` Alnie [this message]
2015-02-25 8:23 ` Takashi Iwai
2015-02-25 8:30 ` Alnie
2015-03-03 3:37 Alnie
2015-03-03 6:10 ` Takashi Iwai
2015-03-03 7:22 ` Alnie
2015-03-03 7:48 ` Takashi Iwai
2015-03-03 9:21 ` Alnie
2015-03-03 21:51 ` Alnie
2015-03-03 21:58 ` Alnie
2015-03-03 22:07 ` Takashi Iwai
2015-03-04 2:12 ` Alnie
2015-03-04 8:00 ` Takashi Iwai
2015-03-04 9:01 ` Alnie
2015-03-04 9:35 ` Takashi Iwai
2015-03-06 22:38 ` Alnie
2015-03-06 22:50 ` Alnie
2015-03-06 23:31 ` Alnie
2015-03-07 7:56 ` Takashi Iwai
2015-03-07 16:28 ` Alnie
2015-03-07 16:32 ` Takashi Iwai
2015-03-07 18:06 ` Alnie
2015-03-09 15:22 ` Alnie
2015-03-09 16:00 ` Takashi Iwai
2015-03-12 3:59 ` Alnie
2015-03-12 6:19 ` Takashi Iwai
2015-03-13 2:41 ` Alnie
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=54ED85FB.9060601@yahoo.com \
--to=alnieb@yahoo.com \
--cc=alsa-devel@alsa-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox