From: Fantu <fantonifabio@tiscali.it>
To: xen-devel@lists.xensource.com
Subject: Re: Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!
Date: Mon, 1 Mar 2010 02:45:52 -0800 (PST) [thread overview]
Message-ID: <27742020.post@talk.nabble.com> (raw)
In-Reply-To: <1267439564.11737.20554.camel@zakaz.uk.xensource.com>
i have problem more before...
CONFIG_SPARSE_IRQ=y on all .config i have used, i can change to n and try or
must set to y?
Ian Campbell-10 wrote:
>
> On Mon, 2010-03-01 at 10:27 +0000, Ian Campbell wrote:
>> On Mon, 2010-03-01 at 10:21 +0000, Pasi Kärkkäinen wrote:
>> > On Mon, Mar 01, 2010 at 01:54:46AM -0800, Fantu wrote:
>> > >
>> > > Now i have redo kernel from xen/master, view kernel panic and
>> calltrace on
>> > > screen, the screenshot:
>> > > http://old.nabble.com/file/p27741588/2.6.31.6_pv_ops_not_start.jpg
>> > > 2.6.31.6_pv_ops_not_start.jpg
>> > >
>> >
>> > Ok.. maybe Jeremy has some ideas about this one. It seems to crash
>> pretty early.
>>
>> This issue is also being discussed in the thread "CONFIG_SPARSE_IRQ
>> breaks single VCPU domain 0 between xen/master and xen/next" started
>> last week. Although it looks like it might not necessarily be tied to
>> CONFIG_SPARSE_IRQ at this point.
>
> It's also possible (likely!) that my change "fix off-by-one error in
> find_unbound_irq" is what is causing this issue in xen/master rather
> than the sparse IRQ thing.
>
> Ian.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
--
View this message in context: http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27742020.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
next prev parent reply other threads:[~2010-03-01 10:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 13:33 Kernel 2.6.31.6 pv_ops freeze on start Fantu
2010-01-07 13:37 ` Pasi Kärkkäinen
2010-01-07 13:43 ` Fantu
2010-01-07 14:01 ` Pasi Kärkkäinen
2010-01-07 17:04 ` Fantu
2010-01-07 21:14 ` Pasi Kärkkäinen
2010-01-08 14:16 ` Fantu
2010-01-21 22:04 ` Jeremy Fitzhardinge
2010-02-16 13:56 ` Fantu
2010-02-16 14:27 ` Pasi Kärkkäinen
2010-02-16 17:49 ` Fantu
2010-02-16 18:31 ` Pasi Kärkkäinen
2010-02-24 8:39 ` Fantu
2010-02-24 8:59 ` Pasi Kärkkäinen
2010-02-24 13:23 ` Fabio Fantoni
2010-02-26 13:32 ` Fantu
2010-02-26 14:42 ` Pasi Kärkkäinen
2010-02-26 15:58 ` Fantu
2010-03-01 9:54 ` Fantu
2010-03-01 10:21 ` Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs! Pasi Kärkkäinen
2010-03-01 10:27 ` Ian Campbell
2010-03-01 10:32 ` Ian Campbell
2010-03-01 10:45 ` Fantu [this message]
2010-03-01 11:05 ` Ian Campbell
2010-03-01 15:34 ` Fantu
2010-03-02 7:09 ` Zhang, Xiantao
2010-03-05 10:30 ` Fantu
2010-03-05 15:41 ` Fantu
2010-04-14 11:46 ` Fantu
2010-04-19 9:25 ` Fantu
2010-04-19 13:52 ` Boot hands - need sync serial console to help Konrad Rzeszutek Wilk
2010-01-13 8:41 ` Kernel 2.6.31.6 pv_ops freeze on start Fantu
2010-01-13 9:12 ` Pasi Kärkkäinen
2010-01-13 11:05 ` Fantu
2010-01-13 15:39 ` Konrad Rzeszutek Wilk
2010-01-15 7:00 ` Fantu
2010-01-15 7:34 ` Pasi Kärkkäinen
2010-01-15 17:01 ` Konrad Rzeszutek Wilk
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=27742020.post@talk.nabble.com \
--to=fantonifabio@tiscali.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).