Re: 2.6.12-rc1-bk2+PREEMPT_BKL: Oops at serio_interrupt

2005-03-30 Thread Dmitry Torokhov
On Wednesday 30 March 2005 04:14, Alexey Dobriyan wrote: > On Wednesday 30 March 2005 10:30, Dmitry Torokhov wrote: > > On Tuesday 29 March 2005 14:49, Alexey Dobriyan wrote: > > > According to vmlinux, c0202947 is at: > > > > > > c020293e : > > > > Could you please try this one instead? Thanks!

Re: 2.6.12-rc1-bk2+PREEMPT_BKL: Oops at serio_interrupt

2005-03-30 Thread Alexey Dobriyan
On Wednesday 30 March 2005 10:30, Dmitry Torokhov wrote: > On Tuesday 29 March 2005 14:49, Alexey Dobriyan wrote: > > According to vmlinux, c0202947 is at: > > > > c020293e : > > Could you please try this one instead? Thanks! Still dies in serport_ldisc_write_wakeup (doesn't matter how to trigge

Re: 2.6.12-rc1-bk2+PREEMPT_BKL: Oops at serio_interrupt

2005-03-29 Thread Dmitry Torokhov
On Tuesday 29 March 2005 14:49, Alexey Dobriyan wrote: > On Tuesday 29 March 2005 23:02, Dmitry Torokhov wrote: > > On Tue, 29 Mar 2005 21:28:20 +0400, Alexey Dobriyan <[EMAIL PROTECTED]> > > wrote: > > > On Tuesday 29 March 2005 10:27, Dmitry Torokhov wrote: > > > > On Monday 28 March 2005 12:26,

Re: 2.6.12-rc1-bk2+PREEMPT_BKL: Oops at serio_interrupt

2005-03-29 Thread Dmitry Torokhov
On Tue, 29 Mar 2005 23:49:55 +0400, Alexey Dobriyan <[EMAIL PROTECTED]> wrote: > On Tuesday 29 March 2005 23:02, Dmitry Torokhov wrote: > > On Tue, 29 Mar 2005 21:28:20 +0400, Alexey Dobriyan <[EMAIL PROTECTED]> > > wrote: > > > On Tuesday 29 March 2005 10:27, Dmitry Torokhov wrote: > > > > On Mon

Re: 2.6.12-rc1-bk2+PREEMPT_BKL: Oops at serio_interrupt

2005-03-29 Thread Alexey Dobriyan
On Tuesday 29 March 2005 23:02, Dmitry Torokhov wrote: > On Tue, 29 Mar 2005 21:28:20 +0400, Alexey Dobriyan <[EMAIL PROTECTED]> wrote: > > On Tuesday 29 March 2005 10:27, Dmitry Torokhov wrote: > > > On Monday 28 March 2005 12:26, Alexey Dobriyan wrote: > > > > Steps to reproduce for me: > > > >

Re: 2.6.12-rc1-bk2+PREEMPT_BKL: Oops at serio_interrupt

2005-03-29 Thread Dmitry Torokhov
On Tue, 29 Mar 2005 21:28:20 +0400, Alexey Dobriyan <[EMAIL PROTECTED]> wrote: > On Tuesday 29 March 2005 10:27, Dmitry Torokhov wrote: > > On Monday 28 March 2005 12:26, Alexey Dobriyan wrote: > > > Steps to reproduce for me: > > > * Boot CONFIG_PREEMPT_BKL=y kernel (.config, dmesg are attache

Re: 2.6.12-rc1-bk2+PREEMPT_BKL: Oops at serio_interrupt

2005-03-29 Thread Alexey Dobriyan
On Tuesday 29 March 2005 10:27, Dmitry Torokhov wrote: > On Monday 28 March 2005 12:26, Alexey Dobriyan wrote: > > Steps to reproduce for me: > > * Boot CONFIG_PREEMPT_BKL=y kernel (.config, dmesg are attached) > > * Start rebooting > > * Start moving serial mouse (I have Genius NetMous

Re: 2.6.12-rc1-bk2+PREEMPT_BKL: Oops at serio_interrupt

2005-03-28 Thread Dmitry Torokhov
On Monday 28 March 2005 12:26, Alexey Dobriyan wrote: > Steps to reproduce for me: > * Boot CONFIG_PREEMPT_BKL=y kernel (.config, dmesg are attached) > * Start rebooting > * Start moving serial mouse (I have Genius NetMouse Pro) > * Right after gpm is shut down I see the oop

2.6.12-rc1-bk2+PREEMPT_BKL: Oops at serio_interrupt

2005-03-28 Thread Alexey Dobriyan
Steps to reproduce for me: * Boot CONFIG_PREEMPT_BKL=y kernel (.config, dmesg are attached) * Start rebooting * Start moving serial mouse (I have Genius NetMouse Pro) * Right after gpm is shut down I see the oops * The system continues to reboot Doing a "# s