Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
# See also bug 403871 reassign 392915 linux-2.6 tags 392915 upstream fixed-upstream patch kthxbye On Wed, 2007-01-10 at 23:35 +0100, Andreas Johansson wrote: On Wed, Jan 10, 2007 at 10:15:15AM +0100, Michel Dänzer wrote: Thanks. I think this is another integer overflow bug in the radeon DRM; can you try the attached patch? Yes, this enables me to use a 32MB AGP aperture setting in the BIOS. Thanks for finding the cause of this problem! I used the Debian package linux-source-2.6.18 version 2.6.18-7 and patched drivers/char/drm/radeon_cp.c with your patch. Just radeon.ko was built, and installed manually. The rest of the kernel package remained as-is, I didn't build a complete package. Attached is the dmesg from my system using the resulting radeon.ko. I guess this is the interesting change: [drm] Can't use AGP base @0xfc00, won't fit Indeed, thanks for testing. Reassigning to the kernel, I pushed the fix to drm git in http://gitweb.freedesktop.org/?p=mesa/drm.git;a=commit;h=8ff026723cf170034173052a58c650c8c1f28c0b Alex: Looking at your Xorg.patched.log again, I'm afraid this won't fix that case; it looks like MC_FB_LOCATION is set up to cover the whole 32 bit address space when the X server starts, and because the radeon driver preserves this register with Option UseFBDev (maybe we should change this, Ben?), the AGP aperture has to overlap the framebuffer. This could be at least partly considered a bug in radeonfb (or even the video BIOS?). -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
On Wed, Jan 10, 2007 at 06:45:57PM +1100, Dave Airlie wrote: can you attach lspci -vv for both cases? Here they are, for reference. (The one with 32MB AGP aperture was taken from a system running a radeon.ko with Michel's patch to radeon_cp.c.) -- Andreas Johansson[EMAIL PROTECTED] http://www.berget.nu/~andjo/ 00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4) Subsystem: ASUSTeK Computer Inc. Unknown device 80e7 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- Latency: 0 Region 0: Memory at fc00 (32-bit, prefetchable) [size=32M] Capabilities: [a0] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x4 Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- Latency: 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: d000-dfff Memory behind bridge: de00-deff Prefetchable memory behind bridge: e000-fbff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- Reset- FastB2B- Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) Subsystem: ASUSTeK Computer Inc. Unknown device 80e7 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:04.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]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 Region 4: I/O ports at b800 [size=16] Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:04.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1a) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32, Cache Line Size: 32 bytes Interrupt: pin D routed to IRQ 11 Region 4: I/O ports at b400 [size=32] Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:04.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1a) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32, Cache Line Size: 32 bytes Interrupt: pin D routed to IRQ 11 Region 4: I/O ports at b000 [size=32] Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
On Wed, Jan 10, 2007 at 10:15:15AM +0100, Michel Dänzer wrote: Thanks. I think this is another integer overflow bug in the radeon DRM; can you try the attached patch? Yes, this enables me to use a 32MB AGP aperture setting in the BIOS. Thanks for finding the cause of this problem! I used the Debian package linux-source-2.6.18 version 2.6.18-7 and patched drivers/char/drm/radeon_cp.c with your patch. Just radeon.ko was built, and installed manually. The rest of the kernel package remained as-is, I didn't build a complete package. Attached is the dmesg from my system using the resulting radeon.ko. I guess this is the interesting change: [drm] Can't use AGP base @0xfc00, won't fit -- Andreas Johansson[EMAIL PROTECTED] http://www.berget.nu/~andjo/ l command line: root=/dev/hda1 ro No local APIC present or hardware disabled mapped APIC to d000 (01402000) Initializing CPU#0 PID hash table entries: 2048 (order: 11, 8192 bytes) Console: colour VGA+ 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 510548k/524208k available (1500k kernel code, 13040k reserved, 602k data, 256k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 1868.17 BogoMIPS (lpj=3736348) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: 00803035 80803035 CPU: L1 I Cache: 64K (32 bytes/line), D cache 64K (32 bytes/line) CPU: L2 Cache: 64K (32 bytes/line) CPU: After all inits, caps: 00803135 80803035 Compat vDSO mapped to e000. CPU: Centaur VIA Ezra stepping 08 Checking 'hlt' instruction... OK. ACPI: Core revision 20060707 ACPI: setting ELCR to 0200 (from 0e20) checking if image is initramfs... it is Freeing initrd memory: 5412k freed NET: Registered protocol family 16 EISA bus registered ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xf0d20, last bus=1 PCI: Using configuration type 1 Setting up standard PCI resources ACPI: Interpreter enabled ACPI: Using PIC for interrupt routing ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Root Bridge [PCI0] (:00) PCI: Probing PCI hardware (bus 00) ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 PCI quirk: region e800-e80f claimed by vt82c686 SMB Boot video device is :01:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT] Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 13 devices PnPBIOS: Disabled by ACPI PNP PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try pci=routeirq. If it helps, post a report pnp: 00:03: ioport range 0xe400-0xe47f could not be reserved pnp: 00:03: ioport range 0xe800-0xe80f has been reserved PCI: Bridge: :00:01.0 IO window: d000-dfff MEM window: de00-deff PREFETCH window: e000-fbff PCI: Setting latency timer of device :00:01.0 to 64 NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 4, 65536 bytes) TCP bind hash table entries: 8192 (order: 3, 32768 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered Simple Boot Flag at 0x3a set to 0x1 audit: initializing netlink socket (disabled) audit(1168466989.612:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) PCI: Disabling Via external APIC routing isapnp: Scanning for PnP cards... isapnp: No Plug Play device found Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:0b: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1 PNP: PS/2 controller doesn't have AUX irq; using default 12 serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 mice: PS/2 mouse device common for all mice EISA: Probing bus 0 at eisa.0 EISA: Detected 0 cards. TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
On Tue, 2007-01-09 at 22:54 +0100, Andreas Johansson wrote:
On Tue, Jan 09, 2007 at 06:18:24PM +0100, Michel Dänzer wrote:
I'm not sure how this could happen though; can you also post the full
kernel output, or at least everything related to AGP and the DRI?
Sure. Attached are the entries from /var/log/messages that I believe
matches the two Xorg log files. Below are the results of grep:ing
for agp and drm.
Thanks. I think this is another integer overflow bug in the radeon DRM;
can you try the attached patch?
--
Earthling Michel Dänzer | http://tungstengraphics.com
Libre software enthusiast | Debian, X and DRI developer
diff --git a/shared-core/radeon_cp.c b/shared-core/radeon_cp.c
index 4135f4d..0fa6535 100644
--- a/shared-core/radeon_cp.c
+++ b/shared-core/radeon_cp.c
@@ -1563,8 +1563,8 @@ static int radeon_do_init_cp(drm_device_t * dev, drm_radeon_init_t * init)
if (dev_priv-flags RADEON_IS_AGP) {
base = dev-agp-base;
/* Check if valid */
- if ((base + dev_priv-gart_size) dev_priv-fb_location
- base (dev_priv-fb_location + dev_priv-fb_size)) {
+ if ((base + dev_priv-gart_size - 1) = dev_priv-fb_location
+ base (dev_priv-fb_location + dev_priv-fb_size - 1)) {
DRM_INFO(Can't use AGP base @0x%08lx, won't fit\n,
dev-agp-base);
base = 0;
@@ -1574,8 +1574,8 @@ static int radeon_do_init_cp(drm_device_t * dev, drm_radeon_init_t * init)
/* If not or if AGP is at 0 (Macs), try to put it elsewhere */
if (base == 0) {
base = dev_priv-fb_location + dev_priv-fb_size;
- if (((base + dev_priv-gart_size) 0xul)
- base)
+ if (base dev_priv-fb_location ||
+ ((base + dev_priv-gart_size) 0xul) base)
base = dev_priv-fb_location
- dev_priv-gart_size;
}
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
On Tue, 2007-01-09 at 16:27 +0100, Andreas Johansson wrote: Attached are two log files, one from a hanging session (the 32MB one) and one from a working (the 128MB one). The diff mostly seems to be due to different offsets. Hmm, it looks like the framebuffer and AGP areas end up overlapping in the card's address space with 32 MB, which could explain the problem. I'm not sure how this could happen though; can you also post the full kernel output, or at least everything related to AGP and the DRI? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
On Tue, Jan 09, 2007 at 06:18:24PM +0100, Michel Dänzer wrote: I'm not sure how this could happen though; can you also post the full kernel output, or at least everything related to AGP and the DRI? Sure. Attached are the entries from /var/log/messages that I believe matches the two Xorg log files. Below are the results of grep:ing for agp and drm. 32 MB Linux agpgart interface v0.101 (c) Dave Jones agpgart: Detected VIA Apollo Pro 133 chipset agpgart: AGP aperture is 32M @ 0xfc00 [drm] Initialized drm 1.0.1 20051102 [drm] Initialized radeon 1.25.0 20060524 on minor 0 agpgart: Found an AGP 2.0 compliant device at :00:00.0. agpgart: Putting AGP V2 device at :00:00.0 into 1x mode agpgart: Putting AGP V2 device at :01:00.0 into 1x mode [drm] Setting GART location based on new memory map [drm] Loading R200 Microcode [drm] writeback test failed 128 MB Linux agpgart interface v0.101 (c) Dave Jones agpgart: Detected VIA Apollo Pro 133 chipset agpgart: AGP aperture is 128M @ 0xf000 [drm] Initialized drm 1.0.1 20051102 [drm] Initialized radeon 1.25.0 20060524 on minor 0 agpgart: Found an AGP 2.0 compliant device at :00:00.0. agpgart: Putting AGP V2 device at :00:00.0 into 1x mode agpgart: Putting AGP V2 device at :01:00.0 into 1x mode [drm] Setting GART location based on new memory map [drm] Loading R200 Microcode [drm] writeback test succeeded in 1 usecs -- Andreas Johansson[EMAIL PROTECTED] http://www.berget.nu/~andjo/ Jan 8 21:17:28 kamari syslogd 1.4.1#18: restart. Jan 8 21:17:28 kamari kernel: klogd 1.4.1#18, log source = /proc/kmsg started. Jan 8 21:17:28 kamari kernel: data) Jan 8 21:17:28 kamari kernel: BIOS-e820: 1ffef000 - 1000 (reserved) Jan 8 21:17:28 kamari kernel: BIOS-e820: 1000 - 2000 (ACPI NVS) Jan 8 21:17:28 kamari kernel: BIOS-e820: - 0001 (reserved) Jan 8 21:17:28 kamari kernel: 511MB LOWMEM available. Jan 8 21:17:28 kamari kernel: DMI 2.3 present. Jan 8 21:17:28 kamari kernel: ACPI: PM-Timer IO Port: 0xe408 Jan 8 21:17:28 kamari kernel: Allocating PCI resources starting at 3000 (gap: 2000:dfff) Jan 8 21:17:28 kamari kernel: Detected 933.110 MHz processor. Jan 8 21:17:28 kamari kernel: Built 1 zonelists. Total pages: 131052 Jan 8 21:17:28 kamari kernel: Kernel command line: root=/dev/hda1 ro Jan 8 21:17:28 kamari kernel: No local APIC present or hardware disabled Jan 8 21:17:28 kamari kernel: Initializing CPU#0 Jan 8 21:17:28 kamari kernel: PID hash table entries: 2048 (order: 11, 8192 bytes) Jan 8 21:17:28 kamari kernel: Console: colour VGA+ 80x25 Jan 8 21:17:28 kamari kernel: Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Jan 8 21:17:28 kamari kernel: Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Jan 8 21:17:28 kamari kernel: Memory: 510548k/524208k available (1500k kernel code, 13040k reserved, 602k data, 256k init, 0k highmem) Jan 8 21:17:28 kamari kernel: Checking if this processor honours the WP bit even in supervisor mode... Ok. Jan 8 21:17:28 kamari kernel: Calibrating delay using timer specific routine.. 1868.17 BogoMIPS (lpj=3736359) Jan 8 21:17:28 kamari kernel: Security Framework v1.0.0 initialized Jan 8 21:17:28 kamari kernel: SELinux: Disabled at boot. Jan 8 21:17:28 kamari kernel: Capability LSM initialized Jan 8 21:17:28 kamari kernel: Mount-cache hash table entries: 512 Jan 8 21:17:28 kamari kernel: CPU: L1 I Cache: 64K (32 bytes/line), D cache 64K (32 bytes/line) Jan 8 21:17:28 kamari kernel: CPU: L2 Cache: 64K (32 bytes/line) Jan 8 21:17:28 kamari kernel: Compat vDSO mapped to e000. Jan 8 21:17:28 kamari kernel: CPU: Centaur VIA Ezra stepping 08 Jan 8 21:17:28 kamari kernel: Checking 'hlt' instruction... OK. Jan 8 21:17:28 kamari kernel: ACPI: Core revision 20060707 Jan 8 21:17:28 kamari kernel: ACPI: setting ELCR to 0200 (from 0e20) Jan 8 21:17:28 kamari kernel: checking if image is initramfs... it is Jan 8 21:17:28 kamari kernel: Freeing initrd memory: 5412k freed Jan 8 21:17:28 kamari kernel: NET: Registered protocol family 16 Jan 8 21:17:28 kamari kernel: EISA bus registered Jan 8 21:17:28 kamari kernel: ACPI: bus type pci registered Jan 8 21:17:28 kamari kernel: PCI: PCI BIOS revision 2.10 entry at 0xf0d20, last bus=1 Jan 8 21:17:28 kamari kernel: PCI: Using configuration type 1 Jan 8 21:17:28 kamari kernel: Setting up standard PCI resources Jan 8 21:17:28 kamari kernel: ACPI: Interpreter enabled Jan 8 21:17:28 kamari kernel: ACPI: Using PIC for interrupt routing Jan 8 21:17:28 kamari kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) Jan 8 21:17:28 kamari kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) Jan 8 21:17:28 kamari kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) Jan 8 21:17:28 kamari kernel:
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
I'm not sure how this could happen though; can you also post the full kernel output, or at least everything related to AGP and the DRI? Sure. Attached are the entries from /var/log/messages that I believe matches the two Xorg log files. Below are the results of grep:ing for agp and drm. can you attach lspci -vv for both cases? Dave. 32 MB Linux agpgart interface v0.101 (c) Dave Jones agpgart: Detected VIA Apollo Pro 133 chipset agpgart: AGP aperture is 32M @ 0xfc00 [drm] Initialized drm 1.0.1 20051102 [drm] Initialized radeon 1.25.0 20060524 on minor 0 agpgart: Found an AGP 2.0 compliant device at :00:00.0. agpgart: Putting AGP V2 device at :00:00.0 into 1x mode agpgart: Putting AGP V2 device at :01:00.0 into 1x mode [drm] Setting GART location based on new memory map [drm] Loading R200 Microcode [drm] writeback test failed 128 MB Linux agpgart interface v0.101 (c) Dave Jones agpgart: Detected VIA Apollo Pro 133 chipset agpgart: AGP aperture is 128M @ 0xf000 [drm] Initialized drm 1.0.1 20051102 [drm] Initialized radeon 1.25.0 20060524 on minor 0 agpgart: Found an AGP 2.0 compliant device at :00:00.0. agpgart: Putting AGP V2 device at :00:00.0 into 1x mode agpgart: Putting AGP V2 device at :01:00.0 into 1x mode [drm] Setting GART location based on new memory map [drm] Loading R200 Microcode [drm] writeback test succeeded in 1 usecs -- Andreas Johansson[EMAIL PROTECTED] http://www.berget.nu/~andjo/ ___ Xorg-driver-ati mailing list [EMAIL PROTECTED] http://lists.x.org/mailman/listinfo/xorg-driver-ati -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
On Sun, 2007-01-07 at 19:41 +0100, Andreas Johansson wrote: Yes, if the agpgart driver can print a message about the aperture size being too small, it should also be able report failure such that the X server doesn't initialize the DRI. Ah, sorry, my wording when referring to fd.o bug 6111 was a bit unclear. On my system at least, agpgart doesn't complain about the aperture being too small, I'm not sure why 32 MB wouldn't be enough anyway, as the radeon driver only uses 8 MB by default. it just states the same value that is set in the BIOS. Are there any other AGP settings there? If so, do their values match the X configuration? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
On Sat, 2007-01-06 at 20:09 +0100, Andreas Johansson wrote: The problem can be worked around by changing the AGP Aperture BIOS setting. Changing this from 32MB to 256MB let me enable DRI. (As suggested by https://bugs.freedesktop.org/show_bug.cgi?id=6111#c30) I'm not sure this can be considered a bug in the radeon driver then, unless maybe there's a way for it to detect the unusable AGP aperture size. OTOH though, there are probably at least two separate problems in this report now, so I'm not sure how to proceed. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
I'm not sure this can be considered a bug in the radeon driver then, unless maybe there's a way for it to detect the unusable AGP aperture size. Prior to upgrading to etch this system ran sarge with X.org packages (6.9) from backports.org. Those were usable even with the aperture size set to 32MB in the BIOS. So, this seems to be either a new issue in X.org 7.1, or a change was made that exposes some underlying problem that was present before. A 2.6.18 kernel was used in both cases. But I must confess that I'm rather ignorant about what the APG aperture setting really does. The motherboard manual doesn't say much, and googling for the term seems to indicate it's a performance optimization. If there are unusable aperture size, ideally either the agpgart driver or the X server should refuse them. (Unless it's hardware and/or BIOS bugs.) Can you suggest a good test case to verify that DRI really works, and it's not just a matter of postponing the lockup? I've run glxgears without any problems. -- Andreas Johansson[EMAIL PROTECTED] http://www.berget.nu/~andjo/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
On Sun, 2007-01-07 at 14:35 +0100, Andreas Johansson wrote: If there are unusable aperture size, ideally either the agpgart driver or the X server should refuse them. (Unless it's hardware and/or BIOS bugs.) Yes, if the agpgart driver can print a message about the aperture size being too small, it should also be able report failure such that the X server doesn't initialize the DRI. Can you suggest a good test case to verify that DRI really works, and it's not just a matter of postponing the lockup? I've run glxgears without any problems. Then it's working. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
Yes, if the agpgart driver can print a message about the aperture size being too small, it should also be able report failure such that the X server doesn't initialize the DRI. Ah, sorry, my wording when referring to fd.o bug 6111 was a bit unclear. On my system at least, agpgart doesn't complain about the aperture being too small, it just states the same value that is set in the BIOS. I merely got the idea to change the setting from reading the freedesktop bug comments. Looking at drivers/char/agp/*.c in the kernel source, it seems that only amd64_agp can complain that the apterture size is too small. I'm using via_agp on my 32-bit system. -- Andreas Johansson[EMAIL PROTECTED] http://www.berget.nu/~andjo/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
I've also experienced this bug, so this is more of a confirmation of this problem on another system. Running xserver-xorg-video-ati 6.6.3-2 on my system with DRI enabled causes the X server to hang in some kind of loop. Keyboard and mouse are unusable, but the system is still up, and remote logins to it are still possible. The X server process consumes as much CPU as it can get, and is not killable. A reboot is required to return the system to a usable state. The graphics card is a Asus A9250GE/TD/256M/A. kamari$ lspci | grep ATI 01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (rev 01) 01:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (Secondary) (rev 01) Snippets from Xorg.log.0 (II) Primary Device is: PCI 01:00:0 (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found (--) Chipset ATI Radeon 9250 5960 (AGP) found (I haven't attached full log files since this is just to confirm the same problem others have reported. Please let me know if you need them.) The problem can be worked around by changing the AGP Aperture BIOS setting. Changing this from 32MB to 256MB let me enable DRI. (As suggested by https://bugs.freedesktop.org/show_bug.cgi?id=6111#c30) Motherboard is Asus TUV4X, which uses a VIA Apollo Pro 133 chipset, according to agpgart. -- Andreas Johansson[EMAIL PROTECTED] http://www.berget.nu/~andjo/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
Michel Dänzer [EMAIL PROTECTED] writes: If you suspect the hardware might be faulty, you could verify that with another OS. FYI, I changed my radeon 8500 by a new 9250, and everything works nice. The strange thing is that I tried the 8500 in another computer (also debian sid) where I don't need DRI, and DRI works there... I guess this is a bit difficult to fix, but I just wanted to add this info... Marc
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
Michel Dänzer [EMAIL PROTECTED] writes: It doesn't. Writeback is a minor performance optimization, the lack of which should not affect operation of the X server. If you suspect the hardware might be faulty, you could verify that with another OS. I tried on ubuntu 6.06, and it's having the same behavior (and I know it was working some time ago with it)... I guess my hardware is dying :/ Sorry for having raised this non-bug... Marc
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
Michel Dänzer [EMAIL PROTECTED] writes: On Wed, 2006-10-25 at 23:04 +0200, [EMAIL PROTECTED] wrote: Michel Dänzer [EMAIL PROTECTED] writes: But it doesn't happen with version 6.6.2? I'm not sure exactly when it stops working... That would be very helpful to know though. Please try older versions, e.g. from http://snapshot.debian.net . I tried with 6.6.2-2 and I have the exact same behavior (kern.log and Xorg.log stop at the same line than with the 6.6.3-2)... If you suspect the hardware might be faulty, you could verify that with another OS. I guess this is the next step... I'll try with ubuntu dapper as I know dri was working fine. Thanks for the help, Marc
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
On Wed, 2006-10-25 at 23:04 +0200, [EMAIL PROTECTED] wrote: Michel Dänzer [EMAIL PROTECTED] writes: But it doesn't happen with version 6.6.2? I'm not sure exactly when it stops working... That would be very helpful to know though. Please try older versions, e.g. from http://snapshot.debian.net . Oct 25 22:53:26 arrakis kernel: [drm] Setting GART location based on new memory map Oct 25 22:53:26 arrakis kernel: [drm] Loading R200 Microcode Oct 25 22:53:26 arrakis kernel: [drm] writeback test failed The last line here is the last line in the log. Is it possible that my hardware is damaged ? I find it strange that the microcode fails to load :/ It doesn't. Writeback is a minor performance optimization, the lack of which should not affect operation of the X server. If you suspect the hardware might be faulty, you could verify that with another OS. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
Michel Dänzer [EMAIL PROTECTED] writes: On Thu, 2006-10-19 at 21:41 +0200, [EMAIL PROTECTED] wrote: Michel Dänzer [EMAIL PROTECTED] writes: And this doesn't happen with version 6.6.2? If so, it would be great if you could try isolating the upstream change that causes it with git-bisect. I'm afraid that's a bit too much as I don't know anything about git... But it doesn't happen with version 6.6.2? I'm not sure exactly when it stops working... That's an odd place for the log to stop... Can you not even log in remotely or ping the machine at this point? If so, can you try re-mounting the filesystem that contains the log file with -o sync before starting the X server and see if you get any more output then? True. Before submiting the bug, I read the logs after several crashes and saw it was not always at the same line. Here's the one with -o sync and latest version of everything (deb sid). Thanks. Does it always stop in the same place with -o sync? Also, is there anything related in /var/log/kern.log? Yes it stops always at the same time. The kernel logs show something that may be interesting: Oct 25 22:53:26 arrakis kernel: [drm] Setting GART location based on new memory map Oct 25 22:53:26 arrakis kernel: [drm] Loading R200 Microcode Oct 25 22:53:26 arrakis kernel: [drm] writeback test failed The last line here is the last line in the log. Is it possible that my hardware is damaged ? I find it strange that the microcode fails to load :/ Marc
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
Michel Dänzer [EMAIL PROTECTED] writes: And this doesn't happen with version 6.6.2? If so, it would be great if you could try isolating the upstream change that causes it with git-bisect. I'm afraid that's a bit too much as I don't know anything about git... Loaddri Does it also happen if you don't enable the DRI? no. Without DRI, X is working fine. That's an odd place for the log to stop... Can you not even log in remotely or ping the machine at this point? If so, can you try re-mounting the filesystem that contains the log file with -o sync before starting the X server and see if you get any more output then? True. Before submiting the bug, I read the logs after several crashes and saw it was not always at the same line. Here's the one with -o sync and latest version of everything (deb sid). Marc X Window System Version 7.1.1 Release Date: 12 May 2006 X Protocol Version 11, Revision 0, Release 7.1.1 Build Operating System: UNKNOWN Current Operating System: Linux arrakis 2.6.18-1-k7 #1 SMP Fri Sep 29 17:06:47 UTC 2006 i686 Build Date: 07 July 2006 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu Oct 19 21:31:25 2006 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor SyncMaster (**) | |--Device Generic Video Card (**) |--Input Device Generic Keyboard (**) |--Input Device Configured Mouse (WW) The directory /usr/X11R6/lib/X11/fonts/misc does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/100dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/75dpi/ does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts/X11/Type1. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts/X11/Type1). (WW) The directory /usr/X11R6/lib/X11/fonts/Type1 does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/100dpi does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/75dpi does not exist. Entry deleted from font path. (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. Entry deleted from font path. (**) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi (==) RgbPath set to /etc/X11/rgb (==) ModulePath set to /usr/lib/xorg/modules (**) Ignoring ABI Version (II) Open ACPI successful (/var/run/acpid.socket) (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.0 X.Org XInput driver : 0.6 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so (II) Module bitmap: vendor=X.Org Foundation compiled for 7.1.1, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/lib/xorg/modules/libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.0 (++) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,3099 card 1043,807f rev 00 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,b099 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:09:0: chip 1106,3038 card 1043,8080 rev 50 class 0c,03,00 hdr 80 (II) PCI: 00:09:1: chip 1106,3038 card 1043,8080 rev 50 class 0c,03,00 hdr 80 (II) PCI: 00:09:2: chip 1106,3104 card 1043,8080 rev 51 class 0c,03,20 hdr 80 (II) PCI: 00:0d:0: chip 1105,8300 card , rev 02 class 04,80,00 hdr 00 (II) PCI: 00:0e:0: chip 1102,0002 card 1102,8027 rev 08 class 04,01,00 hdr 80 (II) PCI: 00:0e:1: chip 1102,7002 card 1102,0020 rev 08 class 09,80,00 hdr 80 (II) PCI: 00:0f:0: chip 109e,0350 card , rev 12 class 04,00,00 hdr 00 (II) PCI: 00:10:0: chip 8086,1229 card 8086,0040 rev 0c class 02,00,00 hdr 00 (II) PCI: 00:11:0: chip 1106,3147 card 1043,808c rev 00 class 06,01,00 hdr 80 (II) PCI: 00:11:1: chip 1106,0571 card 1043,808c rev 06 class 01,01,8a
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
On Thu, 2006-10-19 at 21:41 +0200, [EMAIL PROTECTED] wrote: Michel Dänzer [EMAIL PROTECTED] writes: And this doesn't happen with version 6.6.2? If so, it would be great if you could try isolating the upstream change that causes it with git-bisect. I'm afraid that's a bit too much as I don't know anything about git... But it doesn't happen with version 6.6.2? That's an odd place for the log to stop... Can you not even log in remotely or ping the machine at this point? If so, can you try re-mounting the filesystem that contains the log file with -o sync before starting the X server and see if you get any more output then? True. Before submiting the bug, I read the logs after several crashes and saw it was not always at the same line. Here's the one with -o sync and latest version of everything (deb sid). Thanks. Does it always stop in the same place with -o sync? Also, is there anything related in /var/log/kern.log? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
Package: xserver-xorg-video-ati Version: 1:6.6.3-1 Severity: grave When starting xserver, screen is blank (black) and the systems is frozen (SysRq not working). 'vesa' drivers works but is really slow... 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R200 QL [Radeon 8500 LE] Here is my xorg.conf: (xorg log follows) ---8---8---8---8---8---8---8 # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type man /etc/X11/xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files FontPath/usr/share/fonts/X11/misc FontPath/usr/X11R6/lib/X11/fonts/misc FontPath/usr/share/fonts/X11/cyrillic FontPath/usr/X11R6/lib/X11/fonts/cyrillic FontPath/usr/share/fonts/X11/100dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath/usr/share/fonts/X11/75dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 FontPath/usr/X11R6/lib/X11/fonts/Type1 FontPath/usr/share/fonts/X11/100dpi FontPath/usr/X11R6/lib/X11/fonts/100dpi FontPath/usr/share/fonts/X11/75dpi FontPath/usr/X11R6/lib/X11/fonts/75dpi # path to defoma fonts FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module Loadi2c Loadbitmap Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout fr Option XkbVariantlatin9 EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ExplorerPS/2 Option Emulate3Buttons true EndSection Section Device Identifier Generic Video Card Driver radeon # BusID PCI:1:0:0 EndSection Section Monitor Identifier SyncMaster Option DPMS EndSection Section Screen Identifier Default Screen Device Generic Video Card Monitor SyncMaster DefaultDepth24 SubSection Display Depth 1 Modes 1280x1024 1152x864 1024x768 832x624 800x600 720x400 640x480 EndSubSection SubSection Display Depth 4 Modes 1280x1024 1152x864 1024x768 832x624 800x600 720x400 640x480 EndSubSection SubSection Display Depth 8 Modes 1280x1024 1152x864 1024x768 832x624 800x600 720x400 640x480 EndSubSection SubSection Display Depth 15 Modes 1280x1024 1152x864 1024x768 832x624 800x600 720x400 640x480 EndSubSection SubSection Display Depth 16 Modes 1280x1024 1152x864 1024x768 832x624 800x600 720x400 640x480 EndSubSection SubSection Display Depth 24 Modes 1280x1024 1152x864 1024x768 832x624 800x600 720x400 640x480 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice Configured Mouse EndSection Section DRI Mode0666 EndSection ---8---8---8---8---8 XOrg.log: ---8---8---8---8---8 X Window System Version 7.1.1 Release Date: 12 May 2006 X Protocol Version 11, Revision 0, Release 7.1.1 Build Operating System: UNKNOWN Current Operating System: Linux arrakis 2.6.18-1-k7 #1 SMP Fri Sep 29 17:06:47 UTC 2006 i686 Build Date: 07 July 2006 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default
Bug#392915: xserver-xorg-video-ati: xserver freezes system when starting
On Sat, 2006-10-14 at 08:58 +0200, [EMAIL PROTECTED] wrote: Package: xserver-xorg-video-ati Version: 1:6.6.3-1 Severity: grave When starting xserver, screen is blank (black) and the systems is frozen (SysRq not working). 'vesa' drivers works but is really slow... 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R200 QL [Radeon 8500 LE] And this doesn't happen with version 6.6.2? If so, it would be great if you could try isolating the upstream change that causes it with git-bisect. Loaddri Does it also happen if you don't enable the DRI? (**) Ignoring ABI Version This is generally a bad idea, although it shouldn't cause trouble in this case in theory. (II) RADEON(0): I2C bus DDC initialized. (II) RADEON(0): Legacy BIOS detected (II) RADEON(0): Connector0: DDCType-2, DACType-1, TMDSType-0, ConnectorType-3 (II) RADEON(0): Connector1: DDCType-3, DACType-0, TMDSType--1, ConnectorType-2 (II) RADEON(0): I2C device DDC:ddc2 registered at address 0xA0. (II) RADEON(0): I2C device DDC:ddc2 removed. (II) RADEON(0): DDC Type: 2, Detected Type: 3 ---8---8---8---8---8 That's an odd place for the log to stop... Can you not even log in remotely or ping the machine at this point? If so, can you try re-mounting the filesystem that contains the log file with -o sync before starting the X server and see if you get any more output then? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
