I can do the testing you requested over the next few days.
Can I suggest I start with kernels 3.2.0.10 vs 3.4, since I know that
some time during kernel 3.2 development suspend/resume started working
properly (see bug#863969, comment on 25 Jan 2012, kernel 3.2.0.10.10).
Kernel 3.4.4, in archlinux at the moment, doesn't work, so it might be
good to work backwards from there.
Or to work forwards from early 3.2 kernels to see what happened to fix it?
regards
Peter Hayward
I can do the testing you requested over the next few days.
Can I suggest I start with kernels 3.2.0.10 vs 3.4, since I know that
some time during kernel 3.2 development suspend/resume started working
properly (see bug#863969, comment on 25 Jan 2012, kernel 3.2.0.10.10).
Kernel 3.4.4, in archlinux at the moment, doesn't work, so it might be
good to work backwards from there.
Or to work forwards from early 3.2 kernels to see what happened to fix it?
regards
Peter Hayward
On 16 July 2012 19:04, Joseph Salisbury <email address hidden> wrote: kernel. ubuntu. com/~kernel- ppa/mainline/ v3.4-quantal/ kernel. ubuntu. com/~kernel- ppa/mainline/ v3.5-rc1- quantal/ bugzilla. kernel. org/show_ bug.cgi? id=44851 bugzilla. kernel. org/show_ bug.cgi? id=44851 /bugs.launchpad .net/bugs/ 1024507 /bugs.launchpad .net/linux/ +bug/1024507/ +subscriptions
> I'd like to perform a kernel bisect to identify the commit that caused
> this regression. Would it be possible for you to assist by testing some
> kernels? If so, we need to first identify the kernel version that
> introduce the regression, then we can bisect down to the actual commit.
>
> Can you start by testing the following kernels:
>
> v3.4 final: http://
> v3.5-rc1: http://
>
> ** Bug watch added: Linux Kernel Bug Tracker #44851
> http://
>
> ** Also affects: linux via
> http://
> Importance: Unknown
> Status: Unknown
>
> ** Tags added: performing-bisect
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> 12.10 quantal boots to black screen on iMac
>
> To manage notifications about this bug go to:
> https:/