This is Debian Bug #541172 [1].
There's a patch available there at message #15 [2], but it didn't make into the
package.
It fixes the problem.
Unfortunately it seems there's some issue contacting the package maintainers,
given that bug's age. I tried to help there.
[1]
Meanwhile, is it possible to carry that patch in the Ubuntu package?
This is the patch/debdiff for that, on top of the current source package
in Trusty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-tools in Ubuntu.
Meanwhile, is it possible to carry that patch in the Ubuntu package?
This is the patch/debdiff for that, on top of the current source package
in Trusty.
** Patch added: net-tools_1.60-25ubuntu2.1.debdiff
This has been fixed on the Debian package net-tools version 1.60-26, May
12th 2014.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541172
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-tools in Ubuntu.
Hi Chris,
The package in -proposed fixed this bug.
Test-case from description. Details below.
root@ubuntu:~# apt-cache madison net-tools
net-tools | 1.60-25ubuntu2.1 | http://ports.ubuntu.com/ubuntu-ports/
trusty-proposed/main ppc64el Packages
[...]
I got news we have the patch on top of Ubuntu's src pkg available, and
that it will be attached here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318809
Title:
Support for the ppc64el arch
To
Hi Matthias,
I built a test version of the crash package for internal testing here.
It's probably going to have its round of testing on Monday (due to timezone
differences).
It's just
- the patches above in gdb-7.6-ppc64el.patch (filterdiff --strip=1
--addprefix=gdb-7.6/ patches/*.patch)
Hi Tim,
Ok! The kernel in -proposed has those bits.
They're working.
The expected cpufreq files showed up in /sys/devices/system/cpu/cpu0/cpufreq/*,
and frequency went up and down as expected when setting governors to
performance, powersave, ondemand (default).
--
You received this bug
Question..
The powernv-cpufreq module is not automatically loaded by the kernel (even if
put in the initramfs).
Would it be possible to have it built-in (rather than as a module) in
some time?
As discussed on Ubuntu's kernel-team mailing list, it fails gracefully on
non-compatible hardware
Hi Matthias,
Yes, we need this for trusty.
Thanks.
** Changed in: crash (Ubuntu)
Status: Incomplete = 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/1318809
Title:
Support for
Public bug reported:
Bug originally reported and fixes provided by Brian Hart, IBM.
Various warnings will be seen when building an out-of-tree module with
-Wsign-compare if any of the following are included:
include/linux/bitops.h
include/linux/cpumask.h
include/linux/fb.h
Seen on post-release
The e-mail thread mentions 'Trusty SRU' on subject, but not sure where
to reflect it on this bug's fields.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321791
Title:
Warnings when building
Patches submitted to the mailing list. [1]
Marking this as confirmed since I confirmed Brian's report.
[1] https://lists.ubuntu.com/archives/kernel-team/2014-May/043098.html
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a
Tim asked for waiting the 2 commits in linux-next to make into linux.
I'll ping him when that happens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321791
Title:
Warnings when building
This seems to be 1312623.
The previous description there looks similar to this one:
summary: - fatal error: caught unhandled signal 11
+ fatal error: hadoop causes SEGV in OpenJDK
Maybe this was marked invalid because of that.
Then this should just be marked as
Public bug reported:
Hi,
Is it possible to (discuss how to) enable the crash package to on the
ppc64el arch?
Recently the kernel received the config changes
(CONFIG_CRASH_DUMP=y, CONFIG_RELOCATABLE=y, currently in the -proposed pocket
[1])
Is it hard to move to GDB 7.7? (ppc64el GDB package
This has been fixed on the Debian package net-tools version 1.60-26, May
12th 2014.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541172
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251563
This is Debian Bug #541172 [1].
There's a patch available there at message #15 [2], but it didn't make into the
package.
It fixes the problem.
Unfortunately it seems there's some issue contacting the package maintainers,
given that bug's age. I tried to help there.
[1]
Meanwhile, is it possible to carry that patch in the Ubuntu package?
This is the patch/debdiff for that, on top of the current source package
in Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Meanwhile, is it possible to carry that patch in the Ubuntu package?
This is the patch/debdiff for that, on top of the current source package
in Trusty.
** Patch added: net-tools_1.60-25ubuntu2.1.debdiff
Public bug reported:
From another, less public, bug:
Text by Bill Schmidt:
A GCC bug was found in the little endian vector API that affects use of
the vec_mergeh and vec_mergel interfaces when VSX is enabled (this is
the default for Power8). These interfaces produce the wrong results for
4x32
** Changed in: debian-installer (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358505
Title:
Need Ubuntu to preinstall ppc64-diag and other basic packages
Hi Canonical / Adam,
This is an issue for ppc64el guests too, as it impacts disk hotplug
(internal bug reports).
Fortunately, just installing ppc64-diag will bring in other required
packages for this functionality (powerpc-ibm-utils and librtas pieces).
[...] we need to look into where and
Thanks, Chris!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324544
Title:
makedumpfile: kdump-config load fails with vmlinux kernel (vs.
vmlinuz)
To manage notifications about this bug go to:
Hi Chris Laurent,
Aren't these other 2 ppc64el-specific patches required too?
- kexec/ppc64: Handle reserved memory ranges exported by OPAL firmware.
- kexec/ppc64: Fix up ELF header and dt for PowerNV platform.
I'm not knowledgeable in kexec, but I see those upstream post-2.0.6 as
well.
--
** Patch added: ppc64el-vmlinuz-d-i.debdiff
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358920/+attachment/4181881/+files/ppc64el-vmlinuz-d-i.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hi,
May we discuss/implement switching the kernel image type/filename on
ppc64el from vmlinu*x* to vmlinu*z* ?
Problem:
In the current situation, some issues occur because of 1) or 2):
1) the presence of /boot/vmlinu*x* w/ no debug symbols (vmlinux
Thanks.
For the record, I'll file bugs upstream for the userpace tools failing
(discussed on irc).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358920
Title:
Swith kernel to vmlinuz (from
Thanks for veryfing and confirming this :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1325606
Title:
grub-installer fails on disks 26th (restrictive shell pattern)
To manage notifications
Hi Chris,
The package in -proposed fixed this bug.
Test-case from description. Details below.
root@ubuntu:~# apt-cache madison net-tools
net-tools | 1.60-25ubuntu2.1 | http://ports.ubuntu.com/ubuntu-ports/
trusty-proposed/main ppc64el Packages
[...]
** Patch added: makedumpfile-vmlinux-trusty.debdiff
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1324544/+attachment/4203116/+files/makedumpfile-vmlinux-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: makedumpfile-vmlinux-utopic.debdiff
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1324544/+attachment/4203115/+files/makedumpfile-vmlinux-utopic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attaching debdiffs for Utopic and Trusty.
The patch fixes this issue:
$ sudo kdump-config load
Cannot open `/boot/vmlinuz-3.16.0-14-generic': No such file or directory
* failed to load kdump kernel
Test OK on Utopic:
$ sudo kdump-config load
Modified
Marking as confirmed since this is hit / mentioned as part of LP
#1352056 and LP #1350443
** Changed in: makedumpfile (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Chris,
Thanks for fixing this out.
One question:
[Test Case]
Taken from:
https://wiki.ubuntu.com/Kernel/CrashdumpRecipe
[...]
2) increase crashdump size:
sudo vim /etc/default/grub.d/kexec-tools.cfg
set crashkernel=1024M
Is there any possibility to make this value something
@arges
Ok! Thanks for letting us know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352056
Title:
linux: kdump on Ubuntu 14.04 is not generating a dump.
To manage notifications about this bug
Yes; updating the bug title to disambiguate. Thanks.
** Summary changed:
- grub-installer fails on 26+ disks (restrictive shell pattern)
+ grub-installer fails on disks 26th (restrictive shell pattern)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
(according to this snippet in description)
Problem:
---
grub-installer fails on disks greater than the 26th disk.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1325606
Title:
Thanks, Brian.
I just passed along in the kernel-team mailing list, as Tim requested last time.
I'll ping you once there are news.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321791
Title:
... guy is blazing fast; commits in master-next.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321791
Title:
Warnings when building out-of-tree module with -Wsign-compare
To manage notifications
Hi Kalpana,
Can you please test the version in -proposed?
I dont have virsh handy in my environment, and kdump-tools is not quite
working here (I'll follow up internally).
(add the trusty-proposed repo as in comment #14, then reinstall the
package, if the dev version is still there)
$ sudo
Hi Chris,
Thanks, I see the new version in trusty-proposed.
$ echo 'deb http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed restricted
main multiverse universe' | sudo tee
/etc/apt/sources.list.d/trusty-proposed.list
deb http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed restricted main
Public bug reported:
On ppc64el, there's no vmlinu/z/, only vmlinu/x/.
Thus, kdump-config load fails as follows:
# kdump-config load
Cannot open `/boot/vmlinuz-3.13.0-27-generic': No such file or directory
* failed to load kdump kernel
This small patch (attached) fixes the issue.
It defaults
Chris,
One of the bugs in the way for in-guest generated crash dumps is [1].
Is it possible for you to please help there, just to make it gets assigned
quickly?
Thank you very much,
[1] https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1324544
--
You received this bug notification
Public bug reported:
The cpufreq driver for powernv is currently built as a module (powernv-
cpufreq.ko; see bug 1309576).
It is not automatically loaded in the boot process (even when included
in the initrd).
It is desirable to have it built-in so it automatically loads on systems
booting in
Hi,
This bug is missing log files that will aid in diagnosing the problem. [...]
[...]
This change has been made by an automated script, maintained by the Ubuntu
Kernel Team.
Since the problem's diagnostic is clear (i.e., see the current config
files), and the patch sent to the kernel-team
Thanks, Kalpana.
Changing the tag to verification-done, as per Kalpana's comment #17, as
requested on comment #12.
[...] If this package fixes the bug for you, please add a comment to this
bug,
mentioning the version of the package you tested, and change the tag from
verification-needed
Public bug reported:
Problem:
---
grub-installer fails on disks greater than the 26th disk.
Upfront, I acknowledge this is an unlikely scenario, but that problem was
caught by test teams,
and it might be worth fixing (proposal included below) for some
application/cases/environments.
Attaching patch w/ 'solution proposal' (mentioned in description).
** Patch added: grub-installer-26plus-disks.patch
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1325606/+attachment/4124172/+files/grub-installer-26plus-disks.patch
--
You received this bug notification
Hi Phillip,
Hm, that I'm not sure of..
IIRC that part of the code expects only the disk block device without the
partition number, but I haven't gone through it in detail.
(I guess the [0-9] range is there for disks named after sd1 or something like
that, which I haven't seen yet, but recall
The packages in proposed fix it.
Thanks.
$ ARCH=powerpc make -C /usr/src/linux-headers-`uname -r` M=`pwd` clean modules
21 | fgrep Wsign-compare
include/linux/bitops.h:77:3641: warning: signed and unsigned type in
conditional expression [-Wsign-compare]
include/linux/cpumask.h:603:26: warning:
For the record:
$ uname -r
3.13.0-32-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321791
Title:
Warnings when building out-of-tree module with -Wsign-compare
To manage notifications
Thanks for all the effort involved. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358920
Title:
Switch kernel to vmlinuz (from vmlinux) on ppc64el
To manage notifications about this bug go to:
Except that OPAL/petitboot cannot boot a zImage ... FAIL !~
Epic fail.
Really sorry about that (and the effort involved).
Apologies, everyone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358920
AFAICT from the long description,
this bug needs the patches from these 2 open bugs:
LP #1324544
LP #1349994
Both in 'New' state, so meaning those patches haven't been
committed/released in packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Here's the installer screens confirming patch [1] (in comment #10) fixes
the issue on ppc64el:
Running Vivid installer, with priority=low.
Go through Partition Disks - Guided - use entire disk - (select disk) -
Separate /home, /usr, /var, and /tmp partitions
Before patch:
---
-
Hi Canonical / Brian @brian-murray,
This bug is fixed with these 2 upstream commits in d-i partman-auto:
- [1] ppc64el-only: Combine / and /usr partitions in ppc64el 'multi' recipe
- [2] other archs: Combine / and /usr partitions in 'multi' recipes
I confirm [1] fixes the issue for us
@nio-wiklund
Hi, not sure why it didn't work for your cmdline.
If you're still interested in debugging, the option you entered is correct,
as you can see on net-retriever source code:
if db_get debian-installer/allow_unauthenticated [ $RET = true ]; then
log Not
@pitti
Hi, Martin.
Would you have any update on the process of resolving this (maybe someone/I can
help?), or its severity (what's the impact?)
Thanks a lot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Canonical, @mathieu-tl
Would you have any news on uploading the new/fixed ppc64el recipes for
partman-auto in comment #10?
Funny, yesterday there was an re-upload of the old/broken ppc64el
recipes in partman-auto/118ubuntu5. :)
Thanks!
--
You received this bug notification because you are
There's a workaround available meanwhile -- if you want to use the
currently available netboot image, and can afford skipping the GPG
checks/its implications.
Append this to the kernel command line: debian-
installer/allow_unauthenticated=true
--
You received this bug notification because you
@apw thanks, Andy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413646
Title:
15.04: incomplete debug symbols package - please disable
CONFIG_DEBUG_INFO_SPLIT or package the .dwo files
To
Public bug reported:
The kernel option CONFIG_DEBUG_INFO_SPLIT has been enabled in vivid
(commit bb5f2d940954fb389f16a0f7ad05b5a53a7e5227).
It moves debuginfo to .dwo files, using gcc -split-dwarf.
The kernel packaging received no updates to include the .dwo files, AFAICT.
This results in
*** This bug is a duplicate of bug 1413646 ***
https://bugs.launchpad.net/bugs/1413646
** Changed in: crash (Ubuntu)
Status: New = Confirmed
** This bug has been marked a duplicate of bug 1413646
15.04: incomplete debug symbols package - please disable
CONFIG_DEBUG_INFO_SPLIT or
Hi Adam,
Thanks for looking into this.
I'd like add another reason for your consideration :)
Unless someone can give me a solid reason otherwise, however, I'm going to
make this a wishlist priority,
as the netboot kernel/initrd are published elsewhere ([...]), so it's merely
a
Hi Mathieu,
That's great news! Thank you ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410573
Title:
Expert mode installation fails with error
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1004243 ***
https://bugs.launchpad.net/bugs/1004243
This bug happened due to bug 1004243. Marking as duplicate.
The problem was the /etc/multipath.conf file wasn't copied from
installer to disk, as multipath detection failed (/sbin/multipath was
missing
*** This bug is a duplicate of bug 1004243 ***
https://bugs.launchpad.net/bugs/1004243
This bug happened due to bug 1004243. Marking as duplicate.
The problem was the /etc/multipath.conf file wasn't copied from
installer to disk, as multipath detection failed (/sbin/multipath was
missing
*** This bug is a duplicate of bug 1004243 ***
https://bugs.launchpad.net/bugs/1004243
** This bug has been marked a duplicate of bug 1004243
multipath installs not working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1004243 ***
https://bugs.launchpad.net/bugs/1004243
** This bug has been marked a duplicate of bug 1004243
multipath installs not working
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Adding tag 'verification-done-utopic' as requested in comment 13.
Verification done internally, but the bug mirroring didn't fully did the tags.
** Tags added: verification-done-utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You can find more info about that in preseed, debian installer options.
Basically boot options taken by the installer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403982
Title:
mini.iso
Hi Mathieu,
I just verified with the new package, and it's all set.
There's no /usr anymore, and / is 5.0 GB.
Thank you very much.
│ SCSI2 (0,1,0) (sda) - 34.4 GB QEMU QEMU HARDDISK
│ 1.0 MB FREE SPACE
│ #1 7.3 MBK
│ #2 5.0 GBf ext4
Unrelated comment. It seems the bugproxy quite liked that post/comment
it's been re-posting often. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410573
Title:
Expert mode installation fails
Hi Steve,
Given that we *know* that the UUID is not unique in the multipath scenario,
and know this at install time, I think it's wrong for us to configure the
system
to reference filesystems via this non-unique identifier.
I see your point.
Although, I'm not sure it's technically
To illustrate the problem more clearly:
The 'multipath' command is run *before* the disks over FC show up.
It must wait for them to settle.
There's a wait for SCSI devices already, but it is not enough in this case.
(it actually doesn't work because scsi_wait_scan was removed from the kernel
Constraints:
1) Can't count on udev rules to run 'multipath' (see bug 1431650)
Ideas:
0) sleep when there's no scsi_wait_scan module. (below)
1) make sure related SCSI modules are loaded before scsi_complete_async_scans()
(drivers/scsi/scsi_scan.c) is called.
2) loop waiting for the number of
And illustrating the previous point (root filesystem on single-path
device):
(initramfs) cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinux-3.19.0-8-generic
root=UUID=3809b2f8-dcb0-4a6a-945a-885e384b463e ro break=post-multipath
(initramfs) ls -l /dev/disk/by-uuid
...
Hi Mathieu,
The workaround seems good, but there still tends to be issues bringing up
the multipath devices on boot with QEMU in my testing; just the workaround
isn't always sufficient: break=pre-multipath then resuming helps out there.
May you describe the issues you're seeing?
I guess I
Hi Mathieu,
The workaround seems good, but there still tends to be issues bringing up
the multipath devices on boot with QEMU in my testing; just the workaround
isn't always sufficient: break=pre-multipath then resuming helps out there.
May you describe the issues you're seeing?
I guess I
This looks like bug 1429327 ('multipath' runs *before* all disks show
up).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431650
Title:
Multipath devices take long to initialize during initramfs
This looks like bug 1429327 ('multipath' runs *before* all disks show
up).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1431650
Title:
Multipath devices take long to
Nice comment on a lvm-devel thread:
The removal of scsi_wait_scan doesn't actually mean any of the bus scans are
done when you wait on systemd-udev-settle, so making that change won't
really solve the issue you need. If I'm understanding it right, I think
in a world without scsi-wait-scan,
FYI
This problem becomes more evident/likely if the fix/work-around for bug
1431650 is applied (i.e., no udev time-out for multipath devices).
It seems that the time-out that arises from that bug gives the SCSI scan
time to complete, and by the time the last 'multipath' command runs
This commit should fix this bug, and probably bug 1429327 as well.
https://github.com/hreinecke/multipath-tools/commit/841977fc9c3432702c296d6239e4a54291a6007a
It should allow multipath to be run in udev rules w/out timeout/killing (fixes
this bug),
and thus restore the functioning of
Hi Mathieu,
Hi Mauricio, I'd be very interested in looking at the patches [...]
Sorry for the delay. I missed this w/ some issue w/ email servers.
I'll attach them soon.. just cleaning up 2 minor points.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Mathieu,
Hi Mauricio, I'd be very interested in looking at the patches [...]
Sorry for the delay. I missed this w/ some issue w/ email servers.
I'll attach them soon.. just cleaning up 2 minor points.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
This commit should fix this bug, and probably bug 1429327 as well.
https://github.com/hreinecke/multipath-tools/commit/841977fc9c3432702c296d6239e4a54291a6007a
It should allow multipath to be run in udev rules w/out timeout/killing (fixes
this bug),
and thus restore the functioning of
Possibly good news.
See bug 1431650 comment 10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429327
Title:
ISST-LTE: system drops to initramfs after install on multipath disk
To manage
Updated replies to earlier comments:
comment #6
I think this all goes back to multipath-tools updates that would help a whole
lot; but they may be a little too intrusive past feature freeze -- I'm
looking into just updating the udev rules now.
Just to clarify/respond to that (earlier than
Hi Mathieu,
I did some research for the commit mentioned in comment #10.
Its description clarifies (how/why) it solves this problem, and even
others we would probably hit later (e.g., after booting, SCSI disks
added/removed re-trigerring udev rules, and then involving multipathd).
It's been
Hi Mathieu,
I did some research for the commit mentioned in comment #10.
Its description clarifies (how/why) it solves this problem, and even
others we would probably hit later (e.g., after booting, SCSI disks
added/removed re-trigerring udev rules, and then involving multipathd).
It's been
Updated replies to earlier comments:
comment #6
I think this all goes back to multipath-tools updates that would help a whole
lot; but they may be a little too intrusive past feature freeze -- I'm
looking into just updating the udev rules now.
Just to clarify/respond to that (earlier than
Well, not necessarily. The swap issue is the same as the rootfs one
Ah, yes, you're right.
I was thinking with the assumption that the workaround/patch for the timeout
was in place.
Indeed, if it's not in place, there'll be no swap nor anything multipath'ed at
all.
In the particular case the
Well, not necessarily. The swap issue is the same as the rootfs one
Ah, yes, you're right.
I was thinking with the assumption that the workaround/patch for the timeout
was in place.
Indeed, if it's not in place, there'll be no swap nor anything multipath'ed at
all.
In the particular case the
** Attachment added: Steps to Reproduce
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1430074/+attachment/4339388/+files/reproducing_mpathsep.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Solution Testing
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1430074/+attachment/4339389/+files/testing_mpathsep.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This bug is an umbrella for a number of bugs in the debian-installer with
common
root cause: the different disk-partition separator used for multipath partition
block devices by parted_server (libparted) and some components of the installer.
The specific problems will be
** Patch added: Patch to partman-base
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1430074/+attachment/4339390/+files/partman-base_mpathsep.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: Patch to grub-installer
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1430074/+attachment/4339395/+files/grub-installer_mpathsep.debdiff
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
1 - 100 of 1798 matches
Mail list logo
