Am Donnerstag, 10. Oktober 2002 01:42 schrieb Fabrice Bellet:
> On Thu, Oct 10, 2002 at 12:33:59AM +0200, Michel D�nzer wrote:
> > What date is the DRM source you're using from?
I got that "all" the time with my dual Athlon MP 1900+, but nobody found a
solution so far.
Anyone who can fix the current DRI CVS DRM module build for 2.5.40+?
Only 2.5.40+ (currently -ac3, here) gave good behavior (stuttering during Q3A
cinematics, UT).
> I updated my dri HEAD cvs tree two hours ago, and I rebuilt
> the drm module too.
Which kernel version?
> Oct 10 00:53:32 dhcp7 kernel: [drm] Debug messages ON
> Oct 10 00:53:32 dhcp7 kernel: [drm] AGP 0.99 on AMD Irongate @ 0xe8000000
> 128MB Oct 10 00:53:32 dhcp7 kernel: [drm] Initialized radeon 1.6.0 20020828
> on minor 0 Oct 10 00:53:33 dhcp7 kernel: [drm] Loading R200 Microcode
>
> > What's your IRQ setup?
>
> [root@dhcp7 root]# more /proc/interrupts
> CPU0 CPU1
> 0: 463862 0 XT-PIC timer
> 1: 412 0 XT-PIC keyboard
> 2: 0 0 XT-PIC cascade
> 3: 7274 0 XT-PIC eth0
> 5: 115148 0 XT-PIC aic7xxx, EMU10K1
> 8: 1 0 XT-PIC rtc
> 10: 44102 0 XT-PIC aic7xxx, radeon@PCI:1:5:0
> 11: 22 0 XT-PIC usb-ohci
> 12: 3431 0 XT-PIC PS/2 Mouse
> 14: 10141 0 XT-PIC ide0
> NMI: 0 0
> LOC: 463790 463789
> ERR: 69
> MIS: 0
>
> Hmm, all the interrupts are routed to the same CPU ? the SCSI disk
> is on the first scsi0 controller (irq 5 I assume).
Are you running a "current" kernel with IRQ balancing?
Have you tried with APIC enabled?
ACPI is useful, too (IRQ routing).
<6>ACPI: Subsystem revision 20020918
<6>ACPI: Interpreter enabled
<6>ACPI: Using IOAPIC for interrupt routing
<6>ACPI: PCI Root Bridge [PCI0] (00:00)
<4>PCI: Probing PCI hardware (bus 00)
<7>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
<7>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.OP2P._PRT]
<7>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPP._PRT]
<4>ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 10 11 12 14 15)
<4>ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
<4>ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11 12 14 15)
<4>ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11 12 14 15)
<7>IOAPIC[0]: Set PCI routing entry (2-16 -> 0xa9 -> IRQ 16)
<7>00:00:08[A] -> 2-16 -> IRQ 16
<7>IOAPIC[0]: Set PCI routing entry (2-17 -> 0xb1 -> IRQ 17)
<7>00:00:08[B] -> 2-17 -> IRQ 17
<7>IOAPIC[0]: Set PCI routing entry (2-18 -> 0xb9 -> IRQ 18)
<7>00:00:08[C] -> 2-18 -> IRQ 18
<7>IOAPIC[0]: Set PCI routing entry (2-19 -> 0xc1 -> IRQ 19)
<7>00:00:08[D] -> 2-19 -> IRQ 19
<7>Pin 2-17 already programmed
<7>Pin 2-18 already programmed
> > Does the interrupt count for the radeon increase
> > in /proc/interrupts after this happens?
Here of course (r200). Felix worked on that.
/home/nuetzel> cat /proc/interrupts
CPU0 CPU1
0: 1011369 1026017 IO-APIC-edge timer
1: 2922 2936 IO-APIC-edge i8042
2: 0 0 XT-PIC cascade
7: 1 1 IO-APIC-edge parport0
8: 2 1 IO-APIC-edge rtc
9: 0 0 IO-APIC-level acpi
12: 10328 10520 IO-APIC-edge i8042
16: 9607 9904 IO-APIC-level EMU10K1
17: 1482 1495 IO-APIC-level eth0, eth1, radeon@PCI:1:5:0
18: 27786 27858 IO-APIC-level aic7xxx
NMI: 0 0
LOC: 2037365 2037400
ERR: 0
MIS: 0
> Does a single client work afterwards?
Mostly: NO, I have to reboot with SysRq.
> The previous trace finished with a complete machine hang, after both
> clients terminated with the drmRadeonIrqWait: -16 error.
>
> > Does this work with R200_NO_IRQS?
>
> Setting R200_NO_IRQS=1 didn't change the behaviour. The machine crashed
> after both clients existed with r200WaitForFrameCompletion:
> drmRadeonIrqWait: -16
Like with multiple context here.
I'll try with R200_NO_IRQS and/or R200_DEBUG, now.
-Dieter
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
