| Summary: | sys-apps/util-linux-2.20: dmesg command stops before two consecutive 'newline' in the kernel log buffer | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Maxime Gervais <maxime> |
| Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | mads |
| Priority: | Normal | ||
| Version: | 10.0 | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info
Test module Makefile for test module |
||
Created attachment 288513 [details]
emerge --info
Created attachment 288515 [details]
Test module
Created attachment 288517 [details]
Makefile for test module
I've also noticed that dmesg after a while stops showing new output after updating util-linux... nice that you found out what was causing it. easy to reproduce by doing: # dmesg -c >/dev/null # printf 'one\ntwo\n\nthree\nfour\n' > /dev/kmsg # dmesg latest upstream dmesg has this already fixed should be all set now in the tree; thanks for the report! Commit message: Add fixes from upstream for dmesg stopping with blank newlines http://sources.gentoo.org/sys-apps/util-linux/files/util-linux-2.20-dmesg-newline.patch?rev=1.1 http://sources.gentoo.org/sys-apps/util-linux/files/util-linux-2.20-sysfs-init.patch?rev=1.1 http://sources.gentoo.org/sys-apps/util-linux/util-linux-2.20-r1.ebuild?rev=1.1 |
When I run the dmesg command, the output stops (no error, output code 0) after these lines : md/raid0:md127: md_size is 2500516864 sectors. ******* md127 configuration ********* zone0=[sda1/sdb1/] zone offset=0kb device offset=0kb size=1250258432kb ********************************** This is caused by the following line in the kernel tree (drivers/md/raid0.c:77) that has two consecutive '\n' at the end: printk(KERN_INFO "**********************************\n\n"); - Raw dmesg output (dmesg -r) works fine. - sys-apps/util-linux-2.19.1-r1 works fine. Reproducible: Always Steps to Reproduce: 1. Clear the kernel log buffer (dmesg -C) 1. Load the test module 2. Run dmesg Actual Results: dmesg output: foo Expected Results: dmesg output: foo bar Kernel: sys-kernel/gentoo-sources-3.0.4-r1