On Sat, 8 Dec 2018, John Paul Adrian Glaubitz wrote:
> Hi!
>
> On 12/8/18 9:34 AM, John Paul Adrian Glaubitz wrote:
> > Working on this now. Bisecting between 2.27 and 2.28 and testing on
> > qemu-system now that I have a usable reproducer.
>
> I found the commit which broke glibc on m68k, it i
Hi!
On 12/8/18 9:34 AM, John Paul Adrian Glaubitz wrote:
> Working on this now. Bisecting between 2.27 and 2.28 and testing on
> qemu-system
> now that I have a usable reproducer.
I found the commit which broke glibc on m68k, it is:
b4a5d26d8835d972995f0a0a2f805a8845bafa0b is the first bad comm
On 12/8/18 7:57 AM, Finn Thain wrote:
>> Can you strace the whole procedure (i.e. starting with the call to
>> chroot) from the outside? With time stamps, for preference?
>>
>
> I'd rather wait for the results of Adrian's git bisection before spending
> more time on this bug.
Working on this no
On Sat, 8 Dec 2018, Michael Schmitz wrote:
>
> Can you strace the whole procedure (i.e. starting with the call to
> chroot) from the outside? With time stamps, for preference?
>
I'd rather wait for the results of Adrian's git bisection before spending
more time on this bug.
> The strace you
Finn,
Am 08.12.2018 um 12:37 schrieb Finn Thain:
On Sat, 8 Dec 2018, John Paul Adrian Glaubitz wrote:
This seems to affect qemu-user only while the lock-up problem with dash
occurs on qemu-system only.
Finn, did you verify the lock-up problem on real hardware by any chance?
I don't have m
On 12/8/18 12:37 AM, Finn Thain wrote:
> Well, if it's a qemu bug then it's also an aranym bug.
>
> If you want to reproduce on elgar, you only need 3 files:
> (...)
> At this point dash has hung. If you strace that process from outside the
> chroot, you can see it looping around wait4() = -1 ECH
On Sat, 8 Dec 2018, John Paul Adrian Glaubitz wrote:
>
> This seems to affect qemu-user only while the lock-up problem with dash
> occurs on qemu-system only.
>
> Finn, did you verify the lock-up problem on real hardware by any chance?
>
I don't have my 68k hardware with me at the moment.
>
Hi!
On 12/6/18 2:12 PM, John Paul Adrian Glaubitz wrote:
> There is another serious problem with glibc 2.28 on m68k which makes
> some packages fail to build [1]:
>
> cp -a doc/changes
> /<>/debian/hp2xx/usr/share/doc/hp2xx/changelog_old
> cp -a hp-tests/* /<>/debian/hp2xx/usr/share/doc/hp2xx/hp
Hi!
On 12/7/18 2:32 PM, John Paul Adrian Glaubitz wrote:
> It's related to dash as well since GNU Make (which is what runs debian/rules)
> uses /bin/sh which is pointing to dash:
I have opened a bug report against glibc now:
> https://sourceware.org/bugzilla/show_bug.cgi?id=23960
I don't see th
>> Can you stat these files using native tools (to bypass qemu-user, m68k
>> libc, etc) and confirm their presence?
>
> The interesting part is that "cp -a foo/* bar/" of these files works on
> the command line. What does not work is when this happens inside
> debian/rules.
It's related to dash a
> On Thu, 6 Dec 2018, John Paul Adrian Glaubitz wrote:
> > (sid-m68k-sbuild)root@epyc:/build/hp2xx-j13jUj/hp2xx-3.4.4# dpkg -i
> > /tmp/*deb
I installed those 2.27-8 packages and everything works again. Thanks.
root@panmac:/var/cache/apt/archives# dpkg -i *2.27-8*
dpkg: warning: downgrading l
On 12/7/18 7:27 AM, Finn Thain wrote:
> That's -ENOENT from stat(2) from cp(1) when running under qemu-user,
> right?
>
> Can you stat these files using native tools (to bypass qemu-user, m68k
> libc, etc) and confirm their presence?
The interesting part is that "cp -a foo/* bar/" of these file
On Thu, 6 Dec 2018, John Paul Adrian Glaubitz wrote:
> There is another serious problem with glibc 2.28 on m68k which makes
> some packages fail to build [1]:
>
Interesting.
> [...]
> Downgrading from 2.28 to 2.27 fixes the problem:
>
> (sid-m68k-sbuild)root@epyc:/build/hp2xx-j13jUj/hp2xx-3
There is another serious problem with glibc 2.28 on m68k which makes
some packages fail to build [1]:
cp -a doc/changes
/<>/debian/hp2xx/usr/share/doc/hp2xx/changelog_old
cp -a hp-tests/* /<>/debian/hp2xx/usr/share/doc/hp2xx/hp-tests/
/bin/cp: cannot stat 'hp-tests/*': No such file or directory
m
On Thu, 6 Dec 2018, Eero Tamminen wrote:
> On 12/6/18 1:10 AM, Finn Thain wrote:
> > On Tue, 4 Dec 2018, John Paul Adrian Glaubitz wrote:
> > > On 12/3/18 8:13 AM, Finn Thain wrote:
> > > > The problem turns out to be dash. I got things working again by
> > > > replacing /bin/sh and /bin/dash wit
Hi,
On 12/6/18 1:10 AM, Finn Thain wrote:
On Tue, 4 Dec 2018, John Paul Adrian Glaubitz wrote:
On 12/3/18 8:13 AM, Finn Thain wrote:
The problem turns out to be dash. I got things working again by replacing
/bin/sh and /bin/dash with symlinks to bash and then running
'apt --fix-broken install'
On 12/6/18 12:10 AM, Finn Thain wrote:
> It happens in aranym too. I tried strace,
>
> execve("/root/dash", ["/root/dash", "-c", "/bin/echo"], ["PWD=/",
> "HOME=/", "BOOT_IMAGE=vmlinux", "TERM=linux", "SHLVL=1",
> "_=/usr/bin/strace"]) = 0
> (...)
> The last two lines loop indefinitely, and dash
On Tue, 4 Dec 2018, John Paul Adrian Glaubitz wrote:
> On 12/3/18 8:13 AM, Finn Thain wrote:
> > The problem turns out to be dash. I got things working again by replacing
> > /bin/sh and /bin/dash with symlinks to bash and then running
> > 'apt --fix-broken install' to finish the upgrade.
>
> Th
On 12/3/18 8:13 AM, Finn Thain wrote:
> The problem turns out to be dash. I got things working again by replacing
> /bin/sh and /bin/dash with symlinks to bash and then running
> 'apt --fix-broken install' to finish the upgrade.
Thanks for the heads-up! I just ran into this problem with qemu-syst
On Mon, 3 Dec 2018, I wrote:
> When I ran 'apt-get dist-upgrade' today, the installation got stuck when
> configuring libc6-2.28-1. This package seems to have broken my system --
> any process that gets launched never terminates. Anyone else seen this?
>
The problem turns out to be dash. I got
When I ran 'apt-get dist-upgrade' today, the installation got stuck when
configuring libc6-2.28-1. This package seems to have broken my system --
any process that gets launched never terminates. Anyone else seen this?
--
21 matches
Mail list logo
