From: Shane Chen <inconceivable@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: Xen / Dell 2850 PERC 4e/Di lock up
Date: Tue, 19 Jul 2005 14:39:21 -0700 [thread overview]
Message-ID: <4a51ce970507191439709cc197@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D2826E3@liverpoolst.ad.cl.cam.ac.uk>
On 7/19/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> Have you tried 2.0-testing with 'noirqballance'?
I have to admit and say that I did post before I had turned up the
noirqbalance thread. I've since then compiled a new testing kernel
(dea74c466948d94a181bf0009c44ea51 xen-2.0-testing-src.tgz) and tried
the noirqbalance (and did some more troubleshooting - more below).
First, the noirqbalance does help. The box definitely does not
completely lock up. But it would still sort of pause briefly. I
guess you could say that it stutters. However, I'm not completely
sure I managed to get it working because I never saw "XEN: Platform
quirk -- Disabling IRQ balancing/affinity" when I did `xm dmesg`. So
then the curious question for me is then why it didn't completely hang
when I tried the same thing (multiple times).
Second, it turns out that I lied about the nousb thing. The kernel I
had compiled used USB as modules. So that even if you pass it nousb,
the coldplug script on gentoo manages to load all of the usb modules
regardless.
If I manually unload the usb modules, the lock up completely goes away
(does not stutter). Since I don't need USB for my Xen project, I've
gone ahead and disabled it the in the BIOS.
I'll be glad to provide addtional information or try additional things
and give feedback.
Thanks,
Shane
next prev parent reply other threads:[~2005-07-19 21:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 19:19 Xen / Dell 2850 PERC 4e/Di lock up Ian Pratt
2005-07-19 21:39 ` Shane Chen [this message]
2005-07-20 11:02 ` Keir Fraser
2005-07-20 17:24 ` David H
2005-07-21 17:04 ` Shane Chen
-- strict thread matches above, loose matches on Subject: below --
2005-07-19 17:15 Shane Chen
2005-07-19 17:59 ` Will DeHaan
2005-07-19 18:08 ` Shane Chen
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=4a51ce970507191439709cc197@mail.gmail.com \
--to=inconceivable@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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.