[Bug 1805154] Re: glibc 2.28-0ubuntu1 ADT test failure with linux 4.19.0-5.6

Bug Watch Updater 1805154 at bugs.launchpad.net
Mon Nov 26 15:31:36 UTC 2018


Launchpad has imported 2 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1651010.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2018-11-18T17:29:41+00:00 H.J. wrote:

Under 4.19.2-300 kernel, i686 glibc tests failed with:

FAIL: debug/tst-backtrace5
FAIL: debug/tst-backtrace6
FAIL: nptl/tst-cancel24
FAIL: nptl/tst-cancel24-static
FAIL: nptl/tst-cancelx16
FAIL: nptl/tst-cancelx18
FAIL: nptl/tst-cancelx20
FAIL: nptl/tst-cancelx21
FAIL: nptl/tst-cancelx4
FAIL: nptl/tst-cancelx5
FAIL: nptl/tst-cleanupx4
FAIL: nptl/tst-oncex3
FAIL: nptl/tst-oncex4

[hjl at gnu-skx-1 build-i686-linux]$ debug/tst-backtrace5 --direct
Obtained backtrace with 3 functions
Failure on line 53
[hjl at gnu-skx-1 build-i686-linux]$ 

Under 4.18.18-300 kernel, I got

Obtained backtrace with 7 functions
Function 0: debug/tst-backtrace5(handle_signal+0x1b) [0x804a42b]
Function 1: linux-gate.so.1(__kernel_sigreturn+0) [0xf7f7b0b0]
Function 2: linux-gate.so.1(__kernel_vsyscall+0x9) [0xf7f7b099]
Function 3: /export/build/gnu/tools-build/glibc-32bit/build-i686-linux/libc.so.6(__read+0x2d) [0xf7e99c8d]
Function 4: debug/tst-backtrace5(fn+0x105) [0x804a745]
Function 5: debug/tst-backtrace5(fn+0xd4) [0x804a714]
Function 6: debug/tst-backtrace5(fn+0xd4) [0x804a714]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1805154/comments/0

------------------------------------------------------------------------
On 2018-11-20T21:55:21+00:00 H.J. wrote:

This is caused by

commit 379d98ddf41344273d9718556f761420f4dc80b3
Author: Alistair Strachan <astrachan at google.com>
Date:   Fri Aug 3 10:39:31 2018 -0700

    x86: vdso: Use $LD instead of $CC to link
    
    The vdso{32,64}.so can fail to link with CC=clang when clang tries to find
    a suitable GCC toolchain to link these libraries with.
    
    /usr/bin/ld: arch/x86/entry/vdso/vclock_gettime.o:
      access beyond end of merged section (782)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1805154/comments/2

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/1805154

Title:
  glibc 2.28-0ubuntu1 ADT test failure with linux 4.19.0-5.6

Status in Linux:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Committed
Status in Fedora:
  Confirmed

Bug description:
  Testing failed on:
      amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-bootstrap/disco/amd64/g/glibc/20181119_075302_9b2e2@/log.gz
      i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-bootstrap/disco/i386/g/glibc/20181119_064219_9b2e2@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1805154/+subscriptions



More information about the foundations-bugs mailing list