On Fri 2019-04-26 07:58:49, Bart Van Assche wrote:
> On Fri, 2019-04-26 at 12:32 +0200, Pavel Machek wrote:
> > [detached HEAD 916db0d] Revert "scsi: sd: Inline sd_probe_part2()"
> > 1 file changed, 58 insertions(+), 43 deletions(-)
> > pavel@duo:/data/l/linux-next-32$ git revert
> >
On Fri, 2019-04-26 at 12:32 +0200, Pavel Machek wrote:
> [detached HEAD 916db0d] Revert "scsi: sd: Inline sd_probe_part2()"
> 1 file changed, 58 insertions(+), 43 deletions(-)
> pavel@duo:/data/l/linux-next-32$ git revert
> 21e6ba3f0e0257cce1a226c1f15e0a8ba4338ca3
> Editing file:
On Thu 2019-04-25 06:35:58, Bart Van Assche wrote:
> On 4/25/19 12:33 AM, Pavel Machek wrote:
> > On Wed 2019-04-24 13:56:01, Bart Van Assche wrote:
> >> On Wed, 2019-04-24 at 22:51 +0200, Pavel Machek wrote:
> >>> Unfortunately, that one does not revert cleanly on top of -next.
> >>
> >> Can you
On 4/25/19 12:33 AM, Pavel Machek wrote:
> On Wed 2019-04-24 13:56:01, Bart Van Assche wrote:
>> On Wed, 2019-04-24 at 22:51 +0200, Pavel Machek wrote:
>>> Unfortunately, that one does not revert cleanly on top of -next.
>>
>> Can you try the following:
>>
>> git revert
On Wed 2019-04-24 13:56:01, Bart Van Assche wrote:
> On Wed, 2019-04-24 at 22:51 +0200, Pavel Machek wrote:
> > Unfortunately, that one does not revert cleanly on top of -next.
>
> Can you try the following:
>
> git revert d16ece577bf2cee7f94bab75a0d967bcb89dd2a7 &&
> git revert
On Wed, 2019-04-24 at 12:17 +0200, Pavel Machek wrote:
> On Tue 2019-04-23 07:09:42, Bart Van Assche wrote:
> > On 4/23/19 3:22 AM, Pavel Machek wrote:
> > > > > It boots ok (unlike mainline -- I'm debugging that), and I can suspend
> > > > > and resume... but then cursor in X is moving and I can
On Wed, 2019-04-24 at 22:51 +0200, Pavel Machek wrote:
> Unfortunately, that one does not revert cleanly on top of -next.
Can you try the following:
git revert d16ece577bf2cee7f94bab75a0d967bcb89dd2a7 &&
git revert 21e6ba3f0e0257cce1a226c1f15e0a8ba4338ca3
I will see whether I can come up with
On Wed 2019-04-24 22:48:32, Pavel Machek wrote:
> Hi!
>
> > Not block, but it seems scsi subsystem is:
>
> commit 21e6ba3f0e0257cce1a226c1f15e0a8ba4338ca3
> Author: Bart Van Assche
> Date: Wed Mar 20 13:09:19 2019 -0700
>
> scsi: sd: Rely on the driver core for asynchronous probing
>
>
Hi!
> Not block, but it seems scsi subsystem is:
commit 21e6ba3f0e0257cce1a226c1f15e0a8ba4338ca3
Author: Bart Van Assche
Date: Wed Mar 20 13:09:19 2019 -0700
scsi: sd: Rely on the driver core for asynchronous probing
As explained during the 2018 LSF/MM session about increasing SCSI
On Wed 2019-04-24 12:48:50, Pavel Machek wrote:
> On Wed 2019-04-24 11:54:31, Pavel Machek wrote:
> > On Tue 2019-04-23 07:55:05, Jens Axboe wrote:
> > > On 4/23/19 4:22 AM, Pavel Machek wrote:
> > > > Hi!
> > > >
> > > >>> It boots ok (unlike mainline -- I'm debugging that), and I can suspend
>
On Wed 2019-04-24 11:54:31, Pavel Machek wrote:
> On Tue 2019-04-23 07:55:05, Jens Axboe wrote:
> > On 4/23/19 4:22 AM, Pavel Machek wrote:
> > > Hi!
> > >
> > >>> It boots ok (unlike mainline -- I'm debugging that), and I can suspend
> > >>> and resume... but then cursor in X is moving and I can
On Tue 2019-04-23 07:09:42, Bart Van Assche wrote:
> On 4/23/19 3:22 AM, Pavel Machek wrote:
> >>> It boots ok (unlike mainline -- I'm debugging that), and I can suspend
> >>> and resume... but then cursor in X is moving and I can talk to
> >>> applications cached in memory, but any access to disk
On Tue 2019-04-23 07:55:05, Jens Axboe wrote:
> On 4/23/19 4:22 AM, Pavel Machek wrote:
> > Hi!
> >
> >>> It boots ok (unlike mainline -- I'm debugging that), and I can suspend
> >>> and resume... but then cursor in X is moving and I can talk to
> >>> applications cached in memory, but any access
On Tue 2019-04-23 07:55:05, Jens Axboe wrote:
> On 4/23/19 4:22 AM, Pavel Machek wrote:
> > Hi!
> >
> >>> It boots ok (unlike mainline -- I'm debugging that), and I can suspend
> >>> and resume... but then cursor in X is moving and I can talk to
> >>> applications cached in memory, but any access
On 4/23/19 3:22 AM, Pavel Machek wrote:
>>> It boots ok (unlike mainline -- I'm debugging that), and I can suspend
>>> and resume... but then cursor in X is moving and I can talk to
>>> applications cached in memory, but any access to disk hangs.
>>
>> Mainline problem was identified.
>>
>> But
On 4/23/19 4:22 AM, Pavel Machek wrote:
> Hi!
>
>>> It boots ok (unlike mainline -- I'm debugging that), and I can suspend
>>> and resume... but then cursor in X is moving and I can talk to
>>> applications cached in memory, but any access to disk hangs.
>>
>> Mainline problem was identified.
>>
Hi!
> > It boots ok (unlike mainline -- I'm debugging that), and I can suspend
> > and resume... but then cursor in X is moving and I can talk to
> > applications cached in memory, but any access to disk hangs.
>
> Mainline problem was identified.
>
> But resume is still broken. I took
17 matches
Mail list logo
