public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir Elisseev" <vovan-Ev2gRJHyJ8g@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: 3.10.x - issues with nvidia proprietary drivers
Date: Wed, 07 Aug 2013 11:34:32 +0200	[thread overview]
Message-ID: <524d-52021480-5-10075740@166352631> (raw)

Hello,

I'm using bcache for a few weeks at the moment (started with kernel 3.10) and it works perfectly fine unless I use nvidia proprietary driver (tried 325.08 and 325.15). When nvidia kernel module is not blacklisted system can't be booted properly with X server: display hangs while loading display manager, but system is accessible via ssh and there's no error messages in the log files. The strange thing is that I can boot and start display manager if nvidia module is blacklisted and later loaded by xorg server. With this workaround I can login and everything works just as expected. However, when I try to logout the display goes black (keyboard doesn't works except SysRq keys), but system is accessible via ssh or somehow else. While system hangs in the way described above I can see following s
 uspicious things:
- the X server process is waiting for disk (status Ds+)
- it's not possible to kill the X server process (using any signal)

I'd appreciate if somebody would give any hits on how can I investigate this problem any further.

Thanks in advance,
Vlad.
 

             reply	other threads:[~2013-08-07  9:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07  9:34 Vladimir Elisseev [this message]
     [not found] <1375876717.81516.YahooMailAndroidMobile@web181504.mail.ne1.yahoo.com>
     [not found] ` <1375876717.81516.YahooMailAndroidMobile-XYahOdtEMNkbWpotXP+qY5OW+3bF1jUfVpNB7YpNyf8@public.gmane.org>
2013-08-07 12:02   ` 3.10.x - issues with nvidia proprietary drivers Vladimir Elisseev

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=524d-52021480-5-10075740@166352631 \
    --to=vovan-ev2grjhyj8g@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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