All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Manschwetus <florianmanschwetus@gmx.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [Xen-users] Problem booting xen 4.1.2 on Athlon 64 X2
Date: Thu, 22 Dec 2011 14:32:43 +0100	[thread overview]
Message-ID: <4EF3317B.9020204@gmx.de> (raw)
In-Reply-To: <4EF33E7F02000078000699A2@nat28.tlf.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 1208 bytes --]

Am 22.12.2011 14:28, schrieb Jan Beulich:
>>>> On 22.12.11 at 14:11, Florian Manschwetus<florianmanschwetus@gmx.de>  wrote:
>> Looks acpi_skip_timer_override is not the solution:
>
> That's unfortunate. Next thing for us to know is whether you have
> been told any workaround on the native Linux side to make the
> respective messages disappear (i.e. to consider porting over those
> bits, if they exist).
I not used any workaround to get the linux booting, it is an kde sabayon 
amd64, where I installed using portage gentoo-sources, xen, xen-tools, 
openvswitch
Then gentoo sources compiled following the sabayon custom kernel howto 
using genkernel, with a slightly modified default config (read as the 
config of the original sabayon kernel binary) to support dom0.

Thx,
Florian

>
> If there's no solution known on native Linux, then some debugging
> will need to be done with that system (a first guess would then be
> that the system is actually reporting the wrong override
>
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 0 dfl dfl)
>
> meaning to actually specify global_irq as 2, which would be pretty
> strait forward to hack in for an experiment).
>
> Jan


[-- Attachment #1.2: S/MIME Kryptografische Unterschrift --]
[-- Type: application/pkcs7-signature, Size: 2332 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-12-22 13:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4EF06B14.4070106@gmx.de>
     [not found] ` <4EF0B034.1090708@gmx.de>
2011-12-21 23:49   ` [Xen-users] Problem booting xen 4.1.2 on Athlon 64 X2 Florian Manschwetus
2011-12-22  9:32     ` Jan Beulich
2011-12-22  9:49       ` Florian Manschwetus
     [not found]       ` <4EF2FCED.8010402@gmx.de>
2011-12-22 12:28         ` Jan Beulich
2011-12-22 13:11           ` Florian Manschwetus
2011-12-22 13:28             ` Jan Beulich
2011-12-22 13:32               ` Florian Manschwetus [this message]
2011-12-22 12:54     ` Igor Mammedov
2011-12-22 13:16       ` Florian Manschwetus

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=4EF3317B.9020204@gmx.de \
    --to=florianmanschwetus@gmx.de \
    --cc=JBeulich@suse.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.