From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 78530] Memory corruption on Lenovo t440p with runpm
Date: Tue, 02 Sep 2014 11:34:20 +0000 [thread overview]
Message-ID: <bug-78530-8800-ve3MYDXqu4@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-78530-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2309 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=78530
--- Comment #12 from Dmitry Nezhevenko <dion-OaY5VPdsfhrsG83rWm+8vg@public.gmane.org> ---
Hi,
I also have affected T440p machine that corrupts everything once runtime PM is
enabled or after calling ACPI method to resume card.
It was stated in bumblebee github thread, that adding "memmap=99G$0x100000000"
to kernel fixes issues on affected systems.
My case looks a bit interesting because I have only 4GB of RAM right now, so
disabling everything above 4GB should not change behavior. But it changes!
Adding memmap= magic fixes issue for me.
I've tried to compare /proc/iomem with and without boot options and found one
difference. Once booted with memmap=99G$0x100000000 I'm getting one large
reserved region:
bceff000-18ffffffff : reserved
bda00000-bf9fffff : Graphics Stolen Memory
bfa00000-febfffff : PCI Bus 0000:00
c0000000-d1ffffff : PCI Bus 0000:02
c0000000-cfffffff : 0000:02:00.0
d0000000-d1ffffff : 0000:02:00.0
e0000000-efffffff : 0000:00:02.0
...
All PCI devices are inside this one large region. But if I boot with default
options, iomem is different:
bceff000-bf9fffff : reserved
bda00000-bf9fffff : Graphics Stolen Memory
bfa00000-febfffff : PCI Bus 0000:00
c0000000-d1ffffff : PCI Bus 0000:02
c0000000-cfffffff : 0000:02:00.0
d0000000-d1ffffff : 0000:02:00.0
e0000000-efffffff : 0000:00:02.0
f0000000-f0ffffff : PCI Bus 0000:02
f0000000-f0ffffff : 0000:02:00.0
f1000000-f13fffff : 0000:00:02.0
f1400000-f14fffff : PCI Bus 0000:04
So now this reserved region starting at bceff000 covers all PCI devices.
[ I'm attaching both iomap files ]
To check this I've tried to explicitly reserve whole region by booting with
memmap=1100M$0xbfa00000 parameter. And got pretty similar to mem"map=99G"
iomap. But system still crashes after runtime pm.
I also was able to capture PCI configuration space for NVIDIA card from Win8
(where everything works). So I can confirm that after acpi_call windows also
shows just 0xFF bytes. But once resumed, it's a bit different from linux. Both
files attached.
Any ideas? Maybe card is somehow misconfigured?
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3087 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2014-09-02 11:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 15:22 [Bug 78530] New: Memory corruption on Lenovo t440p with runpm bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-78530-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-05-10 18:23 ` [Bug 78530] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-10 18:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-10 18:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-10 18:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-10 18:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-10 18:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-10 18:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-10 19:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-10 14:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-10 18:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-18 21:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-02 11:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-09-02 11:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-02 11:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-02 11:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-02 11:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-02 11:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-02 11:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-02 11:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-11-04 8:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-07 13:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-24 14:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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=bug-78530-8800-ve3MYDXqu4@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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