[07:49] <UNIm95> apw: Hi. I have tried to update my kernel to   3.13.0-66-generic with linux-image-generic package. But i got Kernel oops.
[07:51] <UNIm95> apw: My first bug report was here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497184
[07:51] <ubot5`> Ubuntu bug 1497184 in linux (Ubuntu Vivid) "Kernel-panic with 3.13.0-64.104 generic kernel (BUG at net/core/skbuff:1290)" [High,Fix released]
[07:54] <UNIm95> After 3.13-64 kernel in 14.04 i cannot use  ubuntu at all
[07:59] <smb> UNIm95, Hm, what upload number (dpkg -l |grep linux-image) is that? Should be 108 to be safe
[08:49] <apw> UNIm95, yeah what smb says, we'd need a specific version number and an indication of whether the kernel oops is the same as that bug
[08:50] <UNIm95> smb: 3.13.0-66.107
[08:51] <smb> UNIm95, Ok, 107 unfortunately had another "issue" you should update once more to get 108
[08:51] <UNIm95> apw: smb Now i'm using web interface of freenode. I havo sound notifications.
[08:51] <UNIm95> I have no sound notifications
[08:52] <UNIm95> Ok. Im will try now.
[08:52] <UNIm95> But after *64 kernel i cannot use my computers.
[08:52] <UNIm95> When i boot i choose *-63 kernel
[08:53] <smb> UNIm95, Ok, sound issues might be part of the problems. One general thing, if you need a computer to be more stable you should disable the proposed pocket once you are good.
[08:53] <apw> you can update from any of the older kernels
[08:55] <UNIm95> smb: No! I have no sound issues. I have noticed you answer only yet.
[08:55] <smb> UNIm95, ah ok. got it
[08:56] <UNIm95> usually I'm using pidgin.
[08:56] <UNIm95> And i got another error.
[08:56] <UNIm95> while updating
[08:56] <UNIm95> E: libpam-systemd: 55.2632:package is in a very bad inconsistent state; you should  reinstall it before attempting configuration
[08:57] <apw> UNIm95, normaly apt tells you what to run to get out of the mess at the bottom
[09:02] <UNIm95> Ok. Last error with libpam-systemd was my fault. I fixed version of this lib in synaptic.
[09:05] <UNIm95> I'm going to reboot. I hope i can boot with *-66.108
[09:06] <smb> That one work for me at least
[09:09] <UNIm95> Ok. Now booted without problems.
[09:09] <UNIm95> No oops messages or errors while loading.
[09:10] <smb> Sounds good. :)
[09:12] <UNIm95> smb: Not really. With *-64.* I got random kernel panic.
[09:12] <UNIm95> smb: usaully first 30 minutes was everything ok.
[09:14] <smb> UNIm95, Well yeah, the initial one in proposed had those issues and was replaced later (again same abi number but incremented upload), then there was a -65 which you seemed to have missed (which was ok as far as I can tell). And now you somehow unfortunately went straight to the next one that caused problems.
[09:16] <smb> UNIm95, As I said before, on machines that need to be more stable, you should disable the "proposed" pocket after you are done testing (often you are asked to enable it to verify something)
[09:20] <UNIm95> smb:  But prororsed have new Firefox, Chromium and thunderbird. This apps i need for  work and life.
[09:22] <smb> UNIm95, Actually no. The proposed pocket has updates first before the go to updates (as a wider testing). If you want things as soon as possible, yes, proposed helps. But you also can get a kernel that breaks your machine (like you did). Not that we really want that to happen too often but ... things happen.
[09:29] <UNIm95> smb: Ok. Thanks for information. I thought than only proposed keeps some apps updated. 
[09:29] <apw> right, allays bear in mind that -proposed is where all the testing occurs, so things in -proposed are effectivly untested when the appear
[09:30] <apw> updates in -proposed migrate to -updates when they are deemed good enough
[09:30] <smb> Yeah that ^ :)
[09:31] <apw> in this case the .107 kernel failed that testing and was replaced without ever reaching -updates, win
[09:34] <smb> In those cases it is good to have more people with proposed enabled to catch things. But it seems there might be a slightly better explanation needed so all those understand the implications and the risk.