From: Nickolay <nickolay@protei.ru>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: stable oops
Date: Tue, 13 Jun 2006 16:19:17 +0400 [thread overview]
Message-ID: <448EAD45.1080403@protei.ru> (raw)
In-Reply-To: <1150194607.5257.317.camel@localhost.localdomain>
Thomas Gleixner wrote:
>On Tue, 2006-06-13 at 14:23 +0400, Nickolay wrote:
>
>
>>Hello.
>>This is bad oops, which appeared every boot of my system.
>>Kernel: 2.6.16.1(stock kernel, w/o any patches).
>>
>>
>>
>
>Can you please put a binary dump of your flash somewhere for download ?
>
> tglx
>
>
>
>
No, sorry, because after some manupulation on the flash, the problem is
go awayed.
But in the future, i can do that, ofcourse.
--
Николай Виноградов
Системный администратор
ООО "НТЦ ПРОТЕЙ"
Россия, 194044, Санкт-Петербург
пр. Большой Сампсониевский д.60 лит.А
тел: (812)449-47-27(5182)
next prev parent reply other threads:[~2006-06-13 12:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 10:23 stable oops Nickolay
2006-06-13 10:30 ` Thomas Gleixner
2006-06-13 12:19 ` Nickolay [this message]
2006-06-13 12:54 ` stable oops(not wrapped) Nickolay
2006-06-13 13:04 ` stable oops David Woodhouse
2006-06-13 14:04 ` Nickolay
2006-06-17 23:10 ` David Woodhouse
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=448EAD45.1080403@protei.ru \
--to=nickolay@protei.ru \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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