On 08/03/2015 03:21 PM, Marcel Moolenaar wrote:
On Aug 3, 2015, at 12:59 PM, Eric Badger eric_bad...@dell.com wrote:
Hi there,
Since r226435, output from kernel printf/log functions is not appended to the message
buffer when in ddb. The commit message doesn't call this out specifically;
On 8/4/15 4:21 AM, Marcel Moolenaar wrote:
On Aug 3, 2015, at 12:59 PM, Eric Badger eric_bad...@dell.com wrote:
Hi there,
Since r226435, output from kernel printf/log functions is not appended to the message
buffer when in ddb. The commit message doesn't call this out specifically; instead it
On 8/4/15 11:36 AM, Julian Elischer wrote:
On 8/4/15 4:21 AM, Marcel Moolenaar wrote:
On Aug 3, 2015, at 12:59 PM, Eric Badger eric_bad...@dell.com
wrote:
Hi there,
Since r226435, output from kernel printf/log functions is not
appended to the message buffer when in ddb. The commit message
On Aug 3, 2015, at 12:59 PM, Eric Badger eric_bad...@dell.com wrote:
Hi there,
Since r226435, output from kernel printf/log functions is not appended to the
message buffer when in ddb. The commit message doesn't call this out
specifically; instead it appears to have been to address
Hi there,
Since r226435, output from kernel printf/log functions is not appended
to the message buffer when in ddb. The commit message doesn't call this
out specifically; instead it appears to have been to address double
printing to the console while in ddb. I noticed this because a ddb
