Bug#907507: coreutils: /bin/dd throws a sig fault in mutex_optimistic_spin+0x164/0x1b0

2018-08-28 Thread Dennis Clarke
Package: coreutils
Version: 8.26-3
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

  Attempt to kill -9 $pid for a process running dd 


   * What exactly did you do (or not do) that was effective (or
 ineffective)?

  Could not kill the process as it seemed hung. 
  I pulled the USB memory stick out of the machine.

   * What was the outcome of this action?

  At some point later the process died as "killed" and 
  the shell prompt was visible.

   * What outcome did you expect instead?

  Expect a normal process to stop when CTRL-C or a kill -9 is 
  issued. 


Other information : 


[694328.800840] usb-storage 1-8:1.0: USB Mass Storage device detected
[694328.801128] scsi host4: usb-storage 1-8:1.0
[694328.801428] usbcore: registered new interface driver usb-storage
[694328.805712] usbcore: registered new interface driver uas
[694329.827892] scsi 4:0:0:0: Direct-Access SanDisk  Cruzer Micro 0.1  
PQ: 0 ANSI: 2
[694329.828724] sd 4:0:0:0: Attached scsi generic sg4 type 0
[694329.831605] sd 4:0:0:0: [sde] 3911679 512-byte logical blocks: (2.00 
GB/1.86 GiB)
[694329.831791] sd 4:0:0:0: [sde] Write Protect is off
[694329.831800] sd 4:0:0:0: [sde] Mode Sense: 03 00 00 00
[694329.831979] sd 4:0:0:0: [sde] No Caching mode page found
[694329.831985] sd 4:0:0:0: [sde] Assuming drive cache: write through
[694329.837463]  sde: sde1
[694329.838365] sd 4:0:0:0: [sde] Attached SCSI removable disk
[694675.048650] INFO: task systemd-udevd:226 blocked for more than 120 seconds.
[694675.048660]   Tainted: P   O4.9.0-7-amd64 #1 Debian 
4.9.110-3+deb9u2
[694675.048663] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[694675.048668] systemd-udevd   D0   226  1 0x0104
[694675.048677]  98a79f4cf400 98a74a50f400 98a7a327af00 
98a7b6c18980
[694675.048686]  98a71e5c4fc0 b066c1d1fb68 b3e0fed9 
b3e103c2
[694675.048694]   98a7b6c18980 b38c2df4 
98a7a327af00
[694675.048702] Call Trace:
[694675.048716]  [] ? __schedule+0x239/0x6f0
[694675.048724]  [] ? schedule+0x32/0x80
[694675.048734]  [] ? mutex_optimistic_spin+0x164/0x1b0
[694675.048741]  [] ? schedule+0x32/0x80
[694675.048749]  [] ? schedule_preempt_disabled+0xa/0x10
[694675.048757]  [] ? __mutex_lock_slowpath+0xb4/0x130
[694675.048766]  [] ? mutex_lock+0x1b/0x30
[694675.048775]  [] ? __blkdev_get+0x6a/0x410
[694675.048783]  [] ? blkdev_get+0x126/0x330
[694675.048791]  [] ? blkdev_get_by_dev+0x40/0x40
[694675.048798]  [] ? do_dentry_open+0x1fb/0x300
[694675.048807]  [] ? path_openat+0x6a3/0x14f0
[694675.048815]  [] ? vsnprintf+0xf3/0x4f0
[694675.048821]  [] ? do_filp_open+0x91/0x100
[694675.048829]  [] ? __seccomp_filter+0x74/0x270
[694675.048835]  [] ? memzero_explicit+0xe/0x10
[694675.048842]  [] ? __check_object_size+0xfa/0x1d8
[694675.048849]  [] ? do_sys_open+0x12e/0x210
[694675.048857]  [] ? do_syscall_64+0x8d/0xf0
[694675.048863]  [] ? entry_SYSCALL_64_after_swapgs+0x58/0xc6
[694719.825638] usb 1-8: USB disconnect, device number 27
[694719.836400] sd 4:0:0:0: [sde] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT 
driverbyte=DRIVER_OK
[694719.836404] sd 4:0:0:0: [sde] tag#0 CDB: Write(10) 2a 00 00 2a 59 58 00 00 
f0 00
[694719.836406] blk_update_request: I/O error, dev sde, sector 2775384
[694719.836407] Buffer I/O error on dev sde, logical block 2775384, lost async 
page write
[694719.836409] Buffer I/O error on dev sde, logical block 2775385, lost async 
page write
[694719.836410] Buffer I/O error on dev sde, logical block 2775386, lost async 
page write
[694719.836411] Buffer I/O error on dev sde, logical block 2775387, lost async 
page write
[694719.836412] Buffer I/O error on dev sde, logical block 2775388, lost async 
page write
[694719.836413] Buffer I/O error on dev sde, logical block 2775389, lost async 
page write
[694719.836414] Buffer I/O error on dev sde, logical block 2775390, lost async 
page write
[694719.836415] Buffer I/O error on dev sde, logical block 2775391, lost async 
page write
[694719.836417] Buffer I/O error on dev sde, logical block 2775392, lost async 
page write
[694719.836418] Buffer I/O error on dev sde, logical block 2775393, lost async 
page write


*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-7-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages coreutils depends on:
ii  libacl1  2.2.52-3+b1
ii  libattr1 1:2.4.47-2+b2
ii  libc62.24-11+deb9u3
ii  libselinux1  2.6-3+b3


Bug#904931: NVRM: GPU at 0000:01:00.0 has fallen off the bus.

2018-08-20 Thread Dennis Clarke


System locks up again but only the display and GPU are dead.

I can ssh in just fine and everything else seems fine.

dmesg say :

[ 1355.774258] NVRM: GPU at PCI::01:00: 
GPU-3b06fc6f-1f69-a174-d221-b4f62fa5fc40

[ 1355.774270] NVRM: GPU Board Serial Number:
[ 1355.774278] NVRM: Xid (PCI::01:00): 79, GPU has fallen off the bus.
[ 1355.774282] NVRM: GPU at :01:00.0 has fallen off the bus.
[ 1355.774286] NVRM: GPU is on Board .
[ 1355.774302] NVRM: A GPU crash dump has been created. If possible, 
please run
   NVRM: nvidia-bug-report.sh as root to collect this data 
before

   NVRM: the NVIDIA kernel module is unloaded.
[ 1356.468504] irq 16: nobody cared (try booting with the "irqpoll" option)
[ 1356.468508] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P   O 
4.9.0-7-amd64 #1 Debian 4.9.110-3+deb9u2
[ 1356.468509] Hardware name: System manufacturer System Product 
Name/PRIME Z270-P, BIOS 0810 07/07/2017
[ 1356.468510]   b9930694 a0e91fdd9a00 
a0e91fdd9ad4
[ 1356.468513]  b96d63e0 a0e91fdd9a00  
ba318940
[ 1356.468515]  0051 b96d676b a0e91fdd9a00 


[ 1356.468517] Call Trace:
[ 1356.468518]  
[ 1356.468522]  [] ? dump_stack+0x5c/0x78
[ 1356.468524]  [] ? __report_bad_irq+0x30/0xc0
[ 1356.468525]  [] ? note_interrupt+0x23b/0x280
[ 1356.468527]  [] ? handle_irq_event_percpu+0x51/0x70
[ 1356.468528]  [] ? handle_irq_event+0x39/0x60
[ 1356.468530]  [] ? handle_fasteoi_irq+0xa0/0x170
[ 1356.468532]  [] ? handle_irq+0x1f/0x30
[ 1356.468534]  [] ? do_IRQ+0x46/0xd0
[ 1356.468536]  [] ? common_interrupt+0x96/0x96
[ 1356.468536]  
[ 1356.468539]  [] ? cpuidle_enter_state+0xa2/0x2d0
[ 1356.468541]  [] ? cpu_startup_entry+0x154/0x240
[ 1356.468543]  [] ? start_kernel+0x447/0x467
[ 1356.468545]  [] ? early_idt_handler_array+0x120/0x120
[ 1356.468547]  [] ? x86_64_start_kernel+0x14c/0x170
[ 1356.468548] handlers:
[ 1356.468550] [] i801_isr [i2c_i801]
[ 1356.468551] Disabling IRQ #16
[ 1373.506781] usb 1-9: USB disconnect, device number 2
[ 1380.819532] usb 1-9: new full-speed USB device number 6 using xhci_hcd
[ 1380.960503] usb 1-9: New USB device found, idVendor=1ef1, idProduct=0017
[ 1380.960506] usb 1-9: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0

[ 1380.960507] usb 1-9: Product: PQLabs MultiTouch Screen
[ 1380.960508] usb 1-9: Manufacturer: PQLabs
[ 1380.961711] input: PQLabs PQLabs MultiTouch Screen as 
/devices/pci:00/:00:14.0/usb1/1-9/1-9:1.0/0003:1EF1:0017.0004/input/input19
[ 1380.962178] hid-multitouch 0003:1EF1:0017.0004: 
input,hiddev0,hidraw2: USB HID v1.11 Mouse [PQLabs PQLabs MultiTouch 
Screen] on usb-:00:14.0-9/input0


I did create  nvidia-bug-report.log.gz

see attached.


Dennis




nvidia-bug-report.log.xz
Description: application/xz


Bug#895452: libquadmath and quadmath.h do not exist on ppc64

2018-04-18 Thread Dennis Clarke

I will test gcc-8-20180415 and see what results I get.



Bug#895452: libquadmath and quadmath.h do not exist on ppc64

2018-04-18 Thread Dennis Clarke


New GCC bigid is being flipped around by Jakub Jelinek ( Red Hat )
who claims this issue is fixed for ppc64 in GCC version 8 that
does not exist anywhere.  Not even in the git repo.

I am trying to figure out what is going on here.

see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82686

see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85440

What a mess .. seems like a new secret gcc codebase exists somewhere
and no one can see it.

Dennis



Bug#895452: some progress bootstrap completes for gcc 7.3.0

2018-04-16 Thread Dennis Clarke

Managed a bootstrap that didn't blow up.

At the moment the assembly output from a trivial test shows that the IBM
extended precision long double type is the default unless one actually
asks for the IEEE754-2008 128-bit datatype.

dclarke@nix:~/pgm/C/ieee754$ 
PATH=/usr/local/build/gcc-7.3.0_linux_4.15.0-2-powerpc64_ppc64.005/gcc:$PATH 
xgcc 
-I/usr/local/build/gcc-7.3.0_linux_4.15.0-2-powerpc64_ppc64.005/gcc/include 
-m64 -g -Wl,-rpath=/usr/local/lib -mcpu=970 -maltivec -mfull-toc 
-mregnames -mabi=ieeelongdouble -S -o ld.s ld.c

xgcc: warning: using IEEE extended precision long double
cc1: warning: using IEEE extended precision long double
dclarke@nix:~/pgm/C/ieee754$ grep "quad" ld.s | grep "0x"
.quad   0x4000921fb54442d1,0x8469898cc51701b8

That data is correct.

dclarke@nix:~/pgm/C/ieee754$ 
PATH=/usr/local/build/gcc-7.3.0_linux_4.15.0-2-powerpc64_ppc64.005/gcc:$PATH 
xgcc 
-I/usr/local/build/gcc-7.3.0_linux_4.15.0-2-powerpc64_ppc64.005/gcc/include 
-m64 -g -Wl,-rpath=/usr/local/lib -mcpu=970 -maltivec -mfull-toc 
-mregnames -mabi=ibmlongdouble -S -o ld.s ld.c

xgcc: warning: using IBM extended precision long double
cc1: warning: using IBM extended precision long double
dclarke@nix:~/pgm/C/ieee754$ grep "quad" ld.s | grep "0x"
.quad   0x400921fb54442d18,0x3ca1a62633145c06

That is a whole other beast of a different colour.

dclarke@nix:~/pgm/C/ieee754$ 
PATH=/usr/local/build/gcc-7.3.0_linux_4.15.0-2-powerpc64_ppc64.005/gcc:$PATH 
xgcc 
-I/usr/local/build/gcc-7.3.0_linux_4.15.0-2-powerpc64_ppc64.005/gcc/include 
-m64 -g -Wl,-rpath=/usr/local/lib -mcpu=970 -maltivec -mfull-toc 
-mregnames -S -o ld.s ld.c

dclarke@nix:~/pgm/C/ieee754$ grep "quad" ld.s | grep "0x"
.quad   0x400921fb54442d18,0x3ca1a62633145c06
dclarke@nix:~/pgm/C/ieee754$

So the default is the IBM type. No idea on the libquadmath yet.

I should have more info on this issue in another 16 or 20 hours.

Dennis



Bug#895452: gcc-7: libquadmath is disabled for gcc 7.3.0 on powerpc64-linux-gnu

2018-04-11 Thread Dennis Clarke

On 11/04/18 04:52 PM, Matthias Klose wrote:

On 11.04.2018 19:04, Dennis Clarke wrote:

Package: gcc-7
Version: 7.3.0-15
Severity: important

Dear Maintainer,

* What led up to the situation?

Attempt to compile a trivial code test that uses #include 
as well as _Float128 datatype and quadmath_snprintf() call fails with

  fatal error: quadmath.h: No such file or directory


I have dark memories, that quadmath didn't build. Please could you check that
again with a native build and a cross build, if you have access to a ppc64 
platform?



I am working on it. I need to get past some new silly dependency that
makes little sense given that the bootstrap fails in stage 3 of all
places :

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82686

So I should ( in theory ) be able to build the gc code in place and in 
the tree in the same manner as gmp, mpfr, mpc and isl.  So I am working

on that but it just isn't working.

In any case I'll get the sources from http://www.hboehm.info/gc/ and 
keep hacking at this on ppc64.


Dennis



Bug#895452: gcc-7: libquadmath is disabled for gcc 7.3.0 on powerpc64-linux-gnu

2018-04-11 Thread Dennis Clarke
Package: gcc-7
Version: 7.3.0-15
Severity: important

Dear Maintainer,

   * What led up to the situation?

Attempt to compile a trivial code test that uses #include 
as well as _Float128 datatype and quadmath_snprintf() call fails with

 fatal error: quadmath.h: No such file or directory

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Wrote a trivial piece of test code and then issued a compile :

$ gcc -mcpu=970 -mno-altivec -g -m64 -std=c99 -pedantic-errors -o s s.c 
s.c:82:10: fatal error: quadmath.h: No such file or directory
 #include 
  ^~~~
compilation terminated.


   * What was the outcome of this action?

Compile can not proceed.


   * What outcome did you expect instead?

Expected a trivial to compile to generate pre-processed intermediate
file and then assembly and then an object file and then a final ELF
executable file that runs as expected.

-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ppc64

Kernel: Linux 4.15.0-2-powerpc64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=C (charmap=ANSI_X3.4-1968), 
LANGUAGE=en_CA:en (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gcc-7 depends on:
ii  binutils  2.30-15
ii  cpp-7 7.3.0-15
ii  gcc-7-base7.3.0-15
ii  libc6 2.27-3
ii  libcc1-0  8-20180402-1
ii  libgcc-7-dev  7.3.0-15
ii  libgcc1   1:8-20180402-1
ii  libgmp10  2:6.1.2+dfsg-3
ii  libisl19  0.19-1
ii  libmpc3   1.1.0-1
ii  libmpfr6  4.0.1-1
ii  libstdc++68-20180402-1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages gcc-7 recommends:
ii  libc6-dev  2.27-3

Versions of packages gcc-7 suggests:
pn  gcc-7-doc 
pn  gcc-7-locales 
ii  gcc-7-multilib7.3.0-15
pn  libasan4-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx2-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- no debconf information