AGP speed not detected properly causing black screen and unkillable Xorg process

Bug #48053 reported by Bruce Milner
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: kernel-image-2.6.15-23-amd64-generic-di

After updating to dapper, I ended up with a black screen and a hung Xorg process that I could not even force kill. Here is the error in the syslog that seems relevant to this problem. The Xorg process was taking all cpu.

---------------------------------------------------------------------------------------
[ 64.049497] [drm] Initialized radeon 1.24.0 20060225 on minor 0
[ 64.933205] agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
[ 64.933220] agpgart: Badness. Don't know which AGP mode to set. [bridge_agpstat:1f000a0a vga_agpstat:ff00021b fell back to:- bridge_agpstat:1f000208 vga_agpstat:ff00021b]
[ 64.933223] agpgart: Bridge couldn't do AGP x4.
[ 64.933229] agpgart: Putting AGP V3 device at 0000:00:00.0 into 0x mode
[ 64.933281] agpgart: Putting AGP V3 device at 0000:01:00.0 into 0x mode

...

[ 69.264076] [drm] Setting GART location based on new memory map
[ 69.264087] [drm] Loading R300 Microcode
[ 69.273656] [drm] writeback test failed
---------------------------------------------------------------------------------------

After doing net searches for similar problems, I ran across some messages about unkillable xorg processes that stated that the AGP speed was being detected incorrectly with newer kernels and some setups. After changing my bios to 4X AGP instead of 8X AGP, xorg works again and the following is the relevant output in the syslog. Note that the writeback test fails above and works below. This system was running breezy just fine before (2.6.12-10).

---------------------------------------------------------------------------------------
blue@crow:/root$ dmesg | grep agp
[ 85.564568] agpgart: Detected AGP bridge 0
[ 85.567727] agpgart: AGP aperture is 64M @ 0xf8000000
[ 85.580437] Linux agpgart interface v0.101 (c) Dave Jones
[ 115.076136] agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
[ 115.076153] agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode
[ 115.076206] agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode
blue@crow:/root$ dmesg | grep drm
[ 114.185322] [drm] Initialized drm 1.0.1 20051102
[ 114.192610] [drm] Initialized radeon 1.24.0 20060225 on minor 0
[ 119.407115] [drm] Setting GART location based on new memory map
[ 119.407207] [drm] Loading R300 Microcode
[ 119.407274] [drm] writeback test succeeded in 1 usecs
---------------------------------------------------------------------------------------

Revision history for this message
Bruce Milner (bruce-ubuntu) wrote :
Download full text (7.1 KiB)

Here is more information about system.

# lspci -v
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8385 [K8T800 AGP] Host Bridge (rev 01)
        Subsystem: ASUSTeK Computer Inc. K8V Deluxe/K8V-X motherboard
        Flags: bus master, 66MHz, medium devsel, latency 8
        Memory at f8000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [80] AGP version 3.5
        Capabilities: [c0] #08 [0060]
        Capabilities: [68] Power Management version 2
        Capabilities: [58] #08 [8001]

0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South] (prog-if 00 [Normal decode])
        Flags: bus master, 66MHz, medium devsel, latency 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 0000a000-0000afff
        Memory behind bridge: fcd00000-fd2fffff
        Prefetchable memory behind bridge: d7f00000-f7efffff
        Capabilities: [80] Power Management version 2

0000:00:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) (prog-if 10 [OHCI])
        Subsystem: ASUSTeK Computer Inc.: Unknown device 808a
        Flags: bus master, medium devsel, latency 64, IRQ 185
        Memory at fd700000 (32-bit, non-prefetchable) [size=2K]
        I/O ports at bc00 [size=128]
        Capabilities: [50] Power Management version 2

0000:00:08.0 RAID bus controller: Promise Technology, Inc. PDC20378 (FastTrak 378/SATA 378) (rev 02)
        Subsystem: ASUSTeK Computer Inc. K8V Deluxe/PC-DL Deluxe motherboard
        Flags: bus master, 66MHz, medium devsel, latency 96, IRQ 169
        I/O ports at ec00 [size=64]
        I/O ports at dc00 [size=16]
        I/O ports at cc00 [size=128]
        Memory at fd900000 (32-bit, non-prefetchable) [size=4K]
        Memory at fd800000 (32-bit, non-prefetchable) [size=128K]
        Capabilities: [60] Power Management version 2

0000:00:0a.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
        Subsystem: ASUSTeK Computer Inc. Marvell 88E8001 Gigabit Ethernet Controller (Asus)
        Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 201
        Memory at fdb00000 (32-bit, non-prefetchable) [size=16K]
        I/O ports at b000 [size=256]
        Expansion ROM at fda00000 [disabled] [size=128K]
        Capabilities: [48] Power Management version 2
        Capabilities: [50] Vital Product Data

0000:00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
        Subsystem: ASUSTeK Computer Inc. A7V600/K8V Deluxe/K8V-X motherboard
        Flags: bus master, medium devsel, latency 64, IRQ 177
        I/O ports at e800 [size=8]
        I/O ports at e400 [size=4]
        I/O ports at e000 [size=8]
        I/O ports at d800 [size=4]
        I/O ports at d400 [size=16]
        I/O ports at d000 [size=256]
        Capabilities: [c0] Power Management version 2

0000:00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
        Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X motherboard
...

Read more...

Revision history for this message
Bruce Milner (bruce-ubuntu) wrote :

One more comment,

The same behaviour is observed when I compile and run the 2.6.16.19 kernel from ftp.kernel.org with the same .config.

Revision history for this message
Zooko Wilcox-O'Hearn (zooko) wrote :

I have the same problem with a Radeon 9200 PRO (see lspci output below). The workaround is to set your AGP speed to 4x instead of 8x in the BIOS. I eagerly await a better solution that will allow me to use 8x AGP.

See also:

http://lkml.org/lkml/2006/5/1/151

0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (rev 01) (prog-if 00 [VGA])
        Subsystem: C.P. Technology Co. Ltd: Unknown device 2094
        Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 185
        Memory at e0000000 (32-bit, prefetchable) [size=128M]
        I/O ports at a000 [size=256]
        Memory at fd000000 (32-bit, non-prefetchable) [size=64K]
        Expansion ROM at fcf00000 [disabled] [size=128K]
        Capabilities: <available only to root>

0000:01:00.1 Display controller: ATI Technologies Inc: Unknown device 5940 (rev 01)
        Subsystem: C.P. Technology Co. Ltd: Unknown device 2095
        Flags: bus master, 66MHz, medium devsel, latency 64
        Memory at d8000000 (32-bit, prefetchable) [size=128M]
        Memory at fce00000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: <available only to root>

Revision history for this message
Zooko Wilcox-O'Hearn (zooko) wrote :
Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

This bug has had no activity for a considerable period. This is a check to see if there is still interest in investigating this bug report.

Changed in linux-source-2.6.15:
status: New → Incomplete
Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

We are closing this report (no response to previous request for expressions of interest in this report). To reopen the report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux-source-2.6.15:
status: Incomplete → Invalid
Changed in linux-source-2.6.15:
status: Invalid → New
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Gildo,

I see you flipped the status back to "New" for this report. Care to comment if this is still an issue for you with the latest Alpha release for the upcoming Intrepid Ibex 8.10 release? http://www.ubuntu.com/testing . Please let us know your results.

Changed in linux:
status: New → Incomplete
Revision history for this message
Ermenegildo Fiorito (fiorito-g) wrote :

Nothing.....
Ubuntu 8.10 Alpha 4
AGP Aperture is 32 MB.

ubuntu@ubuntu:~$ dmesg | grep agp
[ 58.488140] Linux agpgart interface v0.103
[ 58.561112] agpgart: Detected AGP bridge 0
[ 58.562215] agpgart: AGP aperture is 32M @ 0xe4000000
[ 89.116514] agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
[ 89.116545] agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
[ 89.116622] agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
ubuntu@ubuntu:~$

Revision history for this message
Ermenegildo Fiorito (fiorito-g) wrote :

ubuntu@ubuntu:~$ dmesg | grep drm
[ 87.218113] [drm] Initialized drm 1.1.0 20060810
[ 87.291250] [drm] Initialized radeon 1.29.0 20080528 on minor 0
[ 89.256017] [drm] Setting GART location based on new memory map
[ 89.256017] [drm] Can't use AGP base @0xe4000000, won't fit
[ 89.256017] [drm] Loading R200 Microcode
[ 89.256017] [drm] writeback test succeeded in 1 usecs
ubuntu@ubuntu:~$

Any possible solution?

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

Revision history for this message
Bruce Milner (bruce-ubuntu) wrote :

FYI, As the original creator of this bug report, I have given away the motherboard and video card a while back that
were exhibiting these problems, so I will not be able to contribute in a meaningful way to finding this problem or
helping to close this bug report.

Revision history for this message
Zooko Wilcox-O'Hearn (zooko) wrote :

Yeah, my son's computer stopped working -- maybe a powersupply issue? -- so I can't currently test this, and there's no telling if that motherboard will ever come back on-line.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks for the update Bruce.

Gildo - Can you open up a new report regarding the issues you are still seeing. It'll be easier and cleaner for the developers to see just the information for your exact bug and hardware. Additionally, Bruce et al who no longer have the hardware to test won't be spammed with more emails regarding this bug. Thanks.

Changed in linux:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.