From: "werner" <w.landgraf@ru.ru>
To: axboe@kernel.dk, 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@vg
Subject: 2.6.39-rc3-git3 problem etc , reset-resistent problem
Date: Sun, 17 Apr 2011 02:38:58 -0400 [thread overview]
Message-ID: <web-506519881@zbackend1.aha.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
Enclosed pls find a screen foto of another crash with this
reset-resistent problem.
As said, after patching blk and scsi in 2.6.39-rc3-git4 as
someone suggested me to try out, happened crashs short or
longer time after booting, which caused a rather early
crash during subsequent boots, which don't go away even
after re-set or power-off, and occurs again and again with
2.6.39-rcX . This goes away only if I boot with 2.6.38.2
or .3 ; in this case, if after this I boot again with
2.6.39-rc3-git4+patches, then repeats the same, i.e. the
first time it crashs only after the end of booting, but
subsequently again in the early stage.
I think this is a khugepaged problem, or that the computer
wrongly interpretes the video card or anything else as an
scsi or blk device. At least subjectively, the sticking
after booting is very similar to the khugepaged problem
which I reclaimed during 2.6.38-rc1 (or was it .37-rc1 ),
and which then was corrected, but perhaps it wasn't
corrected really and now comes back.
W.Landgraf
---
Professional hosting for everyone - http://www.host.ru
[-- Attachment #2: Foto0050.jpg --]
[-- Type: image/jpeg, Size: 188550 bytes --]
next reply other threads:[~2011-04-17 6:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 6:38 werner [this message]
2011-04-22 18:35 ` 2.6.39-rc3-git3 problem etc , reset-resistent problem Tejun Heo
2011-04-22 20:44 ` werner
-- strict thread matches above, loose matches on Subject: below --
2011-04-16 4:22 werner
2011-04-16 20:38 ` Jens Axboe
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-506519881@zbackend1.aha.ru \
--to=w.landgraf@ru.ru \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=gregkh@suse.de \
--cc=linux-scsi@vg \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).