From mboxrd@z Thu Jan 1 00:00:00 1970 From: "A. Alper ATICI" Subject: Re: The first dosemu-1.2.0 release candidate is available! Date: Wed, 1 Oct 2003 17:12:35 +0300 Sender: linux-msdos-owner@vger.kernel.org Message-ID: <20031001141235.GA400@deskt-xp> References: Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Id: Content-Type: text/plain; charset="us-ascii" To: linux-msdos@vger.kernel.org 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: [] __might_sleep+0x9e/0xc0 [] save_v86_state+0x70/0x200 [] work_notifysig_v86+0x6/0x14 [] 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: [] __might_sleep+0x9e/0xc0 [] save_v86_state+0x70/0x200 [] do_IRQ+0x107/0x140 [] work_notifysig_v86+0x6/0x14 [] 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: [] __might_sleep+0x9e/0xc0 [] save_v86_state+0x70/0x200 [] do_general_protection+0x0/0xb0 [] work_notifysig_v86+0x6/0x14 [] syscall_call+0x7/0xb