-19-generic 3.8.0-19.30
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: phill 2043 F pulseaudio
/dev/snd
Package: linux-image-3.8.0-19-generic 3.8.0-19.30
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: phill 2043 F
-image-3.8.0-19-generic 3.8.0-19.30
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: phill 2043 F pulseaudio
Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: phill 2457 F pulseaudio
/dev/snd/controlC1: phill 2457 F pulseaudio
CRDA: Error: command ['iw
-image-3.13.0-30-generic 3.13.0-30.55
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: phill 2460 F pulseaudio
/dev
COMMAND
/dev/snd/controlC1: phill 2043 F pulseaudio
/dev/snd/controlC0: phill 2043 F pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Fri May 17 10:50:59 2013
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: phill 2043 F pulseaudio
/dev/snd/controlC0: phill 2043 F pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Fri May 17 10:50:59 2013
EcryptfsInUse: Yes
14.04
Package: linux-image-3.13.0-32-generic 3.13.0-32.57
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: phill
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: phill 2043 F pulseaudio
/dev/snd/controlC0: phill 2043 F
: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: phill 2470 F pulseaudio
/dev/snd/controlC0: phill 2470 F pulseaudio
CurrentDesktop: Unity
Date: Fri Oct 3 13:16:10 2014
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=7438ed9e-5099-4d5f-a0c4
-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: phill 2043 F pulseaudio
/dev/snd/controlC0: phill 2043 F pulseaudio
CRDA: Error: command ['iw
Public bug reported:
Running 14.04 LTS Server in a virtual machine on a 14.04 LTS Desktop
host.
When the guest suspends for a long period of time the guest server
becomes unresponsive in both Virtual Machine Viewer and over SSH, with
100% of one CPU core utilised.
A hard reset of the guest is
Public bug reported:
If you run, for example, `cp file1 file1-copy` with several GB of data,
give it a minute, then the user interface stops responding and the mouse
stops moving. There are occasional glimmers of response but it's like
watching a video one frame at a time. I would expect the user
/dev/snd/pcmC0D0p: phill 2715 F...m pulseaudio
/dev/snd/controlC0: phill 2715 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=fab564c9-5c8a-439f-8b9d-a10c8a4b75ad
InstallationDate: Installed on 2015-07-13 (165 days ago)
Install
radeStatus: No upgrade log present (probably fresh install)
+ ---
+ ApportVersion: 2.14.1-0ubuntu3.19
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/pcmC0D0p: phill 2715 F...m pulseaudio
+ /dev/snd/controlC0: phill 2715 F pulseaudio
+ Curr
e amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: phill 2715 F...m pulseaudio
/dev/s
e amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: phill 2715 F...m pulseaudio
e amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: phill 2715 F...m pulseaudio
e amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: phill 2715 F...m pulseaudio
e amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: phill 2715 F...m pulseaudio
uot; - Release amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: phill 2715 F...m pulseaudio
e amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: phill 2715 F...m pulseaudio
uot; - Release amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: phill 2715 F...m pu
e amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: phill 2715 F...m pulseaudio
/dev/s
e amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: phill 2715 F...m pulseaudio
e amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: phill 2715 F...m pulseaudio
/dev/s
e amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: phill 2715 F...m pulseaudio
/dev/s
e amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: phill 2715 F...m pulseaudio
/dev/s
e amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: phill 2715 F...m pulseaudio
/dev/s
No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: phill 2715 F...m pulseaudio
/dev/snd/controlC0: phill 2715 F pulseaudio
CurrentDesk
: linux-image-4.4.0-22-generic 4.4.0-22.40
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: phill 2671 F
Updated the BIOS, no change, kernel log reports the same error.
```
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for phill:
C0CN31WW
07/30/2015
```
That was an endeavour! I should have done it before installing Ubuntu. The
machine has only 32GB
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: phill 2671 F pulseaudio
CurrentDesktop: Unity
Date: Wed Jun 1 19:51:44 2016
HibernationDevice: RESUME=UUID=77cb8394-f284-41ec-969a-74ff33be71d5
InstallationDate: Installed on 2016-05-30 (1 days ago)
InstallationMedia
Kernel 4.4.0 is unusable, screen immediately enters power-save and stays
that way.
After GRUB (or if GRUB is not interrupted) the screen goes into power-
save mode and stays that way. I can type my full-disk decryption
password in and after a some disc activity I hear the "login sound", but
the
Tested the daily ISO:
xenial-desktop-amd64.iso
Mon, 25 Jan 2016 07:58:31 GMT
SHA256SUM: c6dcbd93724704d217e08a75167f0c2188e2847507b782e9127adba017b3fca2
This booted from the DVD but there was widespread video corruption. The shadows
on windows had a scan-line effect, although it was more than one
Cheers. Will do.
It might take a while. I'm still testing 3.16.0-59 for another day or
two just to be sure.
Do you have any suggestions for forcing this sort of bug to surface on-
demand? It would really help speed things up as I'm having to run the
machine for a couple of days to be sure at the
To see if what's resolved? The boot failure or this freeze issue?
FYI - 3.17 has display corruption (large parts of the screen don't get
painted), and my test method wasn't reliable, it's going to take ages
trying to bisect the version to find a potentially fixed one as it looks
like I need the
Quick update: It's taking a couple of days or more to test properly, so
testing the live CD for this issue wont be practical, however, it looks
like it isn't necessary. 3.18.0-031800-generic (from v3.18-vivid)
appears not to have the problem...
v3.16.0-57 INTERMITTENT VIDEO FREEZE ON RESUME
Okay, v4.3-wily boots and does not exhibit the original bug. Same for
v4.1-wily.
Looks like there's another bug here with v4.4-wily as I mentioned, not
sure if another bug should be raised for that?
I also think I have a test that I can perform to reproduce the fault on-
demand - just keep
Public bug reported:
Specifics of the conditions, although these may not be relevant as this
configuration has been working and still works intermittently:
USB Cable is already connected to the computer via extension ports.
Phone is switched on and screen unlocked.
Cable is then inserted into
Still a problem on latest 20.04 kernel (5.11.0-27-generic).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1939628
Title:
Fan goes full speed on resume from suspend
Public bug reported:
On resume from suspend the fan goes full speed.
Regression - this only happens intermittently on kernel 5.8.0-63, but
happens every time on kernel 5.11.0-25.
Running `sensors` after resume shows:
```
$ sensors
thinkpad-isa-
Adapter: ISA adapter
fan1:4776 RPM
Still a problem on latest 20.04 kernel, 5.11.0-38-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1939628
Title:
Fan goes full speed on resume from suspend
Still a problem on latest 20.04 kernel, 5.11.0-36-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1939628
Title:
Fan goes full speed on resume from suspend
I can confirm that the BIOS update makes no difference with kernel
5.13.0-41-generic after a reboot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1939628
Title:
Fan
:
phillw@piglet:~$ uname -a
Linux piglet 3.11.0-3-generic #8-Ubuntu SMP Fri Aug 23 16:49:15 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
As the 1st Beta is creeping up fast, do you need this raising as a new
bug?
Regards,
Phill.
The reply is:
As far as I can tell, the KAVERI firmware (and hardware
** Changed in: linux (Ubuntu Saucy)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1066435
Title:
powerpc: Fixing recursive fault but reboot is
Public bug reported:
When using desktop-installer with lubuntu there is a freeze at the very
end (bug 1225429) which also affects desktop-i386 and desktop-amd64.
There are also unexplained freezes on the system when using it. Further
tracking down has found
The kernel boots and system does not crash when asked to use swap. An
ISO needs to be generated to check that this does fix the issue with the
installer system. (This is just an update from email and IRC
conversations for people following the bug).
--
You received this bug notification because
I'm beginning the thought that
http://ubuntuforums.org/showthread.php?t=2162655p=12735571#post12735571
actually holds the key to this issue. They may well be 2 separate bugs,
but they both head towards zram. It seems very broken.
--
You received this bug notification because you are a member of
hi Joe,
I downloaded http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.12-rc1-saucy/linux-
headers-3.12.0-031200rc1-generic_3.12.0-031200rc1.201309161735_amd64.deb
and then did
sudo dpkg -i linux-
image-3.12.0-031200rc1-generic_3.12.0-031200rc1.201309161735_amd64.deb
Here goes a reboot
Joe,
the new kernel does not have the error as reported on
http://ubuntuforums.org/showthread.php?t=2162655p=12735571#post12735571
I think, there for that the zram team have been true to their word of
having it fixed. This close to kernel freeze, apart from zero, what are
the chances of bumping
Joe,
there is also http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.12-rc2-saucy/
I've not pulled that one in, as you requested rc1. I'm happy to pull
that one in if requested.
Phill.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
at a time. If this fixes the
installer issue, the testers can then run with the kernel and see if
they get random freezes after install.
Thanks for your continued work on this issue,
Phill.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Nio,
I've just pulled it into my dedi-server...
Length: 1049980928 (1001M) [application/x-iso9660-image]
appears to match your file length and md5sum gives
e939fec65cd6d9a01689b22468f2300a ubuntu-13.10-desktop-amd64-lp1227202.iso
That's as close as I can get to confirm things.
Regards,
Phill
which is a lot easier for me to work with. Using GUI across my
slow speed link is painful. I'll have a result in ~ 2.5 hours.
Phill.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1227202
Ubuntu ISO is 1GB+ in size (hence it taking so long for me to download
it). Lubuntu ISO's are CD sized at ~700MB :) Beggars can't be choosers!
512MB is the absolute minimum for Ubuntu (from in 13.04 release), I've
not tried a Ubuntu 13.10 ISO this testing cycle so far.
Phill.
--
You received
Hi Nio,
with the new kernel, zram is turned off. It not only causes the fail
after install, is suspected of random freezes that we've seen but also
http://ubuntuforums.org/showthread.php?t=2162655page=3 It's a shame
they didn't file a bug back then as we'd have had much more time to
investigate
i *think* lubuntu uses a slightly different setting for configuring up
zram in our desktop images. This was turned on only for lubuntu-desktop
as far as I'm aware (e.g. does not apply to alternate).
--
You received this bug notification because you are a member of Kernel
Packages, which is
Joe, it may be worth looking at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215379 to see if
we would be going that route (all far too technical for me !).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Joe,
IMHO this can be marked as invalid. It was just a FUD created when
hunting down the actual issue (which has been wonderfully solved thanks
to your patience).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Nio,
I just popped desktop amd64 onto my VM, no hang and..
swapon -s reports zram as being in use.
Happy days!
Phill.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1227202
Title
Public bug reported:
In the current kernel issuing such a command results in the following
output:
Error: /dev/zram0: unrecognised disk label
Error: /dev/zram1: unrecognised disk label
This bug will be tied to the raring kernel which also sees it.
The 3.12rc1 and 3.12rc2 kernel does not show
As requested, the other issue has been reported at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235525 this is for
saucy. For reporting in raring, please raise a new bug report and
mention the 1235525 bug so the kernel team can look into what the issue
is.
--
You received this bug
ignore the ps -ef, it is a red herring!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1235525
Title:
error on sudo parted -l
Status in “linux” package in Ubuntu:
Confirmed
Status in
zram is called by an upstart job in lubuntu. I'll re-check to see if
zram swap is enabled with the 3.12 kernel, but it will be tomorrow.
Regards,
Phill.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
It seems I made a mess of installing the 3.11.4 kernel... It now seems
to support zram.. I also re-installed the 3.12.rc1 kernel. both show the
parted -l error. Details below:
phillw@piglet:~$ uname -a
Linux piglet 3.11.4-031104-generic #201310051136 SMP Sat Oct 5 15:38:11 UTC
2013 x86_64 x86_64
Joe, I've just had a thought as zram is actually a compressed area
of RAM and not a physical device, why would we expect parted to
recognise what is going on? As far as I can read, it is actually
reporting things entirely correctly.
parted is a disk partitioning and partition resizing
Hi, could you have a read through
https://wiki.ubuntu.com/DebuggingUbiquity and see if you make the bug
reproducable.
Regards,
Phill.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs
@ Erick, please do so using the instructions from #24. The
'conversation' between a bug being reported by lots of people and the
questions so far asked are lamentable. There is a bug, the devs need
more information. Our head of QA suggested the link in #24; which from I
can read should have been
(or what ever it is) and then click on start installation (top left)
Regards,
Phill.
On 22 April 2014 07:25, hamish 1080...@bugs.launchpad.net wrote:
For an xubuntu 14.04 VM, '-vga vmware' and '-vga qxl' work (yay), but
'-vga std' and '-vga cirrus' are still corrupted.
(host qemu-kvm is running
Go drum up some support and nag https://launchpad.net/~mlankhorst to
actually fix it. He knows the fix, just will not commit time to it.
Get it passed around the heat built up (that is get people to mark it
as 'affects me')
Regards,
Phill.
On 23 May 2014 20:27, Kevin Masaryk 1080
Brightening and darkening is working fine with lubuntu 14.04 My hardware
is http://phillw.net/hardware/aDU4RVzY If you want to let the devs know
more of your system please do have a read of
https://wiki.ubuntu.com/QATeam/Hardware This actually makes the tasks of
the devs a little easier as they
https://launchpad.net/~f-jack My dear friend... My reply to the bug was such
that I know it is a bug (and I have asked others to verify). Using #15 does
make things easier as the devs can see who has what and ask if they can check
out things :) Go rally some troups for the bug, go see if you
it may be worth asking the x-server team if they have received the
proposed fix and what their attitude of implementing it is so that it
lands with the kernel team. I've never had communication with the
x-server team, but have found the kernel team to be absolute stars of
the first magnitude in
75 matches
Mail list logo
