On Sat, 2009-02-28 at 19:24 +0100, Bruno Prémont wrote:
> On Sat, 28 February 2009 Eric Anholt wrote:
> > On Sat, 2009-02-28 at 00:47 -0800, Andrew Morton wrote:
> > > The kernel deadlocked on struct_mutex, did it not? That's a kernel
> > > bug regardless of what userspace you're running.
> > >
On Sat, 28 February 2009 Eric Anholt wrote:
> On Sat, 2009-02-28 at 00:47 -0800, Andrew Morton wrote:
> > The kernel deadlocked on struct_mutex, did it not? That's a kernel
> > bug regardless of what userspace you're running.
> >
> > Do we know why this happened?
>
> Userland went stomping all
On Sat, 2009-02-28 at 00:47 -0800, Andrew Morton wrote:
> The kernel deadlocked on struct_mutex, did it not? That's a kernel bug
> regardless of what userspace you're running.
No, it didn't deadlock on struct_mutex, it deadlocked because the
hardware got wedged, and we still don't know how to un
On 28.2.2009 01:20, Eric Anholt wrote:
> KMS support is not a feature of the server but of your 2D driver. You
> want 2.6.2, or things will be bad.
I have 2.5.0. After turning KMS off, problem seems to be solved.
Anyway, I would appreciate a version of the intel driver being in the
Kconfig text
On Fri, Feb 27, 2009 at 02:49:06PM +0100, Jiri Slaby wrote:
> On 27.2.2009 14:04, Sitsofe Wheeler wrote:
> >On Fri, Feb 27, 2009 at 02:32:31AM -0800, Andrew Morton wrote:
> >>On Fri, 27 Feb 2009 10:28:51 +0100 Jiri Slaby wrote:
> >>
> >>>everytime I run X, it gets stuck. Currently running on mmotm
On Sat, 2009-02-28 at 00:47 -0800, Andrew Morton wrote:
> On Sat, 28 Feb 2009 09:31:28 +0100 Jiri Slaby wrote:
>
> > On 28.2.2009 01:20, Eric Anholt wrote:
> > > KMS support is not a feature of the server but of your 2D driver. You
> > > want 2.6.2, or things will be bad.
> >
> > I have 2.5.0.
On Sat, 28 Feb 2009 09:31:28 +0100 Jiri Slaby wrote:
> On 28.2.2009 01:20, Eric Anholt wrote:
> > KMS support is not a feature of the server but of your 2D driver. You
> > want 2.6.2, or things will be bad.
>
> I have 2.5.0. After turning KMS off, problem seems to be solved.
>
> Anyway, I woul
On Fri, 2009-02-27 at 23:12 +, Sitsofe Wheeler wrote:
> On Fri, Feb 27, 2009 at 02:49:06PM +0100, Jiri Slaby wrote:
> > On 27.2.2009 14:04, Sitsofe Wheeler wrote:
> > >On Fri, Feb 27, 2009 at 02:32:31AM -0800, Andrew Morton wrote:
> > >>On Fri, 27 Feb 2009 10:28:51 +0100 Jiri Slaby wrote:
> >
On 27.2.2009 14:04, Sitsofe Wheeler wrote:
> On Fri, Feb 27, 2009 at 02:32:31AM -0800, Andrew Morton wrote:
>> On Fri, 27 Feb 2009 10:28:51 +0100 Jiri Slaby wrote:
>>
>>> everytime I run X, it gets stuck. Currently running on mmotm
>>> 2009-02-26-16-58, but I think this is wider problem. I had i91
On Fri, Feb 27, 2009 at 02:32:31AM -0800, Andrew Morton wrote:
> On Fri, 27 Feb 2009 10:28:51 +0100 Jiri Slaby wrote:
>
> > everytime I run X, it gets stuck. Currently running on mmotm
> > 2009-02-26-16-58, but I think this is wider problem. I had i915 disabled
> > for a long time (until I noti
Hi,
everytime I run X, it gets stuck. Currently running on mmotm
2009-02-26-16-58, but I think this is wider problem. I had i915 disabled
for a long time (until I noticed today).
SysRq : Show Locks Held
Showing all locks held in the system:
3 locks held by events/0/10:
#0: (events){+.+.+.},
On 27.2.2009 11:01, Peter Zijlstra wrote:
> would be good to have sysrq-w output
There was nothing but events. So this is rather an intel driver
userspace bug?
SysRq : Show Blocked State
taskPC stack pid father
events/1 D 011 2
ff
On 27.2.2009 11:12, Jiri Slaby wrote:
> So this is rather an intel driver userspace bug?
Bullshit, ignore me :).
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest is
On Fri, 2009-02-27 at 10:28 +0100, Jiri Slaby wrote:
> SysRq : Show Locks Held
>
> Showing all locks held in the system:
> 3 locks held by events/0/10:
> #0: (events){+.+.+.}, at: [] worker_thread+0x19d/0x340
> #1: (&(&dev_priv->mm.retire_work)->work){+.+...}, at: []
> worker_thread+0x19d/
On Fri, 27 Feb 2009 10:28:51 +0100 Jiri Slaby wrote:
> everytime I run X, it gets stuck. Currently running on mmotm
> 2009-02-26-16-58, but I think this is wider problem. I had i915 disabled
> for a long time (until I noticed today).
>
> SysRq : Show Locks Held
>
> Showing all locks held in t
15 matches
Mail list logo
