From: david mosberger <dmosberger@gmail.com>
To: linux-ia64@vger.kernel.org
Subject: Re: testing mca/init patch
Date: Thu, 01 Sep 2005 01:38:09 +0000 [thread overview]
Message-ID: <ed5aea43050831183858dd0c24@mail.gmail.com> (raw)
In-Reply-To: <200508312343.j7VNhFOZ012157@agluck-lia64.sc.intel.com>
On 8/31/05, tony.luck@intel.com <tony.luck@intel.com> wrote:
> To make life easier for testers, I've applied Keith's patches
> and put them into my test tree.
>
> [snip...]
>
> The above is at least as good as the previous behaivour, but something
> bad happened there at the end. There were also more delays than I
> was expecting.
I tried this quickly on a zx2000 and didn't see any additional delays.
Output looked like this:
---------------------------------------------------------
login: (
cli>toc s
Sending TOC/INIT.
Entered OS INIT handler. PSPÿe301a0
Delaying for 5 seconds...
Processes interrupted by INIT - 0 (cpu 0 task 0xa000000100808000)
Backtrace of pid 1 (init)
Call Trace:
[<a0000001006bca70>] schedule+0x950/0x10c0
spà00000001167d90 bspà00000001161088
[<a0000001006bde10>] schedule_timeout+0xd0/0x1a0
spà00000001167d90 bspà00000001161058
[<a00000010015c000>] do_select+0x3e0/0x7c0
spà00000001167dd0 bspà00000001160f08
[<a00000010015d1d0>] sys_select+0x4f0/0x900
spà00000001167df0 bspà00000001160e40
[<a00000010000b320>] ia64_ret_from_syscall+0x0/0x20
spà00000001167e30 bspà00000001160e40
[<a000000000010620>] __start_ivt_text+0xffffffff00010620/0x400
spà00000001168000 bspà00000001160e40
[snip...]
Backtrace of pid 4352 (bash)
Call Trace:
[<a0000001006bca70>] schedule+0x950/0x10c0
spà0000404574fdb0 bspà00004045749308
[<a0000001006bde70>] schedule_timeout+0x130/0x1a0
spà0000404574fdb0 bspà000040457492d8
[<a0000001003c2040>] read_chan+0x560/0x13e0
spà0000404574fdf0 bspà000040457491a8
[<a0000001003b51b0>] tty_read+0x130/0x1a0
spà0000404574fe20 bspà00004045749158
[<a00000010012d160>] vfs_read+0x1e0/0x340
spà0000404574fe20 bspà00004045749100
[<a00000010012e3b0>] sys_read+0x70/0xe0
spà0000404574fe20 bspà00004045749088
[<a00000010000b320>] ia64_ret_from_syscall+0x0/0x20
spà0000404574fe30 bspà00004045749088
[<a000000000010620>] __start_ivt_text+0xffffffff00010620/0x400
spà00004045750000 bspà00004045749088
INIT dump complete. Monarch on cpu 0 returning to normal service.
---------------------------------------------------------
I didn't see any delays other than the expected 5 sec delay.
--david
--
Mosberger Consulting LLC, voice/fax: 510-744-9372,
http://www.mosberger-consulting.com/
35706 Runckel Lane, Fremont, CA 94536
next prev parent reply other threads:[~2005-09-01 1:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 23:43 testing mca/init patch tony.luck
2005-09-01 1:38 ` david mosberger [this message]
2005-09-01 3:20 ` Keith Owens
2005-09-01 4:58 ` david mosberger
2005-09-01 5:30 ` Keith Owens
2005-09-01 16:43 ` Luck, Tony
2005-09-01 19:35 ` david mosberger
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=ed5aea43050831183858dd0c24@mail.gmail.com \
--to=dmosberger@gmail.com \
--cc=linux-ia64@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