Opened 12 years ago

Closed 11 years ago

#1632 closed enhancement (fixed)

Extended syslog capabilities in KDL

Reported by: pieterpan Owned by: axeld
Priority: low Milestone: Unscheduled
Component: System/Kernel Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Quite often it is not possible to do serial debugging of the kernel (new laptop, no serial port, etc). At the same time, sometimes the syslog is not saved to the harddrive, while for example AHCI is being worked on.

In those times it would be very useful to see all the debug output that scrolls by so quickly. I have 2 requests: 1) Implement a wait-for-next-page feature (see a diff for ticket 1444) Perhaps this can be set in the kernel driver file, or at the boot menu. 2) Actually store the syslog in a buffer and add a KDL command to scroll back into the syslog. (nicer solution, takes a bit more work)

The need for 2 is actually less if 1 is implemented, but still it would be nice to be able to go back and forth and take pictures of the screen.

Attachments (1)

blue_screen.diff (508 bytes ) - added by jackburton 12 years ago.
Make debug output wait for ENTER each time screen page is full (from ticket #1444)

Download all attachments as: .zip

Change History (5)

by jackburton, 12 years ago

Attachment: blue_screen.diff added

Make debug output wait for ENTER each time screen page is full (from ticket #1444)

comment:1 by jackburton, 12 years ago

1 is done. 2 should be too, right ?

comment:2 by axeld, 12 years ago

Milestone: R1Unscheduled
Priority: normallow
  1. is not implemented - what we have added to the kernel are additional tracing capabilities unrelated to the syslog mechanism. It might still be helpful to have better syslog support in the kernel, especially because the tracing is a compile time option.

Anyway, it's at least not really urgent anymore :-)

comment:3 by PieterPanman, 11 years ago

I suppose hrev26684 fixed 2), so this ticket can be closed?

comment:4 by axeld, 11 years ago

Resolution: fixed
Status: newclosed

Indeed, thanks for the note!

Note: See TracTickets for help on using tickets.