This issue should be resolved by
https://git.kernel.org/linus/1dace0116d0b, which appeared in v4.2. If
the kernel contains that commit, the "pci=use_crs" boot parameter should
not be needed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
In comment #40, I mistakenly said we reassign 80:01.0 to an address
that is under PCI0, not PCI1. I had misread the address 0xfd
as 0xfd00, but it is actually 0xfd__, which is just after
the [mem 0x8000-0xfc] range from amd_bus.c, and is not in
any of the apertures
Anybody seeing this problem on a Foxconn K8M890-8237A system, please
test this patch. With it, sound should work without having to boot with
pci=use_crs. If you test it, please attach the complete dmesg log
here. Thanks!
** This bug is no longer a duplicate of bug 662299
Soundcard not
*** This bug is a duplicate of bug 662299 ***
https://bugs.launchpad.net/bugs/662299
Bug #662299 includes several problems with similar symptoms and the same
workaround (booting with pci=use_crs).
Booting with pci=use_crs may be a workaround for this bug as well. If
it is, please attach a
Manuel, does this problem still occur? I can't see what the problem is
in your dmesg logs. Your logs contain 'PCI: Using host bridge windows
from ACPI; if necessary, use pci=nocrs and report a bug', booting with
pci=use_crs shouldn't make a difference on your machine.
If this is still a
Hi timmy,
pci=use_crs shouldn't make any difference on your system, because it
was already automatically enabled even without pci=use_crs.
If you still have an issue with sound or xgifb, please attach a complete
dmesg log.
--
You received this bug notification because you are a member of
pci=use_crs is a workaround but not a fix. If anybody who has this
problem can attach a complete dmesg log, we should be able to fix the
kernel so it works without having to boot with pci=use_crs.
--
You received this bug notification because you are a member of Desktop
Packages, which is
*** This bug is a duplicate of bug 662299 ***
https://bugs.launchpad.net/bugs/662299
Bug #662299 includes several problems with similar symptoms and the same
workaround (booting with pci=use_crs).
Booting with pci=use_crs may be a workaround for this bug as well. If
it is, please attach a
*** This bug is a duplicate of bug 662299 ***
https://bugs.launchpad.net/bugs/662299
Stormhierta 's Micro-Star MS-7253 system, this should be fixed by these
commits, which appeared upstream in v3.3:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=841137170961
*** This bug is a duplicate of bug 662299 ***
https://bugs.launchpad.net/bugs/662299
valkyr's report was on an ASUSTeK M2V-MX SE. That problem should be
fixed by this commit, which appeared upstream in v3.1:
Hi JoseLuisTriana,
1) pci=use_crs shouldn't make a difference on your system because we
enable pci=use_crs automatically on systems with BIOS date of 2008 or
newer, and yours is 02/21/2008
2) Re comment #4, the kernel should be able to configure devices even if
the BIOS didn't set it up
*** This bug is a duplicate of bug 1033299 ***
https://bugs.launchpad.net/bugs/1033299
** This bug has been marked a duplicate of bug 1033299
Ubuntu 12.04 - no sound with VT8237A/VT8251
--
You received this bug notification because you are a member of Desktop
Packages, which is
*** This bug is a duplicate of bug 662299 ***
https://bugs.launchpad.net/bugs/662299
** This bug has been marked a duplicate of bug 662299
Soundcard not detected (workaround: add pci=use_crs to GRUB)
--
You received this bug notification because you are a member of Desktop
Packages,
Eran, can you confirm whether (1) this is still a problem, and (2)
whether pci=use_crs makes a difference? Based on your dmesg log, I
don't see what it would change, but I might have missed something.
If pci=use_crs does make a difference, can you attach complete dmesg
logs with and without it?
I think this should be fixed by these commits:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=841137170961
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a97f4f5e524b
Both appeared upstream in v3.3.
--
You received this bug
For Micro-Star MS-7253 systems, this should be fixed by:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=841137170961
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a97f4f5e524b
which appeared upstream in v3.3. This should fix the
FichdlMaa, you said in comment #12 that pcie=use_crs didn't make a
difference. Can you attach a complete dmesg log with pci=use_crs? I
think it should make some difference (it should change the address
assigned to the 80:01.0 sound device), but that may not be enough to fix
the whole problem.
I see two problems in the initial report from FichdlMaa:
1) Linux ignores ACPI _CRS information and consequently assigns addresses to
the 80:01.0 device that may not work.
2) The page fault: BUG: unable to handle kernel paging request at
c9378000
Booting with pci=use_crs should work
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1033299 is a
different problem from what robusta is reporting here. In 1033299,
pci=use_crs should work around at least part of the problem, but I
don't think it will make a difference here.
Here, we have this:
pci :00:13.0:
19 matches
Mail list logo
