Bugzilla – Bug 204521
runaway memory leak on i815
Last modified: 2006-09-14 13:31:33 UTC
Dell GX150 i815 system with onboard video using main system memory. It has also installed working Debian Etch, Xandros 3, Knoppix 4 & Kubuntu 6.06. Fresh install failed to start in graphics mode. Installed in text mode. On first boot after finishing installation, attempted to run sax2, which aborted without ever getting into any graphics mode after blinking the screen several times trying. When I rebooted and tried again, I opened top on another console. I checked while sax2 was running and found RAM and swap rapidly disappearing. Eventually sax2 ended after consuming almost 2G of RAM with: SaX: no X-Server is running SaX: will start own server if needed SaX: call sax2 -p and select a single device abort # # sax2 -p Chip: 0 is -> Intel I815 00:02:0 0x8086 0x1132 PCI i810 I couldn't tell from the man page which of the above is the device it wants. I tried: # sax2 -c i810 That too produced runaway RAM consumption. /var/log/Xorg.0.log ends with the following (similar to bug 204324 ): 0: Xorg(xf86SigHandler+0x81) [0x80cbb11] 1: [0xb7fba420] 2: /usr/lib/xorg/modules//libfb.so(fbOddTile+0x118) [0xb7b90978] 3: /usr/lib/xorg/modules//libfb.so(fbTile+0x8c) [0xb7b90a3c] 4: /usr/lib/xorg/modules//libfb.so(fbFillRegionTiled+0x19e) [0xb7b912ee] 5: /usr/lib/xorg/modules//libfb.so(fbPaintWindow+0x109) [0xb7b915c9] 6: Xorg [0x8156c21] 7: Xorg(miWindowExposures+0xfa) [0x810c69a] 8: Xorg(MapWindow+0x332) [0x8072c52] 9: Xorg(InitRootWindow+0xbe) [0x8072dee] 10: Xorg(main+0x42f) [0x806e55f] 11: /lib/libc.so.6(__libc_start_main+0xdc) [0xb7d6087c] 12: Xorg(FontFileCompleteXLFS+0x1f5) [0x806d8e1] Fatal server error: Caught signal 11. Server aborting
what does sax2 -p tell you ?
that is answered in comment 0
*ups* sorry yes of course. ok there is only chip Is it possible to create an automatic config file with the following command: sax2 -r -a Thanks
sax2 -r -a also aborts after consuming all RAM and swap: SaX: no X-Server is running SaX: will start own server if needed SaX: call sax2 -p and select a single device abort Might bug 204521 be related?
Oops, bad paste. I meant: Might bug 204324 be related?
I think not but I maybe wrong in that case. Stefan what do you think ? Could you reproduce this problem with one of our Intel devices ? I have only an i915 here which works for me Chip: 0 is -> Intel I815 00:02:0 0x8086 0x1132 PCI i810
*** This bug has been marked as a duplicate of bug 204324 ***