On Wed, 22 Jun 2016 22:14:19 +0200, Alexander Bluhm wrote: > When doing usb debugging with a lot of kernel printfs, the dmesg > buffer can overflow easily. It is annoying that you don't notice > this. Then it is hard to correlate the messages. > > So to make clear what happens, I would like to write such a message > to syslogd: > Jun 22 21:58:16 t430s /bsd: usbd_start_next: pipe=0xffff8000003cf > Jun 22 21:58:16 t430s /bsd: klog: dropped 75602 bytes, message buffer full > Jun 22 21:58:16 t430s /bsd: b_transfer_complete: repeat=0 new head=0x0 > > This also gets me closer to my goal of reliable logging. > > Do we want this feature?
I think so. Ultimately it would be nice to queue up messages in the kernel for later delivery but for now just logging that messages were dropped is an improvement. - todd
