Re: xend gets SIGBUS and cores under -current

["Jonathan A. Kollasch" <jakllsch%kollasch.net@localhost>]

On Fri, May 22, 2009 at 03:56:12PM +1000, Sarton O'Brien wrote:
> On 19/05/2009 9:30 AM, Sarton O'Brien wrote:
>> On 19/05/2009 7:07 AM, Manuel Bouyer wrote:
>>> On Mon, May 18, 2009 at 07:21:52PM +0000, Jonathan A. Kollasch wrote:
>>>> Hi,
>>>>
>>>> I'm trying to update a amd64 dom0 to -current (to use dm(4)).
>>>>
>>>> I've been unable to get xend to stay running. The python interperter
>>>> recives a SIGBUS (signal 10) and dumps core.
>>>>
>>>> The kdump(1) shows interesting oddness:
>>>> 245 8 python2.5 PSIG SIGBUS SIG_DFL: code=SI_USER sent by
>>>> pid=-87363552, uid=32639)
>>>> note the bogus pid and uid, these two values change to different
>>>> yet similar value from trace to trace.
>>>>
>>>> I've tried xenkernel3/xentools3 with python25, and
>>>> xenkernel33/xentools33
>>>> with both python25 and python26. All these cases exhibit a similar
>>>> SIGBUS to xend.
>>>>
>>>> I'm running 5.99.11, sources from about the 17th.
>>>
>>> interesting. I'm running a amd64 5.99.11 kernel on a 5.0 userland, and
>>> don't have issues ...
>>
>> I'm running -current amd64 dom0/domu from May 5th with no issues. I'll
>> update my dev box today and report back tomorrow if nothing else crops
>> up in the meantime.
>
> Sorry for the delay, I've struggled to get a cvs sync that isn't broken.
>
> Built and running as of Fri May 22 11:29:03 EST 2009, all seems to be  
> fine. I haven't updated userland ... yet. uname and package list below.
>
> ~~~~~
>
> The only thing that crosses my mind for your issue is that I seem to  
> remember some xen related changes that required a userland of at least a  
> specific vintage with a new kernel. I only mention it as I'm not sure  
> from what version you are updating.

It's a packages/userland and kernel pain built and installed from scratch.
Everything should be consistent.

I suppose I'll try this again.

        Jonathan Kollasch