Bug#895378: sky2: sky2: did not recover correctly after waking up from S3

To: Manuel Bilderbeek <Manuel.Bilderbeek@gmail.com>
Cc: Laurent Bigonville <bigon@debian.org>, 895378@bugs.debian.org
Subject: Bug#895378: sky2: sky2: did not recover correctly after waking up from S3
From: Salvatore Bonaccorso <carnil@debian.org>
Date: Sun, 23 May 2021 14:58:36 +0200
Message-id: <[🔎] YKpRfH91kvejNMy4@eldamar.lan>
Reply-to: Salvatore Bonaccorso <carnil@debian.org>, 895378@bugs.debian.org
In-reply-to: <153950889213.3295.10687981331214316023.reportbug@fornost.bigon.be>
References: <152338908290.5816.2884078835707892274.reportbug@sonata> <153950889213.3295.10687981331214316023.reportbug@fornost.bigon.be> <152338908290.5816.2884078835707892274.reportbug@sonata>

Control: tags -1 + moreinfo

Hi,

On Sun, Oct 14, 2018 at 11:21:32AM +0200, Laurent Bigonville wrote:
> Source: linux
> Version: 4.18.10-2
> Followup-For: Bug #895378
> 
> Hi,
> 
> I can confirm this (and it's quite annoying).
> 
> It worked fine in 4.14 and it's broken since 4.15.
> 
> I'm trying to bissect the kernel but it is not even booting ("32-bits
> relocation outside of the kernel) and I'm not too sure how to fix that.

Is this still an issue with a recent kernel?

Regards,
Salvatore

Reply to:

Follow-Ups:
- Bug#895378: sky2: sky2: did not recover correctly after waking up from S3
  - From: Manuel Bilderbeek <manuel.bilderbeek@gmail.com>

Prev by Date: Processed: Re: Bug#895378: sky2: sky2: did not recover correctly after waking up from S3
Next by Date: Bug#895895: marked as done (linux-image-4.15.0-2-amd64: shutdown, suspend operations do not work)
Previous by thread: Bug#894542: marked as done (Bluetooth: hci0: command 0x1009 tx timeout)
Next by thread: Processed: Re: Bug#895378: sky2: sky2: did not recover correctly after waking up from S3
Index(es):
- Date
- Thread