Hi, > Please let us know if there are any release critical bugs present -- > regressions vs. 1.0.2.1, doesn't run at all, the RPM is braindead, or > similar. >
I have this machine running 2.6.0-test6 kernel with sleep-inside-spinlock checking enabled. Some time after starting dosemu, the kernel begins to display debug messages and continues sporadically, sometimes loops per second or so. Now that it's a test kernel, I'm not sure if this is a problem of dosemu or not, but one thing for sure is that it stops once dosemu exits. Here is a snapshot of the messages: Debug: sleeping function called from invalid context at include/asm/uaccess.h:473 in_atomic():0, irqs_disabled():1 Call Trace: [<c011b15e>] __might_sleep+0x9e/0xc0 [<c010bdd0>] save_v86_state+0x70/0x200 [<c01095ce>] work_notifysig_v86+0x6/0x14 [<c010957b>] syscall_call+0x7/0xb Debug: sleeping function called from invalid context at include/asm/uaccess.h:473 in_atomic():0, irqs_disabled():1 Call Trace: [<c011b15e>] __might_sleep+0x9e/0xc0 [<c010bdd0>] save_v86_state+0x70/0x200 [<c010b3e7>] do_IRQ+0x107/0x140 [<c01095ce>] work_notifysig_v86+0x6/0x14 [<c010957b>] syscall_call+0x7/0xb Debug: sleeping function called from invalid context at include/asm/uaccess.h:473 in_atomic():0, irqs_disabled():1 Call Trace: [<c011b15e>] __might_sleep+0x9e/0xc0 [<c010bdd0>] save_v86_state+0x70/0x200 [<c010a5b0>] do_general_protection+0x0/0xb0 [<c01095ce>] work_notifysig_v86+0x6/0x14 [<c010957b>] syscall_call+0x7/0xb - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
