[Bug 1916931] Re: omshell returns inconsistent results or segfaults
I've noticed that the omshell as shipped in the package is doing bad things memory access wise... $ valgrind /usr/bin/omshell ==735304== Memcheck, a memory error detector ==735304== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==735304== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==735304== Command: /usr/bin/omshell ==735304== ==735304== Conditional jump or move depends on uninitialised value(s) ==735304==at 0x48760C0: irs_resconf_load (in /usr/lib/x86_64-linux-gnu/libirs-export.so.161.0.1) ==735304==by 0x155D67: dhcp_dns_client_setservers (isclib.c:51) ==735304==by 0x15620B: dns_client_init (isclib.c:381) ==735304==by 0x15620B: dns_client_init (isclib.c:354) ==735304==by 0x1562BB: dhcp_context_create (isclib.c:246) ==735304==by 0x114C15: dhcpctl_initialize (dhcpctl.c:45) ==735304==by 0x11374B: main (omshell.c:118) ==735304== > connect ==735304== Invalid read of size 8 ==735304==at 0x14EC6B: omapi_one_dispatch (dispatch.c:676) ==735304==by 0x14F462: omapi_wait_for_completion (dispatch.c:455) ==735304==by 0x114D62: dhcpctl_connect (dhcpctl.c:115) ==735304==by 0x113F23: main (omshell.c:420) ==735304== Address 0x7010cf0 is 32 bytes inside a block of size 96 free'd ==735304==at 0x483CA3F: free (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==735304==by 0x14A39F: dfree (alloc.c:203) ==735304==by 0x14A39F: omapi_object_dereference (alloc.c:709) ==735304==by 0x14E1DA: omapi_io_dereference (dispatch.c:39) ==735304==by 0x14E1DA: omapi_unregister_io_object (dispatch.c:410) ==735304==by 0x14B217: omapi_disconnect.part.0 (connection.c:528) ==735304==by 0x14B4C4: omapi_disconnect (connection.c:465) ==735304==by 0x14B4C4: omapi_connection_connect_internal (connection.c:728) ==735304==by 0x14B61C: omapi_connection_connect (connection.c:615) ==735304==by 0x14EC4E: omapi_one_dispatch (dispatch.c:693) ==735304==by 0x14F462: omapi_wait_for_completion (dispatch.c:455) ==735304==by 0x114D62: dhcpctl_connect (dhcpctl.c:115) ==735304==by 0x113F23: main (omshell.c:420) ==735304== Block was alloc'd at ==735304==at 0x483DD99: calloc (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==735304==by 0x149F11: dmalloc (alloc.c:71) ==735304==by 0x14A094: omapi_object_allocate (alloc.c:543) ==735304==by 0x14: omapi_io_allocate (dispatch.c:39) ==735304==by 0x14: omapi_register_io_object (dispatch.c:223) ==735304==by 0x14BCA7: omapi_connect_list (connection.c:219) ==735304==by 0x14C012: omapi_connect (connection.c:96) ==735304==by 0x146BD6: omapi_protocol_connect (protocol.c:55) ==735304==by 0x114D21: dhcpctl_connect (dhcpctl.c:106) ==735304==by 0x113F23: main (omshell.c:420) ==735304== dhcpctl_connect: no more When I build ISC's dhcpd from their git repository manually, not using the source package, it works fine. I haven't got to the bottom of it, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916931 Title: omshell returns inconsistent results or segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1916931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835054] Re: Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64
Ah, of course - I should have noticed comment #8 myself, sorry... Just booted with: $ uname -a Linux macchiatobin 5.0.0-25-generic #26-Ubuntu SMP Thu Aug 1 12:05:25 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux $ dpkg -S /boot/vmlinuz-5.0.0-25-generic linux-image-5.0.0-25-generic: /boot/vmlinuz-5.0.0-25-generic and it all looks fine, thanks! May I also inquire about the installer, please? Will the daily builds, particularly the server flavour (as it's the one that is being built for aarch64 these days): http://cdimage.ubuntu.com/ubuntu-server/daily/current/ get updated with the newer kernel once it's released into updates? It would be very important for less-experienced user... ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835054 Title: Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835054] Re: Missing NIC driver for Armada 8040 (Macchiatobin)
Update and good news: I've been reminded that the firmware I have can boot the platform with either ACPI and Device Tree tables. I've been in ACPI mode and now, after flipping to DT, the platform boots fine and all 4 interfaces (one thing I haven't noticed that only one was completely missing previously) get detected and are functional. The wget kernel.org/big.tarball works fine now as well, so I think this proves that the CONFIG_MVPP2=m was all that was needed. Thanks! ** Description changed: At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) - a driver for network controllers(s) in Marvell SOCs, particularly Armada 8040 - - neither as a model or a built-in: + neither as a module or a built-in: $ uname -m aarch64 - $ grep MVPP2 /boot/config-5.0.0-20-generic + $ grep MVPP2 /boot/config-5.0.0-20-generic $ It makes very hard (and impossible for non-advanced users) to install and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) - a reasonably priced and performant server/mini-desktop platform. Could it be added, please, and the installer image re-generated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835054 Title: Missing NIC driver for Armada 8040 (Macchiatobin) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835054] Re: Missing NIC driver for Armada 8040 (Macchiatobin)
Good news: The module is *definitely* built and loads fine. Thanks! Bad news: The driver has some issues... Full boot log attached, but first of all, spot the delay: ... [2.849454] mvpp2 MRVL0110:00 eth0: Using random mac address ee:ad:f4:3c:ad:cf ... [2.932894] mvpp2 MRVL0110:01 eth1: Using random mac address 16:0c:52:c7:5a:cb ... [2.946932] mvpp2 MRVL0110:01 eth2: Using random mac address 7a:b8:9a:01:af:46 ... [2.962885] mvpp2 MRVL0110:01 enamrvl110i1: renamed from eth1 ... [3.229057] mvpp2 MRVL0110:01 rename4: renamed from eth2 ... [3.504865] mvpp2 MRVL0110:00 enamrvl110i0: renamed from eth0 ... [5.334377] Virtual CRAT table created for CPU [5.334414] Parsing CRAT table with 1 nodes [5.334450] Creating topology SYSFS entries [5.334512] Topology: Add CPU node [5.334545] Finished initializing topology [ 63.937562] systemd-udevd[201]: eth2: Worker [221] processing SEQNUM=1947 is taking a long time [ 93.650969] systemd-udevd[221]: eth2: Failed to rename network interface 4 from 'eth2' to 'enamrvl110i1': File exists [ 93.892377] raid6: neonx8 gen() 3687 MB/s [ 93.940370] raid6: neonx8 xor() 3241 MB/s [ 93.988376] raid6: neonx4 gen() 3112 MB/s [ 94.036370] raid6: neonx4 xor() 2696 MB/s [ 94.084377] raid6: neonx2 gen() 2644 MB/s ... Then, the "rename4" interface gets IP over DHCP and things seems ok, until I start generating more traffic (like pulling a tarball from kernel.org)... Then the interface "hangs", ie. no more data gets in nor out, but without any messages in the kernel log. For better or worse, these symptoms more or less match what I observed using Debian Buster installer over the weekend, so I suspect it's an issue with "my" firmware (I believe others made it work on Macchiatobin). >From the "missing driver" perspective, the problem has been fixed :-) ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+attachment/5275626/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835054 Title: Missing NIC driver for Armada 8040 (Macchiatobin) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835054] Re: Missing NIC driver for Armada 8040 (Macchiatobin)
Can't really provide logs here... One thing I figured out in the
meantime is that the source package seems to be building it for armhf:
debian.master/config/config.common.ubuntu:CONFIG_MVPP2=m
debian.master/config/annotations:CONFIG_MVPP2
policy<{'armhf': 'm'}>
so perhaps all is needed is adding a policy for arm64.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835054
Title:
Missing NIC driver for Armada 8040 (Macchiatobin)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835054] [NEW] Missing NIC driver for Armada 8040 (Macchiatobin)
Public bug reported: At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) - a driver for network controllers(s) in Marvell SOCs, particularly Armada 8040 - neither as a model or a built-in: $ uname -m aarch64 $ grep MVPP2 /boot/config-5.0.0-20-generic $ It makes very hard (and impossible for non-advanced users) to install and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) - a reasonably priced and performant server/mini-desktop platform. Could it be added, please, and the installer image re-generated. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835054 Title: Missing NIC driver for Armada 8040 (Macchiatobin) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1692876] Re: ubuntu-server ARM64 ISO images not EFI compliant
> [This is an automated message. I apologize if it reached you > inappropriately; please just reply to this message indicating so.] As far as I can say (even after reviewing the wiki page) there's no relevant source package for that issue, not even the debian-installer one, as the ISO images are built by an "external" infrastructure... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692876 Title: ubuntu-server ARM64 ISO images not EFI compliant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1692876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692876] [NEW] ubuntu-server ARM64 ISO images not EFI compliant
Public bug reported: After downloading a 17.04 ubuntu-server image for ARM64: http://cdimage.ubuntu.com/releases/17.04/release/ubuntu-17.04-server- arm64.iso and using it to create a USB drive with /usr/bin/usb-creator-gtk, I can't boot the installer on my EFI-powered ARM64 machine, because the image is not EFI compliant. See here: $ fdisk -l ubuntu-17.04-server-arm64.iso Disk ubuntu-17.04-server-arm64.iso: 618.1 MiB, 648083456 bytes, 1265788 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes $ file ubuntu-17.04-server-arm64.iso ubuntu-17.04-server-arm64.iso: ISO 9660 CD-ROM filesystem data 'Ubuntu-Server 17.04 arm64' (bootable) As you can see it's just a "flat" ISO 9660 image. In result my EFI firmware doesn't even try using it as it expects a FAT32-formatted EFI partition. Even after transferring the files over, I can't boot it, because it doesn't come with EFI build of Grub (grubaa64.efi). Then, after providing it manually I've managed to install the system, but with problems again - the installer didn't find the media automatically (was probably looking for partitions like /dev/sda1 while the media is only available as /dev/sda). In comparison, the AMD64 version looks like this: $ fdisk -l ubuntu-17.04-server-amd64.iso Disk ubuntu-17.04-server-amd64.iso: 685 MiB, 718274560 bytes, 1402880 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x5aac927d Device Boot Start End Sectors Size Id Type ubuntu-17.04-server-amd64.iso1 * 0 1402879 1402880 685M 0 Empty ubuntu-17.04-server-amd64.iso2 286608 2912154608 2.3M ef EFI (FAT-12/ $ file ubuntu-17.04-server-amd64.iso ubuntu-17.04-server-amd64.iso: DOS/MBR boot sector ISO 9660 CD-ROM filesystem data (DOS/MBR boot sector) 'Ubuntu-Server 17.04 amd64' (bootable); partition 2 : ID=0xef, start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 286608, 4608 sectors Also, Debian testing images work fine, being built the EFI way: $ fdisk -l debian-testing-arm64-netinst.iso Disk debian-testing-arm64-netinst.iso: 200 MiB, 209715200 bytes, 409600 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x DeviceBoot StartEnd Sectors Size Id Type debian-testing-arm64-netinst.iso1 0 407551 407552 199M 83 Linux debian-testing-arm64-netinst.iso2 407552 40959920481M ef EFI (FAT-1 $ ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692876 Title: ubuntu-server ARM64 ISO images not EFI compliant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1692876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643922] Re: Network installer fails to detect network on AMD Overdrive (ARM64)
Just checked and glad to see that http://ports.ubuntu.com/dists/xenial- updates/main/installer-arm64/current/images/MANIFEST.udebs now shows kernel-image-4.4.0-62-generic-di 4.4.0-62.83 with the driver in question built. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643922 Title: Network installer fails to detect network on AMD Overdrive (ARM64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665322] Re: LDAP-based sudo roles stopped working in 16.04
** Description changed:
After upgrading from 14.04 LTS to 16.04 LTS, we noticed that LDAP-based
sudo roles stopped working, meaning users that were able to use sudo in
the past, are rejected now.
After investigation, it turned out to be a known upstream bug:
https://bugzilla.sudo.ws/show_bug.cgi?id=757
which was introduced somewhere between 14.04 and 16.04 timelines.
To cut the long story short, the code is trying to match FQDN host name
(eg. "thehost.domain.com") against host name pattern provided in LDAP
(eg. "sudoHost: thehost") using strcmpi, which will - obviously - fail.
The fix is a single line change patch which found its way into sudo
version 1.8.18:
https://www.sudo.ws/repos/sudo/rev/605c03afc80f
Unfortunately both 16.04 and 16.10 seem to only use 1.8.16 (17.04 seemed
to have jumped to 1.8.19) so will need to carry the patch mentioned
above. Tested it locally and the re-built package with the patch added
- works file. My debian/patches/series looks like this now:
+ works fine. My debian/patches/series looks like this now:
- .../sudo-1.8.16$ cat debian/patches/series
+ .../sudo-1.8.16$ cat debian/patches/series
typo-in-classic-insults.diff
paths-in-samples.diff
keep_home_by_default.patch
also_check_sudo_group.diff
lp1565567.patch
sssd-doesnt-handle-netgroups.diff
sssd-fix-matching-loop.diff
ldap-hostname.diff
.../sudo-1.8.16$ cat debian/patches/ldap-hostname.diff
# HG changeset patch
# User Todd C. Miller
# Date 1473459982 21600
# Node ID 605c03afc80f4c3f55bfae62fcf4974f18cd77e8
# Parent 017866310d2486566cbde9f93486e788d0c046a8
Fix typo that broke short host name matching when the fqdn
flag is enabled. Bug #757
diff -r 017866310d24 -r 605c03afc80f plugins/sudoers/sudoers.c
--- a/plugins/sudoers/sudoers.c Thu Sep 08 16:38:08 2016 -0600
+++ b/plugins/sudoers/sudoers.c Fri Sep 09 16:26:22 2016 -0600
@@ -1069,7 +1069,7 @@
/* Not remote, just use user_host. */
if ((lhost = strdup(user_host)) != NULL) {
if (user_shost != user_host)
- shost = strdup(lhost);
+ shost = strdup(user_shost);
else
shost = lhost;
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665322
Title:
LDAP-based sudo roles stopped working in 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1665322/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665322] Re: LDAP-based sudo roles stopped working in 16.04
** Description changed:
After upgrading from 14.04 LTS to 16.04 LTS, we noticed that LDAP-based
sudo roles stopped working, meaning users that were able to use sudo in
the past, are rejected now.
After investigation, it turned out to be a known upstream bug:
https://bugzilla.sudo.ws/show_bug.cgi?id=757
which was introduced somewhere between 14.04 and 16.04 timelines.
To cut the long story short, the code is trying to match FQDN host name
(eg. "thehost.domain.com") against host name pattern provided in LDAP
(eg. "sudoHost: thehost") using strcmpi, which will - obviously - fail.
The fix is a single line change patch which found its way into sudo
version 1.8.18:
https://www.sudo.ws/repos/sudo/rev/605c03afc80f
Unfortunately both 16.04 and 16.10 seem to only use 1.8.16 (17.04 seemed
to have jumped to 1.8.19) so will need to carry the patch mentioned
above. Tested it locally and the re-built package with the patch added
works file. My debian/patches/series looks like this now:
.../sudo-1.8.16$ cat debian/patches/series
typo-in-classic-insults.diff
paths-in-samples.diff
keep_home_by_default.patch
also_check_sudo_group.diff
+ lp1565567.patch
+ sssd-doesnt-handle-netgroups.diff
+ sssd-fix-matching-loop.diff
ldap-hostname.diff
- .../sudo-1.8.16$ cat debian/patches/ldap-hostname.diff
+ .../sudo-1.8.16$ cat debian/patches/ldap-hostname.diff
# HG changeset patch
# User Todd C. Miller
# Date 1473459982 21600
# Node ID 605c03afc80f4c3f55bfae62fcf4974f18cd77e8
# Parent 017866310d2486566cbde9f93486e788d0c046a8
Fix typo that broke short host name matching when the fqdn
flag is enabled. Bug #757
diff -r 017866310d24 -r 605c03afc80f plugins/sudoers/sudoers.c
--- a/plugins/sudoers/sudoers.c Thu Sep 08 16:38:08 2016 -0600
+++ b/plugins/sudoers/sudoers.c Fri Sep 09 16:26:22 2016 -0600
@@ -1069,7 +1069,7 @@
- /* Not remote, just use user_host. */
- if ((lhost = strdup(user_host)) != NULL) {
- if (user_shost != user_host)
+ /* Not remote, just use user_host. */
+ if ((lhost = strdup(user_host)) != NULL) {
+ if (user_shost != user_host)
- shost = strdup(lhost);
+ shost = strdup(user_shost);
- else
- shost = lhost;
- }
+ else
+ shost = lhost;
+ }
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665322
Title:
LDAP-based sudo roles stopped working in 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1665322/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665322] [NEW] LDAP-based sudo roles stopped working in 16.04
Public bug reported:
After upgrading from 14.04 LTS to 16.04 LTS, we noticed that LDAP-based
sudo roles stopped working, meaning users that were able to use sudo in
the past, are rejected now.
After investigation, it turned out to be a known upstream bug:
https://bugzilla.sudo.ws/show_bug.cgi?id=757
which was introduced somewhere between 14.04 and 16.04 timelines.
To cut the long story short, the code is trying to match FQDN host name
(eg. "thehost.domain.com") against host name pattern provided in LDAP
(eg. "sudoHost: thehost") using strcmpi, which will - obviously - fail.
The fix is a single line change patch which found its way into sudo
version 1.8.18:
https://www.sudo.ws/repos/sudo/rev/605c03afc80f
Unfortunately both 16.04 and 16.10 seem to only use 1.8.16 (17.04 seemed
to have jumped to 1.8.19) so will need to carry the patch mentioned
above. Tested it locally and the re-built package with the patch added
works file. My debian/patches/series looks like this now:
.../sudo-1.8.16$ cat debian/patches/series
typo-in-classic-insults.diff
paths-in-samples.diff
keep_home_by_default.patch
also_check_sudo_group.diff
ldap-hostname.diff
.../sudo-1.8.16$ cat debian/patches/ldap-hostname.diff
# HG changeset patch
# User Todd C. Miller
# Date 1473459982 21600
# Node ID 605c03afc80f4c3f55bfae62fcf4974f18cd77e8
# Parent 017866310d2486566cbde9f93486e788d0c046a8
Fix typo that broke short host name matching when the fqdn
flag is enabled. Bug #757
diff -r 017866310d24 -r 605c03afc80f plugins/sudoers/sudoers.c
--- a/plugins/sudoers/sudoers.c Thu Sep 08 16:38:08 2016 -0600
+++ b/plugins/sudoers/sudoers.c Fri Sep 09 16:26:22 2016 -0600
@@ -1069,7 +1069,7 @@
/* Not remote, just use user_host. */
if ((lhost = strdup(user_host)) != NULL) {
if (user_shost != user_host)
- shost = strdup(lhost);
+ shost = strdup(user_shost);
else
shost = lhost;
}
** Affects: sudo (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665322
Title:
LDAP-based sudo roles stopped working in 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1665322/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643922] Re: Network installer fails to detect network on AMD Overdrive (ARM64)
Allow me to ask a polite and friendly question - can I count on the installer being refreshed any time soon? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643922 Title: Network installer fails to detect network on AMD Overdrive (ARM64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643922] Re: Network installer fails to detect network on AMD Overdrive (ARM64)
Apologies about the delay - I was away from the hardware for a couple of days. Just tested the netboot images from http://cdimage.ubuntu.com/ubuntu- server/daily/current/zesty-server-arm64.iso and it works perfectly fine. Glad to hear that the fix has been propagated into the new releases, but I still need to be able to install the LTS one. If I'm just stupid and miss the point that I can use Zesty installer to install Xenial, do educate me :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643922 Title: Network installer fails to detect network on AMD Overdrive (ARM64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643922] Re: Network installer fails to detect network on AMD Overdrive (ARM64)
** Description changed: Kernel 4.4.0-31.50 used in the newest version of the network installer for Xenial: http://ports.ubuntu.com/dists/xenial-proposed/main/installer- arm64/current/images/MANIFEST.udebs does not contain amd-xgbe module. In result the installer fails to initialize eth0 and can not continue. The lack of module has been addressed by LP#1597573, so that latest available udebs 4.4.0-47.68 now contain the relevant module, but the - netboot image doesn't seem to been regenerated. + netboot image doesn't seem to have been regenerated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643922 Title: Network installer fails to detect network on AMD Overdrive (ARM64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643922] [NEW] Network installer fails to detect network on AMD Overdrive (ARM64)
Public bug reported: Kernel 4.4.0-31.50 used in the newest version of the network installer for Xenial: http://ports.ubuntu.com/dists/xenial-proposed/main/installer- arm64/current/images/MANIFEST.udebs does not contain amd-xgbe module. In result the installer fails to initialize eth0 and can not continue. The lack of module has been addressed by LP#1597573, so that latest available udebs 4.4.0-47.68 now contain the relevant module, but the netboot image doesn't seem to been regenerated. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643922 Title: Network installer fails to detect network on AMD Overdrive (ARM64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 843628] Re: perf failure on panda (omap4)
It may be the same issue as https://bugs.launchpad.net/linaro-landing- team-freescale/+bug/893653/comments/6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/843628 Title: perf failure on panda (omap4) To manage notifications about this bug go to: https://bugs.launchpad.net/linaro-landing-team-ti/+bug/843628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 882956] Re: [Oneiric] [Dell XPS M1330] Gnome session dies at resume
I'd just like to point out that the mentioned script: 1. Is missing "esac" at the end of the file 2. Must be made executable (sudo chmod +x 50_custom) I'll do some testing during the next few days and report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882956 Title: [Oneiric] [Dell XPS M1330] Gnome session dies at resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/882956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 882956] Re: [Oneiric] [Dell XPS M1330] Gnome session dies at resume
This entry in syslog seems relevant (full suspend and resume log attached): Oct 29 18:55:01 rojo gnome-session[9054]: Gdk-WARNING: The program 'gnome-session' received an X Window System error.#012This probably reflects a bug in the program.#012The error was 'XI_BadDevice (invalid Device parameter)'.#012 (Details: serial 167 error_code 149 request_code 141 minor_code 48)#012 (Note to programmers: normally, X errors are reported asynchronously;#012 that is, you will receive the error a while after causing it.#012 To debug your program, run it with the --sync command line#012 option to change this behavior. You can then get a meaningful#012 backtrace from your debugger if you break on the gdk_x_error() function.)#012 (I have the same XPS M1330 variant, but use x86_64 arch) ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/882956/+attachment/2578259/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882956 Title: [Oneiric] [Dell XPS M1330] Gnome session dies at resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/882956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 764796] Re: Enable basic profiling & tracing options in kernel configuation
** Also affects: linaro-landing-team-ti Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/764796 Title: Enable basic profiling & tracing options in kernel configuation To manage notifications about this bug go to: https://bugs.launchpad.net/linaro-landing-team-freescale/+bug/764796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 764796] Re: Enable basic profiling & tracing options in kernel configuation
I just had a look at all the different kernels in https://launchpad.net /~linaro-maintainers/+archive/kernel and the configurations are still very different: lt-mx5 mx5 vexpress omap lt-omap HIGH_RES_TIMERS + + - + + LOCAL_TIMERS N/A N/A+ + + PROFILING + - + + + PERF_EVENTS + - - + - HW_PERF_EVENTS+ - + + - FTRACE- - + + + TRACING/GENERIC_TRACER- - - + + In result only the "omap" image is fully useful for profiling tasks (either with perf or Streamline). Also, I really wonder how the gator- module-* packages in the DS-5 PPA (https://launchpad.net/~linaro- maintainers/+archive/arm-ds5) build at all, as they need the above options being set... And, generally, wouldn't it be a good idea to unify kernel configuration (I mean the non-platform-dependent bits) across LTs and Platforms builds? As we are heading in the direction of Single Kernel to Rule Them All, this will be needed at some point of time anyway. The config files I've extracted from the debs and checked: config-2.6.38-1400-linaro-lt-mx5 config-3.0.0-1001-linaro-mx51 config-3.0.0-1001-linaro-vexpress config-3.0.0-1007-linaro-omap config-3.0.0-1402-linaro-lt-omap $ grep CONFIG_HIGH_RES_TIMERS=y * config-2.6.38-1400-linaro-lt-mx5:CONFIG_HIGH_RES_TIMERS=y config-3.0.0-1001-linaro-mx51:CONFIG_HIGH_RES_TIMERS=y config-3.0.0-1007-linaro-omap:CONFIG_HIGH_RES_TIMERS=y config-3.0.0-1402-linaro-lt-omap:CONFIG_HIGH_RES_TIMERS=y $ grep CONFIG_LOCAL_TIMERS=y * config-3.0.0-1001-linaro-vexpress:CONFIG_LOCAL_TIMERS=y config-3.0.0-1007-linaro-omap:CONFIG_LOCAL_TIMERS=y config-3.0.0-1402-linaro-lt-omap:CONFIG_LOCAL_TIMERS=y $ grep CONFIG_PROFILING=y * config-2.6.38-1400-linaro-lt-mx5:CONFIG_PROFILING=y config-3.0.0-1001-linaro-vexpress:CONFIG_PROFILING=y config-3.0.0-1007-linaro-omap:CONFIG_PROFILING=y config-3.0.0-1402-linaro-lt-omap:CONFIG_PROFILING=y $ grep CONFIG_PERF_EVENTS=y * config-2.6.38-1400-linaro-lt-mx5:CONFIG_PERF_EVENTS=y config-3.0.0-1001-linaro-vexpress:CONFIG_PERF_EVENTS=y config-3.0.0-1007-linaro-omap:CONFIG_PERF_EVENTS=y $ grep CONFIG_HW_PERF_EVENTS=y * config-2.6.38-1400-linaro-lt-mx5:CONFIG_HW_PERF_EVENTS=y config-3.0.0-1001-linaro-vexpress:CONFIG_HW_PERF_EVENTS=y config-3.0.0-1007-linaro-omap:CONFIG_HW_PERF_EVENTS=y $ grep CONFIG_FTRACE=y * config-3.0.0-1001-linaro-vexpress:CONFIG_FTRACE=y config-3.0.0-1007-linaro-omap:CONFIG_FTRACE=y config-3.0.0-1402-linaro-lt-omap:CONFIG_FTRACE=y $ grep -e "\(CONFIG_TRACING=y\|CONFIG_GENERIC_TRACER=y\)" * config-3.0.0-1007-linaro-omap:CONFIG_GENERIC_TRACER=y config-3.0.0-1007-linaro-omap:CONFIG_TRACING=y config-3.0.0-1402-linaro-lt-omap:CONFIG_TRACING=y -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/764796 Title: Enable basic profiling & tracing options in kernel configuation To manage notifications about this bug go to: https://bugs.launchpad.net/linaro-landing-team-freescale/+bug/764796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 764796] Re: Enable basic profiling & tracing options in kernel configuation
** Description changed: Could we have basic profiling & tracing options enabled in Linaro - vexpress kernel? I'd suggest: + kernel? I'd suggest: + CONFIG_HIGH_RES_TIMERS=y (for using hrtimers as a sampling clock) + CONFIG_LOCAL_TIMERS=y (for A9 targets, otherwise hrtimers don't work) CONFIG_PROFILING=y CONFIG_PERF_EVENTS=y CONFIG_HW_PERF_EVENTS=y CONFIG_FTRACE=y - CONFIG_ENABLE_DEFAULT_TRACERS=y - CONFIG_HIGH_RES_TIMERS=y - - (the last one allows using hrtimers as a sampling clock) + CONFIG_TRACING=y and/or CONFIG_GENERIC_TRACER=y (enabled by any tracer, eg. when ENABLE_DEFAULT_TRACERS=y) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/764796 Title: Enable basic profiling & tracing options in kernel configuation To manage notifications about this bug go to: https://bugs.launchpad.net/linaro-landing-team-freescale/+bug/764796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 673820] Re: Ethernet dies during large file transfers on vexpress
Ok, we have managed to fix the problem at the IO FPGA level. The updated bitfile will be release on the next VE CD (end of this year), in the meantime interested parties may contact ARM Support in order to get the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/673820 Title: Ethernet dies during large file transfers on vexpress To manage notifications about this bug go to: https://bugs.launchpad.net/linux-linaro/+bug/673820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 673820] Re: Ethernet dies during large file transfers on vexpress
> Comments! and/or proper symbolic names for those magic numbers would > be good for a final patch, of course :) I thought I made this clear - there will be no final patch :-) The entity responsible for SMC configuration is Boot Monitor. This patch is just a hack to confirm (or deny) my theory. > Do you believe the patch is a fix for this particular issue, or will > it just reduce the probability (and hence frequency) of problems? This hack is a work-around rather than a fix as it is probably too expensive in terms of I/O performance. We may be able to fix it properly on IO FPGA level. No promises, terms and conditions apply ;-) > Note that in either case the smsc911x driver is still believed to have > problems of its own, like incorrect FIFO skipping on bad packets, and > some SMP safety issues. No argument here. Even more - the driver can (and should) detect the problematic situation and perform soft reset to recover. So there are plenty of opportunities for improvements. This doesn't change the fact that (widely defined) hardware behaves incorrectly in this case. Paweł -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. 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/673820 Title: Ethernet dies during large file transfers on vexpress To manage notifications about this bug go to: https://bugs.launchpad.net/linux-linaro/+bug/673820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 673820] Re: Ethernet dies during large file transfers on vexpress
The "lock up" was caused by SMSC RX FIFO underruns caused by maginal timing issue between SMSC and USB host controller. The hack is enforcing additional wait cycle between accesses. Unfortunately it affects all peripherals, thus the performance penalty. What you observe is, I guess, situation when buffers are getting filled with data from Ethernet and are flushed to USB mass storage device and the host controller driver is "taking over" the bus, reducing SMSC traffic. Maybe you could use Streamline to see what is going on there :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/673820 Title: Ethernet dies during large file transfers on vexpress To manage notifications about this bug go to: https://bugs.launchpad.net/linux-linaro/+bug/673820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 673820] Re: Ethernet dies during large file transfers on vexpress
Could anyone give this patch a go? It's just a hack (if I'm right this will have to go to Boot Monitor, not kernel), but it may improve Ethernet stability, potentially at some cost of performance loss. Anyway - let me know. ** Patch added: "ve-eth.patch" https://bugs.launchpad.net/linux-linaro/+bug/673820/+attachment/2299695/+files/ve-eth.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/673820 Title: Ethernet dies during large file transfers on vexpress To manage notifications about this bug go to: https://bugs.launchpad.net/linux-linaro/+bug/673820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 764796] Re: Enable basic profiling & tracing options in kernel configuation
I'm not aware of any problems like that. There used to be some problems with FTRACE and some userspace tools, but it was mostly about symbol de- mangling, so in other words it doesn't break anything else. I've just spoken to Will Deacon and he has similar opinion, so yes - I'd say let's enable all of this on all platforms. Now, I had a look at OMAP flavour configuration and all the relevant options are already enabled there. Note that the "CONFIG_ENABLE_DEFAULT_TRACERS" is not available there, because other tracers are enabled and they select the "CONFIG_GENERIC_TRACER" option (that's the one we really care about ;-). It's all described in commit 5e0a093910876882f91f1d4b8a1635a099e6c7ba "tracing: fix config options to not show when automatically selected" in the main line. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/764796 Title: Enable basic profiling & tracing options in kernel configuation -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 764796] [NEW] Enable basic profiling & tracing options in kernel configuation
Public bug reported: Could we have basic profiling & tracing options enabled in Linaro vexpress kernel? I'd suggest: CONFIG_PROFILING=y CONFIG_PERF_EVENTS=y CONFIG_HW_PERF_EVENTS=y CONFIG_FTRACE=y CONFIG_ENABLE_DEFAULT_TRACERS=y CONFIG_HIGH_RES_TIMERS=y (the last one allows using hrtimers as a sampling clock) ** Affects: linux-linaro-vexpress (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/764796 Title: Enable basic profiling & tracing options in kernel configuation -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 673820] Re: Ethernet dies during large file transfers on vexpress
As said above it rather looks like the SMP problems in the smsc driver. Now, frankly speaking, I totally forgot about this issue, and it looks that I won't have chance to look into it in the nearest time. But, as we have ARM Landing Team now (allegedly ;-) maybe this bug should be assigned to them? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/673820 Title: Ethernet dies during large file transfers on vexpress -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632798] Re: USB/mmc rootfs conflict - vexpress
This is a backport of 8301bb68c6bb9836889641a47443aeb97b763f6c commit in the main line tree. ** Patch added: "ARM: 6310/1: mmci: support different FIFO sizes" https://bugs.launchpad.net/ubuntu/+source/linux-linaro/+bug/632798/+attachment/1901485/+files/0001-ARM-6310-1-mmci-support-different-FIFO-sizes.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632798 Title: USB/mmc rootfs conflict - vexpress -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632798] Re: USB/mmc rootfs conflict - vexpress
This patch adds support for MMCI with extended FIFO size. Kernels prior to 2.6.37 will also need backported commit 8301bb68c6bb9836889641a47443aeb97b763f6c "ARM: 6310/1: mmci: support different FIFO sizes" (will attach it to this bug). ** Patch added: "[PATCH] arm: mmci: Add ARM variant with extended FIFO" https://bugs.launchpad.net/ubuntu/+source/linux-linaro/+bug/632798/+attachment/1901484/+files/0002-arm-mmci-Add-ARM-variant-with-extended-FIFO.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632798 Title: USB/mmc rootfs conflict - vexpress -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632798] Re: USB/mmc rootfs conflict - vexpress
The problem will be worked around by extending the MMC FIFO size. This will be available in the coming VE CD release. A patch will be required on non-mainline kernels to support it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632798 Title: USB/mmc rootfs conflict - vexpress -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632798] Re: USB/mmc rootfs conflict - vexpress
Hack it is, without doubts ;-) I've already sent it upstream anyway, we'll see... Now, a word of comment: At least some of the Linaro file system images are running irqbalance daemon, which will most likely play with MMC and USB interrupts affiliation in runtime. To prevent it from doing so, /etc/default/irqbalance should contain this line: export IRQBALANCE_BANNED_INTERRUPTS="41 42 48" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632798 Title: USB/mmc rootfs conflict - vexpress -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632798] Re: USB/mmc rootfs conflict - vexpress
Have a look at this patch... ** Patch added: "0001-arm-Improve-MMC-performance-on-Versatile-Express.patch" https://bugs.launchpad.net/ubuntu/+source/linux-linaro/+bug/632798/+attachment/1801527/+files/0001-arm-Improve-MMC-performance-on-Versatile-Express.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632798 Title: USB/mmc rootfs conflict - vexpress -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 673820] Re: Ethernet dies during large file transfers on vexpress
Well, I feel it will end on my desk anyway ;-) I can't commit to any dates right now, but I've put this on my list and let you keep you informed. Of course I'll have to reproduce it here... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/673820 Title: Ethernet dies during large file transfers on vexpress -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632798] Re: USB/mmc rootfs conflict - vexpress
It may be even worse - I have some reports that with recent changes in L2 handling, all hell breaks loose during MMC operations. I'll start investigating this next week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632798 Title: USB/mmc rootfs conflict - vexpress -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632798] Re: USB/mmc rootfs conflict - vexpress
I did some further investigations...
1. MMC access are generally terribly slow - 45-50 kB/s writes, 60-65
kB/s reads. Expected value at least in hundreds kB/s - normal cards have
maximum throughput at least 1 MB/s, premium cards up to 5-10 MB/s!
2. USB accesses performed at the same time as MMC ones generate MMC
errors.
3. Reducing MMC clock frequency ("mmci.fmax=190") reduces number of
errors, for the price of slowing down (even more!) transfers.
4. Two possible sources of problem are: a bug in driver or underlying
hardware (VE motherboard peripherals FPGA) problem, with the latter more
probable (as the driver is used - presumably with success - in field).
Due to lack of time here, I'll have to pass the issue to ARM support
team.
--
USB/mmc rootfs conflict - vexpress
https://bugs.launchpad.net/bugs/632798
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184405] Wrong d_fmt definition in pl_PL locale
Public bug reported: Ubuntu 7.10, file /usr/share/i18n/locales/pl_PL, line 215: d_fmt "" This data format definition gives: $ LC_ALL=pl_PL.UTF8 locale -k d_fmt d_fmt="%-d %b %Y" Minus sign is wrong here, isn't it? A symptom of this problem is (among others I believe) a problem with Evolution calendar: https://bugs.launchpad.net/evolution/+bug/32089 Assuming that "%d %b %Y" format is correct for polish date (that's another discussion ;-), the definition should be: d_fmt "" --- bad/pl_PL 2007-08-24 17:02:18.0 +0100 +++ ok/pl_PL2008-01-19 18:56:21.0 + @@ -212,7 +212,7 @@ d_t_fmt "/ / " -d_fmt "" +d_fmt "" t_fmt "" am_pm "";"" t_fmt_ampm "" ** Affects: langpack-locales (Ubuntu) Importance: Undecided Status: New -- Wrong d_fmt definition in pl_PL locale https://bugs.launchpad.net/bugs/184405 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25784] Re: Wrong events for ASUS L3000D
Sorry, I have misspelled... My laptop is Asus A2H (more precisely A2500H) -- Wrong events for ASUS L3000D https://launchpad.net/bugs/25784 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25784] Re: Wrong events for ASUS L3000D
I can confirm the problem for 6.06 using Asus A4H laptop. (ATKD)|(HOTK) solves the problem. Additionally, this model uses slightly different hotkey code for wireless event - in place of "5d" it gives "52", so my asus-wireless file looks like this: event=hotkey (ATKD)|(HOTK) 005[d2] action=/etc/acpi/asus-wireless.sh -- Wrong events for ASUS L3000D https://launchpad.net/bugs/25784 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
