Re: Fwd: [Xen-devel] Segfault When Building Snapshot xen-3d14ce7 kernel From linux/kernel/git/jeremy/xen.git/shortlog

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Fri, 2011-03-18 at 12:14 +0000, John McDermott wrote:
> Sorry, did not go to the list:
> 
> Begin forwarded message:
> 
> > From: "John McDermott (U.S. Navy Employee)" <john.mcdermott@xxxxxxxxxxxx>
> > Date: March 18, 2011 7:56:58 AM EDT
> > To: Pasi KÃrkkÃinen <pasik@xxxxxx>
> > Subject: Re: [Xen-devel] Segfault When Building Snapshot xen-3d14ce7 kernel 
> > From linux/kernel/git/jeremy/xen.git/shortlog
> > 
> > Pasi,
> > 
> > Thanks. I should have said something about that:
> > 
> > I am building the hypervisor about 15 times a day on this box, doing 
> > development on the hypervisor, and have no problems doing that.

Still, neither gcc nor as should segfault, ever, no matter what the
input is. The paths which you mentioned (net/ipv4/blah..) aren't paths
which the Xen support in the really kernel touch.

The fact that compiling the hypervisor build does not trigger the issue
isn't really indicative of anything in particular either since the
inputs to gcc are different.

Are you running the host under Xen when this happens? Which
kernel/hypervisor? Is there anything in your kernel logs?

Anyway, please provide a complete build log.

Ian.

> > 
> > Sincerely,
> > 
> > John
> > 
> > On Mar 18, 2011, at 7:52 AM, Pasi KÃrkkÃinen wrote:
> > 
> >> On Fri, Mar 18, 2011 at 07:44:54AM -0400, John McDermott wrote:
> >>> Xen Developers,
> >>> 
> >>> I downloaded snapshot xen-3d14ce7 (it is currently at the top of the 
> >>> list) yesterday and tried to build it overnight on my Fedora 13 box. It 
> >>> reported
> >>> 
> >>>   gcc: Internal error: Segmentation fault (program as)
> >>> 
> >> 
> >> Hello,
> >> 
> >>> Make reports the error as being in [net/ipv4/ipip.mod.o] but it has "CC 
> >>> net/ipv4/ipip.mod.o" further up the list, above a couple of other files, 
> >>> as successful. The last file listed before the segfault is 
> >>> net/ipv4/netfilter/arptable_filter.mod.o. Sorry I have no further 
> >>> information; I ran it as make -j4. Before I run make clean and re-try as 
> >>> a single thread, to get more error information, is there anything of 
> >>> interest I should look at, to pass along, before I clean? I see there was 
> >>> an update to arp_notify a few commits below this version.
> >>> 
> >> 
> >> So it fails compiling Linux kernel.
> >> Are you sure your hardware is OK? Faulty memory?
> >> 
> >> gcc shouldn't segfault..
> >> 
> >> -- Pasi
> >> 
> >>> Sincerely,
> >>> 
> >>> John
> >>> ----
> >>> What is the formal meaning of the one-line program
> >>> #include "/dev/tty"
> >>> 
> >>> J.P. McDermott                    building 12
> >>> Code 5542                 mcdermott@xxxxxxxxxxxxxxxx
> >>> Naval Research Laboratory voice: +1 202.404.8301
> >>> Washington, DC 20375, US  fax:   +1 202.404.7942
> >>> 
> >>> 
> >>> 
> >>> 
> >>> 
> >>> 
> >>> 
> >>> 
> >>> _______________________________________________
> >>> Xen-devel mailing list
> >>> Xen-devel@xxxxxxxxxxxxxxxxxxx
> >>> http://lists.xensource.com/xen-devel
> > 
> > ----
> > What is the formal meaning of the one-line program
> > #include "/dev/tty"
> > 
> > J.P. McDermott                              building 12
> > Code 5542                                   mcdermott@xxxxxxxxxxxxxxxx
> > Naval Research Laboratory   voice: +1 202.404.8301
> > Washington, DC 20375, US    fax:   +1 202.404.7942
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> 
> ----
> What is the formal meaning of the one-line program
> #include "/dev/tty"
> 
> J.P. McDermott                                building 12
> Code 5542                                     mcdermott@xxxxxxxxxxxxxxxx
> Naval Research Laboratory     voice: +1 202.404.8301
> Washington, DC 20375, US      fax:   +1 202.404.7942
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



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