screen rotates to portrait sometimes

Bug #1070755 reported by Jani Monoses on 2012-10-24
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
ubuntu-nexus7
Low
Sean Feole

Bug Description

Using image 22-0 but I saw this happen earlier.
This time it happened because I plugged the power cable in the almost discharged device.
It went into suspend, and on resume it came up in portrait mode with input still in landscape.

Alex Chiang (achiang) on 2012-10-24
Changed in newark:
importance: Undecided → Low
Chris Wayne (cwayne18) wrote :

Cannot reproduce this

Changed in newark:
status: New → Incomplete
Matt Fischer (mfisch) wrote :

Scott Sweeny just repro'd this.

Changed in newark:
status: Incomplete → Confirmed
information type: Proprietary → Public
affects: newark → ubuntu-nexus7
Matt Fischer (mfisch) on 2012-11-05
tags: added: mobile needs-upstream nexus7
Bryce Harrington (bryce) wrote :

This sounds like a bug in the video driver. Probably should be escalated to nvidia, although they'll likely want a more defined set of steps to reproduce.

Bryce Harrington (bryce) on 2012-11-08
tags: added: tegra3
Sean Feole (sfeole) wrote :

Agreed with comment #3, from past experience with nvidia we should have a clear and concise list to reproduce this before filing a bug with upstream. Along with any valuable logs/data

Bryce Harrington (bryce) wrote :

The fact that display gets rotated but not input makes me think it's some flaw in the tegra3 driver's RANDR handling on resume. If this were on an open source driver, I'd suggest switching on DRI debug flags so we could detect if RANDR events are getting triggered on suspend, however I don't know if tegra provides that debug data in any form. It does not look like there are xorg.conf debugging options that would help.

gnome-power-manager on the other hand does have log data available. If someone can turn that on, reproduce this issue and then collect and attach that log here, it might give some clues.

It would also be interesting to see whether this can be triggered just by ordinary suspend/resume cycles or if it depends on the battery level and/or cord plugging. The g-p-m log might answer that. Or perhaps manually suspend/resume (via pm-suspend I guess?) and experiment with the power cord until you find a reliable reproducer.

Sean Feole (sfeole) wrote :

will try to reproduce and gather data

Changed in ubuntu-nexus7:
assignee: nobody → Sean Feole (sfeole)
Sean Feole (sfeole) wrote :

This problem has also been seen in Raring 13.04, Please see bug# 1088741 .

Richard Johnson (rajid) wrote :

I was asked to post my experience with this bug (when I posted 1088741). Unfortunately, I haven't been able to reproduce it. It seemed to have something to do with moving (not removing, just moving) the power connector during the time when the system was coming up. It happened twice but I haven't been able to get it to happen again. Probably it's some type of hardware falt due to the slight power glitch as the system comes off external power and then back on again, but seems to only be an issue as it's starting up. (Definitely not as important of a problem as the "button1 stuck" problem!)

Alex Chiang (achiang) on 2013-01-28
tags: added: sensors
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers