Re: kernel BUG at kernel/workqueue.c:104!

2005-08-29 Thread Greg KH
On Tue, Aug 23, 2005 at 06:02:45PM +0200, Karl Hiramoto wrote: > Hi, i get this a lot now when doing: "rmmod cp2101 io_edgeport " Why unload both modules? Which device are you having problems with? And can you duplicate this on a kernel that does not have a closed source driver loaded into

Re: kernel BUG at kernel/workqueue.c:104!

2005-08-29 Thread Greg KH
On Tue, Aug 23, 2005 at 06:02:45PM +0200, Karl Hiramoto wrote: Hi, i get this a lot now when doing: rmmod cp2101 io_edgeport Why unload both modules? Which device are you having problems with? And can you duplicate this on a kernel that does not have a closed source driver loaded into it?

Re: kernel BUG at kernel/workqueue.c:104!

2005-08-24 Thread Parag Warudkar
Karl Hiramoto hiramoto.org> writes: > > Hi, i get this a lot now when doing: "rmmod cp2101 io_edgeport " > > I try and do the rmmod, because i loose comunications on the USB to > RS-232 adapters. > [ cut here ]---- > kernel BUG at

Re: kernel BUG at kernel/workqueue.c:104!

2005-08-24 Thread Parag Warudkar
Karl Hiramoto karl at hiramoto.org writes: Hi, i get this a lot now when doing: rmmod cp2101 io_edgeport I try and do the rmmod, because i loose comunications on the USB to RS-232 adapters. [ cut here ] kernel BUG at kernel/workqueue.c:104! invalid operand

kernel BUG at kernel/workqueue.c:104!

2005-08-23 Thread Karl Hiramoto
gular_file): read_ksyms stat /proc/ksyms failed ./ksymoops: No such file or directory No modules in ksyms, skipping objects No ksyms, skipping lsmod Reading Oops report from the terminal [ cut here ]-------- kernel BUG at kernel/workqueue.c:104! invalid operand: [#1] PREEMPT Modu

kernel BUG at kernel/workqueue.c:104!

2005-08-23 Thread Karl Hiramoto
): read_ksyms stat /proc/ksyms failed ./ksymoops: No such file or directory No modules in ksyms, skipping objects No ksyms, skipping lsmod Reading Oops report from the terminal [ cut here ] kernel BUG at kernel/workqueue.c:104! invalid operand: [#1] PREEMPT Modules linked in: cp2101

Re: 2.6.11-rc2-mm1 kernel BUG at kernel/workqueue.c:104

2005-01-25 Thread Zwane Mwaikambo
On Tue, 25 Jan 2005, Andrew Morton wrote: > OK, thanks. I get what appears to be a use-after-free error. > CONFIG_DEBUG_PAGEALLOC is set: > > Program received signal SIGEMT, Emulation trap. > 0xc0272bc2 in kbd_keycode (keycode=57, down=1, hw_raw=0, regs=0xc0673f9c) > at

Re: 2.6.11-rc2-mm1 kernel BUG at kernel/workqueue.c:104

2005-01-25 Thread Roman Zippel
Hi, On Tue, 25 Jan 2005, Andrew Morton wrote: > Roman, binary searching indicates that the bug was introduced by > merge-vt_struct-into-vc_data.patch. The latest version. Ok, that bug is now really embarrassing. :) I removed a bit too much from con_close. bye, Roman diff -ur -X

Re: 2.6.11-rc2-mm1 kernel BUG at kernel/workqueue.c:104

2005-01-25 Thread Andrew Morton
Zwane Mwaikambo <[EMAIL PROTECTED]> wrote: > > On Mon, 24 Jan 2005, Andrew Morton wrote: > > > I can't reproduce it from a quick test here. I'd assume that the keystroke > > came in before the vt's workqueue is initialised. fn_enter() calls > > put_queue() calls con_schedule_flip() calls

Re: 2.6.11-rc2-mm1 kernel BUG at kernel/workqueue.c:104

2005-01-25 Thread Andrew Morton
Zwane Mwaikambo [EMAIL PROTECTED] wrote: On Mon, 24 Jan 2005, Andrew Morton wrote: I can't reproduce it from a quick test here. I'd assume that the keystroke came in before the vt's workqueue is initialised. fn_enter() calls put_queue() calls con_schedule_flip() calls schedule_work()

Re: 2.6.11-rc2-mm1 kernel BUG at kernel/workqueue.c:104

2005-01-25 Thread Roman Zippel
Hi, On Tue, 25 Jan 2005, Andrew Morton wrote: Roman, binary searching indicates that the bug was introduced by merge-vt_struct-into-vc_data.patch. The latest version. Ok, that bug is now really embarrassing. :) I removed a bit too much from con_close. bye, Roman diff -ur -X

Re: 2.6.11-rc2-mm1 kernel BUG at kernel/workqueue.c:104

2005-01-25 Thread Zwane Mwaikambo
On Tue, 25 Jan 2005, Andrew Morton wrote: OK, thanks. I get what appears to be a use-after-free error. CONFIG_DEBUG_PAGEALLOC is set: Program received signal SIGEMT, Emulation trap. 0xc0272bc2 in kbd_keycode (keycode=57, down=1, hw_raw=0, regs=0xc0673f9c) at

Re: 2.6.11-rc2-mm1 kernel BUG at kernel/workqueue.c:104

2005-01-24 Thread Zwane Mwaikambo
On Mon, 24 Jan 2005, Andrew Morton wrote: > I can't reproduce it from a quick test here. I'd assume that the keystroke > came in before the vt's workqueue is initialised. fn_enter() calls > put_queue() calls con_schedule_flip() calls schedule_work() which goes BUG: Boot into runlevel 1

Re: 2.6.11-rc2-mm1 kernel BUG at kernel/workqueue.c:104

2005-01-24 Thread Andrew Morton
Zwane Mwaikambo <[EMAIL PROTECTED]> wrote: > > I pressed a key on a VT during boot and got the following; > > usb-storage: device scan complete > [ cut here ]-------- > kernel BUG at kernel/workqueue.c:104! > invalid operand: [#1] > PREEMPT

2.6.11-rc2-mm1 kernel BUG at kernel/workqueue.c:104

2005-01-24 Thread Zwane Mwaikambo
I pressed a key on a VT during boot and got the following; usb-storage: device scan complete [ cut here ] kernel BUG at kernel/workqueue.c:104! invalid operand: [#1] PREEMPT SMP DEBUG_PAGEALLOC Modules linked in: CPU:0 EIP:0060:[]Not tainted VLI EFLAGS

2.6.11-rc2-mm1 kernel BUG at kernel/workqueue.c:104

2005-01-24 Thread Zwane Mwaikambo
I pressed a key on a VT during boot and got the following; usb-storage: device scan complete [ cut here ] kernel BUG at kernel/workqueue.c:104! invalid operand: [#1] PREEMPT SMP DEBUG_PAGEALLOC Modules linked in: CPU:0 EIP:0060:[c01314af]Not tainted VLI

Re: 2.6.11-rc2-mm1 kernel BUG at kernel/workqueue.c:104

2005-01-24 Thread Andrew Morton
Zwane Mwaikambo [EMAIL PROTECTED] wrote: I pressed a key on a VT during boot and got the following; usb-storage: device scan complete [ cut here ] kernel BUG at kernel/workqueue.c:104! invalid operand: [#1] PREEMPT SMP DEBUG_PAGEALLOC Modules linked

Re: 2.6.11-rc2-mm1 kernel BUG at kernel/workqueue.c:104

2005-01-24 Thread Zwane Mwaikambo
On Mon, 24 Jan 2005, Andrew Morton wrote: I can't reproduce it from a quick test here. I'd assume that the keystroke came in before the vt's workqueue is initialised. fn_enter() calls put_queue() calls con_schedule_flip() calls schedule_work() which goes BUG: Boot into runlevel 1 (console