From: Stephen H. <she...@li...> - 2007-01-26 22:56:40
|
Running on a Intel Core 2 Duo, with 4G of memory. If I enable BIOS remapping (to allow used of all the memory) then the system boots but dies when X starts. If I turn off remapping (so system only hase 3.5G of memory), then everything is fine. Looks like something in the video (DRM) drivers can't handle > 4G of memory. System is running 2.6.20-rc6 with drm and radeon modules. Video card info: 06:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] (prog-if 00 [VGA]) Subsystem: VISIONTEK Unknown device 0401 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, Cache Line Size: 16 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M] Region 1: I/O ports at c800 [size=256] Region 2: Memory at ff9f0000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at ff9c0000 [disabled] [size=128K] Capabilities: <access denied> 00: 02 10 60 5b 07 00 10 00 00 00 00 03 04 00 80 00 10: 08 00 00 e0 01 c8 00 00 00 00 9f ff 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 45 15 01 04 30: 00 00 9c ff 50 00 00 00 00 00 00 00 0a 01 00 00 06:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE] Subsystem: VISIONTEK Unknown device 0400 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, Cache Line Size: 16 bytes Region 0: Memory at ff9e0000 (32-bit, non-prefetchable) [disabled] [size=64K] Capabilities: <access denied> 00: 02 10 70 5b 04 00 10 00 00 00 80 03 04 00 00 00 10: 00 00 9e ff 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 45 15 00 04 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 00 00 -- Stephen Hemminger <she...@li...> |
From: Michel <mi...@tu...> - 2007-01-27 09:47:15
|
On Fri, 2007-01-26 at 14:54 -0800, Stephen Hemminger wrote: > Running on a Intel Core 2 Duo, with 4G of memory. > If I enable BIOS remapping (to allow used of all the memory) > then the system boots but dies when X starts. If I turn off remapping > (so system only hase 3.5G of memory), then everything is fine. > > Looks like something in the video (DRM) drivers can't handle > 4G of memory. > > System is running 2.6.20-rc6 with drm and radeon modules. Please post the full Xorg.0.log file. Would be great if you could also try the drm git tree. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer |
From: Andi K. <ak...@su...> - 2007-01-27 13:07:56
|
On Friday 26 January 2007 23:54, Stephen Hemminger wrote: > Running on a Intel Core 2 Duo, with 4G of memory. > If I enable BIOS remapping (to allow used of all the memory) > then the system boots but dies when X starts. If I turn off remapping > (so system only hase 3.5G of memory), then everything is fine. > > Looks like something in the video (DRM) drivers can't handle > 4G of memory. Does the system run stable (in particularly when you fill all memory) without X? We have had cases in the past where the BIOS just got memory remapping wrong and some memory areas caused hangs. These were on AMD, not Intel, but older Intel desktop chipsets didn't do > 4GB addresses at all and there might be new trouble with that. -Andi |
From: Adam G. <ad...@ev...> - 2007-01-27 16:40:12
Attachments:
signature.asc
|
Andi Kleen wrote: > On Friday 26 January 2007 23:54, Stephen Hemminger wrote: >> Running on a Intel Core 2 Duo, with 4G of memory. >> If I enable BIOS remapping (to allow used of all the memory) >> then the system boots but dies when X starts. If I turn off remapping >> (so system only hase 3.5G of memory), then everything is fine. >> >> Looks like something in the video (DRM) drivers can't handle > 4G of m= emory. >=20 > Does the system run stable (in particularly when you fill all memory)=20 > without X? We have had cases in the past where the BIOS just got > memory remapping wrong and some memory areas caused hangs. These > were on AMD, not Intel, but older Intel desktop chipsets > didn't do > 4GB addresses at all and there might be new trouble > with that. >=20 > -Andi >=20 Could this be the cause of https://bugs.freedesktop.org/show_bug.cgi?id=3D9074 ? The machine in this bug is a Dell with 4GB of memory in 64-bit mode. Is there a log dump I could give that would be useful? dmesg or lspci ? Thanks, Adam |
From: Stephen H. <she...@li...> - 2007-01-30 01:27:49
|
If I do the radical thing and get rid of xorg.conf completely, then X boots without DRI and runs fine. Looks like a DRM/radeon driver. -- Stephen Hemminger <she...@li...> |
From: Stephen H. <she...@li...> - 2007-01-29 22:50:15
|
On Sat, 27 Jan 2007 13:36:03 +0100 Andi Kleen <ak...@su...> wrote: > On Friday 26 January 2007 23:54, Stephen Hemminger wrote: > > Running on a Intel Core 2 Duo, with 4G of memory. > > If I enable BIOS remapping (to allow used of all the memory) > > then the system boots but dies when X starts. If I turn off remapping > > (so system only hase 3.5G of memory), then everything is fine. > > > > Looks like something in the video (DRM) drivers can't handle > 4G of memory. > > Does the system run stable (in particularly when you fill all memory) > without X? We have had cases in the past where the BIOS just got > memory remapping wrong and some memory areas caused hangs. These > were on AMD, not Intel, but older Intel desktop chipsets > didn't do > 4GB addresses at all and there might be new trouble > with that. > > -Andi It seemed stable, I'll try using it as a server (without X). -- Stephen Hemminger <she...@li...> |
From: <rap...@im...> - 2007-01-30 09:17:17
|
Stephen Hemminger wrote: > On Sat, 27 Jan 2007 13:36:03 +0100 > Andi Kleen <ak...@su...> wrote: > >> On Friday 26 January 2007 23:54, Stephen Hemminger wrote: >>> Running on a Intel Core 2 Duo, with 4G of memory. >>> If I enable BIOS remapping (to allow used of all the memory) >>> then the system boots but dies when X starts. If I turn off remapping >>> (so system only hase 3.5G of memory), then everything is fine. >>> >>> Looks like something in the video (DRM) drivers can't handle > 4G of memory. >> Does the system run stable (in particularly when you fill all memory) >> without X? We have had cases in the past where the BIOS just got >> memory remapping wrong and some memory areas caused hangs. These >> were on AMD, not Intel, but older Intel desktop chipsets >> didn't do > 4GB addresses at all and there might be new trouble >> with that. >> >> -Andi > > It seemed stable, I'll try using it as a server (without X). > I have *exactly* 4G of ram and have similar reaction. the machine is still functionnal though, as I was able to go in via ssh and request a reboot |
From: Dave A. <ai...@li...> - 2007-01-30 19:39:37
|
> 06:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] (prog-if 00 [VGA]) > Subsystem: VISIONTEK Unknown device 0401 > 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, Cache Line Size: 16 bytes > Interrupt: pin A routed to IRQ 16 > Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M] > Region 1: I/O ports at c800 [size=256] > Region 2: Memory at ff9f0000 (32-bit, non-prefetchable) [size=64K] > Expansion ROM at ff9c0000 [disabled] [size=128K] > Capabilities: <access denied> > 00: 02 10 60 5b 07 00 10 00 00 00 00 03 04 00 80 00 > 10: 08 00 00 e0 01 c8 00 00 00 00 9f ff 00 00 00 00 > 20: 00 00 00 00 00 00 00 00 00 00 00 00 45 15 01 04 > 30: 00 00 9c ff 50 00 00 00 00 00 00 00 0a 01 00 00 Does it always put the PCI stuff into the top 1GB address range, where does the final 1GB of memory go? or does lspci look diffferent with 4GBs in? Dave. |
From: Stephen H. <she...@li...> - 2007-01-30 22:37:56
Attachments:
lspci-map.txt
lspci-nomap.txt
|
On Tue, 30 Jan 2007 19:39:20 +0000 (GMT) Dave Airlie <ai...@li...> wrote: > > > 06:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] (prog-if 00 [VGA]) > > Subsystem: VISIONTEK Unknown device 0401 > > 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, Cache Line Size: 16 bytes > > Interrupt: pin A routed to IRQ 16 > > Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M] > > Region 1: I/O ports at c800 [size=256] > > Region 2: Memory at ff9f0000 (32-bit, non-prefetchable) [size=64K] > > Expansion ROM at ff9c0000 [disabled] [size=128K] > > Capabilities: <access denied> > > 00: 02 10 60 5b 07 00 10 00 00 00 00 03 04 00 80 00 > > 10: 08 00 00 e0 01 c8 00 00 00 00 9f ff 00 00 00 00 > > 20: 00 00 00 00 00 00 00 00 00 00 00 00 45 15 01 04 > > 30: 00 00 9c ff 50 00 00 00 00 00 00 00 0a 01 00 00 > > > Does it always put the PCI stuff into the top 1GB address range, where > does the final 1GB of memory go? or does lspci look diffferent with 4GBs > in? > > Dave. Here is the lspci output both with the mapped (4G) and non-mapped (3G) BIOS option. -- Stephen Hemminger <she...@li...> |
From: Adam G. <ad...@ev...> - 2007-01-31 05:47:00
Attachments:
signature.asc
signature.asc
|
Dave Airlie wrote: > Does it always put the PCI stuff into the top 1GB address range, where > does the final 1GB of memory go? or does lspci look diffferent with 4GBs > in? > Here is mine, with 4 GB of RAM. 01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B64 [FireGL V3100 (PCIE)] (rev 80) (prog-if 00 [VGA]) Subsystem: ATI Technologies Inc Unknown device 0102 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, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 11 Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M] Region 1: I/O ports at dc00 [size=256] Region 2: Memory at fe9e0000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at fea00000 [disabled] [size=128K] Capabilities: [50] 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- Capabilities: [58] Express Endpoint IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+ Device: Latency L0s <128ns, L1 <2us Device: AtnBtn- AtnInd- PwrInd- Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported- Device: RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 0 Link: Latency L0s <128ns, L1 <1us Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch- Link: Speed 2.5Gb/s, Width x16 Capabilities: [80] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [100] Advanced Error Reporting 00: 02 10 64 5b 07 00 10 00 80 00 00 03 10 00 80 00 10: 08 00 00 f0 01 dc 00 00 00 00 9e fe 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 02 10 02 01 30: 00 00 a0 fe 50 00 00 00 00 00 00 00 0b 01 00 00 /proc/iomem: 00000000-0009ffff : System RAM 00000000-00000000 : Crash kernel 000a0000-000bffff : Video RAM area 000c0000-000cafff : Video ROM 000cd000-000cffff : Adapter ROM 000f0000-000fffff : System ROM 00100000-dfe8abff : System RAM 00200000-00469171 : Kernel code 00469172-0064cccf : Kernel data dfe8ac00-dfe8cbff : ACPI Non-volatile Storage dfe8cc00-dfe8ebff : ACPI Tables dfe8ec00-e3ffffff : reserved f0000000-f7ffffff : PCI Bus #01 f0000000-f7ffffff : 0000:01:00.0 fe600000-fe6fffff : PCI Bus #05 fe6fa800-fe6fafff : 0000:05:02.2 fe6fa800-fe6fafff : ohci1394 fe6fb000-fe6fbfff : 0000:05:05.0 fe6fb000-fe6fb7ff : ohci1394 fe6fc000-fe6fffff : 0000:05:02.2 fe700000-fe7fffff : PCI Bus #04 fe7f0000-fe7fffff : 0000:04:00.0 fe7f0000-fe7fffff : tg3 fe800000-fe8fffff : PCI Bus #02 fe900000-feafffff : PCI Bus #01 fe9e0000-fe9effff : 0000:01:00.0 fe9f0000-fe9fffff : 0000:01:00.1 fea00000-fea1ffff : 0000:01:00.0 febffc00-febfffff : 0000:00:1f.2 febffc00-febfffff : ahci fed00000-fed003ff : HPET 0 fed20000-fed9ffff : reserved fee00000-feefffff : reserved ffa80800-ffa80bff : 0000:00:1d.7 ffa80800-ffa80bff : ehci_hcd ffb00000-ffffffff : reserved 100000000-11bffffff : System RAM Adam |
From: Stephen H. <she...@li...> - 2007-02-23 20:08:50
|
I ended up taking the easy way out and buying a cheap Nvidia card. It works fine with 4G of memory. |