From: "A. Alper ATICI" <alper.atici@softhome.net>
To: linux-msdos@vger.kernel.org
Subject: Re: The first dosemu-1.2.0 release candidate is available!
Date: Wed, 1 Oct 2003 17:12:35 +0300 [thread overview]
Message-ID: <20031001141235.GA400@deskt-xp> (raw)
In-Reply-To: <Pine.LNX.4.44.0309282259090.23676-100000@enm-bo-lt.localdomain>
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
next prev parent reply other threads:[~2003-10-01 14:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 22:21 The first dosemu-1.2.0 release candidate is available! Bart Oldeman
2003-09-30 12:21 ` A. Alper ATICI
2003-09-30 12:50 ` Bart Oldeman
2003-09-30 19:20 ` A. Alper ATICI
2003-09-30 19:35 ` Bart Oldeman
2003-09-30 13:50 ` Ralph Alvy
2003-09-30 14:35 ` Ralph Alvy
2003-09-30 15:02 ` Bart Oldeman
2003-09-30 16:15 ` Robert Komar
2003-09-30 17:13 ` Bart Oldeman
2003-09-30 17:57 ` Robert Komar
2003-10-01 7:21 ` Sylvain Petreolle
2003-10-01 3:17 ` Ralph Alvy
2003-10-01 10:50 ` Bart Oldeman
2003-10-01 21:30 ` Ralph Alvy
2003-09-30 14:37 ` Bart Oldeman
2003-10-01 14:12 ` A. Alper ATICI [this message]
2003-10-01 14:42 ` Bart Oldeman
2003-10-01 15:27 ` Ged Haywood
2003-10-01 19:56 ` Bart Oldeman
2003-10-02 22:10 ` Ralph Alvy
2003-10-02 23:33 ` Bart Oldeman
2003-10-03 0:06 ` Ralph Alvy
2003-10-03 1:38 ` Ralph Alvy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031001141235.GA400@deskt-xp \
--to=alper.atici@softhome.net \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox