[Bug 1643345] Re: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build [Makefile:81: recipe for target 'modules' failed]
I did some poking around to see if I could figure out the root cause. I found there are a whole lot of differences between doing a fresh install of 16.04 and upgrading from 14.04 to 16.04 in terms of how the system is actually setup, so a quick let's try to find the one thing off was not going to fly. Another wall of sorts I hit is the Nvidia installer is a compiled application and I did not want to take the time to reverse engineer it in order to make sure I could replicate what it was doing step by step in order to figure out the exact step it fails on. A thought I had is I could try to figure out the DKMS calls setup to automatically re-compile the kernel module, but by this time I was feeling pretty fed up, so I just re-installed my laptop. With a fresh install of 16.04, the Nvidia drivers both compiled and work without issue as far as I can tell. I tried installing and opening Google Earth and glxgears and those seem to be working fine. Another thing that broke in the 'upgrade' to 16.04 was Bluetooth support. Bluetooth seems to work now that the system is re-installed from scratch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643345 Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build [Makefile:81: recipe for target 'modules' failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1643345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643345] Re: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build [Makefile:81: recipe for target 'modules' failed]
A baseline test I did was to update both a VM with a fresh install of Ubuntu 16.04 and my laptop where I upgraded from 14.04 to 16.04. With both systems up to date (March 25th, 2017) I tried to install the the latest Nvidia 375 drivers. It installed on the VM (though it is kind of worthless here), but hung up on my laptop just like it has in the past. With it both compiling and failing to compile on the same version and patch level of Ubuntu, just different paths to get to this point, I would think this points to an issue with Ubuntu, not Nvidia. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643345 Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build [Makefile:81: recipe for target 'modules' failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1643345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643345] Re: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build [Makefile:81: recipe for target 'modules' failed]
Scott, I tried the same things and got more or less the same result. The older drivers compile, but the machine crashes early in boot. If I remember correctly, this was the case all the way up to 364. Anything above, and I tried all the way up to 375, and it won't compile. I suspect the older drivers crash the system on boot because of the newer kernel on 16.04, which is 4.4 series while nvidia drivers version 364 lists kernel 4.1 and below in its support list. It is a good question why one compiles and another does not. This is one of the reasons why I circle around the notion that something did not get properly updated in the upgrade process build environment wise as it seems the pieces are there for an older driver to compile, but not for the newer one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643345 Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build [Makefile:81: recipe for target 'modules' failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1643345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643345] Re: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build [Makefile:81: recipe for target 'modules' failed]
I spent some time going through posts and trying various things. The best I can reckon from all information gathered so far is something about the upgrade process from 14.04 to 16.04 trips things up for the Nvidia driver build. If Ubuntu 16.04 is installed from scratch, people report it works, but the part of it not working during / after an upgrade from a previous Ubuntu release is consistent. The thing is I have a system that has so much going on on it that starting over would be a huge time kill, so solving this would probably take less time even if it is a bit involved to figure out. Also if it is working on some installations and not others depending on how Ubuntu was installed, that points to a possible issue on the open source side tripping up things on the Nvidia side of the fence. (The notion here clean install of open source 16.04 equals proper environment for Nvidia driver to build while something off kilter about the Ubuntu upgrade process equals broken environment for the Nvidia driver to try to build in. Of course I also would not discount the notion that everything from each team runs to their internally defined spec, but two teams had two different ideas on the details of what is a valid thing to do / expect from the other.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643345 Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build [Makefile:81: recipe for target 'modules' failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1643345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643345] [NEW] nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build
Public bug reported: The default selected nvidia driver 367 does not work in Ubuntu 16.04 64-bit. Hangs on build. Ran killall make in order to get updates to complete. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-367 (not installed) ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 DKMSKernelVersion: 4.4.0-45-generic Date: Sun Nov 20 08:45:49 2016 InstallationDate: Installed on 2014-09-28 (784 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 367.57-0ubuntu0.16.04.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: nvidia-graphics-drivers-367 Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build UpgradeStatus: Upgraded to xenial on 2016-10-20 (31 days ago) modified.conffile..etc.modprobe.d.nvidia-367_hybrid.conf: [deleted] ** Affects: nvidia-graphics-drivers-367 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial ** Description changed: The default selected nvidia driver 367 does not work in Ubuntu 16.04 - 64-bit. + 64-bit. Hangs on build. Ran killall make in order to get updates to + complete. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-367 (not installed) ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 DKMSKernelVersion: 4.4.0-45-generic Date: Sun Nov 20 08:45:49 2016 InstallationDate: Installed on 2014-09-28 (784 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 367.57-0ubuntu0.16.04.1 RelatedPackageVersions: - dpkg 1.18.4ubuntu1.1 - apt 1.2.15 + dpkg 1.18.4ubuntu1.1 + apt 1.2.15 SourcePackage: nvidia-graphics-drivers-367 Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build UpgradeStatus: Upgraded to xenial on 2016-10-20 (31 days ago) modified.conffile..etc.modprobe.d.nvidia-367_hybrid.conf: [deleted] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643345 Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1643345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559741] Re: wide-dhcpv6 client apparently sets incorrect PD specfic vltime
[solved] I seem to have found and fixed the problem and so have some
confirmation I was on the right track in my previous post. Specifically
in file common.c line 3328 I changed:
if (ioctl(s, ioctl_cmd, )) {
debug_printf(LOG_NOTICE, FNAME, "failed to %s an address on %s: %s",
cmdstr, ifname, strerror(errno));
close(s);
return (-1);
}
to:
if (ioctl(s, ioctl_cmd, )) {
if ((strcmp("add",cmdstr) !=0) || (strcmp("File
exists",strerror(errno)) != 0)) { //Ignore if trying to add existing address
debug_printf(LOG_NOTICE, FNAME, "failed to %s an address on %s: %s",
cmdstr, ifname, strerror(errno));
close(s);
return (-1);
}
}
I have gone over 36 hours now and have 3 renew operations in the logs and they
all look identical where before it was obviously not going well once I released
what I needed to look for. Also my internal subnets are still routing. I
figured 3 seemingly perfect renew cycles is enough to declare success in
solving this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559741
Title:
wide-dhcpv6 client apparently sets incorrect PD specfic vltime
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wide-dhcpv6/+bug/1559741/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559741] Re: wide-dhcpv6 client apparently sets incorrect PD specfic vltime
I made some headway in figuring this out. One thing I did not understand was T1 and T2 time and so was looking at the logs at the vltime hour mark. The proper place to be looking for the first error was at the T1 mark when the renew operation takes place. At this point the following happens in the logs: A Date XX:XX:XX machine_name dhcp6c[31722]: update_address: update an address ::::::: pltime=86400, vltime=86400 A Date XX:XX:XX machine_name dhcp6c[31722]: ifaddrconf: failed to add an address on WAN_interface: File exists A Date XX:XX:XX machine_name dhcp6c[31722]: update_ia: failed to update an address ::::::: A Date XX:XX:XX machine_name dhcp6c[31722]: dhcp6_remove_event: removing an event on WAN_interface, state=RENEW I went through the source code to try to trace this out and I came up with the system call to change the IP address fails and this causes the code to update the refresh timer to not execute as it executes after this call except in the case where the former operation fails, then it gets skipped. Once vltime for the WAN interface is reached the WAN interface expires and requests a new address, but the internal interfaces don't request such an update. I believe it is at this point of the WAN interface expiring and re-initing where Cox's server drops the route for the internal subnets. Specifically: 1. In dhcp6c_ia.c line 166 - Calls update_address() 2. In addrconf.c line 177 - Call to na_ifaddrconf() is made. This fails and returns before executing timer code below. 3. In addrconf.c line 396 - ifaddrconf() is made. 4. In common.c line 3398 - System call is made to add /128 IP address issued by DHCPv6 server and fails because the address has not expired yet. At least if I understand correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559741 Title: wide-dhcpv6 client apparently sets incorrect PD specfic vltime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wide-dhcpv6/+bug/1559741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559741] Re: wide-dhcpv6 client apparently sets incorrect PD specfic vltime
I noticed going through the avahi docs that this is used by Apple apparently. Also Cox says there is a compatibility issue with the Apple Airport Extreme and IPv6 failing after a day with the resolution being restart the device. My issue is the IPv6 update for the subnet fails after 24 hours or so, so sounds to be about the same symptoms. Can these two be related? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559741 Title: wide-dhcpv6 client apparently sets incorrect PD specfic vltime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wide-dhcpv6/+bug/1559741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559741] Re: wide-dhcpv6 client apparently sets incorrect PD specfic vltime
Got distracted for a bit, but finally got some testing done. It looks like I was only partially right in that the display formatter was wrong, so now I am seeing the correct time displayed. There is still something going wrong with the dhcpv6 subnet update. Will have to spend more time to properly understand this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559741 Title: wide-dhcpv6 client apparently sets incorrect PD specfic vltime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wide-dhcpv6/+bug/1559741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559741] Re: wide-dhcpv6 client apparently sets incorrect PD specfic vltime
I have found evidence that the wide-dhcpv6 version in Ubuntu 14.04 at least was written on a 32-bit architecture and never properly redesigned for a 64-bit compilation. The evidence for this found in the source code goes as follows: 1. Consistent use of the printf formatter %ul for 32-bit int fields. On a 32-bit architecture this is fine, but on a 64-bit compile with gcc unsigned long (ul) is 64-bits. This explains why the debug print statement grabs extra bytes. It also hints at another problem in that while the printf code is consistently wrong for a 64-bit compile, only the PD specific vltime picks up extra non-zero bytes beyond the 32-bit boundary. As best as I can tell this is due to compiler specific circumstance. 2. As above is a display issue with debugging messages, if you consider there are problems consistent with 32-bit only testing, it seems logical to assume somewhere those extra bytes beyond the 32-bit vltime gets assigned to the timer in an unsafe manner. I think I may have found this in that in prefixconf.c there is an assignment of vltime to tv_sec, which on a 64-bit compile would be assigning a 32-bit unsigned int to a 64-bit integer without a cast. As I normally due a cast for such conversions, I am suspecting without a cast the random bytes beyond the 32-bit boundary are getting sucked in on this particular assignment. For the NA specific vltime value the bytes just happen to be all zero, so no noticed issue, but as the incorrectly implemented printf statement shows, the bytes beyond the 32-bit boundary for the PD specific vltime are not zero and so a tv_sec value for the refresh timer gets set to something ridiculously high. The logs show that the NA specific address gets refreshed at the prescribed time while the PD specific address range does not, so everything matches up for this hypothesis. Now I just need to make some changes and test it all out... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559741 Title: wide-dhcpv6 client apparently sets incorrect PD specfic vltime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wide-dhcpv6/+bug/1559741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559741] Re: wide-dhcpv6 client apparently sets incorrect PD specfic vltime
If it helps, I have been documenting my setup in a templated format here: http://ubuntuforums.org/showthread.php?t=2279612 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559741 Title: wide-dhcpv6 client apparently sets incorrect PD specfic vltime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wide-dhcpv6/+bug/1559741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559741] Re: wide-dhcpv6 client apparently sets incorrect PD specfic vltime
No. As I am understanding the linked documentation, if you are setting up a wide-dhcpv6 server, this can be specified. However seeing I am not an ISP, but instead a customer, I am relegated to being a client and specifying these parameters do not seem to be an option for the client. Especially with IPv6 my understanding is you need the ISP to assign you Internet valid subnets (and parameters of operation) to use for your internal network in order for things to work, so there is two layers to client: one kind of serverish as it delegates subnets to your subnets, but is a client to the ISP IPv6 DHCP server. The second is a pure client for internal nodes to configure themselves. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559741 Title: wide-dhcpv6 client apparently sets incorrect PD specfic vltime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wide-dhcpv6/+bug/1559741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559741] [NEW] wide-dhcpv6 client apparently sets incorrect PD specfic vltime
Public bug reported: This is on Ubuntu 14.04 LTS 64-bit with the last update done on 03/09/2016. I setup wide-dhcpv6 client on my home network to grab IPv6 addresses from my ISP. The /128 address for my firewall is fine and after 24 hours I see in the logs the address just for this external interface being renewed, but the /60 based address block I request for a few internal subnets for my home network do not renew and after 24 hours the ISP stops routing to them. I did a Wireshark capture and all looked well, in particular the IA_PD vltime value looks correct, specifically 0x00015180. However when I run the wide-dhcpv6 client with the -D debug option, I see an incorrect value, specifically 0x7FFF00015180, which is 48-bits long while the hex dumped field in Wireshark is only 32-bits long. These extra bytes don't belong and are not part of the reply from my ISP's server. Ergo, this must be a fault on the wide-dhcpv6 client side. ** Affects: wide-dhcpv6 (Ubuntu) Importance: Undecided Status: New ** Tags: 14.04lts ipv6 renew wide-dhcpv6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559741 Title: wide-dhcpv6 client apparently sets incorrect PD specfic vltime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wide-dhcpv6/+bug/1559741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354620] Re: Recording from microphone stutters when pulseaudio is running
I need to multiplex on a USB sound device and this doesn't seem to work with the ALSA / OSS tangle, plus it really helps to control the volume levels of each application. However with Pulsaudio having broken mic support across the board (tried three different devices and even more are listed on this thread) I am seem to be SOL. This used to work when I was on 8.10. Now I think I am going to have to go back to Windows because I can't get basic audio stuff to work under Linux anymore (and it used to work with some finagling). -- Recording from microphone stutters when pulseaudio is running https://bugs.launchpad.net/bugs/354620 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 117314] Re: latest kernel(2.6.20-16.28) update gives boot problems
I recently ran the update from 6.10 to 7.04 and on first boot I had options between kernel 2.6.20-16-generic and 2.6.20-15-386. Kernel 2.6.20-15-386 works fine. Kernel 2.6.20-16-generic does not boot at all. By default on the splash screen I get a thin sliver on the progress bar and after leaving the system alone for several minutes no progress is made. Disabling the splash screen all I get is a PCI error allocating a memory resource (which I also get in the working -15 kernel on the first line at boot) and a message saying Loading, please wait... and nothing more. -- latest kernel(2.6.20-16.28) update gives boot problems https://bugs.launchpad.net/bugs/117314 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 117314] Re: latest kernel(2.6.20-16.28) update gives boot problems
I figured out a way to get things working. I completely de-installed the -16 kernel and modules and such and re-installed from the command prompt `apt-get install kernel-generic` -- latest kernel(2.6.20-16.28) update gives boot problems https://bugs.launchpad.net/bugs/117314 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
