| Summary: | [Baytrail-M] system can't resume from S3/S4 | ||
|---|---|---|---|
| Product: | DRI | Reporter: | kobeqin <kobe.qin> |
| Component: | DRM/Intel | Assignee: | Jesse Barnes <jbarnes> |
| Status: | CLOSED NOTOURBUG | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | blocker | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
kobeqin
2013-08-04 05:52:35 UTC
There is no information here... Nothing at all to suggest that this is a i915 issue. Attach the dmesg. Check whether the system can suspend and resume without ever loading i915. Jesse is the Batrail owner. We try to add nomodeset, but enter to system and lsmod, i915 still listed. rmmod i915 and this bug still can duplicate. Since i915.ko will not load on Baytrail-M if nomodeset is set, I think something went wrong in testing. (In reply to comment #4) > Since i915.ko will not load on Baytrail-M if nomodeset is set, I think > something went wrong in testing. Adding nomodeset to grub, i915 is listed by lsmod, but used by "0", does it mean that i915 doesn't load? And S3/S4 still can't resume after adding nomodeset Please attach the dmesg. (In reply to comment #6) > Please attach the dmesg. Jani, after entering to S3 or S4, system can't resume anymore. We try to use mincom to print,but it can't work on baytrail-M, do you have any instruction? Jani,due to long time no response, I have written an email to you and have to change the status to NEW until we can carry out a solution to get dmesg or a log from COM port. First things first, please let's make sure you're not loading i915. What kernel parameters are you using? What values do you have for CONFIG_DRM_I915_KMS and CONFIG_VGA_CONSOLE kernel config options? i915.modeset=0 should trump all other options, and should prevent i915 from loading. If you can still reproduce the bug *without* i915 loaded, it's NOTOURBUG. Hmm, might be you need to give a bogus parameter to i915 to prevent it from loading, e.g. i915.foobar (In reply to comment #10) > Hmm, might be you need to give a bogus parameter to i915 to prevent it from > loading, e.g. i915.foobar Disregard that, supposedly this doesn't work anymore since 3.11. (In reply to comment #9) > First things first, please let's make sure you're not loading i915. What > kernel parameters are you using? What values do you have for > CONFIG_DRM_I915_KMS and CONFIG_VGA_CONSOLE kernel config options? > > i915.modeset=0 should trump all other options, and should prevent i915 from > loading. > > If you can still reproduce the bug *without* i915 loaded, it's NOTOURBUG. We have added i915.modeset=0, S3/S4 still can't resume. NOTOURBUG. I'm afraid I don't know who the owner would be, though. As Jani said, it's not our bug after we verified w/o i915. Closing old verified. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.