Bug 666990
| Summary: | abrt doesn't include enough debugging info when filing kernel reports | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | James M. Leddy <james.leddy> |
| Component: | abrt | Assignee: | Jiri Moskovcak <jmoskovc> |
| Status: | CLOSED NOTABUG | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0 | CC: | dfediuck, dvlasenk, gavin, gborsuk, james.leddy, kklic, npajkovs, rvokal |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 666264 | Environment: | |
| Last Closed: | 2011-01-25 17:05:48 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 666264 | ||
| Bug Blocks: | |||
|
Description
James M. Leddy
2011-01-03 23:28:12 UTC
see bug #666264 comment #3 The "Delta way too big!" message is not included in the report. If customers saw this part of the log, they may be able to more easily piece together what happened. I assume dmesg looks like this: Delta way too big! 1234567890 ts=9876543211 write stamp = 123456789 ------------[ cut here ]------------ WARNING: at kernel/trace/ring_buffer.c:1987 rb_reserve_next_event+0x2b2/0x350() (Tainted: G W ---------------- ) Hardware name: 2241B36 ... ... ... More generally, WARN_ON(cond) will result in this log: prev msgs prev msgs prev msgs ------------[ cut here ]------------ WARNING: at path/to/file.c:1234 func+0xOFS/0xLEN() ... ... ... We have a problem here: we do not know whether "prev msgs" contain any useful information pertaining to this WARN_ON() - and if they do, how many lines? It is easy to change abrt so that it grabs N previous lines above "WARNING: at" line. The question is, how big N should be? Good question. I suppose I could try to replicate the results that Dave has seen and get back to you. (In reply to comment #3) > I assume dmesg looks like this: > > > Delta way too big! 1234567890 ts=9876543211 write stamp = 123456789 > ------------[ cut here ]------------ > WARNING: at kernel/trace/ring_buffer.c:1987 rb_reserve_next_event+0x2b2/0x350() > (Tainted: G W ---------------- ) > Hardware name: 2241B36 > ... > ... > ... Good question. That's accurate according to this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/458957 > > > More generally, WARN_ON(cond) will result in this log: > > prev msgs > prev msgs > prev msgs > ------------[ cut here ]------------ > WARNING: at path/to/file.c:1234 func+0xOFS/0xLEN() > ... > ... > ... > > > We have a problem here: we do not know whether "prev msgs" contain any useful > information pertaining to this WARN_ON() - and if they do, how many lines? > > It is easy to change abrt so that it grabs N previous lines above "WARNING: at" > line. The question is, how big N should be? Don't know. Presumably interesting stuff is only at warning level. And if "prev msgs" were 10 minutes ago, they probably aren't relevant. So ideal solution is to filter around time of WARNING: and log level, if that's possible. Semi related, Please include the --[ cut here ]-- and end trace uuid. Several tools, including abrt ko plugin, use these markers. I'm of the belief that this is a bug in the kernel and should be fixed as it crops up. You can see a better way of using WARN_ON in bug 672526 where the message follows the --[please cut here]-- line. |