Bug#513790: libgl1-mesa-dri: SAVAGE(0): [drm] drmSetBusid failed (7, pci:0000:01:00.0), Permission denied

[oopla-pzp]

Package: libgl1-mesa-dri
Version: 6.5.1-0.6
Severity: normal

hello,

I'm seeing msg in subject in the logs, more extensively, here's the result
from " egrep 'dri|drm|enab' /var/log/Xorg.0.log":

        X.Org XInput driver : 0.6
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
(II) Loading sub module "drm"
(II) LoadModule: "drm"
(II) Loading /usr/lib/xorg/modules/linux/libdrm.so
(II) Module drm: vendor="X.Org Foundation"
        ABI class: X.Org XInput driver, version 0.6
(==) AIGLX enabled
(II) Loading /usr/lib/xorg/modules/drivers/savage_drv.so
        ABI class: X.Org XInput driver, version 0.6
        ABI class: X.Org XInput driver, version 0.6
(II) SAVAGE: driver (version 2.1.2) for S3 Savage chipsets: Savage4,
(II) SAVAGE(0): [drm] bpp: 32 depth: 24
(II) SAVAGE(0): [drm] Sarea 2200+284: 2484
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(II) SAVAGE(0): [drm] DRM interface version 1.3
(II) SAVAGE(0): [drm] created "savage" driver at busid "pci:0000:01:00.0"
(II) SAVAGE(0): [drm] added 8192 byte SAREA at 0xf8a52000
(II) SAVAGE(0): [drm] mapped SAREA 0xf8a52000 to 0xa7994000
(II) SAVAGE(0): [drm] framebuffer handle = 0xf0000000
(II) SAVAGE(0): [drm] added 1 reserved context for kernel
(II) SAVAGE(0): [drm] aperture handle = 0xf2000000
(II) SAVAGE(0): [drm] Enabling ShadowStatus for DRI.
(II) SAVAGE(0): [drm] Status handle = 0x2f8f2000
(II) SAVAGE(0): [drm] Status page mapped at 0xa7993000
(II) SAVAGE(0): [dri] visual configs initialized
(**) SAVAGE(0): DRI is enabled
(**) SAVAGE(0): DPMS enabled
(II) SAVAGE(0): Direct rendering enabled
(==) RandR enabled
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(II) AIGLX: Loaded and initialized /usr/lib/dri/savage_dri.so
#--[2]-------
(II) SAVAGE(0): [drm] removed 1 reserved context for kernel
(II) SAVAGE(0): [drm] unmapping 8192 bytes of SAREA 0xf8a52000 at 0xa7994000
(II) SAVAGE(0): [drm] bpp: 32 depth: 24
(II) SAVAGE(0): [drm] Sarea 2200+284: 2484
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(II) SAVAGE(0): [drm] DRM interface version 1.0
(II) SAVAGE(0): [drm] drmSetBusid failed (7, pci:0000:01:00.0), Permission denied
(EE) SAVAGE(0): [drm] DRIScreenInit failed.  Disabling DRI.
(EE) SAVAGE(0): DRI isn't enabled
(**) SAVAGE(0): DPMS enabled
(==) RandR enabled

and # tail -4 /etc/X11/xorg.conf

Section "DRI"
        Mode    0666
EndSection

# ls -l /dev/dri/card0
crw-rw-rw- 1 root root 226, 0 2009-01-31 16:18 /dev/dri/card0

note that up to '#--[2]-' marker above, it's the log from wdm restart and
wm session - indeed, I see glxheads reports DRI and all seems fine; log
after '#--[2]-' marker result from wm session close and back to wdm login.
Then in next wm session glxheads reports

GL_RENDERER: Mesa GLX Indirect

any clues?


thanks
--
 paolo
 
 GPG/PGP id:0x3A47DE45  - B5F9 AAA0 44BD 2B63 81E0  971F C6C0 0B87 3A47 DE45
 - 9/11: the outrageous deception & coverup: http://journalof911studies.com -



--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Brice Goglin]

Paolo wrote:
> Package: libgl1-mesa-dri
> Version: 6.5.1-0.6
> Severity: normal
>
> hello,
>
> I'm seeing msg in subject in the logs, more extensively, here's the result
> from " egrep 'dri|drm|enab' /var/log/Xorg.0.log":
>  

Did it work before? What did you upgrade when it broke?

Any chance you upgrade your Mesa packages to something more recent? Mesa
6.5.1 is very old, we have 7.0.4 in testing/unstable and 7.3 in
experimental...

Brice




--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[oopla-pzp]

On Sun, Feb 01, 2009 at 11:09:14AM +0100, Brice Goglin wrote:
>
> Did it work before? What did you upgrade when it broke?

not sure, I checked only after noticing a glitch in an app. supposed to
take advantage from dri, and - as reported - it does work on first
wdm start -> wm session open, but then it breaks on next
wm close -> wdm -> wm session open.
I've got same system but on other hw, with radeon, which afaikt didn't
show such problem, so far.

> Any chance you upgrade your Mesa packages to something more recent? Mesa
> 6.5.1 is very old, we have 7.0.4 in testing/unstable and 7.3 in
> experimental...

yes, if there are bpo .debs for etch, else I'm afraid I'd wait till next
testing->stable cycle.

thanks

--
 paolo
 
 GPG/PGP id:0x3A47DE45  - B5F9 AAA0 44BD 2B63 81E0  971F C6C0 0B87 3A47 DE45



--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Julien Cristau-6]

On Sun, Feb  1, 2009 at 14:11:11 +0100, Paolo wrote:

> On Sun, Feb 01, 2009 at 11:09:14AM +0100, Brice Goglin wrote:
> >
> > Did it work before? What did you upgrade when it broke?
>
> not sure, I checked only after noticing a glitch in an app. supposed to
> take advantage from dri, and - as reported - it does work on first
> wdm start -> wm session open, but then it breaks on next
> wm close -> wdm -> wm session open.
> I've got same system but on other hw, with radeon, which afaikt didn't
> show such problem, so far.
>
> > Any chance you upgrade your Mesa packages to something more recent? Mesa
> > 6.5.1 is very old, we have 7.0.4 in testing/unstable and 7.3 in
> > experimental...
>
> yes, if there are bpo .debs for etch, else I'm afraid I'd wait till next
> testing->stable cycle.
>

Hi,

What's the status of this in lenny?  I'm afraid there's not much
interest for the savage drivers upstream, but if it still happens this
should be either reported there or marked wontfix.

Cheers,
Julien



--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[oopla-pzp]

On Fri, Nov 06, 2009 at 06:45:20PM +0100, Julien Cristau wrote:
>
> What's the status of this in lenny?  I'm afraid there's not much

sorry, I don't have access to that hw anymore so I'm unable to do further
tests.

> should be either reported there or marked wontfix.

not sure, I don't have enough knowledge / data to state it deserves a
wontfix. I'd leave it open till either lenny drops to oldstable or etch
becomes unsupported.


thx
--
paolo



--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...