Re: X doesn't work anymore

> Hi,
>
> On Fri, Jul 10, 2009 at 10:49:22PM +0200, Michael wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hello,
>>
>> On Jul 10, 2009, at 4:45 PM, Kurt Schreiner wrote:
>> [....]
>>> Yep, including "options PCI_ALLOW_MMAP" gets things going again - as
>>> long as I don't add "radeondrm* at vga?", too. With this added I get
>>> an unusable X server causing 100% sys in vmstat...
>>
>> And that worked before?
> That worked 'till ~ mid June - at least that was the last time I  
> tried.
>
> /var/log/messages.1.gz:Jun 19 22:02:26 ipaddi /netbsd: radeondrm0 at  
> vga0: ATI FireGL M24 GL (unit 0)
> /var/log/messages.1.gz:Jun 19 22:02:26 ipaddi /netbsd: radeondrm0:  
> Initialized radeon 1.26.0 20060524
> /var/log/messages.1.gz:Jun 19 22:02:37 ipaddi /netbsd: info: [drm]  
> Setting GART location based on new memory map
> /var/log/messages.1.gz:Jun 19 22:02:37 ipaddi /netbsd: info: [drm]  
> Loading R300 Microcode
> /var/log/messages.1.gz:Jun 19 22:02:37 ipaddi /netbsd: info: [drm]  
> writeback test failed
> /var/log/messages.1.gz:Jun 19 22:02:37 ipaddi /netbsd: radeondrm0:  
> interrupting at ioapic0 pin 16
>
>> All that changed is how PCI devices are found and through which /dev
>> entry they are mapped, the resulting mappings should be identical.
>> Where does the Xserver spin?
> Doing an ioctl on /dev/dri/card0:
>
>   571      1 Xorg     CALL  ioctl(0xb,_IO('d',0x44),0)
>   571      1 Xorg     RET   ioctl -1 errno 16 Device busy
>   571      1 Xorg     CALL  ioctl(0xb,_IO('d',0x44),0)
>   571      1 Xorg     RET   ioctl -1 errno 16 Device busy
> ^C