On Sat, 2004-01-10 at 11:30, Michel DÃnzer wrote: > On Thu, 2004-01-08 at 00:40, Stephen Waters wrote: > > System: > > MSI K8T Master2-FAR > > Dual Opteron > > Radeon VE > > Debian 'sid' (32-bit Xfree86) > > Kernel 2.6.1-rc2-bk1 > > Have you tried the DRI snapshot packages described in > http://dri.sourceforge.net/snapshots/README.Debian yet?
not yet. If this latest kernel (2.6.1-bk1) doesn't work, I'll give those
patches a shot.
> What stability problem? Note that the getparam ioctl is only used by the
> 3D driver.
It crashed if you did much of anything. :) Sometimes gdm would crash,
sometimes my start-up apps will load and then it will crash.
Currently, I'm writing this on 2.6.1-bk1, AMD64. It seems to work
mostly, but Enlightenment crashes fairly often. I kinda wonder how
hardcore Rasterman got with the asm in Imlib...
The big difference is I compiled Linux DRI radeon as a module this time
instead of statically. That seemed to clear up a good bit of the
stability. I still get the ioctl32 error, though.
> > here are the errors I'm getting (this is Debian 'sid' 32-bit Xfree86,
> > just to be clear):
> >
> > --kern.log--
> > Jan 7 00:42:37 localhost kernel: ioctl32(XFree86:391): Unknown cmd fd(6)
> > cmd(c0246400){00} arg(085d1320) on /dev/dri/card0
> > Jan 7 00:42:37 localhost kernel: ioctl32(XFree86:391): Unknown cmd fd(6)
> > cmd(c0246400){00} arg(085d1320) on /dev/dri/card0
>
> AFAICT this is the DRM_IOCTL_VERSION ioctl, odd that it would be
> missing... I wonder if the ioctls need special treatment for 32 bit
> apps?
Xavier Hienne thinks:
--
I always thought ioctl numbers would be constants among archs but DRM
ioctl numbers depend on the architecture. Here, ioctl c0246400 is
DRM_IOCTL_VERSION, but only on a 32bit arch because the size of a
structure is hardcoded into this number (bits 16 to 29 - see comment in
/usr/src/linux/include/asm/ioctl.h). The pb is that this structure
contains 3 pointers, thus its size goes from 0x024 on a 32 bit arch, to
0x030 (my guess) on a 64 bit arch.
--
> > Jan 7 00:42:46 localhost kernel: XFree86[391]: segfault at 0000000000000077 rip
> > 00000000085d08ec rsp 00000000ffffd6f4 error 6
>
> If this is a 'normal' X server segfault, you should try to get a
> backtrace, e.g. using the xserver-xfree86-dbg package.
i'll get you an 'strace -p' when I can... FYI.
Cheers and thanks for looking at this,
-s
signature.asc
Description: This is a digitally signed message part
