Michele, we are tracking the VSS issue you may be having in bug 1470250.
Is this the same issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
ext4fs still goes randomly readonly for me on both offline and online
backups on 15.10 with linux 4.2.0-18. should I go back to linux 3.x?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
** No longer affects: linux (Ubuntu Precise)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage notifications about this bug go to:
Indeed, the intention here was to go to the HWE kernel for Precise,
3.13.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage notifications
Thanks for the update, Joshua. So it sounds like these patches don't
need to go in to the 3.2 kernel. If that is the case, I'll mark the
Precise bug task as invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
12.04.02 was end of life as of Aug 2014, so only the 3.2 and 3.13
backport kernel from Trusty are now supported.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel
I successfully installed the second Precise test kernel from Joseph on a Ubuntu
Precise 12.04.02 and the vm boots fine.
I should mention that the default kernel is 3.5.0-23-generic. The difference
between kernels are pretty high.
My question is: shouldn't we do rebase to 3.5 version?
--
You
I built a second Precise test kernel. It looks like some addition
prerequisite commits are required.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1445195/precise/
Can you test this kernel to ensure it boots and to see if it resolves
this bug?
Thanks in
I installed the kernel from
http://kernel.ubuntu.com/~jsalisbury/lp1445195/precise/ , on a Ubuntu
12.04 x64 vm on Hyper-V. After installing, the vm won't boot ( NULL
pointer dereference ).
I attached the boot log.
** Attachment added: "Ubuntu12_boot_log.txt"
I was able to create a Precise test kernel with the request patches.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1445195/precise/
There were quite a few prerequisites required to get the requested
patches into Precise. Due to this, these may be too many
** Changed in: linux (Ubuntu Precise)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage
any news for precise (12.04) patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage
** Changed in: linux (Ubuntu Utopic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage
@Frederik These patches are now in Wily and Vivid. They are queued up
to be in the next Utopic and Trusty releases.
I'm still working on backporting the patches to Precise. There are
allot of prerequisites to get them to apply to Precise.
--
You received this bug notification because you are
Joseph, for Trusty proposed the kernel we should be looking at is 3.13.0-62.101?
That's what I was getting on latest 14.04.3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V]
@Chris, yes the Trusty proposed kernel version is 3.13.0-62.101
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage notifications about this
Since this also helps on the backup issue: please merge these patches!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage notifications
Testing complete, no issues found. Thanks!
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug was fixed in the package linux - 3.19.0-23.24
---
linux (3.19.0-23.24) vivid; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1472346
[ Chris J Arges ]
* SAUCE: Don't use atomic read in evlist.c
- LP: #1410673
linux (3.19.0-23.23) vivid;
** Changed in: linux (Ubuntu Wily)
Status: Triaged = Fix Released
** Changed in: linux (Ubuntu Utopic)
Status: Triaged = Fix Committed
** Changed in: linux (Ubuntu Trusty)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of
We just saw this same error on a GEN 1 - Linux 14.04 LTS as well, anyone
else seeing this on GEN 1?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
@dander88 Are you talking on the backup bug? Please report them in bug
1470250.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage
@F-Bosch - yep that VSS backup issue - I will report it in that spot.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage
Our team has tested the Vivid proposed kernel and found no regressions.
Performance is comparable to previous test kernels.
Thanks!
** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
Hi Joseph,
Do you know will these patches will be available in the next kernel
maintenance release?
Thanks!
Steve
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel
@Joseph, I swear I thought I responded to this bug, sorry for the delay.
We have finished testing the Trusty kernel you posted at
http://kernel.ubuntu.com/~jsalisbury/lp1445195/trusty, and confirmed
performance is better.
Thanks!
Steve
--
You received this bug notification because you are a
@f-bosch, @brianv please paste the relevant logs into
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452074 and we will
continue the reliability discussion there. It could be the networking
piece is having a side effect.
--
You received this bug notification because you are a member of
For those affected by the reliability issues and not performance, we
will be using bug 1454758 or bug 1452074 to focus on that issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
A new bug was opened: bug 1470250 . Let's now use that bug to focus on
the VSS Backup issues. That way we can use bug 1452074 to focus on the
patch that affects networking and not storage.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm echoing the previous poster's sentiments:
Reliability Performance
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage notifications
Been running this kernel on Utopic 14.10 since it was released. The
new kernel reduced the frequency of RO errors from almost daily to about
once a week or so but has not eliminated them.
Ditto to previous poster that we're more concerned about reliability
than performance.
--
You received
I agree it's best to focus on performance in this bug, and use bug
1454758 to focus on the reliability issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches
I wanted to give an update into testing the Vivid kernel on 14.04 LTS
re: https://bugs.launchpad.net/bugs/1454758
Our non-critical database production server ran for almost two weeks,
but this morning finally died when the file system went RO overnight due
to VSS backups. This is with the
I build a Trusty test kernel with the requested patches and a few
prerequisites.It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1445195/trusty
@Stephen can you see if this kernel boots now and get the expected
performance gains?
--
You received this bug notification
Thanks for the feedback, Stephen. I'll start the SRU process Utopic.
I'm also working on backports for Trusty and Precise. Just working to
identify all the needed prereq commits.
Thanks again!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Yes that is the correct kernel. I've moved the files to the utopic
directory now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage
We tested the Utopic kernel and it works fine now. No crashes or issues
and performance is better.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches
We'll test this new kernel. It appears the directory
/~jsalisbury/lp1445195/utopic is empty, but it looks like the kernel
was placed in the /~jsalisbury/lp1445195 directory instead. I assume
this is the correct kernel, but to be safe can you confirm?
Thanks!
Steve
--
You received this bug
I built a new utopic test kernel which can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1445195/utopic/
@Stephen can you see if this kernel boots now and get the expected
performance gains?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux (Ubuntu Vivid)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage notifications
At some point it was believed that bug 1454758 was a duplicate of this bug. Or
that this patch set would also fix bug
1454758. See comment #5. However, this original purpose of this bug was to
get storage driver performance updates into Vivid.
The current testing seems to be more specific
@brainv We will do similar tests this weekend and next week. Since we
actually faced the read-only mode once more, I am not feeling
comfortable yet with the current solution. I am going to try to
reproduce the io pattern that we had when system went into read-only. It
was something like `git
@stevez That means you were not able replicate the read-only issue we
had during our tests of the patched Vivid kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel
@f-bosch No, we have not seen that in our testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage notifications about this bug go to:
The test team has tested the Vivid kernel and confirmed that it works as
expected. So let's please ack these patches for the next Vivid kernel.
The Utopic kernel provided crashes at boot time, so we're unable to test
that. Can you help us debug that issue?
--
You received this bug
@Frederik, would it be possible for you to test the Utopic(3.16) kernel
to see if it fails to boot for you like Brian mentioned on comment #27?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
@jsalisbury I guess so, I will try it asap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage notifications about this bug go to:
@jrp How did your Vivid testing do? Were you able to find any
particularities?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage
Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ
Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ
Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ
Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ
The Utopic kernel does not work for us, it crashes. Continuing with
Vivid testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage
@jrp I have tried to discover if there were any differences between the
backup that failed and the other ones. I noticed this one thing. Before
or during backup (cannot recall exactly atm) a 'composer install'
process was running. Composer is a php package manager. It downloads and
deploys many
@jrp Do you have any suggestions on my remarks above? After the machine
went intro read-only we rebooted and started the whole sequence again.
We did not have had any problems since then. As so it seems, the window
of opportunity for the bug to manifest has been decreased drastically.
However, I
@f-bosch We've tested all of the upstream commits as we regularly test
linux-next on Hyper-V (we don't submit patches to Ubuntu until they
accepted upstream except in extreme situations).
We are continuing to investigate reports of problems, but we are having
difficulty reproducing. I think this
Build: 3.19.0-19-generic #19~lp1445195 SMP Tue May 26 17:43:16 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for
@jrp Could you indicate with which commits did you exactly tested the
bug on your side? I understand from jsalisbury that the base for the
current kernel is the master-next branch. He applied the patches
mentioned in his earlier post to that kernel. Are we missing any other
commits?
Another issue
Very unfortunate but the bug has been triggered again.
[154272.293488] sd 2:0:0:0: [storvsc] Sense Key : Unit Attention [current]
[154272.293508] sd 2:0:0:0: [storvsc] Add. Sense: Changed operating definition
[154272.293665] sd 2:0:0:0: Warning! Received an indication that the operating
@brainv We are seeing exactly the same. Backups are not crashing while
we are still creating backups every half an hour. Our perception is that
the bug is fixed, but we are going to add more boxes to see what happens
then.
--
You received this bug notification because you are a member of Ubuntu
@jsalisbury: I only tested the Vivid build.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage notifications about this bug go to:
1st Night Backups Ran okay, with no strange SCSI errors. The following
was logged into syslog:
May 28 00:01:22 test Hyper-V VSS: VSS: op=FREEZE: succeeded
May 28 00:01:21 test kernel: [22188.912452] sd 0:0:0:0: [storvsc] Sense Key :
Unit Attention [current]
May 28 00:01:21 test kernel:
@Chris Valean, Are you still seeing issues with the Trusty test kernel?
@Brian and @Frederick, Did you also test the Trusty and Utopic test
kernels, or just Vivid?
Thanks again for all the help!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Our tests are positive so far. Already creating backups for 19 hours,
with a backup every half an hour.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for
Joseph, did the new kernel for trusty build yesterday has any changes?
I tried to installed it on top of a up-to-date 14.04.2. The kernel installed
fine, however at reboot the VM fails to boot
Files used: http://kernel.ubuntu.com/~jsalisbury/lp1445195/trusty/
Looking now to get a serial log and
@brianv, you should run dpkg --ignore-depends=binutils -i *.deb to
install. The binutils update can be ignored (if you look at the
changelog it is a minor version bump without api changes). Maybe you
should try the 3.19 kernel: we do not have any booting problems while we
are also on trusty.
--
@jrp: Ok. After reboot it was fine: just one process per daemon.
However, now I do not see any logs of FREEZE and THAW anymore (while
backups are successful). I do see the warning that the operating
parameters have changed. Probably nothing to worry about.
Nonetheless, being a programmer myself,
One thing I have noticed already, is new logs regarding received
packages.
May 27 16:30:18 Hyper-V VSS: VSS: op=FREEZE: succeeded
May 27 16:30:18 Hyper-V VSS: VSS: op=FREEZE: succeeded
May 27 16:30:18 Hyper-V VSS: Received packet from untrusted pid:2102
May 27 16:30:18 Hyper-V VSS: Received
In addition to the previous message, there seemed to be two processes
running of the vss and kvp daemon (while there is only one instance of
fcopy). This is weird (I think), but I have seen it before with other
kernels. A reboot helps in that case. This can also be an explanation
for the received
cloud-tools is tied to the kernel version, you may have ended up with
two instances of it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To
We are starting backup tests with new Vivid kernel now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage notifications about this bug go
I downloaded the 3.16-39 kernels and files and applied them to a test
system we have running on Hyper-V.I'm not able to get the -39 kernel
to fully boot. The startup hangs on the following line:
EXT4-fs (sda2) re-mounted. Opts: errors=remount-ro
If I restart the system with kernel -38, I
@brianv I would avoid taking this to production. When these patches go
into -proposed I'll recommend testing again with the rest of proposed
updates to other packages, and other kernel changes that come from other
bugs, and that would be a better time to consider broader tests. I would
recommend
Thanks! So, 3.19 kernel runs fine. Something is wrong with the 3.16
build.I show the VSS and KVP daemons registered as well. I'm going
to let this run a few days and see what happens. I should start to see
the errors during VSS backup tonight if they occur. I may apply this
kernel to a
@Joshua R. Poulson , Are you still seeing issues as well with the test
kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage
@jrp: could you confirm that this might solve my issue with the 3.19
kernel? Is that specific commit required?
Because I was still seeing Warning! Received an indication that the
operating parameters on this target have changed. The Linux SCSI layer
does not automatically adjust these parameters.
@jrp: did you test the 3.19 kernel or did you use trusty and/or utopic
build?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage
I confirmed the Utopic and Trusty test kernels I posted did in fact have
that patch.
I rebuilt the Vivid test kernel with the master-next branch and confirmed it
does have that patch now. It is posted to:
http://kernel.ubuntu.com/~jsalisbury/lp1445195/vivid/
--
You received this bug
I confirmed the Utopic and Trusty test kernels I posted did in fact have
that patch.
I rebuilt the Vivid test kernel with the master-next branch and confirmed it
does have that patch now. It is posted to:
http://kernel.ubuntu.com/~jsalisbury/lp1445195/vivid/
--
You received this bug
@jsalisbury: yes, that patch is important, but it is difficult to
exercise.
@f-bosch: the missing patch might, to really depends on whether your I/O
pattern exercises the bug. That warning, however, is benign. We tested
our submission upstream as a set, not individually.
--
You received this
I think I may have found an issue. The test kernel I build did not contain:
8de5807 scsi: storvsc: Fix a bug in copy_from_bounce_buffer()
That commit is getting applied to the Vivid kernel when it gets the
upstream 3.19.7 updates. Because of this I didn't cherry pick it. That
commit is only
We did not reproduce this issue with our performance testing, but it is
difficult to reproduce. We have a query into our development team to
analyze f-bosch's reports.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Another confirmation that the reported bugs are not fixed in the vivid
build. We have had another crash this morning, same log messages. It
took quite some hours longer than yesterday though, which confirms the
occurrences are still random (we are not able to see the pattern).
--
You received
No luck with the current build.
Linux VPS-Genkgo 3.19.0-18-generic #18 SMP Wed May 20 17:57:26 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
First backup was succesful, second one failed.
[ 2379.049088] sd 2:0:0:0: [storvsc] Sense Key : Unit Attention [current]
[ 2379.049109] sd 2:0:0:0: [storvsc]
Testing in progress.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage notifications about this bug go to:
Testing in progress.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage notifications about this bug go to:
The problem we encountered with HyperV backups, filed here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456985, should be
solved by these patches too.
Our bug is an exact copy of the initial bug that was reported here:
https://social.technet.microsoft.com/Forums/windowsserver/en-US
We now have test kernels available for Trusty, Utopic and Vivid. They are all
available from:
http://kernel.ubuntu.com/~jsalisbury/lp1445195/
It would be great if you could test the kernels for all releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
It sounds like the following commit is also needed to solve bug 1456985
:
commit dc45708ca9988656d706940df5fd102672c5de92
Author: K. Y. Srinivasan k...@microsoft.com
Date: Fri May 1 11:03:02 2015 -0700
storvsc: Set the SRB flags correctly when no data transfer is needed
That commit was
I built Trusty, Utopic and Vivid test kernels, with the commits
requested in this bug, any pre-reqs and commit dc45708ca per bug 1454758
. The details are as follows:
Trusty:
dc45708 storvsc: Set the SRB flags correctly when no data transfer is needed
- Added per bug 1454758
b9ec3a5 scsi:
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Precise)
Importance: Undecided = High
** Changed in: linux (Ubuntu Precise)
Status: New = Triaged
** Changed in: linux (Ubuntu Precise)
Assignee: (unassigned) = Andy
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Wily)
Importance: High
Assignee: Andy Whitcroft (apw)
Status: Triaged
** Also
We will test this kernel. This needs to go to 15.10, 15.04, 14.10,
14.04, and 14.04 HWE.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches for storvsc
To manage
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Vivid)
Status: New = Triaged
** Changed in: linux (Ubuntu Vivid)
Importance: Undecided = High
** Changed in:
The importance for this update, and 1452074, has become critical, due to
customer concerns here
https://social.technet.microsoft.com/Forums/windowsserver/en-US
/8807f61c-565e-45bc-abc4-af09abf59de2/ubuntu-14042-lts-generation-2
-scsi-errors-on-vss-based-backups
--
You received this bug
I built a Vivid test kernel with the 7 requested commits. The test
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1445195/
Can you test this kernel and see if it resolves this bug?
I'll also build a test kernel for bug 1452074 and post a link to it in
that bug report.
96 matches
Mail list logo
