On Tue, 2011-07-12 at 13:05 +0200, Svante Signell wrote: > found 619034 2.6.37-1 > found 619034 2.6.38-1 > found 619034 2.6.38-2 > found 619034 2.6.39-1 > found 619034 2.6.39-2 > thanks > > Anybody looking into this bug?? I still have to use the 2.6.32-5-amd64 > kernel due to this problem. Looks like 2.6.32 complains about an address > space conflict, but at least it boots properly. > > Below is from 2.6.38-2-amd64 boot log attached in message #89: > > [ 0.212397] pci 0000:00:00.0: address space collision: > [mem 0xd0000000-0xd7ffffff pref] conflicts with > GART [mem 0xd0000000-0xd7ffffff] > [ 0.212506] pci 0000:80:01.0: address space collision: > [mem 0xbfffc000-0xbfffffff 64bit] conflicts with > PCI Bus #00 [mem 0x80000000-0xfcffffffff] > > 0000:00:00.0: Host bridge [0600]: VIA Technologies, Inc. K8M890CE Host > Bridge [1106:0336] > > 0000:80:01.0: Audio device [0403]: VIA Technologies, Inc. VT1708/A > [Azalia HDAC] (VIA High Definition Audio Controller) [1106:3288] (rev > 10) > > Where can I report upstream? You already did (alsa-devel@alsa-project.org) and you were requested to do a bisection between Linux 2.6.32 and 2.6.37. You can find binary packages of some of the intermediate versions on <http://snapshot.debian.org/package/linux-2.6/>. Ben. -- Ben Hutchings All extremists should be taken out and shot.
Attachment:
signature.asc
Description: This is a digitally signed message part