All of lore.kernel.org
 help / color / mirror / Atom feed
From: "werner" <w.landgraf@ru.ru>
To: akpm@linux-foundation.org, gregkh@suse.de, mingo@elte.hu,
	tj@kernel.org, randy.dunlap@oracle.com,
	linux-scsi@vger.kernel.org,
	James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: 2.6.39-rc3-git3 problem
Date: Thu, 14 Apr 2011 18:07:56 -0400	[thread overview]
Message-ID: <web-505236688@zbackend1.aha.ru> (raw)

The problem occurs since 2.6.39-rc1 . I reported it at 
that time, but the kernel mailing list very likely put my 
e-mail on spam so that it didn't appear. In another 
reclamation, by a mistake, I wrote 2.6.36-rc1 rather than 
2.6.39-rc1 .

If one starts the computer with text mode, then it crashs 
also, but after very long time, appr. 20-40 min after 
booting.

I on my server / main computer using the fbdev driver, for 
testing out this problem also vesa.   With both it crashs 
short after starting X .

One time when I started it on a laptop, then during the 
boot time, text mode, if the screen switchs to another 
text mode, then the text became very small, 1 cm, on the 
top of the screen, several times side-on-side, so that one 
couldnt read it.  Then I waited and logged in, then I 
started startx  (normally, it goes in grafic mode 
automatically, but at that time not).  Then the grafic 
started normally, but after some 2 min. it crashed.

If the crash occurs in the grafic mode, then it switches 
instantly to the text screen, and the error message is 
visible in text-mode, as visible in the foto.

I started the computer after a crash from an USB key, for 
not overwrite dmesg. But, in none of the message files is 
any message related to the crash.

In  order not to overwrite old dmesg files, it should be 
programmed into the kernel, that dmesg get any suffix, for 
example a random number, or date-time.

I hope that informations are helpful to fix this.

If someone fix it, then it can send to me as a normal 
patch, with the kernel number, and any git number (like 
the normal git files / kernel gits), because then I can 
apply the patch and compile the kernel with my normal 
kernel-compiling script.

W.Landgraf

Linux SYS
---
Professional hosting for everyone - http://www.host.ru

                 reply	other threads:[~2011-04-14 23:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-505236688@zbackend1.aha.ru \
    --to=w.landgraf@ru.ru \
    --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 \
    /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.