From: Dmitry Katsubo <dma_k@mail.ru>
To: "U.Mutlu" <for-gmane@mutluit.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: How to set DPOFUA=0 ?
Date: Tue, 19 Jan 2016 23:10:37 +0100 [thread overview]
Message-ID: <569EB45D.1020102@mail.ru> (raw)
In-Reply-To: <569EA17B.7050601@mail.ru>
> Solved:
>
> By installing a the latest kernel and headers from Debian backports solved the
> problem:
>
> apt-get -t jessie-backports install linux-image-amd64 linux-headers-amd64
>
> Info about backports configuration:
> http://backports.debian.org/Instructions/
>
> # uname -a
> Linux panther 4.2.0-0.bpo.1-amd64 #1 SMP Debian 4.2.6-3~bpo8+2 (2015-12-14)
> x86_64 GNU/Linux
>
> After this nigtmare-ish experience I would suggest the debian maintainers
> to trash the default jessie kernel 3.16 and replace it with the above
> 4.2 kernel; otherwise unexperienced users will wonder why their new SSD etc.
> isn't working in debian/ubuntu & co., as happened to me... :-(
I have missed that your message. Solved? Amazing, because the patch I had in
mind was not applied to 4.2.6. Also the device you are reporting has different
productId. I think that in newer kernels (4.x) another driver is used (UAS),
which has already given device logged as "special", see
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/usb/storage/unusual_uas.h#n145
/* Reported-by: Takeo Nakayama <javhera@gmx.com> */
UNUSUAL_DEV(0x357d, 0x7788, 0x0000, 0x9999,
"JMicron",
"JMS566",
USB_SC_DEVICE, USB_PR_DEVICE, NULL,
US_FL_NO_REPORT_OPCODES),
However it does not have US_FL_BROKEN_FUA flag set. Mystery.
--
With best regards,
Dmitry
prev parent reply other threads:[~2016-01-19 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 1:25 How to set DPOFUA=0 ? U.Mutlu
2015-12-29 11:30 ` U.Mutlu
2015-12-29 11:43 ` Julian Calaby
2015-12-29 18:04 ` U.Mutlu
2016-01-19 20:50 ` Dmitry Katsubo
2016-01-19 22:10 ` Dmitry Katsubo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=569EB45D.1020102@mail.ru \
--to=dma_k@mail.ru \
--cc=for-gmane@mutluit.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.