mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Igor Podlesny" <for.poige+linux@gmail.com>
To: "Willy Tarreau" <w@1wt.eu>
Cc: linux-kernel@vger.kernel.org
Subject: > I even didn't have a backtrace.
Date: Mon, 29 Dec 2008 14:03:09 +0700	[thread overview]
Message-ID: <43d009740812282303r2015e6beyc2dae4c26d6aa686@mail.gmail.com> (raw)

2008/12/29 Igor Podlesny <for.poige+linux@gmail.com>:
> 2008/12/29 Willy Tarreau <w@1wt.eu>:
>> On Mon, Dec 29, 2008 at 12:39:55PM +0700, Igor Podlesny wrote:
> [...]
>> Well, I won't say that I find them 100% rock solid, but you seem to be
>> able to reproduce a lot of serious issues. Have you filed bug reports
>> to get them fixed ? You cannot expect people to fix bugs they're not
>> aware of !
>
>        I even didn't have a backtrace. What's to fill in? "It just crashed 2
> times, Dear Bugzilla"? :-)
>
	BTW, I wonder -- can the kernel store crash related information (if
any) in RAM, at certain addresses, so it can survive warm reboot and
get displayed "in dmesg" on the next boot?

-- 
End of message. Next message?

             reply	other threads:[~2008-12-29  7:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29  7:03 Igor Podlesny [this message]
2008-12-30  2:17 ` Daniel Barkalow
     [not found] <fa.49EGxNgCILq/XfuGCazHZV8OJlg@ifi.uio.no>
     [not found] ` <4958C2CE.7060206@yahoo.com>
2008-12-29 12:52   ` Igor Podlesny
     [not found] <fa.q3E31Fk9IOYkDJ38/mQp9Iyp2TI@ifi.uio.no>
     [not found] ` <fa.qMGHzuTz1nuoHKywmH/aLmriclo@ifi.uio.no>
     [not found]   ` <fa.LbTTdeLVGfaCxioVgNMO13Libio@ifi.uio.no>
2008-12-29 12:59     ` Sitsofe Wheeler
2008-12-29 14:07       ` Matthew Garrett
     [not found] <bOpT3-2LN-13@gated-at.bofh.it>
     [not found] ` <bOpT3-2LN-15@gated-at.bofh.it>
     [not found]   ` <bOpT3-2LN-11@gated-at.bofh.it>
2008-12-29 19:24     ` Bodo Eggert
2008-12-29 23:33       ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43d009740812282303r2015e6beyc2dae4c26d6aa686@mail.gmail.com \
    --to=for.poige+linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w@1wt.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®