I'm not familiar with kernel mailing list so I don't know why my patch
was ignored. Maybe format of email was not proper, or I send wrong
recipients.
I also updated the patch, so I attach the latest version.
** Patch added:
"0001-Fix-for-initialize-drives-not-capable-to-handle-maxi.patch"
ht
Yes, I have sent the patch, but until today no one answered
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783906
Title:
Linux 4.15 and onwards fails to initialize some hard drives
To manage notifi
I tuned a little a previous patch
** Patch added:
"0001-Fix-for-initialize-drives-not-capable-to-handle-maxi.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783906/+attachment/5264605/+files/0001-Fix-for-initialize-drives-not-capable-to-handle-maxi.patch
--
You received this bu
There is patch to issue I described above
** Patch added:
"0001-libata-Fix-for-initialize-drives-not-capable-to-hand.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783906/+attachment/5264201/+files/0001-libata-Fix-for-initialize-drives-not-capable-to-hand.patch
--
You received
Ok, I find out what happens.
While standard SATA setup, chain of functions is called: ... ->
ata_eh_recover -> ata_eh_reset. If SATA is not initialized, then hard
reset is performed (function ata_do_reset() ).
In both drivers I have, function ata_do_reset() returns 0, even if after
this reset dev
Maybe this conversation should be moved to Linux linux-ide mailing list.
There is some technical decisions to make and may it's better to consult
it with other developers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
No, my device doesn't work with 6Gbps. In kernel 4.14 if my drive was
offline, function sata_down_spd_limit() cut down link->sata_spd_limit to
1, so it corresponds to 1.5Gbps, and was working. But it wasn't even try
to set limit to 3Gbps.
In my device, unfortunately mask and link->sata_spd_limit i
I think that I fixed second part of my issue.
I modified patch 0001-libata-sata_down_spd_limit-should-record-link-
speed-.patch
** Patch added:
"0001-libata-sata_down_spd_limit-should-record-link-speed-.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783906/+attachment/5263913/+
I can split my issue into two cases:
1. My HDD inside DVD enclosure is not discovered. Then I have to reset
stata device 3 or 4 times by "echo "- - -" >
/sys/class/scsi_host/host1/scan" command
2. After stata resets, function sata_down_spd_limit() is called.
* In Linux 4.14 this function set up
I forgot to say that even on Linux 4.14 I have to execute manually
script while booting:
echo "- - -" > /sys/class/scsi_host/host1/scan
So, only after this reset sata my laptop can see external HDD. Since
Linux 4.15 resetting has no effect.
I am analyzing how libata setup is working, so I will t
I can confirm that bug still exists in Linux Kernel 5.1.0.
I created patch to fix this issue.
** Patch added: "fix_for_lenovo_b50-70_inverted_internal_microphone_bug.patch"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1524215/+attachment/5262687/+files/fix_for_lenovo_b50-70_inve
Unfortunately patch "0001-libata-sata_down_spd_limit-should-record-link-
speed-.patch" don't work.
Here is my dmesg dump with proposed debug info
https://paste.ubuntu.com/p/vxTM3jdMv9/
I'm not familiar with libata and sata_down_spd_limit function, but
"return -EINVAL;" spoils functionality for me
Hi!
I have similar issue as described in topic. I have two drives, one
primary SSD and second HDD inside DVD enclosure.
Both drives works fine until kernel version 4.15.0-rc4 (exact commit
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a83cb7e6ada140f8b932c223511f10
13 matches
Mail list logo
