From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Morten Bøgeskov" <xen-users@morten.bogeskov.dk>
Cc: xen-devel@lists.xensource.com,
Mark Williamson <mark.williamson@cl.cam.ac.uk>
Subject: Re: [Xen-users] 2.6.23 oops
Date: Thu, 11 Oct 2007 14:47:14 -0700 [thread overview]
Message-ID: <470E99E2.7070300@goop.org> (raw)
In-Reply-To: <20071011232116.e28c5kuo64o5woow@whitelist.dk>
Morten Bøgeskov wrote:
> Quoting Jeremy Fitzhardinge <jeremy@goop.org>:
>
>> Morten Bøgeskov wrote:
>>> I've applied both, and tried with and without SMP, with exactly the
>>> same result as before.
>>>
>>> UP hangs after "installing Xen timer for CPU 0"
>>
>> Ah, OK. I'd overlooked this one. Hm, I probably haven't tried UP in a
>> while.
>>
>>> SMP the oops'es the same way except the line no. is now 78.
>>
>> Oh, that's odd. Could you resend your original bug report? What kind
>> of load does it fail under?
>
> I can't really say what load. It doesn't get that far.
Odd.
> I've included .config
It seems a bit small. Can you send your whole .config so I can rebuild
your kernel?
J
next prev parent reply other threads:[~2007-10-11 21:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071011144817.n5x1drwcgug44sg0@whitelist.dk>
2007-10-11 15:29 ` [Xen-users] 2.6.23 oops Mark Williamson
2007-10-11 16:27 ` Mark Williamson
2007-10-11 18:22 ` Morten Bøgeskov
2007-10-11 18:53 ` Mark Williamson
2007-10-11 16:41 ` Jeremy Fitzhardinge
2007-10-11 19:00 ` Morten Bøgeskov
2007-10-11 21:04 ` Jeremy Fitzhardinge
2007-10-11 21:21 ` Morten Bøgeskov
2007-10-11 21:47 ` Jeremy Fitzhardinge [this message]
2007-10-12 9:46 ` Morten Bøgeskov
2007-10-12 15:30 ` Jeremy Fitzhardinge
2007-10-12 15:34 ` Mark Williamson
2007-10-12 15:40 ` Keir Fraser
2007-10-12 15:50 ` Jeremy Fitzhardinge
2007-10-12 4:14 ` Mark Williamson
2007-10-12 6:21 ` Jeremy Fitzhardinge
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=470E99E2.7070300@goop.org \
--to=jeremy@goop.org \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@morten.bogeskov.dk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.