I used this to reliably and conveniently produce kernel messages and
verify that dmesg has new stuff:
$ sudo dmesg -c
$ sudo /etc/init.d/apparmor restart
Reloading AppArmor profiles : done.
$ sudo dmesg -c
[68804.887693] type=1505 audit(1218098412.816:494): operation="profile_replace"
name="/usr/share/gdm/guest-session/Xsession" name2="default" pid=27662
[68805.155782] type=1505 audit(1218098413.084:495): operation="profile_replace"
name="/usr/lib/cups/backend/cups-pdf" name2="default" pid=27667
[68805.156318] type=1505 audit(1218098413.084:496): operation="profile_replace"
name="/usr/sbin/cupsd" name2="default" pid=27667
I started this in the background before:
sudo /etc/init.d/klogd stop
sudo tail -f /proc/kmsg
no output from the latter
printk looks correct to me:
$ cat /proc/sys/kernel/printk
4 4 1 7
** Changed in: linux (Ubuntu Intrepid)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Confirmed => Triaged
--
No messages in /proc/kmsg
https://bugs.launchpad.net/bugs/255635
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
