linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sergei S." <bender.rodriguez@open.by>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-fbdev-devel@lists.sourceforge.net,
	bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 12712] New: s2disk hangs with nvidiafb
Date: Sun, 15 Feb 2009 23:11:26 +0200	[thread overview]
Message-ID: <web-45680874@post.open.by> (raw)
In-Reply-To: <20090215111720.6860a225.akpm@linux-foundation.org>

Sun, 15 Feb 2009 11:17:20 -0800
  Andrew Morton <akpm@linux-foundation.org> wrote:

Hello.

> 
> (switched to email.  Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
> 
> On Sun, 15 Feb 2009 09:41:11 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> 
>> http://bugzilla.kernel.org/show_bug.cgi?id=12712
>> 
>>            Summary: s2disk hangs with nvidiafb
>>            Product: Drivers
>>            Version: 2.5
>>      KernelVersion: 2.6.29-rc5
>>           Platform: All
>>         OS/Version: Linux
>>               Tree: Mainline
>>             Status: NEW
>>           Severity: high
>>           Priority: P1
>>          Component: Video(AGP)
>>         AssignedTo: airlied@linux.ie
>>         ReportedBy: bender.rodriguez@open.by
> 
> This is an fbdev problem, I guess.  I'll reassign the report.

OK.
(This is my first bug-report)


> 
>> 
>> Latest working kernel version:2.6.29-rc5
>> Earliest failing kernel version:not tested
> 
> I assume what you mean here is that 2.6.29-rc5 fails, and that you're
> not aware of any earlier kernel version which did not fail.
> 

I've tested
2.6.27-14, 2.6.29-rc4 (git-5, git-7), 2.6.29-rc5

all of them fails to s2disk with nvidiafb.

dmesg | grep buf
[    1.651258] Console: switching to colour frame buffer device 160x50
[    1.652466] nvidiafb: PCI nVidia NV1d framebuffer (64MB @ 0xC0000000)
[    1.652846] vesafb: framebuffer at 0xc0000000, mapped to 0xfd980000, using
6144k, total 131072k
[    1.653320] fb1: VESA VGA frame buffer device


s2disk works ok with:
dmesg | grep buf
[    0.802424] vesafb: framebuffer at 0xc0000000, mapped to 0xf8080000, using
6144k, total 131072k
[    0.862236] Console: switching to colour frame buffer device 128x48
[    0.922487] fb0: VESA VGA frame buffer device


you can download my .config here:
  http://bugzilla.kernel.org/attachment.cgi?id=20255&action=view



> 
>> Distribution:debian lenny
>> Hardware Environment:asus f3jc
>> Software Environment:
>> Problem Description: s2disk hangs before switching to console ("s2disk:
>> Snapshotting system" message ->REISUB) with nvidiafb.
>> 
>> Device Drivers -> Graphics support -> Support for frame buffer devices -> [*]
>> nVidia Framebuffer Support
>> dmesg.0 | grep buf
>> [    1.658735] Console: switching to colour frame buffer device 160x50
>> [    1.659929] nvidiafb: PCI nVidia NV1d framebuffer (64MB @ 0xC0000000)
>> [    1.660386] vesafb: framebuffer at 0xc0000000, mapped to 0xfd180000, using
>> 6144k, total 131072k
>> [    1.660825] fb1: VESA VGA frame buffer device
>> 
>> hangs.
>> 
>> Device Drivers -> Graphics support -> Support for frame buffer devices -> []
>> nVidia Framebuffer Support
>> 
>> dmesg | grep buf
>> [    0.802424] vesafb: framebuffer at 0xc0000000, mapped to 0xf8080000, using
>> 6144k, total 131072k
>> [    0.862236] Console: switching to colour frame buffer device 128x48
>> [    0.922487] fb0: VESA VGA frame buffer device
>> 
>> in this case everything works OK.
>> 
> 

----------------------------------------------------
...а теперь оплатить широкополосный доступ
в сеть »нтернет ByFly можно электронными деньгами EasyPay.
http://www.easypay.by/

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel

  reply	other threads:[~2009-02-15 22:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-12712-10286@http.bugzilla.kernel.org/>
2009-02-15 19:17 ` [Bugme-new] [Bug 12712] New: s2disk hangs with nvidiafb Andrew Morton
2009-02-15 21:11   ` Sergei S. [this message]
2009-02-16 19:59     ` Krzysztof Helt
2009-02-16 22:56       ` Sergei S.
2009-02-21 23:23 Sergei S.
  -- strict thread matches above, loose matches on Subject: below --
2009-02-22 10:47 Sergei S.
     [not found] ` <20090222150504.a77dc9b3.krzysztof.h1@poczta.fm>
2009-02-23  8:24   ` Bender aka Sergei S.
2009-02-27  7:55   ` Bender aka Sergei S.

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-45680874@post.open.by \
    --to=bender.rodriguez@open.by \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).