From: "Sergei S." <bender.rodriguez@open.by>
To: Krzysztof Helt <krzysztof.h1@poczta.fm>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-fbdev-devel@lists.sourceforge.net,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 12712] New: s2disk hangs with nvidiafb
Date: Tue, 17 Feb 2009 00:56:48 +0200 [thread overview]
Message-ID: <web-45816320@post.open.by> (raw)
In-Reply-To: <20090216205947.d024cf25.krzysztof.h1@poczta.fm>
Mon, 16 Feb 2009 20:59:47 +0100
Krzysztof Helt <krzysztof.h1@poczta.fm> wrote:
Hello.
> On Sun, 15 Feb 2009 23:11:26 +0200
> "Sergei S." <bender.rodriguez@open.by> wrote:
>>
>> 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
>>
>
> Interesting, you have two framebuffers running on a single card. Does the s2disk
> works for you if you select nvidiafb and turn off vesa framebuffer?
>
2.6.29-rc5 (vesafb, no nvidiafb)
dmesg | grep buf
[ 0.779860] vesafb: framebuffer at 0xc0000000, mapped to 0xf8080000, using 6144k,
total 131072k
[ 0.839688] Console: switching to colour frame buffer device 128x48
[ 0.899922] fb0: VESA VGA frame buffer device
s2disk works ok.
2.6.29-rc5 (no vesafb, nvidiafb)
dmesg | grep buf
[ 1.556692] Console: switching to colour frame buffer device 160x50
[ 1.558905] nvidiafb: PCI nVidia NV1d framebuffer (64MB @ 0xC0000000)
s2disk doesn't work with nvidiafb.
> Can you post the same lines for the latest working kernel with both vesa and nvidia
> framebuffers selected?
>
Sure.
[!!!Copy-paste from prev. posts]
working kernel with vesafb and nvidifb selected (s2disk fails).
2.6.29-rc5
dmesg | 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
2.6.27-14
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
[!!] current build (2.6.29-rc5 vesafb, nvidiafb)
dmesg | grep buf
[ 0.944049] Console: switching to colour frame buffer device 160x50
[ 0.945233] nvidiafb: PCI nVidia NV1d framebuffer (64MB @ 0xC0000000)
[ 0.945675] vesafb: framebuffer at 0xc0000000, mapped to 0xfd180000, using 6144k,
total 131072k
[ 0.946119] fb1: VESA VGA frame buffer device
s2disk fails.
Regards,
Sergey
> Regards,
> Krzysztof
>
>
> ----------------------------------------------------------------------
> Zostan mistrzem parkowania w Bombaju!
> Zagraj >> http://link.interia.pl/f204e
>
----------------------------------------------------
...а теперь оплатить широкополосный доступ
в сеть »нтернет 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
next prev parent reply other threads:[~2009-02-16 22:56 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.
2009-02-16 19:59 ` Krzysztof Helt
2009-02-16 22:56 ` Sergei S. [this message]
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-45816320@post.open.by \
--to=bender.rodriguez@open.by \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=krzysztof.h1@poczta.fm \
--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 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.