This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug testsuite/23493] Test suite makes all CPU stuck forever on kernel 4.16.16 (Fedora 27)


https://sourceware.org/bugzilla/show_bug.cgi?id=23493

--- Comment #6 from agentzh <agentzh at gmail dot com> ---
The command I used to run the stap test suite was this:

```
sudo time make -j8 installcheck-parallel |& tee result.txt
```

I've attached the full `result.txt` produced that night to this PR for your
reference.

I've also attached the full /var/log/messages file content during the test run
period (also included messages right before I started running the stap test
suite and right after I rebooted the machine on the next day to avoid any
confusions).

Some observations from the result.txt and /var/log/messages files:

1. Aug 6 23:18 I started running the test with the command `sudo time make -j8
installcheck-parallel |& tee result.txt` (see result.txt)

2. Aug 7 00:35:57 or later: the stap test suite generates the last few lines of
output to stderr/stdout (see result.txt)

3. Aug  7 00:34:16 The kernel generated the last line of output to
/var/log/messages, which was "work2 kernel:
stap_e0ad497a0eaf9de8589606c16f0b585_79159: unknown parameter 'pt' ignored"
After that, no kernel dmesg output until I rebooted the machine with force.

4. Aug  7 08:28:03 I got up in the morning and rebooted the machine with force.

The virtual machine running the tests has 8GB of RAM:

```
$ free
              total        used        free      shared  buff/cache   available
Mem:        8143832      646244     1851164       98824     5646424     6997500
Swap:       2097148           0     2097148
```

It has 8 logical CPU cores (4 physical CPU cores with hyperthreading enabled).

Please let me know if you need any further information. Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]