ppc build fail

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

ppc build fail

Rüdiger Meier
Hi,

since some weeks ppc build fail very often with something like
--------
Waiting for device /dev/vda to appear:  ok
fsck from util-linux 2.21.2
fsck: fsck.ext4: not found
fsck: error 2 while executing fsck.ext4 for /dev/vda
fsck failed. Mounting root device read-only.
Mounting root /dev/vda
mount -o ro,defaults -t ext4 /dev/vda /root
run-init: /.build/build: Exec format error
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100

[<800147ac>] (unwind_backtrace+0x0/0xf8) from [<805220dc>]
(panic+0x8c/0x1e0)
[<805220dc>] (panic+0x8c/0x1e0) from [<800246c8>] (do_exit+0x850/0x8b8)
[<800246c8>] (do_exit+0x850/0x8b8) from [<80024894>]
(do_group_exit+0x3c/0xc4)
[<80024894>] (do_group_exit+0x3c/0xc4) from [<8002492c>]
(__wake_up_parent+0x0/0x18)
Rebooting in 1 seconds..No buildstatus set, either the base system is
broken (glibc/bash/perl)
----------

Is this a know problem?

cu,
Rudi
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: ppc build fail

Dinar Valeev
On Tue, May 7, 2013 at 4:15 PM, Ruediger Meier <[hidden email]> wrote:

> Hi,
>
> since some weeks ppc build fail very often with something like
> --------
> Waiting for device /dev/vda to appear:  ok
> fsck from util-linux 2.21.2
> fsck: fsck.ext4: not found
> fsck: error 2 while executing fsck.ext4 for /dev/vda
> fsck failed. Mounting root device read-only.
> Mounting root /dev/vda
> mount -o ro,defaults -t ext4 /dev/vda /root
> run-init: /.build/build: Exec format error
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
That problem I'm not aware of.

Do you remember where it happens? We have some memory issues, with the
new build machines.
Like Invalid pointer errors or Inappropriate ioctl.

>
> [<800147ac>] (unwind_backtrace+0x0/0xf8) from [<805220dc>]
> (panic+0x8c/0x1e0)
> [<805220dc>] (panic+0x8c/0x1e0) from [<800246c8>] (do_exit+0x850/0x8b8)
> [<800246c8>] (do_exit+0x850/0x8b8) from [<80024894>]
> (do_group_exit+0x3c/0xc4)
> [<80024894>] (do_group_exit+0x3c/0xc4) from [<8002492c>]
> (__wake_up_parent+0x0/0x18)
> Rebooting in 1 seconds..No buildstatus set, either the base system is
> broken (glibc/bash/perl)
> ----------
>
> Is this a know problem?
>
> cu,
> Rudi
> --
> To unsubscribe, e-mail: [hidden email]
> To contact the owner, e-mail: [hidden email]
>
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: ppc build fail

Andreas Schwab-2
Dinar Valeev <[hidden email]> writes:

> Like Invalid pointer errors or Inappropriate ioctl.

Those inappropriate ioctl errors are unlikely the real error, but a case
of lost errno value, ie. reading errno too late.

Andreas.

--
Andreas Schwab, SUSE Labs, [hidden email]
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: ppc build fail

Rüdiger Meier
In reply to this post by Dinar Valeev
On Tuesday 07 May 2013, Dinar Valeev wrote:

> On Tue, May 7, 2013 at 4:15 PM, Ruediger Meier <[hidden email]> wrote:
> > Hi,
> >
> > since some weeks ppc build fail very often with something like
> > --------
> > Waiting for device /dev/vda to appear:  ok
> > fsck from util-linux 2.21.2
> > fsck: fsck.ext4: not found
> > fsck: error 2 while executing fsck.ext4 for /dev/vda
> > fsck failed. Mounting root device read-only.
> > Mounting root /dev/vda
> > mount -o ro,defaults -t ext4 /dev/vda /root
> > run-init: /.build/build: Exec format error
> > Kernel panic - not syncing: Attempted to kill init!
> > exitcode=0x00000100
>
> That problem I'm not aware of.
>
> Do you remember where it happens? We have some memory issues, with
> the new build machines.
> Like Invalid pointer errors or Inappropriate ioctl.


For example here
osc remotebuildlog home:rudi_m umpf openSUSE_12.3_ports ppc | less

Maybe see also the other packages in home:rudi_m

Could also be that my setup is wrong!? I have this one to mix all ports
into openSUSE_12.3_ports:
---
<repository name="openSUSE_12.3_ports">
  <path project="openSUSE:12.3" repository="ports"/>
  <path project="devel:ARM:AArch64:12.3" repository="standard"/>
  <path project="devel:ARM:12.3:Contrib:RaspberryPi" repository="standard"/>
  <arch>aarch64</arch>
  <arch>armv5el</arch>
  <arch>armv7l</arch>
  <arch>ppc</arch>
  <arch>ppc64</arch>
</repository>
---

cu,
Rudi
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: ppc build fail

Dinar Valeev
On Tue, May 7, 2013 at 4:59 PM, Ruediger Meier <[hidden email]> wrote:

> On Tuesday 07 May 2013, Dinar Valeev wrote:
>> On Tue, May 7, 2013 at 4:15 PM, Ruediger Meier <[hidden email]> wrote:
>> > Hi,
>> >
>> > since some weeks ppc build fail very often with something like
>> > --------
>> > Waiting for device /dev/vda to appear:  ok
>> > fsck from util-linux 2.21.2
>> > fsck: fsck.ext4: not found
>> > fsck: error 2 while executing fsck.ext4 for /dev/vda
>> > fsck failed. Mounting root device read-only.
>> > Mounting root /dev/vda
>> > mount -o ro,defaults -t ext4 /dev/vda /root
>> > run-init: /.build/build: Exec format error
>> > Kernel panic - not syncing: Attempted to kill init!
>> > exitcode=0x00000100
>>
>> That problem I'm not aware of.
>>
>> Do you remember where it happens? We have some memory issues, with
>> the new build machines.
>> Like Invalid pointer errors or Inappropriate ioctl.
>
>
> For example here
> osc remotebuildlog home:rudi_m umpf openSUSE_12.3_ports ppc | less
It seems you're trying to build arm here:
/usr/bin/qemu-system-arm -no-reboot -nographic -net none -enable-kvm
-M vexpress-a15 -dtb /boot/a15-guest.dtb -cpu cortex-a15

>
> Maybe see also the other packages in home:rudi_m
>
> Could also be that my setup is wrong!? I have this one to mix all ports
> into openSUSE_12.3_ports:
> ---
> <repository name="openSUSE_12.3_ports">
>   <path project="openSUSE:12.3" repository="ports"/>
>   <path project="devel:ARM:AArch64:12.3" repository="standard"/>
>   <path project="devel:ARM:12.3:Contrib:RaspberryPi" repository="standard"/>
>   <arch>aarch64</arch>
>   <arch>armv5el</arch>
>   <arch>armv7l</arch>
>   <arch>ppc</arch>
>   <arch>ppc64</arch>
> </repository>
> ---
>
> cu,
> Rudi
> --
> To unsubscribe, e-mail: [hidden email]
> To contact the owner, e-mail: [hidden email]
>
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: ppc build fail

gregfreemyer
In reply to this post by Dinar Valeev
On Tue, May 7, 2013 at 10:40 AM, Dinar Valeev <[hidden email]> wrote:

> On Tue, May 7, 2013 at 4:15 PM, Ruediger Meier <[hidden email]> wrote:
>> Hi,
>>
>> since some weeks ppc build fail very often with something like
>> --------
>> Waiting for device /dev/vda to appear:  ok
>> fsck from util-linux 2.21.2
>> fsck: fsck.ext4: not found
>> fsck: error 2 while executing fsck.ext4 for /dev/vda
>> fsck failed. Mounting root device read-only.
>> Mounting root /dev/vda
>> mount -o ro,defaults -t ext4 /dev/vda /root
>> run-init: /.build/build: Exec format error
>> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
> That problem I'm not aware of.
>
> Do you remember where it happens? We have some memory issues, with the
> new build machines.
> Like Invalid pointer errors or Inappropriate ioctl.

I get PPC build failure notifications on occasion recently.

When I look to see what status is, it is typically "blocked" and
binaries are available from previous builds.  Then a day or two later
I check again and the build log shows success.

Here's a hermes emails from 3 days ago, trimmed to only have PPC
failures.  Some of these may be real.  I've quit chasing down PPC
failures since they seem to be mostly false alarms:

Digest TOC:
[ 1. Sat, 4 May 2013 20:31:28 +0200] Build failure of
security/bulk_extractor openSUSE_Factory_PowerPC/ppc
[ 2. Sat, 4 May 2013 20:25:55 +0200] Build failure of
security/sleuthkit openSUSE_Factory_PowerPC/ppc
<snip>
[ 7. Sat, 4 May 2013 15:57:26 +0200] Build failure of
devel:libraries:c_c++/libregf openSUSE_Factory_ppc/ppc
[ 8. Sat, 4 May 2013 09:58:18 +0200] Build failure of
security/mac-robber openSUSE_Factory_PowerPC/ppc

[ 1. Sat, 4 May 2013 20:31:28 +0200] Build failure of
security/bulk_extractor openSUSE_Factory_PowerPC/ppc

Package bulk_extractor (version 1.3.1-25.6) of
project security failed to build
for openSUSE_Factory_PowerPC / ppc.

Review the build log:
   osc remotebuildlog security bulk_extractor openSUSE_Factory_PowerPC
ppc | less

Check out the package for editing:
   osc checkout security bulk_extractor


[ 2. Sat, 4 May 2013 20:25:55 +0200] Build failure of
security/sleuthkit openSUSE_Factory_PowerPC/ppc

Package sleuthkit (version 4.0.2-31.10) of
project security failed to build
for openSUSE_Factory_PowerPC / ppc.

Review the build log:
   osc remotebuildlog security sleuthkit openSUSE_Factory_PowerPC ppc | less

Check out the package for editing:
   osc checkout security sleuthkit

<snip>

[ 7. Sat, 4 May 2013 15:57:26 +0200] Build failure of
devel:libraries:c_c++/libregf openSUSE_Factory_ppc/ppc

Package libregf (version 0~20130319-11.2) of
project devel:libraries:c_c++ failed to build
for openSUSE_Factory_ppc / ppc.

Review the build log:
   osc remotebuildlog devel:libraries:c_c++ libregf
openSUSE_Factory_ppc ppc | less

Check out the package for editing:
   osc checkout devel:libraries:c_c++ libregf


[ 8. Sat, 4 May 2013 09:58:18 +0200] Build failure of
security/mac-robber openSUSE_Factory_PowerPC/ppc

Package mac-robber (version 1.02-11.9) of
project security failed to build
for openSUSE_Factory_PowerPC / ppc.

Review the build log:
   osc remotebuildlog security mac-robber openSUSE_Factory_PowerPC ppc | less

Check out the package for editing:
   osc checkout security mac-robber


--
Greg
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: ppc build fail

Dinar Valeev
On Tue, May 7, 2013 at 5:28 PM, Greg Freemyer <[hidden email]> wrote:

> On Tue, May 7, 2013 at 10:40 AM, Dinar Valeev <[hidden email]> wrote:
>> On Tue, May 7, 2013 at 4:15 PM, Ruediger Meier <[hidden email]> wrote:
>>> Hi,
>>>
>>> since some weeks ppc build fail very often with something like
>>> --------
>>> Waiting for device /dev/vda to appear:  ok
>>> fsck from util-linux 2.21.2
>>> fsck: fsck.ext4: not found
>>> fsck: error 2 while executing fsck.ext4 for /dev/vda
>>> fsck failed. Mounting root device read-only.
>>> Mounting root /dev/vda
>>> mount -o ro,defaults -t ext4 /dev/vda /root
>>> run-init: /.build/build: Exec format error
>>> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
>> That problem I'm not aware of.
>>
>> Do you remember where it happens? We have some memory issues, with the
>> new build machines.
>> Like Invalid pointer errors or Inappropriate ioctl.
>
> I get PPC build failure notifications on occasion recently.
>
> When I look to see what status is, it is typically "blocked" and
> binaries are available from previous builds.  Then a day or two later
> I check again and the build log shows success.
>
> Here's a hermes emails from 3 days ago, trimmed to only have PPC
> failures.  Some of these may be real.  I've quit chasing down PPC
> failures since they seem to be mostly false alarms:
>
> Digest TOC:
> [ 1. Sat, 4 May 2013 20:31:28 +0200] Build failure of
> security/bulk_extractor openSUSE_Factory_PowerPC/ppc
> [ 2. Sat, 4 May 2013 20:25:55 +0200] Build failure of
> security/sleuthkit openSUSE_Factory_PowerPC/ppc
> <snip>
> [ 7. Sat, 4 May 2013 15:57:26 +0200] Build failure of
> devel:libraries:c_c++/libregf openSUSE_Factory_ppc/ppc
> [ 8. Sat, 4 May 2013 09:58:18 +0200] Build failure of
> security/mac-robber openSUSE_Factory_PowerPC/ppc
>
> [ 1. Sat, 4 May 2013 20:31:28 +0200] Build failure of
> security/bulk_extractor openSUSE_Factory_PowerPC/ppc
>
> Package bulk_extractor (version 1.3.1-25.6) of
> project security failed to build
> for openSUSE_Factory_PowerPC / ppc.
>
> Review the build log:
>    osc remotebuildlog security bulk_extractor openSUSE_Factory_PowerPC
> ppc | less
>
> Check out the package for editing:
>    osc checkout security bulk_extractor
>
>
> [ 2. Sat, 4 May 2013 20:25:55 +0200] Build failure of
> security/sleuthkit openSUSE_Factory_PowerPC/ppc
>
> Package sleuthkit (version 4.0.2-31.10) of
> project security failed to build
> for openSUSE_Factory_PowerPC / ppc.
>
> Review the build log:
>    osc remotebuildlog security sleuthkit openSUSE_Factory_PowerPC ppc | less
>
> Check out the package for editing:
>    osc checkout security sleuthkit
>
> <snip>
>
> [ 7. Sat, 4 May 2013 15:57:26 +0200] Build failure of
> devel:libraries:c_c++/libregf openSUSE_Factory_ppc/ppc
>
> Package libregf (version 0~20130319-11.2) of
> project devel:libraries:c_c++ failed to build
> for openSUSE_Factory_ppc / ppc.
>
> Review the build log:
>    osc remotebuildlog devel:libraries:c_c++ libregf
> openSUSE_Factory_ppc ppc | less
>
> Check out the package for editing:
>    osc checkout devel:libraries:c_c++ libregf
>
>
> [ 8. Sat, 4 May 2013 09:58:18 +0200] Build failure of
> security/mac-robber openSUSE_Factory_PowerPC/ppc
>
> Package mac-robber (version 1.02-11.9) of
> project security failed to build
> for openSUSE_Factory_PowerPC / ppc.
>
> Review the build log:
>    osc remotebuildlog security mac-robber openSUSE_Factory_PowerPC ppc | less
>
> Check out the package for editing:
>    osc checkout security mac-robber
If those packages failing on either build65 or build66, this is a
known problem. Triggering rebuild makes package built.

We're trying hard to reproduce such failure locally, so we can fix
KVM. But so far this happens only within OBS. No luck with trying to
reproduce it locally.

>
>
> --
> Greg
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: ppc build fail

Rüdiger Meier
In reply to this post by Dinar Valeev
On Tuesday 07 May 2013, Dinar Valeev wrote:
> On Tue, May 7, 2013 at 4:59 PM, Ruediger Meier <[hidden email]>
wrote:
> > On Tuesday 07 May 2013, Dinar Valeev wrote:
> >> On Tue, May 7, 2013 at 4:15 PM, Ruediger Meier <[hidden email]>
wrote:

> >> > Hi,
> >> >
> >> > since some weeks ppc build fail very often with something like
> >> > --------
> >> > Waiting for device /dev/vda to appear:  ok
> >> > fsck from util-linux 2.21.2
> >> > fsck: fsck.ext4: not found
> >> > fsck: error 2 while executing fsck.ext4 for /dev/vda
> >> > fsck failed. Mounting root device read-only.
> >> > Mounting root /dev/vda
> >> > mount -o ro,defaults -t ext4 /dev/vda /root
> >> > run-init: /.build/build: Exec format error
> >> > Kernel panic - not syncing: Attempted to kill init!
> >> > exitcode=0x00000100
> >>
> >> That problem I'm not aware of.
> >>
> >> Do you remember where it happens? We have some memory issues, with
> >> the new build machines.
> >> Like Invalid pointer errors or Inappropriate ioctl.
> >
> > For example here
> > osc remotebuildlog home:rudi_m umpf openSUSE_12.3_ports ppc | less
>
> It seems you're trying to build arm here:
> /usr/bin/qemu-system-arm -no-reboot -nographic -net none -enable-kvm
> -M vexpress-a15 -dtb /boot/a15-guest.dtb -cpu cortex-a15

But why it's using arm when I build for ppc arch?


> > Maybe see also the other packages in home:rudi_m
> >
> > Could also be that my setup is wrong!? I have this one to mix all
> > ports into openSUSE_12.3_ports:
> > ---
> > <repository name="openSUSE_12.3_ports">
> >   <path project="openSUSE:12.3" repository="ports"/>
> >   <path project="devel:ARM:AArch64:12.3" repository="standard"/>
> >   <path project="devel:ARM:12.3:Contrib:RaspberryPi"
> > repository="standard"/> <arch>aarch64</arch>
> >   <arch>armv5el</arch>
> >   <arch>armv7l</arch>
> >   <arch>ppc</arch>
> >   <arch>ppc64</arch>
> > </repository>
> > ---

I changed my setup now to

  <repository name="openSUSE_12.3_ports">
    <path project="openSUSE:12.3" repository="ports"/>
    <arch>armv7l</arch>
    <arch>ppc</arch>
    <arch>ppc64</arch>
  </repository>

... and it works again. But don't know what was wrong with my former
setup.

BTW is it correct that it's using qemu-system-ppc64 for ppc builds?


cu,
RUdi
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: ppc build fail

Dinar Valeev
On Tue, May 7, 2013 at 6:16 PM, Ruediger Meier <[hidden email]> wrote:

> On Tuesday 07 May 2013, Dinar Valeev wrote:
>> On Tue, May 7, 2013 at 4:59 PM, Ruediger Meier <[hidden email]>
> wrote:
>> > On Tuesday 07 May 2013, Dinar Valeev wrote:
>> >> On Tue, May 7, 2013 at 4:15 PM, Ruediger Meier <[hidden email]>
> wrote:
>> >> > Hi,
>> >> >
>> >> > since some weeks ppc build fail very often with something like
>> >> > --------
>> >> > Waiting for device /dev/vda to appear:  ok
>> >> > fsck from util-linux 2.21.2
>> >> > fsck: fsck.ext4: not found
>> >> > fsck: error 2 while executing fsck.ext4 for /dev/vda
>> >> > fsck failed. Mounting root device read-only.
>> >> > Mounting root /dev/vda
>> >> > mount -o ro,defaults -t ext4 /dev/vda /root
>> >> > run-init: /.build/build: Exec format error
>> >> > Kernel panic - not syncing: Attempted to kill init!
>> >> > exitcode=0x00000100
>> >>
>> >> That problem I'm not aware of.
>> >>
>> >> Do you remember where it happens? We have some memory issues, with
>> >> the new build machines.
>> >> Like Invalid pointer errors or Inappropriate ioctl.
>> >
>> > For example here
>> > osc remotebuildlog home:rudi_m umpf openSUSE_12.3_ports ppc | less
>>
>> It seems you're trying to build arm here:
>> /usr/bin/qemu-system-arm -no-reboot -nographic -net none -enable-kvm
>> -M vexpress-a15 -dtb /boot/a15-guest.dtb -cpu cortex-a15
>
> But why it's using arm when I build for ppc arch?
>
>
>> > Maybe see also the other packages in home:rudi_m
>> >
>> > Could also be that my setup is wrong!? I have this one to mix all
>> > ports into openSUSE_12.3_ports:
>> > ---
>> > <repository name="openSUSE_12.3_ports">
>> >   <path project="openSUSE:12.3" repository="ports"/>
>> >   <path project="devel:ARM:AArch64:12.3" repository="standard"/>
>> >   <path project="devel:ARM:12.3:Contrib:RaspberryPi"
>> > repository="standard"/> <arch>aarch64</arch>
>> >   <arch>armv5el</arch>
>> >   <arch>armv7l</arch>
>> >   <arch>ppc</arch>
>> >   <arch>ppc64</arch>
>> > </repository>
>> > ---
>
> I changed my setup now to
>
>   <repository name="openSUSE_12.3_ports">
>     <path project="openSUSE:12.3" repository="ports"/>
>     <arch>armv7l</arch>
>     <arch>ppc</arch>
>     <arch>ppc64</arch>
>   </repository>
>
> ... and it works again. But don't know what was wrong with my former
> setup.
>
> BTW is it correct that it's using qemu-system-ppc64 for ppc builds?
Yes.
>
>
> cu,
> RUdi
> --
> To unsubscribe, e-mail: [hidden email]
> To contact the owner, e-mail: [hidden email]
>
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]