OK - so after a bit more digging into things (and a poke by Mike) - I think
most of the stuff already exists.
Normal run time issues:
--
- MTD_OOPS - on 2007-06-28 this was added to Linus's tree:
http://lkml.org/lkml/2007/6/18/234
CONFIG_MTD_OOPS
tristate
On Fri, Jun 26, 2009 at 10:39:50AM -0400, Robin Getz wrote:
OK - so after a bit more digging into things (and a poke by Mike) - I think
most of the stuff already exists.
Normal run time issues:
--
- MTD_OOPS - on 2007-06-28 this was added to Linus's tree:
On Fri, Jun 26, 2009 at 13:42, David VomLehn wrote:
On Fri, Jun 26, 2009 at 10:39:50AM -0400, Robin Getz wrote:
OK - so after a bit more digging into things (and a poke by Mike) - I think
most of the stuff already exists.
Normal run time issues:
--
- MTD_OOPS - on
On Fri 26 Jun 2009 13:42, David VomLehn pondered:
On Fri, Jun 26, 2009 at 10:39:50AM -0400, Robin Getz wrote:
OK - so after a bit more digging into things (and a poke by Mike) - I
think
most of the stuff already exists.
Normal run time issues:
--
- MTD_OOPS
On Sat 13 Jun 2009 14:59, Wolfgang Denk pondered:
Dear Russell King,
In message 20090613102642.gb7...@flint.arm.linux.org.uk you wrote:
The other way I've seen people read out crash messages is using a
debugger to dump the kernel's log buffer directly. That seems to work
as well as
Dear Russell King,
In message 20090613102642.gb7...@flint.arm.linux.org.uk you wrote:
The other way I've seen people read out crash messages is using a
debugger to dump the kernel's log buffer directly. That seems to work
as well as any other method, and has the advantage that it doesn't
On Wed, Jun 10, 2009 at 09:26:40PM -0400, Robin Getz wrote:
On 17 Oct 2007, after much discussion and debate, Mike added add two new
functions for reading the kernel log buffer (from kernel space).
On Thu, Jun 11, 2009 at 02:52:38PM -0400, Robin Getz wrote:
On Thu 11 Jun 2009 13:53, David VomLehn pondered:
On Wed, Jun 10, 2009 at 09:26:40PM -0400, Robin Getz wrote:
...
Our kernel does crash, so we have to do this. I had submitted a patch a
while ago that tweaks emit_log_char, but this
On Thu, Jun 11, 2009 at 11:22:57AM -0700, Tim Bird wrote:
David VomLehn wrote:
Our kernel does crash, so we have to do this. I had submitted a patch a
while ago that tweaks emit_log_char, but this was bounced, reasonably,
because it would be interferring with the great majority of people
On 6/11/09 11:52 AM, Robin Getz wrote:
On Thu 11 Jun 2009 13:53, David VomLehn pondered:
On Wed, Jun 10, 2009 at 09:26:40PM -0400, Robin Getz wrote:
I would be interested in Paul and Russell - how have you solved this
issue? (Or do your kernel's never crash? :)
Our kernel does crash, so we
On Thu, Jun 11, 2009 at 13:53, David VomLehn wrote:
On Wed, Jun 10, 2009 at 09:26:40PM -0400, Robin Getz wrote:
On 17 Oct 2007, after much discussion and debate, Mike added add two new
functions for reading the kernel log buffer (from kernel space).
Dear David VomLehn,
In message 20090612003302.ga23...@cuplxvomd02.corp.sa.net you wrote:
However, the value and what's being proposed here and what I and others
proposed--at least in the embedded kingdom--seems high and the features and
implementation needn't be mutually exclusive.
I
12 matches
Mail list logo
