All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <MWHPR03MB26691FB87F0823E2E62868BABF5B0@MWHPR03MB2669.namprd03.prod.outlook.com>

diff --git a/a/1.txt b/N1/1.txt
index d3e883a..4763059 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,7 +1,6 @@
 > From: hch@lst.de [mailto:hch@lst.de]
 > Sent: Wednesday, February 15, 2017 00:35
-> > I tested today's linux-next (next-20170214) + the 2 patches just now an=
-d
+> > I tested today's linux-next (next-20170214) + the 2 patches just now and
 > got
 > > a weird result:
 > > sometimes the VM stills hung with a new calltrace (BUG: spinlock bad
@@ -14,8 +13,7 @@ d
 > Yes.
 It's due to an uninitialized spinlock. Please see the below.
 
-> > Actually previously I saw the "BUG: spinlock bad magic" message once, b=
-ut
+> > Actually previously I saw the "BUG: spinlock bad magic" message once, but
 > I
 > > couldn't repro it later, so I didn't mention it to you.
 >
@@ -27,25 +25,17 @@ We should always see the message.
 >
 > A few questions on the dmesg:
 >
-> [    6.208794] sd 2:0:0:0: [storvsc] Sense Key : Illegal Request [current=
-]
-> [    6.209447] sd 2:0:0:0: [storvsc] Add. Sense: Invalid command operatio=
-n
+> [    6.208794] sd 2:0:0:0: [storvsc] Sense Key : Illegal Request [current]
+> [    6.209447] sd 2:0:0:0: [storvsc] Add. Sense: Invalid command operation
 > code
-> [    6.210043] sd 3:0:0:0: [storvsc] Sense Key : Illegal Request [current=
-]
-> [    6.210618] sd 3:0:0:0: [storvsc] Add. Sense: Invalid command operatio=
-n
+> [    6.210043] sd 3:0:0:0: [storvsc] Sense Key : Illegal Request [current]
+> [    6.210618] sd 3:0:0:0: [storvsc] Add. Sense: Invalid command operation
 > code
-> [    6.212272] sd 2:0:0:0: [storvsc] Sense Key : Illegal Request [current=
-]
-> [    6.212897] sd 2:0:0:0: [storvsc] Add. Sense: Invalid command operatio=
-n
+> [    6.212272] sd 2:0:0:0: [storvsc] Sense Key : Illegal Request [current]
+> [    6.212897] sd 2:0:0:0: [storvsc] Add. Sense: Invalid command operation
 > code
-> [    6.213474] sd 3:0:0:0: [storvsc] Sense Key : Illegal Request [current=
-]
-> [    6.214051] sd 3:0:0:0: [storvsc] Add. Sense: Invalid command operatio=
-n
+> [    6.213474] sd 3:0:0:0: [storvsc] Sense Key : Illegal Request [current]
+> [    6.214051] sd 3:0:0:0: [storvsc] Add. Sense: Invalid command operation
 > code
 >
 > I didn't see anything like this in the other logs.  Are these messages
@@ -79,8 +69,7 @@ IMO we should ignore the messages, which should be harmless.
 > 00000000, .owner: <none>/-1, .owner_cpu: 0
 > [    7.538436] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.10.0-rc8-next-
 > 20170214+ #1
-> [    7.539142] Hardware name: Microsoft Corporation Virtual Machine/Virtu=
-al
+> [    7.539142] Hardware name: Microsoft Corporation Virtual Machine/Virtual
 > Machine, BIOS 090006  04/28/2016
 > [    7.539142] Call Trace:
 > [    7.539142]  <IRQ>
@@ -97,25 +86,22 @@ al
 > l *(timesync_onchannelcallback+0x153)
 
 (gdb) l *(timesync_onchannelcallback+0x153)
-0xffffffffc0104593 is in timesync_onchannelcallback (drivers/hv/hv_util.c:2=
-79).
+0xffffffffc0104593 is in timesync_onchannelcallback (drivers/hv/hv_util.c:279).
 274             } else {
 275                     /*
-276                      * Save the adjusted time sample from the host and =
-the snapshot
+276                      * Save the adjusted time sample from the host and the snapshot
 277                      * of the current system time for PTP device.
 278                      */
 279                     spin_lock_irqsave(&host_ts.lock, flags);
 280
-281                     cur_reftime =3D hyperv_cs->read(hyperv_cs);
-282                     host_ts.host_time =3D hosttime;
-283                     host_ts.ref_time =3D cur_reftime;
+281                     cur_reftime = hyperv_cs->read(hyperv_cs);
+282                     host_ts.host_time = hosttime;
+283                     host_ts.ref_time = cur_reftime;
 
 It turns out the "host_ts.lock" isn't initialized with spin_lock_init().
 I'll submit a patch for this.
 
-However, the SCSI issue (i.e. *sometimes* the VM fails to boot) is still th=
-ere, I think.
+However, the SCSI issue (i.e. *sometimes* the VM fails to boot) is still there, I think.
 We need to continue to debug...
 
 Thanks,
diff --git a/a/content_digest b/N1/content_digest
index f234e4b..c46c13d 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -35,7 +35,7 @@
   "From\0Dexuan Cui <decui\@microsoft.com>\0"
 ]
 [
-  "Subject\0RE: Boot regression (was \"Re: [PATCH] genhd: Do not hold event\tlock when scheduling workqueue elements\")\0"
+  "Subject\0RE: Boot regression (was \"Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements\")\0"
 ]
 [
   "Date\0Wed, 15 Feb 2017 13:51:33 +0000\0"
@@ -67,8 +67,7 @@
 [
   "> From: hch\@lst.de [mailto:hch\@lst.de]\n",
   "> Sent: Wednesday, February 15, 2017 00:35\n",
-  "> > I tested today's linux-next (next-20170214) + the 2 patches just now an=\n",
-  "d\n",
+  "> > I tested today's linux-next (next-20170214) + the 2 patches just now and\n",
   "> got\n",
   "> > a weird result:\n",
   "> > sometimes the VM stills hung with a new calltrace (BUG: spinlock bad\n",
@@ -81,8 +80,7 @@
   "> Yes.\n",
   "It's due to an uninitialized spinlock. Please see the below.\n",
   "\n",
-  "> > Actually previously I saw the \"BUG: spinlock bad magic\" message once, b=\n",
-  "ut\n",
+  "> > Actually previously I saw the \"BUG: spinlock bad magic\" message once, but\n",
   "> I\n",
   "> > couldn't repro it later, so I didn't mention it to you.\n",
   ">\n",
@@ -94,25 +92,17 @@
   ">\n",
   "> A few questions on the dmesg:\n",
   ">\n",
-  "> [    6.208794] sd 2:0:0:0: [storvsc] Sense Key : Illegal Request [current=\n",
-  "]\n",
-  "> [    6.209447] sd 2:0:0:0: [storvsc] Add. Sense: Invalid command operatio=\n",
-  "n\n",
+  "> [    6.208794] sd 2:0:0:0: [storvsc] Sense Key : Illegal Request [current]\n",
+  "> [    6.209447] sd 2:0:0:0: [storvsc] Add. Sense: Invalid command operation\n",
   "> code\n",
-  "> [    6.210043] sd 3:0:0:0: [storvsc] Sense Key : Illegal Request [current=\n",
-  "]\n",
-  "> [    6.210618] sd 3:0:0:0: [storvsc] Add. Sense: Invalid command operatio=\n",
-  "n\n",
+  "> [    6.210043] sd 3:0:0:0: [storvsc] Sense Key : Illegal Request [current]\n",
+  "> [    6.210618] sd 3:0:0:0: [storvsc] Add. Sense: Invalid command operation\n",
   "> code\n",
-  "> [    6.212272] sd 2:0:0:0: [storvsc] Sense Key : Illegal Request [current=\n",
-  "]\n",
-  "> [    6.212897] sd 2:0:0:0: [storvsc] Add. Sense: Invalid command operatio=\n",
-  "n\n",
+  "> [    6.212272] sd 2:0:0:0: [storvsc] Sense Key : Illegal Request [current]\n",
+  "> [    6.212897] sd 2:0:0:0: [storvsc] Add. Sense: Invalid command operation\n",
   "> code\n",
-  "> [    6.213474] sd 3:0:0:0: [storvsc] Sense Key : Illegal Request [current=\n",
-  "]\n",
-  "> [    6.214051] sd 3:0:0:0: [storvsc] Add. Sense: Invalid command operatio=\n",
-  "n\n",
+  "> [    6.213474] sd 3:0:0:0: [storvsc] Sense Key : Illegal Request [current]\n",
+  "> [    6.214051] sd 3:0:0:0: [storvsc] Add. Sense: Invalid command operation\n",
   "> code\n",
   ">\n",
   "> I didn't see anything like this in the other logs.  Are these messages\n",
@@ -146,8 +136,7 @@
   "> 00000000, .owner: <none>/-1, .owner_cpu: 0\n",
   "> [    7.538436] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.10.0-rc8-next-\n",
   "> 20170214+ #1\n",
-  "> [    7.539142] Hardware name: Microsoft Corporation Virtual Machine/Virtu=\n",
-  "al\n",
+  "> [    7.539142] Hardware name: Microsoft Corporation Virtual Machine/Virtual\n",
   "> Machine, BIOS 090006  04/28/2016\n",
   "> [    7.539142] Call Trace:\n",
   "> [    7.539142]  <IRQ>\n",
@@ -164,29 +153,26 @@
   "> l *(timesync_onchannelcallback+0x153)\n",
   "\n",
   "(gdb) l *(timesync_onchannelcallback+0x153)\n",
-  "0xffffffffc0104593 is in timesync_onchannelcallback (drivers/hv/hv_util.c:2=\n",
-  "79).\n",
+  "0xffffffffc0104593 is in timesync_onchannelcallback (drivers/hv/hv_util.c:279).\n",
   "274             } else {\n",
   "275                     /*\n",
-  "276                      * Save the adjusted time sample from the host and =\n",
-  "the snapshot\n",
+  "276                      * Save the adjusted time sample from the host and the snapshot\n",
   "277                      * of the current system time for PTP device.\n",
   "278                      */\n",
   "279                     spin_lock_irqsave(&host_ts.lock, flags);\n",
   "280\n",
-  "281                     cur_reftime =3D hyperv_cs->read(hyperv_cs);\n",
-  "282                     host_ts.host_time =3D hosttime;\n",
-  "283                     host_ts.ref_time =3D cur_reftime;\n",
+  "281                     cur_reftime = hyperv_cs->read(hyperv_cs);\n",
+  "282                     host_ts.host_time = hosttime;\n",
+  "283                     host_ts.ref_time = cur_reftime;\n",
   "\n",
   "It turns out the \"host_ts.lock\" isn't initialized with spin_lock_init().\n",
   "I'll submit a patch for this.\n",
   "\n",
-  "However, the SCSI issue (i.e. *sometimes* the VM fails to boot) is still th=\n",
-  "ere, I think.\n",
+  "However, the SCSI issue (i.e. *sometimes* the VM fails to boot) is still there, I think.\n",
   "We need to continue to debug...\n",
   "\n",
   "Thanks,\n",
   "-- Dexuan"
 ]
 
-875cd6d0ffc4614dbbe50d196a7da89f332248e7060b1c6fe23b957ca332da70
+1afa096e6d8f722ec5741f94b3e51fbeefc5cd815ec814af4f3fdcdea5893927

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.