Summary: | [HSW ULT]Resume from S3 result in system reboot, with warm boot | ||
---|---|---|---|
Product: | DRI | Reporter: | cancan,feng <cancan.feng> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | CLOSED NOTOURBUG | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | major | ||
Priority: | high | CC: | cancan.feng, przanoni, yangweix.shui |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
cancan,feng
2013-05-22 09:58:01 UTC
We seem to have a pile of "hsw ult only" bugs. Are those all on the same machine? Paulo can you please confirm whether this is supposed to work on ult or not (I don't have a machine myself to test)? (In reply to comment #1) > We seem to have a pile of "hsw ult only" bugs. Are those all on the same > machine? > No, they don't seem to happen on the same machine. To this issue, it happens on machine which info followed: HSW ULT: C0 stepping 1 (id=0x0a26, rev 09),cpu MHz:1400 GT3(0x20) 1100MHz I also tested it on another hsw ult machine, but can't reproduce, which info followed: HSW ULT: B0 stepping (id=0x0a16, rev 03), CPU 0.80GHz, GT2(0x10) 600MHz; > Paulo can you please confirm whether this is supposed to work on ult or not > (I don't have a machine myself to test)? By the way, when I removed i915 and retested it, this issue still there. (In reply to comment #2) > (In reply to comment #1) > > We seem to have a pile of "hsw ult only" bugs. Are those all on the same > > machine? > > > > No, they don't seem to happen on the same machine. To this issue, it happens > on machine which info followed: > HSW ULT: C0 stepping 1 (id=0x0a26, rev 09),cpu MHz:1400 GT3(0x20) 1100MHz > > I also tested it on another hsw ult machine, but can't reproduce, which info > followed: > HSW ULT: B0 stepping (id=0x0a16, rev 03), CPU 0.80GHz, GT2(0x10) 600MHz; > Could this be related with the BIOS version? What's the BIOS version of the machine that doesn't work? > > Paulo can you please confirm whether this is supposed to work on ult or not > > (I don't have a machine myself to test)? The C stepping ULT machine I have here suspends and resumes fine (S3) on today's drm-intel-next-queued. > By the way, when I removed i915 and retested it, this issue still there. Instead of "removing" i915, what happens if you completely blacklist i915 (i.e., never load it)? If the problem still happens, then it's not the fault of the graphics driver. (In reply to comment #4) > (In reply to comment #2) > > (In reply to comment #1) > > > We seem to have a pile of "hsw ult only" bugs. Are those all on the same > > > machine? > > > > > > > No, they don't seem to happen on the same machine. To this issue, it happens > > on machine which info followed: > > HSW ULT: C0 stepping 1 (id=0x0a26, rev 09),cpu MHz:1400 GT3(0x20) 1100MHz > > > > I also tested it on another hsw ult machine, but can't reproduce, which info > > followed: > > HSW ULT: B0 stepping (id=0x0a16, rev 03), CPU 0.80GHz, GT2(0x10) 600MHz; > > > > Could this be related with the BIOS version? What's the BIOS version of the > machine that doesn't work? Here is the current BIOS information: BIOS Version HSWLPTU1.86C.0114.R07.1303182216 I will upgrade the BIOS version to verify whether if this is related with BIOS version. > > > > > Paulo can you please confirm whether this is supposed to work on ult or not > > > (I don't have a machine myself to test)? > > The C stepping ULT machine I have here suspends and resumes fine (S3) on > today's drm-intel-next-queued. Did you warm boot the machine to test suspend and resume? Because this issue only happens with warm boot a machine.. > > > > By the way, when I removed i915 and retested it, this issue still there. > > Instead of "removing" i915, what happens if you completely blacklist i915 > (i.e., never load it)? If the problem still happens, then it's not the fault > of the graphics driver. Yeah, I tried again with completely blacklist i915, the problem still happens..So, maybe this is not our bug. Paulo implied that USB might be part of the problem. Can you please try out what happens with a kernel without any usb support enabled (i.e. CONFIG_USB=n)? (In reply to comment #7) > Paulo implied that USB might be part of the problem. Can you please try out > what happens with a kernel without any usb support enabled (i.e. > CONFIG_USB=n)? I'd try a newer BIOS first. decreasing severity as this is likely not our driver bug. (In reply to comment #8) > (In reply to comment #7) > > Paulo implied that USB might be part of the problem. Can you please try out > > what happens with a kernel without any usb support enabled (i.e. > > CONFIG_USB=n)? > > I'd try a newer BIOS first. Upgrade BIOS to 128.00, upgrade KSC to 1.13, now S3 can resume successfully. So can we close this bug? Yeah, I think so. 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.