Information: Forum is in read-only mode
For details and other support options see

extracting kernel warnings

This is the place for developers to discuss bugs, new features and everything else about code changes.

Moderator: alorbach

Google Ads

extracting kernel warnings

Postby semenzato » Wed Apr 17, 2013 10:37 pm


I would like to extract the complete text of Linux kernel warnings as they are logged, for instance:

[117959.231085] ------------[ cut here ]------------
[117959.231100] WARNING: at /mnt/host/source/src/third_party/kernel/files/drivers/gpu/drm/i915/intel_dp.c:351 intel_dp_check_edp+0x6b/0xb9()
[117959.231113] Hardware name: Link
[117959.231117] eDP powered off while attempting aux channel communication.
[117959.231240] Pid: 10508, comm: X Tainted: G WC 3.4.0 #1
[117959.231247] Call Trace:
[117959.231393] [<ffffffff810d3117>] ? fsnotify_access+0x58/0x60
[117959.231402] [<ffffffff810d3791>] ? vfs_read+0xad/0xd7
[117959.231411] [<ffffffff810e175f>] sys_ioctl+0x56/0x7b
[117959.231420] [<ffffffff810d37fe>] ? sys_read+0x43/0x73
[117959.231431] [<ffffffff8146b7d2>] system_call_fastpath+0x16/0x1b
[117959.231439] ---[ end trace f16822cad7406ced ]---

I can do this pretty easily with a daemon that watches for changes to /var/log/messages (via inotify) and parses them. But I am wondering if an rsyslogd-based solution wouldn't be simpler. Except I don't see an obvious way. I could well be wrong, but the parser module only talks about parsing single "messages", which I am guessing are isolated lines. I considered writing my own loadable module based on imklog.c, but that seems harder than a separate parser (written for flex, for instance).

If anybody has advice on this, it will be very welcome.

Posts: 1
Joined: Wed Apr 17, 2013 10:28 pm

Urgent Question?

  • Pulling out your Hair?
  • Wasting Time and Money?
  • Deadline Approaching?

Google Ads

Return to Developer's Corner

Who is online

Users browsing this forum: No registered users and 0 guests