All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20190724014510.GD22421@ming.t460p>

diff --git a/a/1.txt b/N1/1.txt
index efce40b..33c1ba2 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,4 +1,4 @@
-On Tue, Jul 23, 2019 at 04:56:10PM -0500, davidc502 wrote:
+On Tue, Jul 23, 2019@04:56:10PM -0500, davidc502 wrote:
 > Ming,
 > 
 > On 7/23/19 4:38 PM, davidc502 wrote:
@@ -7,36 +7,36 @@ On Tue, Jul 23, 2019 at 04:56:10PM -0500, davidc502 wrote:
 > > On 7/22/19 11:38 PM, Ming Lei wrote:
 > > > Hi,
 > > > 
-> > > On Mon, Jul 22, 2019 at 09:39:07PM -0500, davidc502 wrote:
-> > > > See attached:  nvme_io_trace.log
+> > > On Mon, Jul 22, 2019@09:39:07PM -0500, davidc502 wrote:
+> > > > See attached:? nvme_io_trace.log
 > > > > 
 > > > > 
 > > > > On 7/22/19 9:19 PM, Ming Lei wrote:
 > > > > > Hi,
 > > > > > 
-> > > > > On Sat, Jul 20, 2019 at 09:41:24PM -0500, davidc502 wrote:
-> > > > > >    Hello,
+> > > > > On Sat, Jul 20, 2019@09:41:24PM -0500, davidc502 wrote:
+> > > > > > ? ?Hello,
 > > > > > > 
-> > > > > >    I've assembled a X570 board with a 1TB AORUS NVMe Gen4 SSD.
+> > > > > > ? ?I've assembled a X570 board with a 1TB AORUS NVMe Gen4 SSD.
 > > > > > > 
-> > > > > >    When attempting to fstrim the NVMe, I receive the following error.
-> > > > > >    davidc502@Ryzen-3900x:~$ sudo fstrim -a -v
-> > > > > >    fstrim: /boot/efi: FITRIM ioctl failed: Input/output error
-> > > > > >    fstrim: /: FITRIM ioctl failed: Input/output error
+> > > > > > ? ?When attempting to fstrim the NVMe, I receive the following error.
+> > > > > > ? ?davidc502 at Ryzen-3900x:~$ sudo fstrim -a -v
+> > > > > > ? ?fstrim: /boot/efi: FITRIM ioctl failed: Input/output error
+> > > > > > ? ?fstrim: /: FITRIM ioctl failed: Input/output error
 > > > > > > 
-> > > > > >    Anyhow, I have put some details below which might be
+> > > > > > ? ?Anyhow, I have put some details below which might be
 > > > > > > helpful. Note that
 > > > > > > this NVMe is supposed to be TRIM and SMART compliant.
 > > > > > > The SMART outputs are
-> > > > > > available using the utility “nvme-cli”.
-> > > > > >    I am willing to provide whatever command outputs that
+> > > > > > available using the utility ?nvme-cli?.
+> > > > > > ? ?I am willing to provide whatever command outputs that
 > > > > > > are needed to help
 > > > > > > solve this issue.
 > > > > > > 
-> > > > > >    OS= Ubuntu 18.4.2 LTS
-> > > > > >    Different Kernels I’ve tried = 5.1.16, 5.2 rc7, and 4.18
-> > > > > >    fstrim version =  fstrim from util-linux 2.31.1
-> > > > > >    Firmware version for Aorus NVMe = EGFM11.0
+> > > > > > ? ?OS= Ubuntu 18.4.2 LTS
+> > > > > > ? ?Different Kernels I?ve tried = 5.1.16, 5.2 rc7, and 4.18
+> > > > > > ? ?fstrim version =? fstrim from util-linux 2.31.1
+> > > > > > ? ?Firmware version for Aorus NVMe = EGFM11.0
 > > > > > > 
 > > > > > I saw discard timeout on HGST 1.6TB NVMe, not sure if yours
 > > > > > is same with
@@ -48,7 +48,7 @@ On Tue, Jul 23, 2019 at 04:56:10PM -0500, davidc502 wrote:
 > > > > > 
 > > > > > 1) queue limits log:
 > > > > > 
-> > > > >     #(cd /sys/block/nvme0n1/queue && find . -type f -exec
+> > > > > ????#(cd /sys/block/nvme0n1/queue && find . -type f -exec
 > > > > > grep -aH . {} \;)
 > > > > > 
 > > > > > 
@@ -56,8 +56,8 @@ On Tue, Jul 23, 2019 at 04:56:10PM -0500, davidc502 wrote:
 > > > > > 
 > > > > > - enable nvme IO trace before running fstrim:
 > > > > > 
-> > > > >     #echo 1  > /sys/kernel/debug/tracing/events/nvme_setup_cmd/enable
-> > > > >     #echo 1  >
+> > > > > ????#echo 1? > /sys/kernel/debug/tracing/events/nvme_setup_cmd/enable
+> > > > > ????#echo 1? >
 > > > > > /sys/kernel/debug/tracing/events/nvme_complete_rq/enable
 > > > > > 
 > > > > > - run fstrim
@@ -65,11 +65,11 @@ On Tue, Jul 23, 2019 at 04:56:10PM -0500, davidc502 wrote:
 > > > > > - after the fstrim failure is triggered, disable the nvme io
 > > > > > trace & post the log:
 > > > > > 
-> > > > >     #echo 0  > /sys/kernel/debug/tracing/events/nvme_setup_cmd/enable
-> > > > >     #echo 0  >
+> > > > > ????#echo 0? > /sys/kernel/debug/tracing/events/nvme_setup_cmd/enable
+> > > > > ????#echo 0? >
 > > > > > /sys/kernel/debug/tracing/events/nvme_complete_rq/enable
 > > > > > 
-> > > > >     #cp    /sys/kernel/debug/tracing/trace /root/nvme_io_trace.log
+> > > > > ????#cp??? /sys/kernel/debug/tracing/trace /root/nvme_io_trace.log
 > > > > > 
 > > > > > 
 > > > > > 
@@ -78,13 +78,13 @@ On Tue, Jul 23, 2019 at 04:56:10PM -0500, davidc502 wrote:
 > > > > 
 > > > > Hello Ming
 > > > > 
-> > > > Thank you for the quick reply --  See attached
-> > >  From the IO trace, discard command(nvme_cmd_dsm) is failed:
+> > > > Thank you for the quick reply --? See attached
+> > > ?From the IO trace, discard command(nvme_cmd_dsm) is failed:
 > > > 
-> > >    kworker/15:1H-462   [015] .... 91814.342452: nvme_setup_cmd:
+> > > ?? kworker/15:1H-462?? [015] .... 91814.342452: nvme_setup_cmd:
 > > > nvme0: disk=nvme0n1, qid=7, cmdid=552, nsid=1, flags=0x0, meta=0x0,
 > > > cmd=(nvme_cmd_dsm nr=0, attributes=4)
-> > >            <idle>-0     [013] d.h. 91814.342708: nvme_complete_rq:
+> > > ?????????? <idle>-0???? [013] d.h. 91814.342708: nvme_complete_rq:
 > > > nvme0: disk=nvme0n1, qid=7, cmdid=552, res=0, retries=0, flags=0x0,
 > > > status=8198
 > > > 
@@ -116,11 +116,11 @@ On Tue, Jul 23, 2019 at 04:56:10PM -0500, davidc502 wrote:
 > > David
 > > 
 > > 
-> I have attempted to CC ilnux-nvme@lists.infradead.org, but receive a
-> immediate notification " 550 Unknown recipient ".  So it just gets bounced
+> I have attempted to CC ilnux-nvme at lists.infradead.org, but receive a
+> immediate notification " 550 Unknown recipient ".? So it just gets bounced
 > back to me.
 
-It should have been linux-nvme@lists.infradead.org.
+It should have been linux-nvme at lists.infradead.org.
 
 Thanks,
 Ming
diff --git a/a/content_digest b/N1/content_digest
index 01af920..c2269fb 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -4,15 +4,12 @@
  "ref\020190723043803.GB13829@ming.t460p\0"
  "ref\038cf2485-727b-268d-f42c-6c53b971cb87@tds.net\0"
  "ref\05ef41ec4-abb8-90bf-e2eb-8a62f51ad951@tds.net\0"
- "From\0Ming Lei <ming.lei@redhat.com>\0"
- "Subject\0Re: fstrim error - AORUS NVMe Gen4 SSD\0"
+ "From\0ming.lei@redhat.com (Ming Lei)\0"
+ "Subject\0fstrim error - AORUS NVMe Gen4 SSD\0"
  "Date\0Wed, 24 Jul 2019 09:45:12 +0800\0"
- "To\0davidc502 <davidc502@tds.net>\0"
- "Cc\0linux-block@vger.kernel.org"
- " linux-nvme@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
- "On Tue, Jul 23, 2019 at 04:56:10PM -0500, davidc502 wrote:\n"
+ "On Tue, Jul 23, 2019@04:56:10PM -0500, davidc502 wrote:\n"
  "> Ming,\n"
  "> \n"
  "> On 7/23/19 4:38 PM, davidc502 wrote:\n"
@@ -21,36 +18,36 @@
  "> > On 7/22/19 11:38 PM, Ming Lei wrote:\n"
  "> > > Hi,\n"
  "> > > \n"
- "> > > On Mon, Jul 22, 2019 at 09:39:07PM -0500, davidc502 wrote:\n"
- "> > > > See attached:\302\240 nvme_io_trace.log\n"
+ "> > > On Mon, Jul 22, 2019@09:39:07PM -0500, davidc502 wrote:\n"
+ "> > > > See attached:? nvme_io_trace.log\n"
  "> > > > \n"
  "> > > > \n"
  "> > > > On 7/22/19 9:19 PM, Ming Lei wrote:\n"
  "> > > > > Hi,\n"
  "> > > > > \n"
- "> > > > > On Sat, Jul 20, 2019 at 09:41:24PM -0500, davidc502 wrote:\n"
- "> > > > > > \302\240 \302\240Hello,\n"
+ "> > > > > On Sat, Jul 20, 2019@09:41:24PM -0500, davidc502 wrote:\n"
+ "> > > > > > ? ?Hello,\n"
  "> > > > > > \n"
- "> > > > > > \302\240 \302\240I've assembled a X570 board with a 1TB AORUS NVMe Gen4 SSD.\n"
+ "> > > > > > ? ?I've assembled a X570 board with a 1TB AORUS NVMe Gen4 SSD.\n"
  "> > > > > > \n"
- "> > > > > > \302\240 \302\240When attempting to fstrim the NVMe, I receive the following error.\n"
- "> > > > > > \302\240 \302\240davidc502@Ryzen-3900x:~$ sudo fstrim -a -v\n"
- "> > > > > > \302\240 \302\240fstrim: /boot/efi: FITRIM ioctl failed: Input/output error\n"
- "> > > > > > \302\240 \302\240fstrim: /: FITRIM ioctl failed: Input/output error\n"
+ "> > > > > > ? ?When attempting to fstrim the NVMe, I receive the following error.\n"
+ "> > > > > > ? ?davidc502 at Ryzen-3900x:~$ sudo fstrim -a -v\n"
+ "> > > > > > ? ?fstrim: /boot/efi: FITRIM ioctl failed: Input/output error\n"
+ "> > > > > > ? ?fstrim: /: FITRIM ioctl failed: Input/output error\n"
  "> > > > > > \n"
- "> > > > > > \302\240 \302\240Anyhow, I have put some details below which might be\n"
+ "> > > > > > ? ?Anyhow, I have put some details below which might be\n"
  "> > > > > > helpful. Note that\n"
  "> > > > > > this NVMe is supposed to be TRIM and SMART compliant.\n"
  "> > > > > > The SMART outputs are\n"
- "> > > > > > available using the utility \342\200\234nvme-cli\342\200\235.\n"
- "> > > > > > \302\240 \302\240I am willing to provide whatever command outputs that\n"
+ "> > > > > > available using the utility ?nvme-cli?.\n"
+ "> > > > > > ? ?I am willing to provide whatever command outputs that\n"
  "> > > > > > are needed to help\n"
  "> > > > > > solve this issue.\n"
  "> > > > > > \n"
- "> > > > > > \302\240 \302\240OS= Ubuntu 18.4.2 LTS\n"
- "> > > > > > \302\240 \302\240Different Kernels I\342\200\231ve tried = 5.1.16, 5.2 rc7, and 4.18\n"
- "> > > > > > \302\240 \302\240fstrim version =\302\240 fstrim from util-linux 2.31.1\n"
- "> > > > > > \302\240 \302\240Firmware version for Aorus NVMe = EGFM11.0\n"
+ "> > > > > > ? ?OS= Ubuntu 18.4.2 LTS\n"
+ "> > > > > > ? ?Different Kernels I?ve tried = 5.1.16, 5.2 rc7, and 4.18\n"
+ "> > > > > > ? ?fstrim version =? fstrim from util-linux 2.31.1\n"
+ "> > > > > > ? ?Firmware version for Aorus NVMe = EGFM11.0\n"
  "> > > > > > \n"
  "> > > > > I saw discard timeout on HGST 1.6TB NVMe, not sure if yours\n"
  "> > > > > is same with\n"
@@ -62,7 +59,7 @@
  "> > > > > \n"
  "> > > > > 1) queue limits log:\n"
  "> > > > > \n"
- "> > > > > \302\240\302\240\302\240\302\240#(cd /sys/block/nvme0n1/queue && find . -type f -exec\n"
+ "> > > > > ????#(cd /sys/block/nvme0n1/queue && find . -type f -exec\n"
  "> > > > > grep -aH . {} \\;)\n"
  "> > > > > \n"
  "> > > > > \n"
@@ -70,8 +67,8 @@
  "> > > > > \n"
  "> > > > > - enable nvme IO trace before running fstrim:\n"
  "> > > > > \n"
- "> > > > > \302\240\302\240\302\240\302\240#echo 1\302\240 > /sys/kernel/debug/tracing/events/nvme_setup_cmd/enable\n"
- "> > > > > \302\240\302\240\302\240\302\240#echo 1\302\240 >\n"
+ "> > > > > ????#echo 1? > /sys/kernel/debug/tracing/events/nvme_setup_cmd/enable\n"
+ "> > > > > ????#echo 1? >\n"
  "> > > > > /sys/kernel/debug/tracing/events/nvme_complete_rq/enable\n"
  "> > > > > \n"
  "> > > > > - run fstrim\n"
@@ -79,11 +76,11 @@
  "> > > > > - after the fstrim failure is triggered, disable the nvme io\n"
  "> > > > > trace & post the log:\n"
  "> > > > > \n"
- "> > > > > \302\240\302\240\302\240\302\240#echo 0\302\240 > /sys/kernel/debug/tracing/events/nvme_setup_cmd/enable\n"
- "> > > > > \302\240\302\240\302\240\302\240#echo 0\302\240 >\n"
+ "> > > > > ????#echo 0? > /sys/kernel/debug/tracing/events/nvme_setup_cmd/enable\n"
+ "> > > > > ????#echo 0? >\n"
  "> > > > > /sys/kernel/debug/tracing/events/nvme_complete_rq/enable\n"
  "> > > > > \n"
- "> > > > > \302\240\302\240\302\240\302\240#cp\302\240\302\240\302\240 /sys/kernel/debug/tracing/trace /root/nvme_io_trace.log\n"
+ "> > > > > ????#cp??? /sys/kernel/debug/tracing/trace /root/nvme_io_trace.log\n"
  "> > > > > \n"
  "> > > > > \n"
  "> > > > > \n"
@@ -92,13 +89,13 @@
  "> > > > \n"
  "> > > > Hello Ming\n"
  "> > > > \n"
- "> > > > Thank you for the quick reply --\302\240 See attached\n"
- "> > > \302\240From the IO trace, discard command(nvme_cmd_dsm) is failed:\n"
+ "> > > > Thank you for the quick reply --? See attached\n"
+ "> > > ?From the IO trace, discard command(nvme_cmd_dsm) is failed:\n"
  "> > > \n"
- "> > > \302\240\302\240 kworker/15:1H-462\302\240\302\240 [015] .... 91814.342452: nvme_setup_cmd:\n"
+ "> > > ?? kworker/15:1H-462?? [015] .... 91814.342452: nvme_setup_cmd:\n"
  "> > > nvme0: disk=nvme0n1, qid=7, cmdid=552, nsid=1, flags=0x0, meta=0x0,\n"
  "> > > cmd=(nvme_cmd_dsm nr=0, attributes=4)\n"
- "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240 <idle>-0\302\240\302\240\302\240\302\240 [013] d.h. 91814.342708: nvme_complete_rq:\n"
+ "> > > ?????????? <idle>-0???? [013] d.h. 91814.342708: nvme_complete_rq:\n"
  "> > > nvme0: disk=nvme0n1, qid=7, cmdid=552, res=0, retries=0, flags=0x0,\n"
  "> > > status=8198\n"
  "> > > \n"
@@ -130,13 +127,13 @@
  "> > David\n"
  "> > \n"
  "> > \n"
- "> I have attempted to CC ilnux-nvme@lists.infradead.org, but receive a\n"
- "> immediate notification \" 550 Unknown recipient \".\302\240 So it just gets bounced\n"
+ "> I have attempted to CC ilnux-nvme at lists.infradead.org, but receive a\n"
+ "> immediate notification \" 550 Unknown recipient \".? So it just gets bounced\n"
  "> back to me.\n"
  "\n"
- "It should have been linux-nvme@lists.infradead.org.\n"
+ "It should have been linux-nvme at lists.infradead.org.\n"
  "\n"
  "Thanks,\n"
  Ming
 
-ea4d387fa22b1afefbd0e4714a2575b0018578676d3aa625a22817af0a30372d
+6bef827980e686d2bc92053dd27657b0b02c612aa8ec59f5b8b09c5b8c3977d6

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.