On Sun, 29 Jul 2018 11:52:10 +0200 Tomas Janousek wrote:
> Hi Julian,
>
> On Fri, Jul 27, 2018 at 09:31:42PM +1000, Julian Calaby wrote:
> > > Does adding the kernel parameter "ahci.mobile_lpm_policy=1" avoid
this?
> >
> > No, booting with that parameter makes no difference.
>
> Can you try
On Tue, Jul 31, 2018 at 01:40:45AM +0900, YOSHINO Yoshihito wrote:
> I have the same problem.
> Setting "dm_mod.use_blk_mq=0 scsi_mod.use_blk_mq=0" works well.
>
FWIW, same here on Dell Latitude 5580.
# cat /sys/bus/scsi/devices/2\:0\:0\:0/model
SAMSUNG SSD PM87
# cat
Hi Tomas,
On Sun, Jul 29, 2018 at 7:52 PM Tomas Janousek wrote:
>
> Hi Julian,
>
> On Fri, Jul 27, 2018 at 09:31:42PM +1000, Julian Calaby wrote:
> > > Does adding the kernel parameter "ahci.mobile_lpm_policy=1" avoid this?
> >
> > No, booting with that parameter makes no difference.
>
> Can you
Package: src:linux
Followup-For: Bug #904441
Dear Maintainer,
I have the same problem.
Setting "dm_mod.use_blk_mq=0 scsi_mod.use_blk_mq=0" works well.
$ cat /sys/bus/scsi/devices/0\:0\:0\:0/model
APPLE SSD TS0128
$ cat /sys/bus/scsi/devices/0\:0\:0\:0/rev
0219
Regards,
--
YOSHINO Yoshihito
Hi again,
On Sun, Jul 29, 2018 at 11:52:10AM +0200, Tomas Janousek wrote:
> Unfortunately, the above code doesn't prevent laptop-mode-tools, tlp nor
> custom udev rules from enabling runtime-pm for devices so if you use any of
> that, you might be having runtime-pm enabled on devices that don't
Hi Julian,
On Fri, Jul 27, 2018 at 09:31:42PM +1000, Julian Calaby wrote:
> > Does adding the kernel parameter "ahci.mobile_lpm_policy=1" avoid this?
>
> No, booting with that parameter makes no difference.
Can you try "dm_mod.use_blk_mq=0 scsi_mod.use_blk_mq=0" as well?
Block multiqueue was
Package: src:linux
Version: 4.17.8-1
Followup-For: Bug #904441
Dear Maintainer,
Same issue here; 4.16.0-2-amd64 works fine; ahci.mobile_lpm_policy=1
does not help.
$ cat /sys/bus/scsi/devices/0\:0\:0\:0/model
ST9500325ASG
$ cat /sys/bus/scsi/devices/0\:0\:0\:0/rev
APM1
Happy to help debug
Hi Ben,
On Wed, Jul 25, 2018 at 2:23 AM Ben Hutchings wrote:
>
> Control: tag -1 moreinfo
>
> On Tue, 2018-07-24 at 21:25 +1000, Julian Calaby wrote:
> > Package: src:linux
> > Version: 4.17.8-1
> > Severity: important
> >
> > Dear Maintainer,
> >
> > Linux 4.17.0-1-amd64 (4.17.8-1) causes my
Ritesh, you sent this to the list and not the reporter (or the BTS).
Not that it matters, because:
On Thu, 2018-07-26 at 15:42 +0545, Ritesh Raj Sarraf wrote:
[...]
> Are you using any power saving tools ?
> I've seen the same behavior with SATA disks on my machines but it
> happened much
On Tue, 2018-07-24 at 21:25 +1000, Julian Calaby wrote:
> FROM MEMORY, the last disk related messages are:
>
> sda: Synchronising SCSI cache
> sda: Stopping disk
>
> Please note that as I cannot boot that kernel, this bug report was
> compiled on
> 4.16.0-2-amd64 (4.16.16-2) instead.
>
>
Control: tag -1 moreinfo
On Tue, 2018-07-24 at 21:25 +1000, Julian Calaby wrote:
> Package: src:linux
> Version: 4.17.8-1
> Severity: important
>
> Dear Maintainer,
>
> Linux 4.17.0-1-amd64 (4.17.8-1) causes my laptop (Thinkpad X200) to fail to
> boot.
>
> During a boot with Systemd the disk
Processing control commands:
> tag -1 moreinfo
Bug #904441 [src:linux] linux-image-4.17.0-1-amd64: system disk stopped during
boot
Added tag(s) moreinfo.
--
904441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: src:linux
Version: 4.17.8-1
Severity: important
Dear Maintainer,
Linux 4.17.0-1-amd64 (4.17.8-1) causes my laptop (Thinkpad X200) to fail to
boot.
During a boot with Systemd the disk gets stopped erroneously approximately
after udev "coldplugs" anything that hasn't been autodetected
13 matches
Mail list logo