0000:00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 01)
Subsystem: Dell: Unknown device 0126
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 0
Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
Capabilities: <available only to root>
0000:00:02.0 VGA compatible controller: Intel Corp. 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01) (prog-if 00 [VGA])
Subsystem: Dell: Unknown device 0126
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 9
Region 0: Memory at e8000000 (32-bit, prefetchable) [size=128M]
Region 1: Memory at ff680000 (32-bit, non-prefetchable) [size=512K]
Capabilities: <available only to root>
0000:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01) (prog-if 00 [UHCI])
Subsystem: Dell: Unknown device 0126
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
Interrupt: pin A routed to IRQ 9
Region 4: I/O ports at ff80 [size=32]
0000:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01) (prog-if 00 [UHCI])
Subsystem: Dell: Unknown device 0126
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
Interrupt: pin B routed to IRQ 11
Region 4: I/O ports at ff60 [size=32]
0000:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01) (prog-if 00 [UHCI])
Subsystem: Dell: Unknown device 0126
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
Interrupt: pin C routed to IRQ 10
Region 4: I/O ports at ff40 [size=32]
0000:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI Controller (rev 01) (prog-if 20 [EHCI])
Subsystem: Dell: Unknown device 0126
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
Interrupt: pin D routed to IRQ 3
Region 0: Memory at ffa00800 (32-bit, non-prefetchable) [size=1K]
Capabilities: <available only to root>
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 81) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR+
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: ff800000-ff9fffff
BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
0000:00:1f.0 ISA bridge: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) LPC Bridge (rev 01)
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
0000:00:1f.1 IDE interface: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) UltraATA-100 IDE Controller (rev 01) (prog-if 8a [Master SecP PriP])
Subsystem: Dell: Unknown device 0126
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
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at <unassigned>
Region 1: I/O ports at <unassigned>
Region 2: I/O ports at <unassigned>
Region 3: I/O ports at <unassigned>
Region 4: I/O ports at ffa0 [size=16]
Region 5: Memory at 1ff00000 (32-bit, non-prefetchable) [size=1K]
0000:00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
Subsystem: Dell: Unknown device 0126
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-
Interrupt: pin B routed to IRQ 11
Region 4: I/O ports at dc80 [size=32]
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
Subsystem: Dell: Unknown device 0126
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
Interrupt: pin B routed to IRQ 11
Region 0: I/O ports at d800 [size=256]
Region 1: I/O ports at dc40 [size=64]
Region 2: Memory at ffa00400 (32-bit, non-prefetchable) [size=512]
Region 3: Memory at ffa00000 (32-bit, non-prefetchable) [size=256]
Capabilities: <available only to root>
0000:01:0c.0 Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller (rev 02)
Subsystem: Dell: Unknown device 002e
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: 64 (63750ns min), Cache Line Size: 0x10 (64 bytes)
Interrupt: pin A routed to IRQ 10
Region 0: Memory at ff8e0000 (32-bit, non-prefetchable) [size=128K]
Region 2: I/O ports at ecc0 [size=64]
Capabilities: <available only to root>
>
> I am experiencing problems with DRM on my Dell Optiplex GX260.
> I am running a Debian Sarge with Vanilla Linux 2.6.11 and XFree 4.3.0.
> This one appeared while playing crack-attack and lead to a crash
> of the X server.
>
a) does it work with 2.6.10?
b) does it work if you turn off intelfb?
Dave.
Dave Airlie <[email protected]> wrote:
>
> >
> > I am experiencing problems with DRM on my Dell Optiplex GX260.
> > I am running a Debian Sarge with Vanilla Linux 2.6.11 and XFree 4.3.0.
> > This one appeared while playing crack-attack and lead to a crash
> > of the X server.
> >
>
> a) does it work with 2.6.10?
> b) does it work if you turn off intelfb?
>
afacit we're still waiting for an answer from Brice on this one?
Andrew Morton a ?crit :
> Dave Airlie <[email protected]> wrote:
>
>>>I am experiencing problems with DRM on my Dell Optiplex GX260.
>>>I am running a Debian Sarge with Vanilla Linux 2.6.11 and XFree 4.3.0.
>>>This one appeared while playing crack-attack and lead to a crash
>>>of the X server.
>>>
>>
>>a) does it work with 2.6.10?
>>b) does it work if you turn off intelfb?
>>
>
> afacit we're still waiting for an answer from Brice on this one?
Sorry about that, we start to talk about it in private with Dave.
But, I did not really it since Keenan Pepper told me it was due
to a bug in the XFree 4.3 driver.
I am now using Xorg and didn't see any DRM problem since.
However, I can't confirm that my bug was surely due to the XFree driver
and not to the kernel driver since Xorg uses i915 instead of i830.
Keenan, do you have details ?
I was also talking about a problem in intelfb on this box (i845G).
Basically, it works great during startup. But from what I remember, it
always crashes when switching from X to a text console.
I'll try to debug this one soon.
Brice
Brice Goglin <[email protected]> wrote:
>
> Andrew Morton a ?crit :
> > Dave Airlie <[email protected]> wrote:
> >
> >>>I am experiencing problems with DRM on my Dell Optiplex GX260.
> >>>I am running a Debian Sarge with Vanilla Linux 2.6.11 and XFree 4.3.0.
> >>>This one appeared while playing crack-attack and lead to a crash
> >>>of the X server.
> >>>
> >>
> >>a) does it work with 2.6.10?
> >>b) does it work if you turn off intelfb?
> >>
> >
> > afacit we're still waiting for an answer from Brice on this one?
>
> Sorry about that, we start to talk about it in private with Dave.
> But, I did not really it since Keenan Pepper told me it was due
> to a bug in the XFree 4.3 driver.
> I am now using Xorg and didn't see any DRM problem since.
> However, I can't confirm that my bug was surely due to the XFree driver
> and not to the kernel driver since Xorg uses i915 instead of i830.
> Keenan, do you have details ?
OK, that sounds promising. Would you view this as a regression? Was XFree
4.3 working OK on earlier 2.6 kernels?
> I was also talking about a problem in intelfb on this box (i845G).
> Basically, it works great during startup. But from what I remember, it
> always crashes when switching from X to a text console.
> I'll try to debug this one soon.
Great. Please cc [email protected] and myself when
you have more.
> Sorry about that, we start to talk about it in private with Dave.
> But, I did not really it since Keenan Pepper told me it was due
> to a bug in the XFree 4.3 driver.
> I am now using Xorg and didn't see any DRM problem since.
> However, I can't confirm that my bug was surely due to the XFree driver
> and not to the kernel driver since Xorg uses i915 instead of i830.
> Keenan, do you have details ?
Yes, I talked to Alan Hourihane about it and he identified it as a
memory allocation bug in the i810 X server driver. It's not related to
DRI - it happens even with DRI turned off - so it wouldn't matter which
DRM module is being used.
Andrew Morton a ?crit :
> Brice Goglin <[email protected]> wrote:
>>Sorry about that, we start to talk about it in private with Dave.
>>But, I did not really it since Keenan Pepper told me it was due
>>to a bug in the XFree 4.3 driver.
>>I am now using Xorg and didn't see any DRM problem since.
>>However, I can't confirm that my bug was surely due to the XFree driver
>>and not to the kernel driver since Xorg uses i915 instead of i830.
>>Keenan, do you have details ?
>
>
> OK, that sounds promising. Would you view this as a regression? Was XFree
> 4.3 working OK on earlier 2.6 kernels?
From what I remember, X had never been stable on this box.
So I'll vote for no regression here.
The main reason for this bug report was that I was tired
of getting a crash, say every two weeks. But now Xorg works
great.
Regards,
Brice