Answering myself.
On Sat, Dec 29, 2012 at 11:58 AM, Mathieu Malaterre <ma...@debian.org> wrote:
> On Sat, Dec 29, 2012 at 12:46 AM, Ben Hutchings <b...@decadent.org.uk> wrote:
>> On Thu, 2012-12-27 at 18:03 +0100, Mathieu Malaterre wrote:
>>> found 644174 3.7.1-1~experimental.1
>>> thanks
>>>
>>> I could reproduce the issue with latest kernel. Thx
>>
>> You never answered Jonathan's last questions:
>
> Ooops !
>
>>> Hm. Mathieu, is it possible to suspend-to-disk ("echo disk
>>> >/sys/power/state")
>>> and resume with a USB device plugged into the USB 3.0 port?
>
> Indeed this works flawlessly. Went to shell typed:
>
> $ sudo su -
> # echo disk >/sys/power/state
>
> Waited until the cursor fade away. Computer automatically turned off.
> Switched USB mouse from USB 2.0 port to USB 3.0. Turned on, no issue !
> Mouse was working as should from USB 3.0 port.
>
>>> Please also attach output from "acpidump" after a successful boot.
>
> Attached.
>
>>> Can you reproduce this when booting in recovery mode with
>>> i915.modeset=0 appended to the kernel command line?
>
> See result.jpg. The message (at least the last line) really looks like
> what I get when booting in recovery mode.
>
> Steps:
> - Sytem > Shut down > Restart
> From GRUB menu:
> - select second line (recovery on a 3.2 bpo kernel)
> - 'e'
> - select line with "ro single"
> - appended "915.modeset=0" right after the 'single' word (space separated).
If I append "i915.modeset=0" then everything is fine on my side.,
sorry for the typo.
Thanks
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
