Bug 197805
Summary: | 4.14.0-rc8 - Oops - EIP: __blk_rq_unmap_user - unable to handle kernel paging request | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | newsmails |
Component: | Serial ATA | Assignee: | Tejun Heo (tj) |
Status: | NEW --- | ||
Severity: | normal | ||
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 4.14.0-rc8 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
lspci
syslog trace |
Created attachment 260543 [details]
syslog trace
Idem with all next kernels. And now with 4.14.3. The problem occurs often when I do "lilo -v" after compiling a kernel. Maybe important :a script does the following at start (powertop advice) : echo "sata power management" echo 'min_power' > '/sys/class/scsi_host/host0/link_power_management_policy'; echo 'min_power' > '/sys/class/scsi_host/host1/link_power_management_policy'; echo 'min_power' > '/sys/class/scsi_host/host2/link_power_management_policy'; echo 'min_power' > '/sys/class/scsi_host/host3/link_power_management_policy'; Idem on 4.14.4 It is always the same address 6b6b6b7b. BUG: unable to handle kernel paging request at 6b6b6b7b surprising to still see this so old and reproducible bug... It occurs again when doing lilo -v after compiling 4.14.10 |
Created attachment 260541 [details] lspci cpu : Skylake i3 6100H Distribution : slackware 14.2 32 bits I attach : - lspci - syslog trace