[Bug 345124] New: S3 failed on AMD SB600/SB700+RS690/RS780 platform

newer
[Bug 366515] New: natural keyboard...

older
[Bug 372815] New: Oops on Thinkpad...

bugzilla_noreply＠novell.com

30 Nov 2007 30 Nov '07

07:38

https://bugzilla.novell.com/show_bug.cgi?id=345124 Summary: S3 failed on AMD SB600/SB700+RS690/RS780 platform Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: henry.su@amd.com QAContact: qa@suse.de CC: shane.huang@amd.com Found By: System Test S3 suspends successfully,but it failed on resuming, the screen is black, and the system gets no response. I try the everything hinted on http://en.opensuse.org/S2ram and http://en.opensuse.org/Pm-utils, but got no lock. 1.boot with init=/bin/bash at the boot prompt into a minimal environment, get a kernel panic: /bin/bash: showopts: No such file or directory Kernel panic - not syncing: Attempted to kill init! 2.s2ram with the following variations does not work: s2ram -f -a 1 s2ram -f -a 2 s2ram -f -a 3 s2ram -f -p -m s2ram -f -p -s s2ram -f -m s2ram -f -s s2ram -f -p s2ram -f -a 1 -m s2ram -f -a 1 -s 3. add S2RAM_OPTS="--force --vbe_post","pm-suspend" and "pm-suspend --quirk-vbe-post" does not work. Note: S3 works fine on the same plaform with: 1. OpenSUSE10.1 and SLED/SLES10 (SP1), the command is "powersave -u"; configure the s2ram options in /etc/powersave/sleep as: SUSPEND2RAM_FORCE="yes" SUSPEND2RAM_VBE_POST="yes" 2. OpenSUSE10.2, the command is "s2ram -f -p"; Basically, "s2ram -f -p" should work for S3 on OpenSUSE10.3, but it failed.(maybe the graphics card was not POSTed from resuming, I change the graphics driver from fbdev to vesa) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date

bugzilla_noreply＠novell.com

30 Nov 30 Nov

07:40

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 henry su changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |henry.su@amd.com, libin.yang@amd.com Priority|P5 - None |P1 - Urgent -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:59

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124#c1 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.provo.novell.com |seife@novell.com --- Comment #1 from Thomas Renninger 2007-11-30 03:59:17 MST --- AFAIK you need to post us your dmidecode output. Seife will then whitelist this machine, so that the BIOS is posted automatically. There is a new ACPI BIOS interface that should tell the OS whether the video rom needs to be posted or not. I haven't seen any machine/BIOS implementing it yet. Could you just give it a short try and remove or comment out the one line in (BTW, does brightness switching work? ): install video /bin/true Then load the video module and attach the output of last lines (video module related) from /var/log/messages If it didn't before, do brightness buttons work now? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:59

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |henry.su@amd.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

12:57

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124#c2 Stefan Seyfried changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fseidel@novell.com, pavel@novell.com, | |seife@novell.com AssignedTo|seife@novell.com |kernel-maintainers@forge.provo.novell.com Status|NEEDINFO |NEW Info Provider|henry.su@amd.com | --- Comment #2 from Stefan Seyfried 2007-11-30 05:57:34 MST --- Thomas: It worked with 10.2, but no longer does with 10.3. => back to kernel for fixing. Henry, you need to put init=/bin/bash as the last parameter on the kernel commandline, then it will work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

14:40

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124#c3 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bk@novell.com Status|NEW |ASSIGNED --- Comment #3 from Thomas Renninger 2007-11-30 07:40:32 MST --- What kind of laptop is this? Is there a sony/thoshiba/asus/... or other vendor specific ACPI module loaded? If yes, can you try to blacklist it in /etc/modprobe.d/xy with e.g. install MODULE_NAME logger "Module xy blacklisted" and try again. Does it work without X started (e.g. "3" passed as boot parameter)? Can you still try out things suggested in the second half of comment #1. Do you have firewire cable to connect two laptops with each other? If yes you could debug this with firescope... Bernhard could advise which cable you'd need. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

22:20

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124#c7 Pavel Machek changed: What |Removed |Added ---------------------------------------------------------------------------- Group|novellonly | AssignedTo|kernel-maintainers@forge.provo.novell.com |pavel@novell.com Severity|Critical |Normal CC Accessible|1 |0 Reporter Accessible|1 |0 --- Comment #7 from Pavel Machek 2007-11-30 15:20:25 MST --- As this happens on production machines, too, it should not be secret. amd: For new machines, please fix the bios so that it works with s2ram -f -a 3 It is really easy; we just need video to be posted on both boot and s3 resume. cat2 system certainly does _not_ do the right thing. trenn: -p contains x86 emulator. It seems like emulator hit an instruction it could not deal with. stefan: if it worked in 10.2 and is broken in 10.3... that's bad. Can we play our usual "does it work with minimal drivers" and "bisect to search when it broke" tricks? Set severity to normal. Yes it is an ugly bug . But unless it is very widespread or unless we promised that it will work.... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

3 Dec 3 Dec

06:43

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124#c8 --- Comment #8 from henry su 2007-12-02 23:43:43 MST --- Created an attachment (id=185583) --> (https://bugzilla.novell.com/attachment.cgi?id=185583) the dmidecode output -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

07:45

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124#c9 --- Comment #9 from henry su 2007-12-03 00:45:32 MST --- Hi Thomas: For OpenSUSE10.3,do you know if S3 work well with any SB600 laptops? So far, there are no SB700 productions yet(see the attached dmidecode ),I test the S3 on our trevally board(engineering sample,not for resale) with standard USB logitech keyboard, no brightness btn,Num Lock and Caps Lock have no reponse when S3 failed. S3 also failed with text mode (boot with 3; vga=0); I comment out the "install video in /etc/modprobe.d/xorg-x11-driver-video,could you please give me more information on how to load the video module again? I install the video and get following error: linux-1h3n:~ # install video /bin/true install: cannot stat `video': No such file or directory S3 works fine with SLED10, SLES10, OpenSUSE10,OpenSUSE10.1,OpenSUSE10.2; I will rebuild a new kernel while no controller drivers except SATA driver,should it help us to figure out what is wrong if I rebuild a new kernel on OpenSUSE10.3 with the OpenSUSE10.2 kernel source code? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:19

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124#c10 --- Comment #10 from henry su 2007-12-03 01:19:11 MST --- I have firewire cable to connect two laptops now, and I need more information about the cables and how to setup the debug environment. There is an option to rePOST the graphics card on S3 resume in BIOS, but it does not help at all. btw,I will test this issue with our internal graphics driver may. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:22

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124#c11 --- Comment #11 from henry su 2007-12-03 01:22:24 MST --- sorry,I have only serial port cables. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:05

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124#c12 --- Comment #12 from Thomas Renninger 2007-12-03 03:05:19 MST --- I have HP 6715 and a Tohsiba Satallite A210, both do not work. They do not work with init=/bin/bash and they do not work with vga=normal

...

I will rebuild a new kernel while no controller drivers except SATA driver,should it help us to figure out what is wrong if I rebuild a new kernel on OpenSUSE10.3 with the OpenSUSE10.2 kernel source code? IMO it is worth to start a bisect. Get the latest torvalds kernel via git clone. Use the SUSE .config to build the kernels and mark the 2.6.16 good and 2.6.22 bad. git bisect should lead you to the offending patch then which broke it.

Pavel: I wonder whether the video posting is not working here anymore? Can this be debugged without suspending? This would also be a case were ohci1394_dma=resume (or similar) would make sense. The firewire port should get enabled at very early resume time to be able to read out kernel log buffer as soon as possible. Hmm, ok in this case even ssh is still working afterwards, but if the machine would hang at early resume time, this would be helpful for debugging..., maybe Pavel could give us a hint in which function Bernhard could add a hook to enable the firewire controller very early... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:35

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124#c13 --- Comment #13 from henry su 2007-12-03 03:35:42 MST --- I wonder if you need one SB700 reference board, I like to apply this board for your further debug. I think if S3 works well on SB600 platform with OpenSUSE10.3, it should work on SB700's too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11:25

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124#c14 --- Comment #14 from Pavel Machek 2007-12-03 04:25:11 MST --- I have CAT2 (RX780/SB600) board here. S3 seems to work here (with self-compiled 2.6.24-rcSomething). S2ram seems to work here, modulo video. If you tell me how to POST the video, I think I can get it to work fairly quickly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11:46

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124#c15 --- Comment #15 from Thomas Renninger 2007-12-03 04:46:14 MST --- I tried 2.6.18 10.2 kernel, but on my systems the Sata disk will not be detected with this one... How did you test with those older kernels? Pavel: S2ram seems to work here, modulo video. Do you mean it works but screen always stays black (or only sometimes?)? If yes, it is exactly what I see with the two (already sold) machines. Henry: To get the video driver loaded you have to delete or comment the contents of this file: /etc/modprobe.d/xorg-x11-driver-video Then: modprobe video -> The blacklist got removed recently and the video module should load automatically soon (not 10.3). This should give us brightness support on a lot machines (works fine here). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

12:25

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124#c16 Pavel Machek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |henry.su@amd.com --- Comment #16 from Pavel Machek 2007-12-03 05:25:42 MST --- Thomas: s2ram -f works here, reliably AFAICT, but screen stays black (also reliably). Henry, how do I tell BIOS to post the card? CAT2 (RX780/SB600) board here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

12:52

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124#c17 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eich@novell.com --- Comment #17 from Thomas Renninger 2007-12-03 05:52:42 MST --- Egbert might know that, if not we need this info from AMD... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

4 Dec 4 Dec

02:43

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c18 --- Comment #18 from henry su 2007-12-03 19:42:59 MST --- Thanks for your kind reply. Pavel: there is a configuration item in system BIOS to enable the rePOST funcion,Advanced->ACPI configuration->General ACPI configuration->Repost video on S3 resume(No, Yes). Thomas: 2.6.18 10.2 kernel may not includes the SATA device ID, please check the drivers/ata/ahci.c: 1)for SB600 sata controller, set the SATA mode as AHCI in system BIOS: /* ATI */ { PCI_VDEVICE(ATI, 0x4380), board_ahci }, /* ATI SB600 non-raid */ { PCI_VDEVICE(ATI, 0x4381), board_ahci }, /* ATI SB600 raid */ 2) for SB700: { PCI_VDEVICE(ATI, 0x4390), board_ahci_sb600 }, /* ATI SB700 IDE */ { PCI_VDEVICE(ATI, 0x4391), board_ahci_sb600 }, /* ATI SB700 AHCI */ { PCI_VDEVICE(ATI, 0x4392), board_ahci_sb600 }, /* ATI SB700 nraid5 */ { PCI_VDEVICE(ATI, 0x4393), board_ahci_sb600 }, /* ATI SB700 raid5 */ { PCI_VDEVICE(ATI, 0x4394), board_ahci_sb600 }, /* ATI SB700 flash*/ Since it takes time to download the source code with git-clone, I fetch the latest 2.6.24-rc3-mm2 to build a new kernel, and give you the result later. I upload the dmesgs of commenting the "install video /bin/true" and modprobing the video here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

02:45

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c19 --- Comment #19 from henry su 2007-12-03 19:45:11 MST --- Created an attachment (id=185712) --> (https://bugzilla.novell.com/attachment.cgi?id=185712) dmesg of commenting the "install video /bin/true" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

02:47

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c20 --- Comment #20 from henry su 2007-12-03 19:47:32 MST --- Created an attachment (id=185713) --> (https://bugzilla.novell.com/attachment.cgi?id=185713) dmesg of modprobing video -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:14

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c21 --- Comment #21 from Thomas Renninger 2007-12-04 01:14:31 MST --- Henry: Has the video module really be loaded? (lsmod |grep video). If yes, it seems as if your system does not support the video ACPI extension. Using a more recent BIOS might help, those extensions (at least brightness switching) should be supported with BIOS Vista support (working here). Henry: There are ACPI video functions which help OS to post VGA devices (ACPI spec 3.0b): B.4.6 _VPO (Video POST Options) and B.4.3 _ROM (Get ROM Data), B.4.4 _GPD (Get POST Device) and B.4.5 _SPD (Set POST Device). Which tells the OS whether the graphics devices can be posted and _SPD just posts it. Can you please find out whether ATI itself is providing ACPI snippets to the HW vendors containing the right video ACPI BIOS code (similar like AMD is with cpufreq interface, e.g. _PSS). I couldn't find any suspend/sleeping state related info there, but I execpt that if a video device is marked that it can be posted, it should be posted on suspend. If this interface can (or is intended) to be used in such a way (maybe we should reask at Intel or whoever had the idea for those functions), this would be a great possibility for us to come around our whitelist. Most Laptops should have working s2ram out of the box without the need of manually testing whether VGA posting is needed then. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:53

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c22 --- Comment #22 from henry su 2007-12-04 01:53:43 MST --- yes, the video was probed, and I attach the dmesg here. nux-1h3n:~ # lsmod |grep video video 37264 0 As far as I know, the rePOST function has been implemented in system BIOS,but it seems there are something wrongs with it, since it is a workaround for windows, and now windows do not need the rePOST any more, so BIOS engineers do not care about the rePOST for S3 now. I am not famliar with the ASL/AML,so I attach the DSDT here,. this issue exists the latest kernel(2.6.24-rc3-mm2), I also rebuild a new kernel with 10.2 source code(2.6.18), but it cannot boot normally. I will update the latest BIOS... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:04

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c23 --- Comment #23 from henry su 2007-12-04 02:04:34 MST --- Created an attachment (id=185746) --> (https://bugzilla.novell.com/attachment.cgi?id=185746) dmesg of commenting the "install video /bin/true" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:04

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c24 --- Comment #24 from henry su 2007-12-04 02:04:57 MST --- Created an attachment (id=185747) --> (https://bugzilla.novell.com/attachment.cgi?id=185747) dmesg of modprobing video -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:35

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c25 --- Comment #25 from henry su 2007-12-04 02:35:33 MST --- I decode the DSDT table, get following errors: ------------------------------------------------------------------------ Intel ACPI Component Architecture ASL Optimizing Compiler version 20060912 [Sep 21 2007] Copyright (C) 2000 - 2006 Intel Corporation Supports ACPI Specification Revision 3.0a ACPI Error (nsaccess-0531): ACPI path has too many parent prefixes (^) - reached beyond root node [20060912] ACPI Warning (nsaccess-0709): NsLookup: Type mismatch on PCIE (RegionField), searching for (Device) [20060912] ACPI Error (nsaccess-0531): ACPI path has too many parent prefixes (^) - reached beyond root node [20060912] Maximum error count (200) exceeded dsdt.dsl 332: \_SB.IRQC () Error 4062 - ^ Object does not exist (\_SB.IRQC) dsdt.dsl 490: LNKC, Error 4062 - ^ Object does not exist (LNKC) dsdt.dsl 498: LNKD, Error 4062 - ^ Object does not exist (LNKD) dsdt.dsl 506: LNKA, Error 4062 - ^ Object does not exist (LNKA) dsdt.dsl 514: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 522: LNKD, Error 4062 - ^ Object does not exist (LNKD) dsdt.dsl 530: LNKA, Error 4062 - ^ Object does not exist (LNKA) dsdt.dsl 538: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 546: LNKC, Error 4062 - ^ Object does not exist (LNKC) dsdt.dsl 554: LNKA, Error 4062 - ^ Object does not exist (LNKA) dsdt.dsl 562: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 570: LNKC, Error 4062 - ^ Object does not exist (LNKC) dsdt.dsl 578: LNKD, Error 4062 - ^ Object does not exist (LNKD) dsdt.dsl 586: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 594: LNKC, Error 4062 - ^ Object does not exist (LNKC) dsdt.dsl 602: LNKD, Error 4062 - ^ Object does not exist (LNKD) dsdt.dsl 610: LNKA, Error 4062 - ^ Object does not exist (LNKA) dsdt.dsl 618: LNKC, Error 4062 - ^ Object does not exist (LNKC) dsdt.dsl 626: LNKD, Error 4062 - ^ Object does not exist (LNKD) dsdt.dsl 634: LNKA, Error 4062 - ^ Object does not exist (LNKA) dsdt.dsl 642: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 650: LNKD, Error 4062 - ^ Object does not exist (LNKD) dsdt.dsl 658: LNKA, Error 4062 - ^ Object does not exist (LNKA) dsdt.dsl 666: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 674: LNKC, Error 4062 - ^ Object does not exist (LNKC) dsdt.dsl 682: LNKA, Error 4062 - ^ Object does not exist (LNKA) dsdt.dsl 690: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 698: LNKC, Error 4062 - ^ Object does not exist (LNKC) dsdt.dsl 706: LNKD, Error 4062 - ^ Object does not exist (LNKD) dsdt.dsl 714: LNKG, Error 4062 - ^ Object does not exist (LNKG) dsdt.dsl 722: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 730: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 738: LNKC, Error 4062 - ^ Object does not exist (LNKC) dsdt.dsl 746: LNKD, Error 4062 - ^ Object does not exist (LNKD) dsdt.dsl 754: LNKC, Error 4062 - ^ Object does not exist (LNKC) dsdt.dsl 762: LNKD, Error 4062 - ^ Object does not exist (LNKD) dsdt.dsl 770: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 778: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 1086: LNKC, Error 4062 - ^ Object does not exist (LNKC) dsdt.dsl 1094: LNKD, Error 4062 - ^ Object does not exist (LNKD) dsdt.dsl 1102: LNKA, Error 4062 - ^ Object does not exist (LNKA) dsdt.dsl 1110: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 1154: LNKC, Error 4062 - ^ Object does not exist (LNKC) dsdt.dsl 1162: LNKD, Error 4062 - ^ Object does not exist (LNKD) dsdt.dsl 1170: LNKA, Error 4062 - ^ Object does not exist (LNKA) dsdt.dsl 1178: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 1222: LNKD, Error 4062 - ^ Object does not exist (LNKD) dsdt.dsl 1230: LNKA, Error 4062 - ^ Object does not exist (LNKA) dsdt.dsl 1238: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 1246: LNKC, Error 4062 - ^ Object does not exist (LNKC) dsdt.dsl 1290: LNKA, Error 4062 - ^ Object does not exist (LNKA) dsdt.dsl 1298: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 1306: LNKC, Error 4062 - ^ Object does not exist (LNKC) dsdt.dsl 1314: LNKD, Error 4062 - ^ Object does not exist (LNKD) dsdt.dsl 1358: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 1366: LNKC, Error 4062 - ^ Object does not exist (LNKC) dsdt.dsl 1374: LNKD, Error 4062 - ^ Object does not exist (LNKD) dsdt.dsl 1382: LNKA, Error 4062 - ^ Object does not exist (LNKA) dsdt.dsl 1426: LNKC, Error 4062 - ^ Object does not exist (LNKC) dsdt.dsl 1434: LNKD, Error 4062 - ^ Object does not exist (LNKD) dsdt.dsl 1442: LNKA, Error 4062 - ^ Object does not exist (LNKA) dsdt.dsl 1450: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 1494: LNKD, Error 4062 - ^ Object does not exist (LNKD) dsdt.dsl 1502: LNKA, Error 4062 - ^ Object does not exist (LNKA) dsdt.dsl 1510: LNKB, Error 4062 - ^ Object does not exist (LNKB) dsdt.dsl 1518: LNKC, Error 4062 - ^ Object does not exist (LNKC) dsdt.dsl 1562: LNKF, Error 4062 - ^ Object does not exist (LNKF) dsdt.dsl 1570: LNKG, Error 4062 - ^ Object does not exist (LNKG) dsdt.dsl 1578: LNKH, Error 4062 - ^ Object does not exist (LNKH) dsdt.dsl 1586: LNKE, Error 4062 - ^ Object does not exist (LNKE) dsdt.dsl 1594: LNKG, Error 4062 - ^ Object does not exist (LNKG) dsdt.dsl 1602: LNKH, Error 4062 - ^ Object does not exist (LNKH) dsdt.dsl 1610: LNKE, Error 4062 - ^ Object does not exist (LNKE) dsdt.dsl 1618: LNKF, Error 4062 - ^ Object does not exist (LNKF) dsdt.dsl 1626: LNKH, Error 4062 - ^ Object does not exist (LNKH) dsdt.dsl 1634: LNKE, Error 4062 - ^ Object does not exist (LNKE) dsdt.dsl 1642: LNKF, Error 4062 - ^ Object does not exist (LNKF) dsdt.dsl 1650: LNKG, Error 4062 - ^ Object does not exist (LNKG) dsdt.dsl 1658: LNKE, Error 4062 - ^ Object does not exist (LNKE) dsdt.dsl 1666: LNKF, Error 4062 - ^ Object does not exist (LNKF) dsdt.dsl 1674: LNKG, Error 4062 - ^ Object does not exist (LNKG) dsdt.dsl 1682: LNKH, Error 4062 - ^ Object does not exist (LNKH) dsdt.dsl 1690: LNKF, Error 4062 - ^ Object does not exist (LNKF) dsdt.dsl 1698: LNKG, Error 4062 - ^ Object does not exist (LNKG) dsdt.dsl 1706: LNKG, Error 4062 - ^ Object does not exist (LNKG) dsdt.dsl 2072: If (OSCF) Error 4094 - ^ syntax error, unexpected PARSEOP_IF dsdt.dsl 2140: Method (_PRT, 0, NotSerialized) Error 4055 - ^ Name already exists in scope (_PRT) dsdt.dsl 2699: If (ECEN) Error 4094 - ^ syntax error, unexpected PARSEOP_IF dsdt.dsl 2702: OperationRegion (ECBP, SystemIO, ECIN, 0x02) Error 4062 - Object does not exist ^ (ECIN) dsdt.dsl 2708: OperationRegion (ECIO, SystemIO, ECIN, 0x02) Error 4062 - Object does not exist ^ (ECIN) dsdt.dsl 2744: Acquire (ECMU, 0x5000) Error 4062 - Object does not exist ^ (ECMU) dsdt.dsl 2758: Release (ECMU) Error 4062 - Object does not exist ^ (ECMU) dsdt.dsl 2764: Acquire (ECMU, 0x1388) Error 4062 - Object does not exist ^ (ECMU) dsdt.dsl 2765: Acquire (MLMU, 0x1388) Error 4062 - Object does not exist ^ (MLMU) dsdt.dsl 2780: Release (MLMU) Error 4062 - Object does not exist ^ (MLMU) dsdt.dsl 2781: Release (ECMU) Error 4062 - Object does not exist ^ (ECMU) dsdt.dsl 2786: Acquire (ECMU, 0x1388) Error 4062 - Object does not exist ^ (ECMU) dsdt.dsl 2787: Acquire (MLMU, 0x1388) Error 4062 - Object does not exist ^ (MLMU) dsdt.dsl 2802: Release (MLMU) Error 4062 - Object does not exist ^ (MLMU) dsdt.dsl 2803: Release (ECMU) Error 4062 - Object does not exist ^ (ECMU) dsdt.dsl 2948: CreateByteField (RSRC, \_SB.PCI0.SBRG.ECIR._CRS._Y01._MIN, IO1) Error 4062 - Object does not exist ^ (\_SB.PCI0.SBRG.ECIR._CRS._Y01._MIN) dsdt.dsl 2950: CreateByteField (RSRC, \_SB.PCI0.SBRG.ECIR._CRS._Y01._MAX, IO3) Error 4062 - Object does not exist ^ (\_SB.PCI0.SBRG.ECIR._CRS._Y01._MAX) dsdt.dsl 2952: CreateWordField (RSRC, \_SB.PCI0.SBRG.ECIR._CRS._Y02._INT, IRQV) Error 4062 - Object does not exist ^ (\_SB.PCI0.SBRG.ECIR._CRS._Y02._INT) dsdt.dsl 2953: Acquire (ECMU, 0x1388) Error 4062 - Object does not exist ^ (ECMU) dsdt.dsl 2966: Release (ECMU) Error 4062 - Object does not exist ^ (ECMU) dsdt.dsl 3023: Acquire (ECMU, 0x1388) Error 4062 - Object does not exist ^ (ECMU) dsdt.dsl 3031: Release (ECMU) Error 4062 - Object does not exist ^ (ECMU) dsdt.dsl 3146: If (ECEN) Error 4062 - Object does not exist ^ (ECEN) dsdt.dsl 3148: PPTS (Arg0) Error 4066 - ^ Object is not accessible from this scope (PPTS) dsdt.dsl 3154: If (ECEN) Error 4062 - Object does not exist ^ (ECEN) dsdt.dsl 3156: WWAK (Arg0) Error 4066 - ^ Object is not accessible from this scope (WWAK) dsdt.dsl 3307: CreateDWordField (CRS, \_SB.PCI0.SBRG.HPET._Y03._BAS, HPT) Error 4062 - Object does not exist ^ (\_SB.PCI0.SBRG.HPET._Y03._BAS) dsdt.dsl 3313: Device (^PCIE) Error 4014 - From ACPI CA Subsystem ^ (AE_NOT_FOUND Failure from lookup %s ) dsdt.dsl 3315: Name (_HID, EisaId ("PNP0C02")) Error 4066 - ^ Object is not accessible from this scope (_HID) dsdt.dsl 3316: Name (_UID, 0x11) Error 4066 - ^ Object is not accessible from this scope (_UID) dsdt.dsl 3317: Name (CRS, ResourceTemplate () Error 4066 - ^ Object is not accessible from this scope (CRS_) dsdt.dsl 3324: Method (_CRS, 0, NotSerialized) Error 4066 - ^ Object is not accessible from this scope (_CRS) dsdt.dsl 3326: CreateDWordField (CRS, \_SB.PCI0.PCIE._Y04._BAS, BAS1) Error 4066 - Object is not accessible from this scope ^ (BAS1) dsdt.dsl 3326: CreateDWordField (CRS, \_SB.PCI0.PCIE._Y04._BAS, BAS1) Error 4066 - Object is not accessible from this scope ^ (CRS_) dsdt.dsl 3326: CreateDWordField (CRS, \_SB.PCI0.PCIE._Y04._BAS, BAS1) Error 4062 - Object does not exist ^ (\_SB.PCI0.PCIE._Y04._BAS) dsdt.dsl 3327: CreateDWordField (CRS, \_SB.PCI0.PCIE._Y04._LEN, LEN1) Error 4066 - Object is not accessible from this scope ^ (LEN1) dsdt.dsl 3327: CreateDWordField (CRS, \_SB.PCI0.PCIE._Y04._LEN, LEN1) Error 4066 - Object is not accessible from this scope ^ (CRS_) dsdt.dsl 3327: CreateDWordField (CRS, \_SB.PCI0.PCIE._Y04._LEN, LEN1) Error 4062 - Object does not exist ^ (\_SB.PCI0.PCIE._Y04._LEN) dsdt.dsl 3328: Store (PCIB, BAS1) Error 4066 - ^ Object is not accessible from this scope (BAS1) dsdt.dsl 3329: Store (PCIL, LEN1) Error 4066 - ^ Object is not accessible from this scope (LEN1) dsdt.dsl 3330: Return (CRS) Error 4066 - ^ Object is not accessible from this scope (CRS_) dsdt.dsl 3334: Device (OMSC) Error 4062 - Object does not exist ^ (OMSC) dsdt.dsl 3336: Name (_HID, EisaId ("PNP0C02")) Error 4066 - ^ Object is not accessible from this scope (_HID) dsdt.dsl 3337: Name (_UID, Zero) Error 4066 - ^ Object is not accessible from this scope (_UID) dsdt.dsl 3338: Name (CRS, ResourceTemplate () Error 4066 - ^ Object is not accessible from this scope (CRS_) dsdt.dsl 3349: Method (_CRS, 0, NotSerialized) Error 4066 - ^ Object is not accessible from this scope (_CRS) dsdt.dsl 3353: CreateDWordField (CRS, \_SB.PCI0.SBRG.OMSC._Y05._LEN, ML01) Error 4062 - Object does not exist ^ (ML01) dsdt.dsl 3353: CreateDWordField (CRS, \_SB.PCI0.SBRG.OMSC._Y05._LEN, ML01) Error 4066 - Object is not accessible from this scope ^ (CRS_) dsdt.dsl 3353: CreateDWordField (CRS, \_SB.PCI0.SBRG.OMSC._Y05._LEN, ML01) Error 4062 - Object does not exist ^ (\_SB.PCI0.SBRG.OMSC._Y05._LEN) dsdt.dsl 3354: CreateDWordField (CRS, \_SB.PCI0.SBRG.OMSC._Y05._BAS, MB01) Error 4062 - Object does not exist ^ (MB01) dsdt.dsl 3354: CreateDWordField (CRS, \_SB.PCI0.SBRG.OMSC._Y05._BAS, MB01) Error 4066 - Object is not accessible from this scope ^ (CRS_) dsdt.dsl 3354: CreateDWordField (CRS, \_SB.PCI0.SBRG.OMSC._Y05._BAS, MB01) Error 4062 - Object does not exist ^ (\_SB.PCI0.SBRG.OMSC._Y05._BAS) dsdt.dsl 3355: CreateDWordField (CRS, \_SB.PCI0.SBRG.OMSC._Y06._LEN, ML02) Error 4062 - Object does not exist ^ (ML02) dsdt.dsl 3355: CreateDWordField (CRS, \_SB.PCI0.SBRG.OMSC._Y06._LEN, ML02) Error 4066 - Object is not accessible from this scope ^ (CRS_) dsdt.dsl 3355: CreateDWordField (CRS, \_SB.PCI0.SBRG.OMSC._Y06._LEN, ML02) Error 4062 - Object does not exist ^ (\_SB.PCI0.SBRG.OMSC._Y06._LEN) dsdt.dsl 3356: CreateDWordField (CRS, \_SB.PCI0.SBRG.OMSC._Y06._BAS, MB02) Error 4062 - Object does not exist ^ (MB02) dsdt.dsl 3356: CreateDWordField (CRS, \_SB.PCI0.SBRG.OMSC._Y06._BAS, MB02) Error 4066 - Object is not accessible from this scope ^ (CRS_) dsdt.dsl 3356: CreateDWordField (CRS, \_SB.PCI0.SBRG.OMSC._Y06._BAS, MB02) Error 4062 - Object does not exist ^ (\_SB.PCI0.SBRG.OMSC._Y06._BAS) dsdt.dsl 3357: Store (0xFEC00000, MB01) Error 4062 - Object does not exist ^ (MB01) dsdt.dsl 3358: Store (0x1000, ML01) Error 4062 - Object does not exist ^ (ML01) dsdt.dsl 3359: Store (0xFEE00000, MB02) Error 4062 - Object does not exist ^ (MB02) dsdt.dsl 3360: Store (0x1000, ML02) Error 4062 - Object does not exist ^ (ML02) dsdt.dsl 3363: Return (CRS) Error 4066 - ^ Object is not accessible from this scope (CRS_) dsdt.dsl 3367: Device (^^RMEM) Error 4063 - ^ Object not found or not accessible from scope (^^RMEM) dsdt.dsl 3369: Name (_HID, EisaId ("PNP0C01")) Error 4066 - ^ Object is not accessible from this scope (_HID) dsdt.dsl 3370: Name (_UID, One) Error 4066 - ^ Object is not accessible from this scope (_UID) dsdt.dsl 3371: Name (CRS, ResourceTemplate () Error 4066 - ^ Object is not accessible from this scope (CRS_) dsdt.dsl 3394: Method (_CRS, 0, NotSerialized) Error 4066 - ^ Object is not accessible from this scope (_CRS) dsdt.dsl 3396: CreateDWordField (CRS, \_SB.RMEM._Y07._BAS, BAS1) Error 4066 - Object is not accessible from this scope ^ (BAS1) dsdt.dsl 3396: CreateDWordField (CRS, \_SB.RMEM._Y07._BAS, BAS1) Error 4066 - Object is not accessible from this scope ^ (CRS_) dsdt.dsl 3396: CreateDWordField (CRS, \_SB.RMEM._Y07._BAS, BAS1) Error 4062 - Object does not exist ^ (\_SB.RMEM._Y07._BAS) dsdt.dsl 3397: CreateDWordField (CRS, \_SB.RMEM._Y07._LEN, LEN1) Error 4066 - Object is not accessible from this scope ^ (LEN1) dsdt.dsl 3397: CreateDWordField (CRS, \_SB.RMEM._Y07._LEN, LEN1) Error 4066 - Object is not accessible from this scope ^ (CRS_) dsdt.dsl 3397: CreateDWordField (CRS, \_SB.RMEM._Y07._LEN, LEN1) Error 4062 - Object does not exist ^ (\_SB.RMEM._Y07._LEN) dsdt.dsl 3398: CreateDWordField (CRS, \_SB.RMEM._Y08._BAS, BAS2) Error 4062 - Object does not exist ^ (BAS2) dsdt.dsl 3398: CreateDWordField (CRS, \_SB.RMEM._Y08._BAS, BAS2) Error 4066 - Object is not accessible from this scope ^ (CRS_) dsdt.dsl 3398: CreateDWordField (CRS, \_SB.RMEM._Y08._BAS, BAS2) Error 4062 - Object does not exist ^ (\_SB.RMEM._Y08._BAS) dsdt.dsl 3399: CreateDWordField (CRS, \_SB.RMEM._Y08._LEN, LEN2) Error 4062 - Object does not exist ^ (LEN2) dsdt.dsl 3399: CreateDWordField (CRS, \_SB.RMEM._Y08._LEN, LEN2) Error 4066 - Object is not accessible from this scope ^ (CRS_) dsdt.dsl 3399: CreateDWordField (CRS, \_SB.RMEM._Y08._LEN, LEN2) Error 4062 - Object does not exist ^ (\_SB.RMEM._Y08._LEN) dsdt.dsl 3400: CreateDWordField (CRS, \_SB.RMEM._Y09._LEN, LEN3) Error 4062 - Object does not exist ^ (LEN3) dsdt.dsl 3400: CreateDWordField (CRS, \_SB.RMEM._Y09._LEN, LEN3) Error 4066 - Object is not accessible from this scope ^ (CRS_) dsdt.dsl 3400: CreateDWordField (CRS, \_SB.RMEM._Y09._LEN, LEN3) Error 4062 - Object does not exist ^ (\_SB.RMEM._Y09._LEN) dsdt.dsl 3401: CreateDWordField (CRS, \_SB.RMEM._Y0A._BAS, BAS4) Error 4062 - Object does not exist ^ (BAS4) dsdt.dsl 3401: CreateDWordField (CRS, \_SB.RMEM._Y0A._BAS, BAS4) Error 4066 - Object is not accessible from this scope ^ (CRS_) dsdt.dsl 3401: CreateDWordField (CRS, \_SB.RMEM._Y0A._BAS, BAS4) Error 4062 - Object does not exist ^ (\_SB.RMEM._Y0A._BAS) dsdt.dsl 3402: CreateDWordField (CRS, \_SB.RMEM._Y0A._LEN, LEN4) Error 4062 - Object does not exist ^ (LEN4) dsdt.dsl 3402: CreateDWordField (CRS, \_SB.RMEM._Y0A._LEN, LEN4) Error 4066 - Object is not accessible from this scope ^ (CRS_) dsdt.dsl 3402: CreateDWordField (CRS, \_SB.RMEM._Y0A._LEN, LEN4) Error 4062 - Object does not exist ^ (\_SB.RMEM._Y0A._LEN) dsdt.dsl 3410: Store (0x000C0000, BAS1) Error 4066 - Object is not accessible from this scope ^ (BAS1) dsdt.dsl 3411: Subtract (MG1B, BAS1, LEN1) Error 4066 - Object is not accessible from this scope ^ (BAS1) dsdt.dsl 3411: Subtract (MG1B, BAS1, LEN1) Error 4066 - Object is not accessible from this scope ^ (LEN1) dsdt.dsl 3416: Store (0x000C0000, BAS1) Error 4066 - Object is not accessible from this scope ^ (BAS1) dsdt.dsl 3417: Store (0x00020000, LEN1) Error 4066 - Object is not accessible from this scope ^ (LEN1) dsdt.dsl 3422: Store (Local0, BAS2) Error 4062 - Object does not exist ^ (BAS2) dsdt.dsl 3423: Subtract (0x00100000, BAS2, LEN2) Error 4062 - Object does not exist ^ (BAS2) dsdt.dsl 3423: Subtract (0x00100000, BAS2, LEN2) Error 4062 - Object does not exist ^ (LEN2) dsdt.dsl 3427: Subtract (MG2B, 0x00100000, LEN3) Error 4062 - Object does not exist ^ (LEN3) dsdt.dsl 3428: Store (MH1B, BAS4) Error 4062 - Object does not exist ^ (BAS4) dsdt.dsl 3429: Subtract (Zero, BAS4, LEN4) Error 4062 - Object does not exist ^ (BAS4) dsdt.dsl 3429: Subtract (Zero, BAS4, LEN4) Error 4062 - Object does not exist ^ (LEN4) dsdt.dsl 3430: Return (CRS) Error 4066 - ^ Object is not accessible from this scope (CRS_) dsdt.dsl 3434: Device (RMSC) Error 4062 - Object does not exist ^ (RMSC) dsdt.dsl 3436: Name (_HID, EisaId ("PNP0C02")) Error 4066 - ^ Object is not accessible from this scope (_HID) dsdt.dsl 3437: Name (_UID, 0x10) Error 4066 - ^ Object is not accessible from this scope (_UID) dsdt.dsl 3438: Name (CRS, ResourceTemplate () Error 4066 - ^ Object is not accessible from this scope (CRS_) dsdt.dsl 3651: Method (_CRS, 0, NotSerialized) Error 4066 - ^ Object is not accessible from this scope (_CRS) dsdt.dsl 3653: CreateWordField (CRS, \_SB.PCI0.SBRG.RMSC._Y0B._MIN, GP00) Error 4062 - Object does not exist ^ (GP00) dsdt.dsl 3653: CreateWordField (CRS, \_SB.PCI0.SBRG.RMSC._Y0B._MIN, GP00) Error 4066 - Object is not accessible from this scope ^ (CRS_) dsdt.dsl 3653: CreateWordField (CRS, \_SB.PCI0.SBRG.RMSC._Y0B._MIN, GP00) Error 4062 - Object does not exist ^ (\_SB.PCI0.SBRG.RMSC._Y0B._MIN) dsdt.dsl 3654: CreateWordField (CRS, \_SB.PCI0.SBRG.RMSC._Y0B._MAX, GP01) Error 4062 - Object does not exist ^ (GP01) dsdt.dsl 3654: CreateWordField (CRS, \_SB.PCI0.SBRG.RMSC._Y0B._MAX, GP01) Error 4066 - Object is not accessible from this scope ^ (CRS_) dsdt.dsl 3654: CreateWordField (CRS, \_SB.PCI0.SBRG.RMSC._Y0B._MAX, GP01) Error 4062 - Object does not exist ^ (\_SB.PCI0.SBRG.RMSC._Y0B._MAX) dsdt.dsl 3655: CreateByteField (CRS, \_SB.PCI0.SBRG.RMSC._Y0B._LEN, GP0L) Error 4062 - Object does not exist ^ (GP0L) dsdt.dsl 3655: CreateByteField (CRS, \_SB.PCI0.SBRG.RMSC._Y0B._LEN, GP0L) Error 4066 - Object is not accessible from this scope ^ (CRS_) dsdt.dsl 4161: Scope, 0, NotSerialized) Error 4094 - ^ syntax error, unexpected PARSEOP_SCOPE, expecting $end Maximum error count (200) exceeded ASL Input: dsdt.dsl - 5069 lines, 153537 bytes, 1179 keywords Compilation complete. 201 Errors, 0 Warnings, 0 Remarks, 2 Optimizations -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:36

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c26 --- Comment #26 from henry su 2007-12-04 02:36:32 MST --- Created an attachment (id=185758) --> (https://bugzilla.novell.com/attachment.cgi?id=185758) original DSDT table in /proc/acpi/dsdt -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:37

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c27 --- Comment #27 from henry su 2007-12-04 02:37:57 MST --- Created an attachment (id=185760) --> (https://bugzilla.novell.com/attachment.cgi?id=185760) ouput of "iasl -d dsdt.bat" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:38

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c28 --- Comment #28 from henry su 2007-12-04 02:38:40 MST --- Created an attachment (id=185761) --> (https://bugzilla.novell.com/attachment.cgi?id=185761) output of "iasl -tc dsdt.dsl" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:39

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c29 --- Comment #29 from henry su 2007-12-04 02:39:09 MST --- Created an attachment (id=185762) --> (https://bugzilla.novell.com/attachment.cgi?id=185762) errors of "iasl -tc dsdt.dsl" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:46

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c30 --- Comment #30 from Thomas Renninger 2007-12-04 02:46:57 MST --- If you could provide Pavel with some more details about "since it is a workaround for windows, and now windows do not need the rePOST any more", this would be great. E.g. how is Windows doing it now, do they use the ACPI functions or what else..., we also need a mechanism to detect whether we need to post or not or set some flag that it's not needed or however it works... Can you attach full acpidump output pls (best with mime type set to text/plain). There is a flag below the comment field: "This comment provides the needed information". If you are set in "Needinfo", can you set this flag as soon as you provided the requested info. It's mostly unused, especially on more important bugs, but it may help to not loose track of a bug... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

5 Dec 5 Dec

02:21

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c31 --- Comment #31 from henry su 2007-12-04 19:21:26 MST --- Created an attachment (id=185921) --> (https://bugzilla.novell.com/attachment.cgi?id=185921) acpidump output -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

02:29

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c32 --- Comment #32 from henry su 2007-12-04 19:29:14 MST --- Windows would post the graphics while resuming from S3, so BIOS should not do this any more, the BIOS engineers don't known how to do this either,they said the windows drivers is confidential. I updated the latest BIOS, it does not work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

12:25

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c33 --- Comment #33 from Thomas Renninger 2007-12-05 05:25:52 MST --- Created an attachment (id=185992) --> (https://bugzilla.novell.com/attachment.cgi?id=185992) Partly fixed up DSDT Henry: The main problem of this DSDT is that IF and AND statements are used outside of methods. The Intel/Linux interpreter does not like this at all and mixes up scopes. I even get: Maximum error count (200) exceeded at a first compile. This ACPI implementation does also not support any video ACPI extensions as described in: ACPI spec 3.0b: APPENDIX B: Video Extensions B ACPI Extensions for Display Adapters (I only checked the most common, I doubt any graphics functions are declared). Where does this BIOS come from? This urgently needs fixing! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:15

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

...

Windows would post the graphics while resuming from S3, so BIOS should not do this any more, the BIOS engineers don't known how to do this either,they said the windows drivers is confidential. Sorry, how should this work? The Windows engineers know the hardware better

https://bugzilla.novell.com/show_bug.cgi?id=345124 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c34 --- Comment #34 from Thomas Renninger 2007-12-05 06:15:09 MST --- About comment #32: than the HW vendors? Maybe there is some ACPI flag or as soon as the ACPI brightness functions are there (a good indication for Vista BIOS support), the OS is posting the VGA device in any case? Henry: the M$ driver may be confidental, but they probably colaborated in some way with the HW vendors, e.g. telling them, pls do not post the VGA device anymore, our driver is doing it or whatever (not sure who really is in charge here, I expect the BIOS developing company which should be the mainboard vendor)... If we could get some more information here (e.g. what is the trigger for OS to post or not) that would be great. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

14:19

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c35 --- Comment #35 from Pavel Machek 2007-12-05 07:19:54 MST ---

...

Pavel: there is a configuration item in system BIOS to enable the rePOST funcion,Advanced->ACPI configuration->General ACPI configuration->Repost video on S3 resume(No, Yes).

Advanced menu contains "PnP Configuration" and "Advanced Chipset Control" submenus (and some options). Bios identifies itself as "CAT2-BIOS-A0D-07september2007". in Info. I briefly tried searching the other menus, but I can't see anythign similar. Do I need a new bios? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

6 Dec 6 Dec

01:35

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c37 henry su changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|henry.su@amd.com | --- Comment #37 from henry su 2007-12-05 18:35:37 MST --- Pavel:I also saw these errors while compiling the DSDT table.This BIOS comes from AMD BIOS team,I will sent these errors to them. Yes, the ACPI configuration is in Advanced menu in most SB600/SB700 BIOS,maybe there are some differences with our BIOSes. Do you need a RS690/SB700 reference board? I like to help someone else(Joachim) to sent it to you for the debugging. Thomas:Thanks for the information, I have sent one email to AMD graphics driver team, but got no reponse till now. In this RS690/SB700 platform,most distributions such as RHEL,redflag,ubuntu, SLED and OpenSUSE10.2 must use the vbetool or S2ram to POST the graphics while resuming from S3,otherwise it would fail,so maybe it is better for us to find out the difference between 10.2 and 10.3 firstly, especially ACPI related. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:17

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c38 --- Comment #38 from Pavel Machek 2007-12-06 01:17:15 MST --- Yes, newer reference board would certainly be welcome. Additional bonus if it does not hang up randomly and does not sound like a jet plane ;-). ..actually, if you can get me updated BIOS that has the "rePOST option", that would be very useful, too.. and I guess BIOS can be sent over network, unlike reference board. I think we tried vbetool, and it did not work. Are you sure it works with 10.2? Anyway, vbetool is very bad solution. Yes, it gets the job done, but it makes debugging pretty much impossible. It is important to fix BIOS in a way that vbetool is not needed. (And that does not necessarily mean rePOST option, simply making sure that we can do lcall 0xc000, 3 to post the bios is enough for nice work, and enough fro debugging). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:36

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c39 --- Comment #39 from Pavel Machek 2007-12-06 01:36:43 MST --- (Can someone confirm 10.2 actually works on amd systems? What is used to resume the video?) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:48

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c40 --- Comment #40 from henry su 2007-12-06 01:48:06 MST --- Yes, I confirmed that it works on our RS690/SB700 system with OpenSUSE 10.1,10.2 and SLED10 ( and SP1),SLES10, one exception is 10.3. the command for 10.2 is "s2ram -f -p -s" I sent to email to you since I do not know which system BIOS you want, the cat system is RS485+SB600? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:55

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c41 --- Comment #41 from Pavel Machek 2007-12-06 01:55:38 MST --- I did not get an email. My bios screen says Build time: 09/11/07 17:52:41 AMD CAT2 (DDR2 + RX780/SB600) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:05

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c42 --- Comment #42 from henry su 2007-12-06 02:05:11 MST --- RX780 + SB600 + EC (CAT 2 Rev A) Phoenix Evaluation/Test BIOS: The latest update is 09 Nov 2007, so the BIOS should be the latest one now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:07

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c43 --- Comment #43 from henry su 2007-12-06 02:07:36 MST --- Created an attachment (id=186121) --> (https://bugzilla.novell.com/attachment.cgi?id=186121) The latest BIOS for CAT2 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:27

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c44 --- Comment #44 from Pavel Machek 2007-12-06 03:27:23 MST --- I did BIOS update (thanks!). Now it will not even boot linux ... hangs at checking hlt instruction. I tried nohlt, but it hanged, too. And I still don't see 'Video Post' option in the BIOS :-(. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:28

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c45 --- Comment #45 from Pavel Machek 2007-12-06 03:28:24 MST --- (nohlt, idle=poll makes it boot) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:35

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c46 --- Comment #46 from Pavel Machek 2007-12-06 03:35:50 MST --- ..Turning off C1E support and one more option makes it boot. Good. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:41

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c47 --- Comment #47 from Pavel Machek 2007-12-06 03:41:10 MST --- Ok, s2ram -f -p -s seems to work here on 2.6.23 kernel with self-compiled s2ram. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:18

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c48 --- Comment #48 from Thomas Renninger 2007-12-06 06:18:47 MST --- On my two machines 10.2 kernel is also not working (s2ram). The problem of the not found disk was a (I expect) a mkintrd bug. sd_mod was not included in initrd... 10.3 and 10.2 kernel show exactly the same symptoms. With -p option it behaves a bit different. Switching vitual terminals shows some (totally messed) graphics output. I think I can remember such messes on a very old machine. There it happened sometimes and switching virtual consoles helped to get working graphics back, here it does not (maybe this helps?). Pavel: What version of s2ram have you used? Do you think it's worth trying a newer one? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

18:42

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c49 --- Comment #49 from Pavel Machek 2007-12-06 11:42:58 MST --- I'm not sure how to identify s2ram. whitelist.c is: RCS file: /cvsroot/suspend/suspend/whitelist.c,v Working file: whitelist.c head: 1.115 revision 1.115 date: 2007/11/07 12:55:25; author: seife; state: Exp; lines: +149 -11 ..anyway, I'm using 32-bit distro for some obscure reasons, perhaps that matters? Henry, were you using 32-bit or 64-bit system? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

7 Dec 7 Dec

01:58

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c50 --- Comment #50 from henry su 2007-12-06 18:58:05 MST --- I am using a x86_64bit system, Pavel, Could you please send the s2ram source code to me? I want to try this version on my system,the email address is henry.su@amd.com. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:40

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c51 --- Comment #51 from Pavel Machek 2007-12-07 03:40:45 MST --- Pointer to sources sent in another email. Trenn, Henry: can you try 32-bit version? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11:36

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c52 --- Comment #52 from Thomas Renninger 2007-12-07 04:36:09 MST --- s2ram -f -p -s also works here, with i386 and x86_64 kernel with 10.3 suspend package. Pavel/Seife, do you need dmidecode? I wonder whether: - all machines with this chipset should be whitelisted - all machines with VISTA capable (dmidecode, BIOS newer than... should get whitelisted to used these params). Maybe it is as Henry stated and all newer (Vista capable) machines need this? Hmm, only the HP is coming up again, not the Toshiba (even keyboard LEDs not reacting anymore). But this could be something graphics unrelated, I will debug this at some later point, playing a bit with firescope... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

8 Dec 8 Dec

09:08

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c53 --- Comment #53 from henry su 2007-12-08 02:08:25 MST --- Pavel:I will try the i386 version next Monday. Thomas: it works on 10.2 or 10.3? I found that it worked on 10.2. btw:do you ever notice that s3 failed with fbdev driver, I have to change the graphics driver from fbdev to vesa mannually to support the ACPI function, maybe we need to add the NOFB to the whitelists. "S2ram -f -a 3" works with 10.2 on shiner board(RS780/SB700),it seems that the rePOST is not necessary on this board. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10 Dec 10 Dec

08:32

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c54 --- Comment #54 from Pavel Machek 2007-12-10 01:32:28 MST --- Thomas: No whitelisting of prototypes, I'd say. Henry: Congrats with shiner board. Just make sure production stuff works as well. Is there some docs for cat2 system somewhere? It has nice debug display and lots of switches, but I don't know how to control half the display nor what the switches do... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:12

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c55 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mark.langsdorf@amd.com, joachim.deguara@amd.com --- Comment #55 from Thomas Renninger 2007-12-10 06:12:33 MST --- Pavel: The machine I tested here is production: HP Compaq 6715b The other one seem to have another problem with s2ram, I try to find out if I find the time, it's a Toshiba Satellite A210. IMO we urgently need to find out how Windows detects whether and how the card gets posted. I am pretty sure there is a mechanism for Vista to autodetect that... I expect it should have been the ACPI video extensions (the posting parts), but as no vendor is declaring them in BIOS it must be something else. Henry: it would be great if you could try to find that out. You probably need a guy at ATI who is in touch with the Windows ATI driver(s). They must know how things are done at Windows and whether or how Windows (Vista!) can detect that automatically. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11 Dec 11 Dec

07:57

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c56 --- Comment #56 from henry su 2007-12-11 00:57:35 MST --- Pavel: I try the i386 version, but it has the same symptom. it is regretable that the CAT2 document should not public, but the good thing is the trevally board(RS690/SB700) has been sent to Joachim Plack, so it would be available soon,thanks. Thomas:I am not find the right guys who can tell us how the vista detect the rePOST setting in system BIOS, it take a little time to figure that. Joachim Plack: I got your address from Deguara, Joachim, it is sad if the address is wrong :( email:jplack@novell.com SUSE Linux Product GmbH ATTN: Joachim Plack Maxfeldstrasse 5 90409 Nuernberg Germany -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:48

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c57 --- Comment #57 from henry su 2007-12-11 01:48:57 MST --- Joachim Plack: the trevally board includes a motherboard , a microprocess and a heatsink, please let me know while you receive the right property, thanks. One more thing is,we can only USB keyboard and USB mouse on this board, the PS/2 does not work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

12:04

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c58 --- Comment #58 from Stefan Seyfried 2007-12-11 05:04:10 MST --- (In reply to comment #53 from henry su)

...

"S2ram -f -a 3" works with 10.2 on shiner board(RS780/SB700),it seems that the rePOST is not necessary on this board.

JFTR, "-a3" does POST the graphics chip, just with a different method than VBE_POST. With "-a1" (and -a3), we jump into the BIOS POST routine directly from the kernel (Pavel, please correct me if i'm stating something totally wrong :-) With VBE_POST, we run the BIOS POST routine from userspace using an x86 emulator. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13 Dec 13 Dec

10:53

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c59 --- Comment #59 from henry su 2007-12-13 03:53:32 MST --- One good news is that s3 resumed well on shiner(RS780/SB700) board with the following options: #s2ram --force #s2ram -f -a 1 #s2ram -f -a 3 I can see some messages in the console: swithing from vt7 to vt1 fbcon fb0 state 1 fbcon fb0 state 0 switching back to vt7 Also,the system can resume with the command "echo mem > /sys/power/state",one difference is that the screen color is wrong, some like 256 colors; However,the system seems to be broken,I cannot use most commands such as dmesg,vim ... ,but ls is ok; the screen color is not right,the same message comes up in the console: #dmesg bash /bin/dmesg: Input/output error -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

14 Dec 14 Dec

02:22

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c60 --- Comment #60 from henry su 2007-12-13 19:22:14 MST --- In addition,it is abnormal that now the S3 takes about 2 seconds to resume. I also copy all files in /etc/powersave/ from SLED10 to the same directory of 10.3, and use the powersave -u to enter S3, the system resumes with the following message: Received error reply: /usr/lib/hal/scripts/linux/hal-system-power-suspend-linux: line50: /usr/bin/hal-find-by-capability: Input/output error /usr/lib/hal/scripts/linux/hal-system-power-suspend-linux: line 50: /usr/bin/hal-find-by-capability: Input/output error Could not send suspend to ram request to HAL Could someone else explain what does it mean? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

02:30

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c61 --- Comment #61 from henry su 2007-12-13 19:30:54 MST --- Created an attachment (id=187551) --> (https://bugzilla.novell.com/attachment.cgi?id=187551) /usr/lib/hal/scripts/linux/hal-system-power-suspend-linux -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

15 Dec 15 Dec

04:22

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c62 --- Comment #62 from henry su 2007-12-14 21:22:56 MST --- sorry, two minutes to resume from S3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

18 Dec 18 Dec

11:36

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c63 --- Comment #63 from Stefan Seyfried 2007-12-18 04:36:26 MST --- (In reply to comment #60 from henry su)

...

I also copy all files in /etc/powersave/ from SLED10 to the same directory of 10.3, and use the powersave -u to enter S3, the system resumes with the following message: Received error reply: /usr/lib/hal/scripts/linux/hal-system-power-suspend-linux: line50: /usr/bin/hal-find-by-capability: Input/output error /usr/lib/hal/scripts/linux/hal-system-power-suspend-linux: line 50: /usr/bin/hal-find-by-capability: Input/output error Could not send suspend to ram request to HAL

Could someone else explain what does it mean?

First, /etc/powersave/* is no longer used for suspend in 10.3, see http://en.opensuse.org/Pm-utils for the current infrastructure. You can still use "powersave -u" and "powersave -U", but they now work via HAL and pm-utils. It looks like hal or dbus has some problem on your machine. Does it work after a reboot? Do you have all recent online updates installed on the 10.3 machine? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

19 Dec 19 Dec

02:46

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c64 --- Comment #64 from henry su 2007-12-18 19:46:23 MST --- The system returns to normal if I do a reboot,no online update,and I will update all packets and tell you the test result later.the Input/output error maybe a HW bug on SB700 A11, we have fixed it on the A12 version. one good news is that S3 works well on RS780/SB700 A12(shiner) with ATI graphics driver, but it failed on RS690/SB700(trevally) A11 board,so we have to figure out why it works well with 10.2 and SLED10(SP1) on the same board. Thomas said he received the trevally board yesterday(in jack's office now?), so please have a test on it firstly, also,the board is used to do a full test with SLED10 SP2,as far as I know,it is very important for AMD to make sure everything work fine with SLED10 SP2 on this board. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

18:01

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c65 --- Comment #65 from Stefan Seyfried 2007-12-19 11:01:10 MST --- (In reply to comment #64 from henry su)

...

The system returns to normal if I do a reboot,no online update,and I will

Ok, there have been dbus updates that fix symptoms like this one.

...

update all packets and tell you the test result later.the Input/output error maybe a HW bug on SB700 A11, we have fixed it on the A12 version.

I don't think that this is a hardware problem, unless the hardware problem causes random processes to die or misbehave :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

25 Dec 25 Dec

12:41

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c66 --- Comment #66 from Pavel Machek 2007-12-25 05:41:04 MST --- Did we receive new hw ("trevally board")? Is it needed in Nurnberg, or could it perhaps be sent to Prague? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

7 Jan 7 Jan

09:48

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c67 Pavel Machek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |jplack@novell.com --- Comment #67 from Pavel Machek 2008-01-07 02:48:07 MST --- JOachim, can you comment? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

8 Jan 8 Jan

08:05

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c68 --- Comment #68 from henry su 2008-01-08 01:05:02 MST --- hi Pavel, I sent this board and hope we can debug this issue together since it works well on all distributions except OpenSUSE10.3. I still have no update now. Also we would verify if SLED/SLES 10 sp2 runs well on this board. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11 Jan 11 Jan

14:05

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User jplack@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c69 Joachim Plack changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|jplack@novell.com | --- Comment #69 from Joachim Plack 2008-01-11 07:05:51 MST --- The trevally has finally arrived. I'll ask Frank to handle the HW issue with you. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

28 Jan 28 Jan

11:38

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c72 --- Comment #72 from Pavel Machek 2008-01-28 04:38:50 MST --- Henry, could you split this into two bugs, one for each board? Actually.. I believe the cat2 simply works...? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

2 Feb 2 Feb

12:04

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c73 Pavel Machek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |henry.su@amd.com --- Comment #73 from Pavel Machek 2008-02-02 05:04:11 MST --- .. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13 Feb 13 Feb

03:16

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c74 --- Comment #74 from henry su 2008-02-12 20:16:24 MST --- Hi Pavel, Sorry for taking a long vacation ... I have found the root cause of this issue for these two boards, and I would provide the patch later. This issue only exists in native ide and legacy ide mode, there is one patch which forces the the legacy ide mode to ahci at booting, but it does not force it back to ahci after resume from s3. So the system is in AHCI mode before suspend to ram, but it is in ide mode after resume from s3 because BIOS would reset the system to ide mode at the beginning of resume, now the hard disk cannot be detected. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:30

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c75 --- Comment #75 from henry su 2008-02-13 01:30:36 MST --- Created an attachment (id=194595) --> (https://bugzilla.novell.com/attachment.cgi?id=194595) patch to fix this issue this patch has been ACKed by jeff, will be upsteamed soon. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:32

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c76 --- Comment #76 from henry su 2008-02-13 01:32:10 MST --- Hi Pavel, Could you please help us verify if the patch fix this issue, I already verified it on my own side, thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11:39

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c77 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|henry.su@amd.com |teheo@novell.com --- Comment #77 from Thomas Renninger 2008-02-13 04:39:02 MST --- Tejun, can you review and take the patch if it's ok. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

23:45

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User joachim.deguara@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c78 --- Comment #78 from Joachim Deguara 2008-02-13 16:45:30 MST --- FYI this has been submitted upstream at: http://marc.info/?l=linux-kernel&m=120193210731753&w=2 actually from that thread it is waiting on Greg KH's approval after it got ACKed by Jeff Garzik -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

14 Feb 14 Feb

00:57

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c79 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|teheo@novell.com | --- Comment #79 from Tejun Heo 2008-02-13 17:57:09 MST --- Yeah, looks good to me. Committing to SL103 and HEAD. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

18 Feb 18 Feb

19:28

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User joachim.deguara@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c81 --- Comment #81 from Joachim Deguara 2008-02-18 12:28:03 MST --- Would this be something to consider for SLED 10 SP2? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

21 Feb 21 Feb

02:10

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c82 --- Comment #82 from Tejun Heo 2008-02-20 19:10:44 MST --- This one will be good for SLED10SP2 but backporting would require backporting PCI_FIXUP_RESUME too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

25 Feb 25 Feb

11:16

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c84 Pavel Machek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|pavel@novell.com | Resolution| |FIXED --- Comment #84 from Pavel Machek 2008-02-25 04:16:28 MST --- I do not think we should (attempt to) fix this in SLES10SP2... it just does not have enough infrastructure. Plus, this probably should be fixed in the BIOS. Ok, I understand this was probably only one of problems on AMD SB[67]* platforms, but this bug got long and tangled, and we got part of this fixed... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

26 Feb 26 Feb

05:15

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User crane.cai@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c85 --- Comment #85 from crane cai 2008-02-25 22:15:21 MST --- PCI_FIXUP_RESUME is not only used by our patch, you can see many in quirk.c source file. I recommend use it. BIOS can't fix it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

29 Feb 29 Feb

06:24

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c88 --- Comment #88 from henry su 2008-02-28 23:24:37 MST --- Hi Pavel, I add the s2ram options(S2RAM_OPTS="-f -a 1") in the config file in /etc/pm, S3 resumes successfully with SUSE 10.3 final, but it failed with SUSE 11.0 Alpha 2 I386. Do you know what the differences between these two OSes, I think the differences would help us find out the root cause. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:39

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c89 --- Comment #89 from Thomas Renninger 2008-02-29 02:39:54 MST --- Henry: Testing suspend with 11.0 Alpha2 makes not that much sense (Pavel knows more about the details), as it is still 2.6.24 based and there have been heavy changes introduced. The next Alpha/Beta will be 2.6.25 based or you can already try out these changes with this kernel: http://ftp.suse.com/pub/projects/kernel/kotd/HEAD/x86_64/kernel-default.rpm (should be 2.6.25.rc3 currently). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

3 Mar 3 Mar

09:53

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User henry.su@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c90 --- Comment #90 from henry su 2008-03-03 02:53:34 MST --- Thomas, I install the kernel rpm from the following location: http://ftp.suse.com/pub/projects/kernel/kotd/HEAD/i386/kernel-default.rpm but it failed to boot up with the 2.6.25.rc3 on rs780/sb700 platform,CPU debug code is FF. copy from dmesg: ---------------------------- Linux version 2.6.24-6-default (geeko@buildhost) (gcc version 4.3.0 20080131 (experimental) [trunk revision 131976] (SUSE Linux) ) #1 SMP 2008/01/31 14:27:52 UTC BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f400 (usable) BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000006ffb0000 (usable) BIOS-e820: 000000006ffb0000 - 000000006ffbe000 (ACPI data) BIOS-e820: 000000006ffbe000 - 000000006ffe0000 (ACPI NVS) BIOS-e820: 000000006ffe0000 - 000000006ffee000 (reserved) BIOS-e820: 000000006fff0000 - 0000000070000000 (reserved) ...... virtual kernel memory layout: fixmap : 0xffdf2000 - 0xfffff000 (2100 kB) pkmap : 0xff800000 - 0xffc00000 (4096 kB) vmalloc : 0xf8800000 - 0xff7fe000 ( 111 MB) lowmem : 0xc0000000 - 0xf8000000 ( 896 MB) .init : 0xc041c000 - 0xc0457000 ( 236 kB) .data : 0xc02e43bc - 0xc04158e4 (1221 kB) .text : 0xc0100000 - 0xc02e43bc (1936 kB I will try to build the 2.6.25.rc3 with the source code. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

7 Mar 7 Mar

11:03

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c91 --- Comment #91 from Thomas Renninger 2008-03-07 04:03:35 MST --- I tried with a SB700 chipset on an HP phenom workstation. I used the latest kernel (2.6.25-rc4-git1 with SUSE x86_64 default .config) s2ram works again with: s2ram -s -f -p But ps2 keyboard is not functional afterwards. Any ideas? USB keyboard, mouse works fine, attaching afterwards or if already attached before suspending (maybe just your PS2 keyboard does not work anymore?). But I used a x86_64 kernel, maybe this is a arch specific problem you see? Hmm, also your kernel seems not to be a 2.6.25 based one: 2.6.24-6-default? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:04

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345124#c92 --- Comment #92 from Thomas Renninger 2008-03-07 09:04:48 MST --- BTW: Seife told me to use -m instead of -s that would be: "s2ram -f -p -m" It seems to be a bit faster: -s, --vbe_save: save VBE state before suspending and restore after resume. -m, --vbe_mode: get VBE mode before suspend and set it after resume (from: http://en.opensuse.org/S2ram) The one stores the whole state, the other only the mode? Works fine here. Hmm, I wonder whether the PS2 keyboard broke away on my tests because I used no_console_suspend which might have influence the SuperIO chip where serial, ps2 and others are connected to. I cannot test it right now, just for info. We really need to figure out how to wake up graphics without whitelisting... If it really needs bigger in-kernel graphics access support, I wonder whether this could be achieved for SLES11? It hurts so much, that most machines would just work, but like that none is working out of the box, everything needs whitelisting... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

21 Mar 21 Mar

03:24

New subject: [Bug 345124] S3 failed on AMD SB600/SB700+RS690/RS780 platform

https://bugzilla.novell.com/show_bug.cgi?id=345124 Shane Huang changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |372857 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

5881

Age (days ago)

5993

Last active (days ago)

List overview

Download

85 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 345124] New: S3 failed on AMD SB600/SB700+RS690/RS780 platform

tags

participants (1)