From: Jens Axboe <axboe@kernel.dk>
To: werner <w.landgraf@ru.ru>
Cc: James.Bottomley@HansenPartnership.com, mingo@elte.hu,
Andrew Morton <akpm@linux-foundation.org>,
gregkh@suse.de, tj@kernel.org, randy.dunlap@oracle.com,
linux-scsi@vger.kernel.org
Subject: Re: 2.6.39-rc3-git3 problem etc , reset-resistent problem
Date: Sat, 16 Apr 2011 22:38:40 +0200 [thread overview]
Message-ID: <4DA9FE50.6000303@kernel.dk> (raw)
In-Reply-To: <web-506106345@zbackend1.aha.ru>
On 2011-04-16 06:22, werner wrote:
>
>
> Pls see the enclosed screen foto.
>
> After the crashs of 2.6.39-rcX , which I already
> reclaimed, and after -rc3-git4 and the patch suggested me
> to try out, the computer in vesa grafic mode crashs
> quickly, in fbdev only after longer time. After this
> crash, on re-booting, happens early during the boot
> process a next kind of crash. This don't go away on
> reset nor on power off, i.e. booting
> 2.6.39-rc3-git4-patchs again, it repeats. Only after
> rebooting with 2.6.38.2 or another working kernel, one can
> booting again with 2.6.39-rc3-git4-patchs -- until after
> its next crash, when the same happens again.
>
> Some of these secondary crashs show a message: ata1:
> nv: stopping hardreset on occupied port, and after
> this the system attempts wrongly to understand the nv
> grafic card as a hard disc, and claims about read errors,
> until it crash.
>
> Some of these secondary crashs, instead, look like the
> enclosed foto, also understanding something wrongly as an
> ata1 device.
Any chance you can setup a network console or serial console and capture
all of those messages?
--
Jens Axboe
next prev parent reply other threads:[~2011-04-16 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 4:22 2.6.39-rc3-git3 problem etc , reset-resistent problem werner
2011-04-16 20:38 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-17 6:38 werner
2011-04-22 18:35 ` Tejun Heo
2011-04-22 20:44 ` werner
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=4DA9FE50.6000303@kernel.dk \
--to=axboe@kernel.dk \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=tj@kernel.org \
--cc=w.landgraf@ru.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.