[Bug 2060275] Re: pmproxy crash at startup in libpcp_web.so.1

-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060275 Title: pmproxy crash at startup in libpcp_web.so.1 To manage notifications about this bug go to:

[Bug 1962785] Re: dtrace predictable temp file causes race

Suggest adding commit cfabd38cfdd75e also, which makes it more robust toward identical concurrent jobs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962785 Title: dtrace predictable temp file

[Bug 1830226] Re: systemtap currently broken in xenial

Dan, nice to hear of the nightly-build PPA. If there were one coupled to a fresher elfutils (0.178+), then you'd get a nice combination of new systemtap and auto-downloaded debuginfod content (even for xenial). https://sourceware.org/elfutils/Debuginfod.html -- You received this bug

[Bug 1883343] Re: systemtap fails to build C due to __NR_compat_clock_getres define errors

I suspect what you'll need is a collection of #if/#endif guards around the definitions of those macros: diff --git a/runtime/linux/compat_unistd.h b/runtime/linux/compat_unistd.h index 5a26b77bbccb..45e8b4d6c3d9 100644 --- a/runtime/linux/compat_unistd.h +++ b/runtime/linux/compat_unistd.h @@

Re: [Bug 1830226] Re: systemtap currently broken in xenial

Hi - > This version of systemtap needs to be dependent on kernel 4.4.0-143 #169 or later. Please note that upstream systemtap 4.1 supports the whole range of kernels 2.6 through 5.1ish. - FChE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1832741] Re: Systemtap regression on Linux 5.2.0-rc4+

> Am I running 3.2 or 4.2 when I do sudo stap

[Bug 1832741] Re: Systemtap regression on Linux 5.2.0-rc4+

OK, that would be new -- but just make sure you're running the new stap for that test not an accidental old one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832741 Title: Systemtap regression on

[Bug 1832741] Re: Systemtap regression on Linux 5.2.0-rc4+

systemtap 4.1 compensates for the kbuild changes made in linux 5.0-ish that caused the breakage you are noticing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832741 Title: Systemtap regression

[Bug 1830726] Re: systemtap for hwe kernels

Thanks for testing. systemtap goes to a lot of trouble to provide backward compatibility to preexisting scripts, so really that should not be a problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1830726] Re: systemtap for hwe kernels

Does git/master systemtap, or the recently released v4.1 not work on -all- your kernels? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830726 Title: systemtap for hwe kernels To manage

[Bug 1827819] Re: Systemtap stapconf header is not generated

commit eb8c8de940cb5e9256323e67a1757f9a45afed8c Author: Frank Ch. Eigler Date: Sat Feb 2 14:50:32 2019 -0600 linux 5.0-rc3 adaptations should help We're planning to release stap 4.1 within days, with this fix (and including up to kernel 5.1 support). -- You received this bug

[Bug 1545330] Re: [wily][regression] systemtap script compilation broken by new kernels

By the way, a simple diagnostic for whether any particular version of systemtap has been ported to a kernel is to run % stap -V Systemtap translator/driver (version 4.1/0.174, rpm 4.1-0.20190327git2ede4cecb20c.fc28) Copyright (C) 2005-2019 Red Hat, Inc. and others This is free software; see the

Re: [Bug 1795545] [NEW] Systemtap incompatible with ubuntu 18.04

Hi - This commit appears to fix this problem. https://sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=8bc64034509474bee3fb7996b2a9e74c8bc27281 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1763525] Re: systemtap module compilation fails due to `__GFP_REPEAT` undeclared

stap 3.2 includes this fix: commit 73e0af29bb4c1edc1d6e22405ce404dd10569afd Author: David Smith Date: Tue Jul 25 16:09:42 2017 -0500 Updated tapset/linux/memory.stp for rawhide kernels. * tapset/linux/memory.stp (__gfp_flag_str): Updated for rawhide kernels

[Bug 1557673] Re: systemtap does not work on xenial, struct module changes

> does that cover wily also? Pre-release systemtap is also being tested with pre-release 4.6 linux, so should work fine on wily etc. I can only speak as upstream, not for ubuntu packaging though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1557673] Re: systemtap does not work on xenial, struct module changes

Upstream commit 3f040971e7e should fix this. (Also, we plan to have a systemtap 3.0 release shortly, with this and other fixes.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557673 Title:

[Bug 1537125] Re: ubuntu-14.04.04: fail to run systemtap test suites

Ravi, systemtap can pass through the $SYSTEMTAP_DEBUGINFO_PATH variable to elfutils, which controls where debuginfo files are sought. If you can get a working $SYSTEMTAP_DEBUGINFO_PATH set by hand, we can plop that definition into systemtap proper. -- You received this bug notification because

Re: [Bug 1537125] Re: ubuntu-14.04.04: fail to run systemtap test suites

Hi - > I have just tested with the systemtap 2.9 package presently in xenial, > and the following test case fails the same way there as with systemtap > 2.3 in trusty: > > # stap -v -e 'probe vfs.read {printf("read performed\n"); exit()}' > [...] > semantic error: while resolving probe point:

[Bug 295975] Re: generating callgraphs is broken

Possibly related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325713 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/295975 Title: generating callgraphs is broken To manage notifications

[Bug 1325713] [NEW] need vdso*.so images installed under /lib/modules for systemtap etc.

Public bug reported: The vdso* files are built into the kernel for loading into userspace binaries to accelerate various kernel-related operations. These files do not need to be packaged installed for the system to operate, and indeed they aren't part of the linux-image* deb's in Ubuntu.

[Bug 1325713] Lspci.txt

apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1325713/+attachment/4124376/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325713 Title: need

[Bug 1325713] ProcCpuinfo.txt

apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1325713/+attachment/4124377/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325713

[Bug 1325713] Re: need vdso*.so images installed under /lib/modules for systemtap etc.

apport information ** Tags added: apport-collected trusty ** Description changed: The vdso* files are built into the kernel for loading into userspace binaries to accelerate various kernel-related operations. These files do not need to be packaged installed for the system to operate,

[Bug 1325713] CurrentDmesg.txt

apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1325713/+attachment/4124375/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325713

[Bug 1325713] ProcEnviron.txt

apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1325713/+attachment/4124378/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325713

[Bug 1325713] UdevLog.txt

apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1325713/+attachment/4124382/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325713 Title:

[Bug 1325713] UdevDb.txt

apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1325713/+attachment/4124381/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325713 Title:

[Bug 1325713] ProcModules.txt

apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1325713/+attachment/4124380/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325713

[Bug 1325713] ProcInterrupts.txt

apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1325713/+attachment/4124379/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1325713] WifiSyslog.txt

apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1325713/+attachment/4124383/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 320638] Re: hot-add/remove in mixed (IDE/SATA/USB/SD-card/...) RAIDs with device mapper on top = data corruption (bio too big device md0 (248 240))

The resolution of fix released is incorrect: the kernel bug is still present. The debian bug was closed due to age rather due to being fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/320638

[Bug 1272039] Re: pmmgr eating CPU, continuously logging errors to pmmgr.log

The problem is that the /var/log/pcp/pmmgr directory is not created with proper permissions. Run # chown pcp:pcp /var/log/pcp/pmmgr and it will start working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1286865] [NEW] systemtap build of signals script fails

Hi - /tmp/stapXgPFfW/stap_d2a2e82b4e48884fc1a41654236e4050_17396_src.c:1375:16: error: incompatible types when assigning to type ‘int64_t’ from type ‘kuid_t’ STAP_RETVALUE = current_uid(); ^ [...] Please see upstream commits c91d2e7cc99 and 0d135d775e. - FChE -- You

[Bug 1237390] Re: stap fails with 3.8 kernel in precise

This problem was fixed in upstream systemtap in commit e14ac0e274c back in Apr. 2012, and included in subsequent releases 1.8, 2.0, 2.1, 2.2, and 2.3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1203590] Re: [MIR] systemtap

Seth, the lttng-ust development bits don't require systemtap as a whole, but the sys/sdt.h header file. (Systemtap is not for only kernel instrumentation these days, by the way; with dyninst can be used pure-userspace.) -- You received this bug notification because you are a member of Ubuntu

[Bug 1075772] Re: stap fails with: error: implicit declaration of function ‘unregister_uprobe’

I believe this problem was fixed back in version 1.8, as well as the current version of 2.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075772 Title: stap fails with: error: implicit

[Bug 832868] Re: systemtap version 1.4-1ubuntu1 failed to build in oneiric

Upstream commit 5d8a0a fixes this problem. It is included in stap version 1.5 and 1.6. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/832868 Title: systemtap version 1.4-1ubuntu1 failed to build in

[Bug 815944] Re: systemtap on Oneiric breaks because of kernel commit 449a66fd1fa75d36dca917704827c40c8f416bca

Fixed in systemtap upstream; also in release 1.6. commit 0bbb80098decc9c4c43a1800538007d86b600bba Author: Josh Stone jist...@redhat.com Date: Tue Jun 7 11:23:13 2011 -0700 stapconf: Conditionalize stacktrace_ops.warning{,_symbol} -- You received this bug notification because you are a

[Bug 803549] Re: Error using tapset functions, i.e. euid()

This may be related to upstream commit: commit 6899576f99ddd612520f7cdb4987155fad27bc6e Author: Frank Ch. Eigler f...@redhat.com Date: Thu May 12 19:53:30 2011 -0400 runtime/autoconf: gcc 4.6 fix false -Werror positives Upstream release 1.6 includes this and many other possibly

[Bug 669641] Re: systemtap fails to discover installed debug modules

Ritesh, can you provide a pointer to the details? -- systemtap fails to discover installed debug modules https://bugs.launchpad.net/bugs/669641 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 345960] Re: No Poulsbo Support in Jaunty

lspci -vvn for a Fujitsu Lifebook U820 with the same graphics chip: https://bugs.launchpad.net/bugs/314175 -- No Poulsbo Support in Jaunty https://bugs.launchpad.net/bugs/345960 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 244315] Re: linux-image-debug should create a symlink

It may make sense to just move the vmlinux-FOO-debug file out of /boot and right into /lib/modules/`uname -r`/vmlinux, since /boot is typically space-constrained anyway. -- linux-image-debug should create a symlink https://bugs.launchpad.net/bugs/244315 You received this bug notification

[Bug 106957] Re: Systemtap should require kernel debug information

Miek, it is possible that this is a systemtap or kernel problem (in which case we'd appreciate hearing more details about the crash - see http://sourceware.org/systemtap/wiki/HowToReportBugs). But it is also possible that your rebuilt kernel does not exactly match the one you're *running*. This