This bug was fixed in the package linux - 4.2.0-21.25
---
linux (4.2.0-21.25) wily; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1522108
[ Upstream Kernel Changes ]
* staging/dgnc: fix info leak in ioctl
- LP: #1509565
- CVE-2015-7885
*
This bug was fixed in the package linux - 3.19.0-41.46
---
linux (3.19.0-41.46) vivid; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1522918
[ Upstream Kernel Changes ]
* Revert "dm: fix AB-BA deadlock in __dm_destroy()"
- LP: #1522766
* dm: fix
Since the fix for this bug is also being released in stable kernels
(Trusty got the fix from 3.13 and vivid would get it from 3.19), I am
tagging this bug as verified.
** Tags removed: verification-needed-vivid verification-needed-wily
** Tags added: verification-done-vivid verification-done-wily
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-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
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
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Vivid)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Wily)
Status: New => Fix
Oops.. .Nvm I forgot that this won't be an issue until after commit
34b48db, regardless of the same code being in the kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475166
Title:
Ubuntu
@kashyap-desai
I was just looking at cherrypicking this fix to 15.10, but then realized I
don't see why this wouldn't affect 12.04 or 14.04 as well. Does this affect
all supported Ubuntu releases?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It's landed in linus' tree as commit
357ae967ad66e357f78b5cfb5ab6ca07fb4a7758.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475166
Title:
Ubuntu 15.04 Install Error with Avago Controller
To
Hi Bryan
Now that patch has been submitted upstream (by Kashyap), what is the
rough timeline for this commit to merge ?
Thanks
Adi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475166
Title:
Hi Adi,
I see the patch got posted here - https://www.spinics.net/lists/linux-
scsi/msg89336.html and it has been reviewed.
I'm guessing it will be part of a scsi pull request in the recently
opened 4.4 merge window. That looks imminent. Depending on when it
lands, the Ubuntu kernel update
We are in process of submit patches to upstream. We are waiting for few
older patch series to get committed, otherwise there will be a confusion
over series of patches and we may not see clean commit. Once we post
patch for this issue, I will update the BZ with commit id or link
pointing to
@bryanquigley @kashyap
Has the update landed yet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475166
Title:
Ubuntu 15.04 Install Error with Avago Controller
To manage notifications about this
@kashyap
>Current Driver count max_sectors based on PAGE_SIZE. This is wrong. We will
>fix and send patch to upstream.
Thanks for the analysis and working upstream. Post here when it lands and I
can see about getting it back to 15.04/15.10.
Just for clarify workaround of anyone reading:
@ Bryan -
1. This is an issue with Avago Driver. Driver code snippet -
instance->max_sectors_per_req = instance->max_num_sge *
PAGE_SIZE / 512;
if (tmp_sectors && (instance->max_sectors_per_req > tmp_sectors))
instance->max_sectors_per_req = tmp_sectors;
@ Brayn - Sorry for my earlier comment about 256K IO size. I thought
customer is using released FW packages.
I just realize that FW version 24.10.0-0002 is Internal development
release and not a product GCA. Our current development series has 1024K
support. Looks like there may be some bug in FW
@kashyap-desai thanks for that, it could be a simple firmware reporting issue
or the kernel code needs to be updated to handle a new case.
megaraid_sas_base.c [1] mentions that it generates the max_sectors limits from
data provided from the firmware.
4096 is defined in a few other places within
@ Bryan - I see what you say... It is bit confusing...you are confuse
with max_sectors module parameter. That parameter is only for bit old
controllers. See below PnP ID checks in driver code.
/*
* Check if the module parameter value for max_sectors can be used
*/
if
@kashyap-desai thanks for checking. AFAICT it's been at 1024 for at
least the 14.04 release as well.
Thanks for noting what FW status 0x3 means, that will help any future
tests we do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Avago controller support 256K max IO. max_sector_hw_kb should be 256.
Anything like 1024 or 4096 is invalid. Once FW receive more than it can
support, IO will be failed and print like " megasas: FW status 0x3"
will dump on console from Driver. I will check how Driver behaves using
14.10 Kernel
So assuming the the value max_sectors_kb is changed to 1024 (with the
2048 kernel command line) that means we need to figure out what the
correct value is for the Avago controller. Currently it's set as 4096
in the kernel according to C#28. It appears 1024 works, but if we get
the actual value
I haven't checked the values after successful install. I can check and
let you know.
Are you saying that what I tried:
adding megaraid_sas.max_sectors=2048 wouldn't sustain on reboot ? and hence
forth might have issues rebooting and getting in on OS ?
--
You received this bug notification
Yes it would only be for one boot, to use that as a workaround you want
to add it permanently to GRUB_CMDLINE_LINUX_DEFAULT in
/etc/default/grub. Then run sudo update-grub.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Adi,
Just to confirm my understanding of this bug, did doing so change the
value of max_sectors_kb / max_hw_sectors_kb? I don't believe it would
have survived the reboot after the install, but you could try adding it
to the kernel command line of the installed system and see.
Bryan
--
You
Hey Bryan
Editing the boot options to include this string, seems to help install
15.04 onto disk behind avago controller without any errors.
megaraid_sas.max_sectors=2048
Adi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the bisect results! We can confirm that this fixes the issue by
manually specifying the max_sectors_kb and seeing if that fixes the issue.
1. Boot the server installation and stop at the partitioning screen (this way
we make sure it has detected everything)
2. Switch to another VT
Hello Bryan
I tried to your work around:
A) Go to the 15.04 installation partition screen to see all disks are
detected
B) Go to VT and check the values of nodes
/sys/devices/pci:00/:00:00.0/:01:00.0/host4/target4:2:0/4:2:0:0
/block/sde/queue # cat max_sectors_kb
4096
All that patch appears to do is to remove an artificial limit for all
devices to 1024. I haven't been able to reproduce the option reset on
my systems, so here is what I would try:
Try setting the controller option and see if that sticks [1]:
rmmod megaraid_sas
modprobe megaraid_sas
Hey Bryan
modprobe megaraid_sas max_sectors=2048
Doesn¹t seem to help either.
Same error.
Thanks
Adi
On 8/24/15, 2:53 PM, Bryan Quigley bryan.quig...@canonical.com
wrote:
All that patch appears to do is to remove an artificial limit for all
devices to 1024. I haven't been able to
Hi Bryan,
We have done bisection, and found the first bad commit is 34b48db as shown
below.
With this bad commit, the filesystem returns I/O error while copying files to
disk.
We use the same config file copy from ubuntu 14.10, and follow the build
instruction[1].
Would you like to build an
Hi Adi,
1)
We have met a similar problem when we build 3.16 kernel like your C#1822, and
there goes a solution by Johnny.
You have to modify scripts/package/builddeb in linux kernel source as something
like:
...
ppc*)
debarch=$(grep -q CPU_LITTLE_ENDIAN=y $KCONFIG_CONFIG echo
Thanks a ton Boga! That hellps!
Bryan
Here is a difference between custom config of a Kernel version where bug
is NOT seen (3.18) and where it is seen (3.19)
https://www.diffchecker.com/kgudgvt3
There are bunch of config differences. Could any of these could have
cause the issue ?
One of the
** Changed in: linux (Ubuntu)
Assignee: Chris J Arges (arges) = Bryan Quigley (bryanquigley)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475166
Title:
Ubuntu 15.04 Install Error with Avago
Sorry, I forgot that was also in C#17. I just wanted to minimize the
chance the kernel build/git operations would be affected by the IO
issues. Sticking with 14.10 for the bisection is perfect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
1) Yes there is a consistent I/O error like the one i attached in my last
comment for v 3.19 and v 4.1 dmesg. This happens across multiple reboots
2)Yes, it was the I/O corruption that caused it.
Regarding what you recommended in C17 regarding installing 15.04 on SATA
and stuff. I am not sure
Sorry I misunderstood, I'm guessing if you go back to v3.16 it would be
fine? Perhaps something about the build is wrong at the checkout
preventing that.
There are two ways to try proceeding:
git bisect skip (trys to pick another commit) and see if it builds PPC64LE
checkout v3.18 or 3.17 and
As I mentioned in my Comment 18
I can't get further with bisection since:
I am at a bisect state between 3.16 and 3.19 where I can't generate a
Little Indian kernel deb package. (PPC64LE). All it generates is a
POWERPC deb. Console doesn't let me customize it in the config make
oldconfig stage,
1) I would definitely recommend booting up/checking the logs multiple times on
every leg of the test to ensure that it gets a consistent result.
2) I don't understand how this would have happened. It does occur to me that
if we're dealing with possible IO corruption there could be other
1)
Even though I was able to boot up with kernels v3.19 or v4.1 smoothly. On
closer inspection of Dmesg logs. There is an I/O error during bootup for 3.19
and 4.1 which I don't see for v3.16 kernel. This error is similar to the one
we get in 15.04 installation to RAID.
Dmesg logs are attached
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475166
Title:
Ubuntu 15.04 Install Error with Avago Controller
To manage
Thanks Bryan
1)
I tried 14.10 with 4.1 Kernel and build seems to boot fine.
Apart from checking that boot-up happens fine, is there any other sanity
I need to check ?
2)
Here is diff between default configs from uptopic (left) and vivid (right) :
https://www.diffchecker.com/dpu3ggpv
Is
1) I would at least try booting multiple times.
If possible I would try partitioning so you have extra space and can set up a
new ext4 partition on the Controller for every test. Then deleting before
running the next one.
In fact, I'd recommend for the next test to install 15.04 on a SATA
14.10 with 3.19 is NOT a failure. It boots up fine.
So am not sure now if a bisection makes sense at all.
Please let me know if you have any follow up experiments in mind.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You can also try building 3.19 with the config from Ubuntu - see the
bottom of GitKernelBuild for more. Alternatively you could grab the
config from a 15.04 using step 4 in GitKernelBuild.
[1] http://kernel.ubuntu.com/git/ubuntu/ubuntu-
vivid.git/tree/debian.master/config
--
You received this
It would be worth trying 4.1 as well built from source as that should
match the other kernel test above. Small fixes do make it after the
release and that should rule that out.
The most likely possibility that I see is that it is an Ubuntu specific kernel
config change.
It could also be
Hi Adi,
I would go ahead and proceed with a bisect. The first step would be to
test if you can build[1] the 14.10 (git checkout v3.16) kernel and it
boots fine.
Then confirm the failure of 3.19 before proceeding to a normal bisect
[1].
Which if everything above is expected, would be git bisect
Agree, a bisect would be the best course of action. Let us know if you
need any assistance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475166
Title:
Ubuntu 15.04 Install Error with Avago
Hey Chris
Is there anything else you'd want us to try regarding this bug ?
Boga seems to have been able to upgrade the kernel.
I have shown that in 15.04 live image also, partitioning and mounting a
ext4 File system returns an I/O error in above post.
Based on these findings can we start to
Hello Chris
Hi from Adi
Here is a update on my findings from 15.04 PPC64LE Live image:
I tried latest driver from avago 06.809.16. Preliminary every thing
looked okay: Creating, deleting and accessing RAID0 volume.
However, coming to particular error that we are facing that: 15.04
Ubuntu Disk
Hi Chris,
Please let us clarify first, we install the following package first:
linux-header-all
linux-header-generic
linux-image
We reboot the system and it hangs with above messages.
So we re-installed a new 14.10 system and update packages by the following
order again:
linux-header-all
Ok let's try one more kernel. So get machine into working state with 14.10,
then install the following v4.1 kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/7714824
If this also fails, we'll need to either bisect between v3.16..v3.19, and or
try and figure out
Hi Chris,
Sorry for the late replay.
We did install the kernel 3.19.0.22 in Ubuntu 14.10, and the OS is not able to
boot up anymore.
Please check the messages as below, thanks!
1. The message from 14.10 with original kernel to 3.19.0.22 kernel
installation completion.
[0.00] OPAL V3
Bosa,
3.19 series ppc64el kernels can be found here in the vivid archive:
https://launchpad.net/ubuntu/vivid/+source/linux
Go ahead and try this one:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/7546230
These two should be sufficient:
Hi Chris,
Please see our feedback as below,
1) No, we only use in-box driver.
2) Yes, we can install OS by 14.10 first and try to update the kernel to vivid.
But we did not find vivid kernel for PPC64EL under
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/ Would you like to
provide
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475166
Title:
Ubuntu 15.04 Install Error with Avago
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Chris J Arges (arges)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475166
Title:
Ubuntu 15.04 Install Error with Avago Controller
To
A few questions:
1) Are you using any out of tree drivers for your controller?
2) Are you able to install 14.10 then install a newer kernel? Does this produce
a similar failure? This would be helpful in debugging as we could get things
like a crashdump or additional debugging information.
3) If
57 matches
Mail list logo
