Re: linux-next: Tree for May 22

[Rafael J. Wysocki]

On Thursday, 22 of May 2008, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since next-20080522:
> 
> The three patches reverted from the driver-core tree yesterday have been
> removed from there.
> 
> The net tree (actually the wireless tree) had a trivial conflict with the
> wireless-current tree.
> 
> One of the sound tree build patches has been merged.
> 
> The semaphore-removal tree still needed three patches reverted because similar
> patches were merged into upstream and the scsi-rc-fixes trees.
> 
> The bkl-removal tree had a conflict with the arm tree because the arm
> tree removed a file that was changed.
> 
> I have applied the following temporary patch for known build problems:
> 
> 	"Fix various 8390 builds" - the net tree broke builds on various
> architectures - hopefully this patch will go into the net tree shortly.
> 	"build failure with netfilter on __nf_ct_helper_find()" - breakage
> due to the moving of stuff from list.h to rculist.h

This one and the previous linux-next can't resume from suspend to RAM on my
HP nx6325.  The problem is reliably reproducible 100% of the time.

The patch that causes it to happen, as identified by bisection, is:

commit 3dcefa9419f3b8a49921d2218c93a3ddba8e0855
Author: Bartlomiej Zolnierkiewicz <bzolnier@xxxxxxxxx>
Date:   Thu May 22 10:40:19 2008 +1000

    ide: use __generic_unplug_device() in ide_do_drive_cmd()

    Cc: FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx>
    Cc: Borislav Petkov <petkovbb@xxxxxxxxx>
    Cc: Jens Axboe <jens.axboe@xxxxxxxxxx>
    Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@xxxxxxxxx>

Reverting it along with the next IDE patches (up to and including
commit fd42e6df0fd163411f5c655b4bde4fb6a8910edc
"ide: remove action argument in ide_do_drive_cmd") makes the problem go away.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/