-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>
> This panic starts at:
> https://svnweb.freebsd.org/base?view=revision&revision=278473
>
> If I use 278472, I can boot the Xen VM normally.
>
> If I use head and set hw.x2apic_enable="0" in loader.conf and boot
> head (278970), it boots norm
On Thu, Feb 19, 2015 at 11:50:49AM -0800, Neel Natu wrote:
> Hi Adrian,
>
> On Wed, Feb 18, 2015 at 10:09 PM, Adrian Chadd wrote:
> > Hi,
> >
> > Since this is the (at least) second round of "x2apic support broke me"
> > changes, can we please either back them out or set it to default to
> > '0'
Hi Adrian,
On Wed, Feb 18, 2015 at 10:09 PM, Adrian Chadd wrote:
> Hi,
>
> Since this is the (at least) second round of "x2apic support broke me"
> changes, can we please either back them out or set it to default to
> '0' for now?
>
I don't think that is necessary.
This is -current and there is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>
> This panic starts at:
> https://svnweb.freebsd.org/base?view=revision&revision=278473
>
> If I use 278472, I can boot the Xen VM normally.
>
> If I use head and set hw.x2apic_enable="0" in loader.conf and boot
> head (278970), it boots norm
Hi,
Since this is the (at least) second round of "x2apic support broke me"
changes, can we please either back them out or set it to default to
'0' for now?
Thanks,
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/17/15 12:30, Sean Bruno wrote:
> On 02/17/15 12:26, Konstantin Belousov wrote:
>> On Tue, Feb 17, 2015 at 12:00:04PM -0800, Sean Bruno wrote:
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
>>>
>>> On 02/17/15 00:56, Konstantin Belousov wr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/17/15 12:26, Konstantin Belousov wrote:
> On Tue, Feb 17, 2015 at 12:00:04PM -0800, Sean Bruno wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
>>
>> On 02/17/15 00:56, Konstantin Belousov wrote:
>>> On Mon, Feb 16, 2015 at 08:10:06PM
On Tue, Feb 17, 2015 at 12:00:04PM -0800, Sean Bruno wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 02/17/15 00:56, Konstantin Belousov wrote:
> > On Mon, Feb 16, 2015 at 08:10:06PM -0800, Sean Bruno wrote:
> >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
> >>
> >> https://
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/17/15 00:56, Konstantin Belousov wrote:
> On Mon, Feb 16, 2015 at 08:10:06PM -0800, Sean Bruno wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
>>
>> https://people.freebsd.org/~sbruno/Xen_APIC_panic.png
>>
>> I suspect that there ma
https://people.freebsd.org/~sbruno/Xen_APIC_panic.png
I suspect that there may be one or two more lines above this that are
relevant to this panic, but XENHVM kernel's now panic booting on Xen
server. The working kernel output looks like this:
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-fi
On Mon, Feb 16, 2015 at 08:10:06PM -0800, Sean Bruno wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> https://people.freebsd.org/~sbruno/Xen_APIC_panic.png
>
> I suspect that there may be one or two more lines above this that are
> relevant to this panic, but XENHVM kernel's now pan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
https://people.freebsd.org/~sbruno/Xen_APIC_panic.png
I suspect that there may be one or two more lines above this that are
relevant to this panic, but XENHVM kernel's now panic booting on Xen
server. The working kernel output looks like this:
Fre
12 matches
Mail list logo