All of lore.kernel.org
 help / color / mirror / Atom feed
From: "werner" <w.landgraf@ru.ru>
To: James.Bottomley@HansenPartnership.com, mingo@elte.hu,
	Andrew Morton <akpm@linux-foundation.org>,
	werner <w.landgraf@ru.ru>,
	gregkh@suse.de, tj@kernel.org, randy.dunlap@oracle.comlin
Subject: 2.6.39-rc3-git3 problem   etc , reset-resistent problem
Date: Sat, 16 Apr 2011 00:22:00 -0400	[thread overview]
Message-ID: <web-506106345@zbackend1.aha.ru> (raw)

[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]



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.


I hope someone can find and correct that error.


W.Landgraf
---
Professional hosting for everyone - http://www.host.ru

[-- Attachment #2: Foto0049.jpg --]
[-- Type: image/jpeg, Size: 184750 bytes --]

             reply	other threads:[~2011-04-16  4:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-16  4:22 werner [this message]
2011-04-16 20:38 ` 2.6.39-rc3-git3 problem etc , reset-resistent problem Jens Axboe
  -- 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=web-506106345@zbackend1.aha.ru \
    --to=w.landgraf@ru.ru \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=mingo@elte.hu \
    --cc=randy.dunlap@oracle.comlin \
    --cc=tj@kernel.org \
    /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.