On Thu, Aug 02, 2018 at 07:15:30AM +0800, Ming Lei wrote:
> I just checked my daily test log, looks this issue is reported 1st time
> on next-20180731.
>From the diff between next-20180727 and next-20180731 in drivers/scsi
nothing really sticks out.
$ PAGER= git diff --stat
On Wed, Aug 01, 2018 at 02:06:11PM +0200, Johannes Thumshirn wrote:
> On Wed, Aug 01, 2018 at 08:00:44PM +0800, Ming Lei wrote:
> > On Wed, Aug 01, 2018 at 07:52:19PM +0800, Ming Lei wrote:
> > > On Wed, Aug 01, 2018 at 12:24:00PM +0100, Matt Hart wrote:
> > > > On 1 August 2018 at 11:59, Mark
On Wed, Aug 01, 2018 at 02:50:40PM +0100, Guillaume Tucker wrote:
>
> Sure, although it didn't make any apparent difference, still on
> next-20180731:
>
> https://lava.collabora.co.uk/scheduler/job/1215417
>
> The .config file I used is available here, with just
> CONFIG_BLK_DEV_RAM=y on
On 01/08/18 13:40, Johannes Thumshirn wrote:
On Wed, Aug 01, 2018 at 01:37:17PM +0100, Guillaume Tucker wrote:
The kernel images I used have the git revision in their file name
to make it clear where they came from, they were built with
x86_64_defconfig. The links to the kernel and ramdisks
On 01/08/18 12:25, Johannes Thumshirn wrote:
On Wed, Aug 01, 2018 at 11:59:19AM +0100, Mark Brown wrote:
On Wed, Aug 01, 2018 at 06:51:09PM +0800, Ming Lei wrote:
You may have to provide some clue, such as dmesg log, boot disk, ...
I guess you don't use virtio-scsi/virtio-blk since both
On Wed, Aug 01, 2018 at 08:00:44PM +0800, Ming Lei wrote:
> On Wed, Aug 01, 2018 at 07:52:19PM +0800, Ming Lei wrote:
> > On Wed, Aug 01, 2018 at 12:24:00PM +0100, Matt Hart wrote:
> > > On 1 August 2018 at 11:59, Mark Brown wrote:
> > > > On Wed, Aug 01, 2018 at 06:51:09PM +0800, Ming Lei wrote:
On Wed, Aug 01, 2018 at 07:52:19PM +0800, Ming Lei wrote:
> On Wed, Aug 01, 2018 at 12:24:00PM +0100, Matt Hart wrote:
> > On 1 August 2018 at 11:59, Mark Brown wrote:
> > > On Wed, Aug 01, 2018 at 06:51:09PM +0800, Ming Lei wrote:
> > >
> > >> You may have to provide some clue, such as dmesg
On Wed, Aug 01, 2018 at 07:52:21PM +0800, Ming Lei wrote:
> On Wed, Aug 01, 2018 at 12:24:00PM +0100, Matt Hart wrote:
> > On 1 August 2018 at 11:59, Mark Brown wrote:
> > > On Wed, Aug 01, 2018 at 06:51:09PM +0800, Ming Lei wrote:
> > >
> > >> You may have to provide some clue, such as dmesg
On Wed, Aug 01, 2018 at 12:24:00PM +0100, Matt Hart wrote:
> On 1 August 2018 at 11:59, Mark Brown wrote:
> > On Wed, Aug 01, 2018 at 06:51:09PM +0800, Ming Lei wrote:
> >
> >> You may have to provide some clue, such as dmesg log, boot disk, ...
> >
> >> I guess you don't use
On Wed, Aug 01, 2018 at 12:24:00PM +0100, Matt Hart wrote:
> And a full LAVA boot log from my lab
> http://lava.streamtester.net/scheduler/job/138067
>
> QEMU command line here:
> http://lava.streamtester.net/scheduler/job/138067#L75
>
> And a LAVA job definition, which includes the url of the
On Wed, Aug 01, 2018 at 11:59:19AM +0100, Mark Brown wrote:
> On Wed, Aug 01, 2018 at 06:51:09PM +0800, Ming Lei wrote:
>
> > You may have to provide some clue, such as dmesg log, boot disk, ...
>
> > I guess you don't use virtio-scsi/virtio-blk since both run at blk-mq
> > mode at default, even
On 1 August 2018 at 11:59, Mark Brown wrote:
> On Wed, Aug 01, 2018 at 06:51:09PM +0800, Ming Lei wrote:
>
>> You may have to provide some clue, such as dmesg log, boot disk, ...
>
>> I guess you don't use virtio-scsi/virtio-blk since both run at blk-mq
>> mode at default, even though without
On Wed, Aug 01, 2018 at 06:51:09PM +0800, Ming Lei wrote:
> You may have to provide some clue, such as dmesg log, boot disk, ...
> I guess you don't use virtio-scsi/virtio-blk since both run at blk-mq
> mode at default, even though without d5038a13eca72fb.
Boot logs and so on can be found here:
On Wed, Aug 01, 2018 at 11:33:03AM +0100, Mark Brown wrote:
> On Wed, Aug 01, 2018 at 11:05:36AM +0100, Guillaume Tucker wrote:
> > On 31/07/18 16:14, kernelci.org bot wrote:
>
> > > Boot Regressions Detected:
> > [...]
> > > x86:
> > >
> > > x86_64_defconfig:
> > > qemu:
> > >
On Wed, Aug 01, 2018 at 11:05:36AM +0100, Guillaume Tucker wrote:
> On 31/07/18 16:14, kernelci.org bot wrote:
> > Boot Regressions Detected:
> [...]
> > x86:
> >
> > x86_64_defconfig:
> > qemu:
> > lab-baylibre: failing since 1 day (last pass: next-20180727 -
> >
On 31/07/18 16:14, kernelci.org bot wrote:
next/master boot: 179 boots: 11 failed, 167 passed with 1 offline
(next-20180731)
Full Boot Summary:
https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20180731/
Full Build Summary:
16 matches
Mail list logo
