This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/15908] New: On ARM fc19 hw_watch_addr.stp example causes kernel hang and "BUG: scheduling while atomic:" and lock up
- From: "wcohen at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Thu, 29 Aug 2013 19:33:08 +0000
- Subject: [Bug runtime/15908] New: On ARM fc19 hw_watch_addr.stp example causes kernel hang and "BUG: scheduling while atomic:" and lock up
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=15908
Bug ID: 15908
Summary: On ARM fc19 hw_watch_addr.stp example causes kernel
hang and "BUG: scheduling while atomic:" and lock up
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: wcohen at redhat dot com
On both Samsung arm chromebook and compulab trimslice runing fc19 running the
tests with a "make installcheck" causes the machines to hang when the
hw_watch_addr.stp test is run. The trimslice is running an updated version of
fc19 (as of 2013-08-29) with kernel-3.10.9-200.fc19.armv7hl
chromebook has locally built linux-3.11-rc7 kernel built with the instructions
on:
http://people.redhat.com/wcohen/chromebook/booting-3.11kernel.txt
To reproduce:
-check out the current git repo of sytemtap
-build and install
-run the examples with:
make installcheck RUNTESTFLAGS="--debug systemtap.examples/check.exp"
Eventually gets to running hw_watch_addr.stp and the machine hangs. One the
trimslice the serial console spews out a lot of output of the form:
FAIL: ./systemtap.examples/general/stopwatches build
FAIL: ./systemtap.examples/io/iostat-scsi build
[ 2332.364553] BUG: scheduling while atomic: systemd-journal/157/0x40000001
[ 2332.394534] BUG: scheduling while atomic: systemd-journal/157/0x40000001
[ 2332.394545] BUG: scheduling while atomic: rs:main Q:Reg/309/0x40000001
[ 2332.404517] BUG: scheduling while atomic: rs:main Q:Reg/309/0x40000001
[ 2332.414450] BUG: scheduling while atomic: rs:main Q:Reg/309/0x40000001
[ 2332.424526] BUG: scheduling while atomic: systemd-journal/157/0x40000001
[ 2332.424532] BUG: scheduling while atomic: rs:main Q:Reg/309/0x40000001
[ 2332.434519] BUG: scheduling while atomic: rs:main Q:Reg/309/0x40000001
[ 2332.444443] BUG: scheduling while atomic: rs:main Q:Reg/309/0x40000001
[ 2332.464532] BUG: scheduling while atomic: rs:main Q:Reg/309/0x40000001
[ 2332.474528] BUG: scheduling while atomic: rs:main Q:Reg/309/0x40000001
[ 2332.494513] BUG: scheduling while atomic: rs:main Q:Reg/309/0x40000001
[ 2332.494539] BUG: scheduling while atomic: systemd-journal/157/0x40000001
[ 2332.514516] BUG: scheduling while atomic: systemd-journal/157/0x40000001
[ 2332.514526] BUG: scheduling while atomic: rs:main Q:Reg/309/0x40000001
[ 2332.527834] BUG: scheduling while atomic: rs:main Q:Reg/309/0x40000001
[ 2332.544550] BUG: scheduling while atomic: rs:main Q:Reg/309/0x40000001
...
After this need to reboot the machine. Would expect that the test runs or
fails, but doesn't take the machine down.
--
You are receiving this mail because:
You are the assignee for the bug.