Re: DRI breakage, 2.6.11-mm[123]
> > Same symptoms with 2.6.11-bk8. damn.. am travelling at the moment, won't get a chance to take a detailed look for a while.. I'll see can I figure it out just from code inspection... Dave. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: DRI breakage, 2.6.11-mm[123]
Dave Jones <[EMAIL PROTECTED]> writes: > On Sun, Mar 13, 2005 at 10:13:49AM +1100, Dave Airlie wrote: > > On Sat, 12 Mar 2005 19:29:20 +, Sean Neakums <[EMAIL PROTECTED]> wrote: > > > Sean Neakums <[EMAIL PROTECTED]> writes: > > > > > > > The following happens with 2.6.11-mm[123]. (I didn't have time to > > > > investigate earlier; sorry.) It does not happen with 2.6.11-rc3-mm2 > > > > and 2.6.11. I have tested 2.6.11-mm3 with dri disabled (by not > > > > loading X's dri module) and it also does not happen then. > > > > > > Also happens on 2.6.11-mm3 with bk-drm.patch reverted. > > > > > > To expand on my crappy report, the graphics card is a Radeon 9200: > > > > Wierd the -mm tree has currently very few drm changes over the non-mm > > tree and if reverting bk-drm doesn't help it sounds like something in > > the generic ioctl code may be gone wrong... > > > > Can you try a 2.6.12-bk snapshot.. it may be the multi-head patches > > are buggy > > Could be. Given the other agp problems didn't get spotted in -mm > my confidence in those patches has dropped off somewhat in the > last few days. > > Hopefully it's something simple. Same symptoms with 2.6.11-bk8. -- Dag vijandelijk luchtschip de huismeester is dood - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: DRI breakage, 2.6.11-mm[123]
On Sun, Mar 13, 2005 at 10:13:49AM +1100, Dave Airlie wrote: > On Sat, 12 Mar 2005 19:29:20 +, Sean Neakums <[EMAIL PROTECTED]> wrote: > > Sean Neakums <[EMAIL PROTECTED]> writes: > > > > > The following happens with 2.6.11-mm[123]. (I didn't have time to > > > investigate earlier; sorry.) It does not happen with 2.6.11-rc3-mm2 > > > and 2.6.11. I have tested 2.6.11-mm3 with dri disabled (by not > > > loading X's dri module) and it also does not happen then. > > > > Also happens on 2.6.11-mm3 with bk-drm.patch reverted. > > > > To expand on my crappy report, the graphics card is a Radeon 9200: > > Wierd the -mm tree has currently very few drm changes over the non-mm > tree and if reverting bk-drm doesn't help it sounds like something in > the generic ioctl code may be gone wrong... > > Can you try a 2.6.12-bk snapshot.. it may be the multi-head patches > are buggy Could be. Given the other agp problems didn't get spotted in -mm my confidence in those patches has dropped off somewhat in the last few days. Hopefully it's something simple. Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: DRI breakage, 2.6.11-mm[123]
On Sat, 12 Mar 2005 19:29:20 +, Sean Neakums <[EMAIL PROTECTED]> wrote: > Sean Neakums <[EMAIL PROTECTED]> writes: > > > The following happens with 2.6.11-mm[123]. (I didn't have time to > > investigate earlier; sorry.) It does not happen with 2.6.11-rc3-mm2 > > and 2.6.11. I have tested 2.6.11-mm3 with dri disabled (by not > > loading X's dri module) and it also does not happen then. > > Also happens on 2.6.11-mm3 with bk-drm.patch reverted. > > To expand on my crappy report, the graphics card is a Radeon 9200: Wierd the -mm tree has currently very few drm changes over the non-mm tree and if reverting bk-drm doesn't help it sounds like something in the generic ioctl code may be gone wrong... Can you try a 2.6.12-bk snapshot.. it may be the multi-head patches are buggy Dave. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: DRI breakage, 2.6.11-mm[123]
Sean Neakums <[EMAIL PROTECTED]> writes: > The following happens with 2.6.11-mm[123]. (I didn't have time to > investigate earlier; sorry.) It does not happen with 2.6.11-rc3-mm2 > and 2.6.11. I have tested 2.6.11-mm3 with dri disabled (by not > loading X's dri module) and it also does not happen then. Also happens on 2.6.11-mm3 with bk-drm.patch reverted. To expand on my crappy report, the graphics card is a Radeon 9200: :01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200] (rev 01) -- Dag vijandelijk luchtschip de huismeester is dood - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
DRI breakage, 2.6.11-mm[123]
The following happens with 2.6.11-mm[123]. (I didn't have time to investigate earlier; sorry.) It does not happen with 2.6.11-rc3-mm2 and 2.6.11. I have tested 2.6.11-mm3 with dri disabled (by not loading X's dri module) and it also does not happen then. When I start X, I get a screen full of what looks like random pixels. Apart from the pointer, X seems generally non-functional. The X server (Debian's 4.3.0.dfsg.1-1) is spinning doing the following, apparently indefinitely (fd 5 is /dev/dri/card0): ioctl(5, 0x6444, 0) = -1 EBUSY (Device or resource busy) ioctl(5, 0x6444, 0) = -1 EBUSY (Device or resource busy) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) ioctl(5, 0x6444, 0) = -1 EBUSY (Device or resource busy) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) ioctl(5, 0x6444, 0) = -1 EBUSY (Device or resource busy) ioctl(5, 0x6444, 0) = -1 EBUSY (Device or resource busy) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) ioctl(5, 0x6444, 0) = -1 EBUSY (Device or resource busy) Kernel configuration at http://flynn.zork.net/~sneakums/config-2.6.11-mm3 -- Dag vijandelijk luchtschip de huismeester is dood - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
