From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Subject: Re: [uml-devel] 2.6.15-rc2
Date: Sat, 3 Dec 2005 04:47:46 +0100 [thread overview]
Message-ID: <200512030447.47095.blaisorblade@yahoo.it> (raw)
In-Reply-To: <12276.1133324450@sandelman.ottawa.on.ca>
On Wednesday 30 November 2005 05:20, Michael Richardson wrote:
> Running a kernel which is not 2.6.15-rc2 (but a couple of merges back,
> looking for a place where it works), I get:
> If I try with "mode=tt", (vs skas0) it boots, but on shutdown, I get:
I got it too, and actually I think it's triggerable by playing with proc
(something like ps with the "l" flag should do, but never tested). I've even
diagnosed and sent a report to Jeff, we just need to fix it up.
It was introduced in the sysrq-t patch - some macros return 0xdeadbeef when
SKAS mode is compile-time disabled, and have only a SKAS implementation
(which is broken for TT mode but is used there too).
Btw, it was not in the first Allan's version that bug, it was introduced
later.
> EIP: 0073:[<40101e18>] CPU: 0 Not tainted ESP: 007b:bf8cec8c EFLAGS:
> 00000246 Not tainted
> EAX: ffffffda EBX: 40189880 ECX: ffffffff EDX: 00000000
> ESI: bf8ced38 EDI: 00000000 EBP: bf8cec98 DS: 007b ES: 007b
> a09ff800: [<a00395bf>] show_regs+0x1cf/0x1e0
> a09ff828: [<a001d25c>] panic_exit+0x2c/0x50
> a09ff838: [<a00506cd>] notifier_call_chain+0x2d/0x50
> a09ff858: [<a003d922>] panic+0x72/0x110
> a09ff874: [<a0022d1e>] wait_stub_done+0xfe/0x180
> a09ff8f4: [<a0023792>] copy_context_skas0+0x1c2/0x270
> a09ff9d4: [<a0022aac>] init_new_context_skas+0x11c/0x1b0
> a09ffa08: [<a003bf97>] copy_mm+0x367/0x3a0
> a09ffa50: [<a003c969>] copy_process+0x499/0xe60
> a09ffb40: [<a003d39e>] do_fork+0x6e/0x1ca
> a09ffbac: [<a001a33b>] sys_fork+0x8b/0xb0
> a09ffbe0: [<a0024512>] handle_syscall+0x112/0x140
> a09ffc5c: [<a0022ed1>] handle_trap+0x31/0x140
> a09ffc84: [<a002357a>] userspace+0x1da/0x230
> a09ffce0: [<a0023f35>] new_thread_handler+0xe5/0x120
> a09ffd20: [<a01cb468>] __restore+0x0/0x8
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2005-12-03 3:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 4:20 [uml-devel] 2.6.15-rc2 Michael Richardson
2005-11-30 13:39 ` Rob Landley
2005-11-30 16:34 ` Michael Richardson
2005-11-30 17:27 ` Rob Landley
2005-12-01 16:03 ` [uml-devel] 2.6.15-rc2 Michael Richardson
2005-12-03 3:46 ` Blaisorblade
2005-12-03 3:47 ` Blaisorblade [this message]
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=200512030447.47095.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=mcr@sandelman.ottawa.on.ca \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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