** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1831276
Title:
Gnome wayland hangs
Apologies if I missed this, but did anyone report this to Nvidia?
Either via https://nvidia.custhelp.com/app/answers/detail/a_id/44
/~/where-can-i-get-support-for-linux-drivers%3F or their forum here:
https://forums.developer.nvidia.com/c/gpu-unix-graphics/linux/148
Likely more helpful to use
Closing this per above comment. Thanks. It still seems eventually that
MTRR might be drop-able, but won't just leave this open waiting for
future.
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
I can get sound to work with a 5.4 kernel - but it's still not great...
I haven't found a UCM file that let's it just work yet. What does work
is using the alsactl -f downloaded/asound.state.txt bit and then VLC is
able to play sound with Audio device set to chtmax98090, Direct hardware
device
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is
Trusty release has gone end of support for this package, so marking this
as such.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is
Newer releases should have this fix.
** Tags removed: raring verification-needed verification-needed-trusty
** Tags added: verification-failed-trusty
** Tags removed: verification-failed-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Tags added: sts
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1850185
Title:
[linux-azure] 19.04 regression of KDUMP
Status in linux-azure package in Ubuntu:
New
Bug
This was fixed in the latest 4.15 kernels (linux-hwe 4.15.0-60.67)
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Released
** Changed in: linux-hwe (Ubuntu)
Status: New => Fix Released
** Changed in: linux-hwe (Ubuntu Bionic)
Status: New => Invalid
**
My reproducer for Disco+ is a different bug. I get input/output errors
very quickly once specifying nfs vers=4.0. If you don't specify it, it
works fine.
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix
Thanks for reporting this bug and helping to make Ubuntu better.
Was an upstream bug ever filed? Was a clear reproducer ever identified?
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
** Changed in: linux (Ubuntu Zesty)
Status: Triaged => Confirmed
** Changed in:
** Also affects: linux-hwe (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe (Ubuntu Cosmic)
Status: New => Won't Fix
** Changed in: linux-hwe (Ubuntu Disco)
Status: New => Won't Fix
--
You received this bug notification because you are a member of
I was also able to reproduce this on Eoan by specifying vers=4.0 - where
I thought it should be fixed.
I was able to confirm that the -proposed 4.15 kernel (I tested xenial
HWE version) does have the fix and it
works:https://lists.ubuntu.com/archives/xenial-
changes/2019-August/025318.html
--
I was able to reproduce this. Minor note, that you need to specify
vers=4.0 in the mount options, nfs 4.1+ appears to not be affected by
this.
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Public bug reported:
This is on nvidia 430, which is only packages in PPAs so far.
I've reproduced this by just playing a Youtube video (Not using wayland
enabled Firefox, but Beta snappy version) or by switching tabs while on
a google hangout meet.
The video or hangout continues but the screen
Couldn't find a bug, but it's described as a known issue here:
https://blogs.gnome.org/uraeus/2019/04/03/preparing-for-fedora-
workstation-30/
Given the description above it seems to be waiting on a new nvidia
driver - still an issue on 430.14.
--
You received this bug notification because you
Was the kernel updated? Trying running an older kernel and see if it
might just be a regression in our kernel..
--
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/1791427
Title:
Touchpad
Looks like there was a BIOS (1.34) release on the 23rd - has anyone
tried that yet? https://pcsupport.lenovo.com/us/en/products/LAPTOPS-
AND-NETBOOKS/THINKPAD-X-SERIES-LAPTOPS/THINKPAD-X1-CARBON-6TH-GEN-TYPE-
20KH-20KG/downloads/DS502282
--
You received this bug notification because you are a
Try this:
1. Edit /etc/gdm3/custom.conf as root/with sudo
2. Uncomment the line WaylandEnable=false so it looks like below:
[daemon]
# Uncoment the line below to force the login screen to use Xorg
WaylandEnable=false
3. Reboot and see if the issue still occurs.
--
You received this bug
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
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/1747507
Title:
starting VMs causing retpoline4 to reboot
Status
@Andy Whitcroft (apw), just want to confirm that this doesn't need to be
tracked further. Everything seems to work fine in Bionic. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This is fixed with Linux desktop 4.13.0-35-generic #39-Ubuntu SMP Mon
Feb 12 11:06:39 UTC 2018
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This bug appears fixed with that kernel, thanks!
--
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/1747507
Title:
starting VMs causing retpoline4 to reboot
Status in linux package in
Tried disabling some BIOS settings including trusted computing and
hyperthreading which didn't have any effect.
Tried getting more info with linux-crashdump but it doesn't seem to work.
I am currently running with no kvm issues with mainline v4.15.1 and Full AMD
retpoline.
--
You received this
Might be related, might not. This is displayed before the reboot.
host doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
I did downgrade from the testing qemu packages, maybe that changed my
VMs, but that still shouldn't cause a host reboot (or kvm with no
options).
** Attachment
** Description changed:
Using 4.13.0-33.36~retpoline4 kernel test kernel from ppa
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/spectre/.
CPU: AMD Ryzen 7 1700 Eight-Core Processor
Ubuntu: 17.10.
Steps to reproduce (has occurred both times I tried it):
- 1. Run
Public bug reported:
Using 4.13.0-33.36~retpoline4 kernel test kernel from ppa
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/spectre/.
CPU: AMD Ryzen 7 1700 Eight-Core Processor
Ubuntu: 17.10.
Steps to reproduce (has occurred both times I tried it):
1. Run virsh start (or start
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1732013
Title:
Drop Floppy Drive Support from kernel?
Status in
Public bug reported:
1) Proposed for 18.04
2) Whichever kernel 4.14 or 4.15
Can we drop Floppy support from the kernel for Bionic?
I see very small activity about Floppy drives in the 2012 timeframe (LP
and AskUbuntu), but I can't see much of a use for floppy drives in 2018.
Advantages to
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1718688
Title:
Can't
Thanks for trying, not so easy to debug on a live session. Lets see if
we can reproduce it locally.
I'm hoping you are running Ubuntu locally (which version?), if so could you try
to see if you can reproduce the problem using a mainline kernel build of 4.13 -
I'm curious if it works if you just remove the splash line from the
command line (press F6 when booting).
--
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/1718936
Title:
Can't boot Artful
Good to know. If tail works around this by default is there any other
reason to keep the coreutils task open?
--
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/882147
Title:
overlayfs does
tail -f /var/log/syslog worked for me with 17.10 dev | kernel 4.12.
(Tested by turning network on and off).
--
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/882147
Title:
overlayfs does
** Changed in: unity-2d
Status: Confirmed => Invalid
--
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/957426
Title:
[spread] no support for slideshow wallpapers
Status in
I thought it was related to my system being a brand new Ryzen with ZRam
and 32GB of memory (no real swap) but apparently not.
A BIOS update bricked that motherboard so I'm back on my older
Phenom(tm) II X4 945 with 12 GB of RAM (now no ZRAM). Just got the issue
again. Now, I have *no* swap
>From my latest testing, we do currently support machines that don't have
PAT support (really old 32 bit x86). So this can be revisited at some
future point when we go 64 bit only for x86.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
@David, yes with few exceptions the kernel gets backported to Trusty HWE
after it's released for Xenial. As an example, the 4.4.0-34 kernel was
just released for Xenial and is also in Trusty as HWE already.
--
You received this bug notification because you are a member of Kernel
Packages, which
The fixes mentioned are also part of the 4.4.16 stable series, which will land
in the next kernel cycle (August 29th ish). That should be 4.4.0-35 (or higher)
in Ubuntu kernel versions.
See- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607404
--
You received this bug notification
Verified working with both -33 and -34 kernels
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1603719
Thanks Seth. That kernel fixes it for me.
--
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/1603719
Title:
[regression] NFS client: access problems after updating to kernel
I also tried Upstream v4.4.15 (35467dc7630af60abacc330f64029d081f160530)
which does not have the issue. Going to bisect shortly.
** Summary changed:
- NFS client: access problems after updating to kernel 4.4.0-31-generic
+ [regression] NFS client: access problems after updating to kernel
This was fixed at least in 16.10 (and likely in 16.04 as well).
(kexec-tools no longer makes the change by default).
** Changed in: kexec-tools (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Does anyone still have this issue or should I close this?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
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/1401741
@mkostrikin
That provides another confirmation like from comment #17 about the 4.2.0
kernel/wily.
We could still use testing for:
3.13.0-78 (on trusty - Non-HWE)
3.16.0-61 (on trusty - utopic-HWE - linux-image-generic-lts-utopic)
3.19.0-50 (on trusty - vivid-HWE - linux-image-generic-lts-vivid)
My testing could not find any difference in boot time using systemd's
tools.
--
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/1163587
Title:
mtrr_cleanup: can not find optimal value,
This bug was marked Incomplete some time ago and was supposed to
autoclose after 90 days. I'm going to close it manually due to no
activity (and likely the issue has gone away/been fixed).
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug
Oops.. .Nvm I forgot that this won't be an issue until after commit
34b48db, regardless of the same code being in the kernel.
--
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/1475166
Title:
@kashyap-desai
I was just looking at cherrypicking this fix to 15.10, but then realized I
don't see why this wouldn't affect 12.04 or 14.04 as well. Does this affect
all supported Ubuntu releases?
--
You received this bug notification because you are a member of Kernel
Packages, which is
It seems MTRR support is being deprecated now -
http://lkml.iu.edu/hypermail/linux/kernel/1508.3/04830.html, commit
2baa891e42d84159b693eadd44f6fe1486285bdc.
Perhaps disabling MTRR (as opposed to just mtrr_cleanup) might be
considered for xenial? I believe it may affect boot time when the
Got another confirmation that the patch (first one) fixes the issue.
--
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/1508706
Title:
Networking hangs on azure using hv_netvsc; bisected
It's landed in linus' tree as commit
357ae967ad66e357f78b5cfb5ab6ca07fb4a7758.
--
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/1475166
Title:
Ubuntu 15.04 Install Error with Avago
Hi Adi,
I see the patch got posted here - https://www.spinics.net/lists/linux-
scsi/msg89336.html and it has been reviewed.
I'm guessing it will be part of a scsi pull request in the recently
opened 4.4 merge window. That looks imminent. Depending on when it
lands, the Ubuntu kernel update
One time event and no evidence of it happening again on 4.2 kernel.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@kashyap
>Current Driver count max_sectors based on PAGE_SIZE. This is wrong. We will
>fix and send patch to upstream.
Thanks for the analysis and working upstream. Post here when it lands and I
can see about getting it back to 15.04/15.10.
Just for clarify workaround of anyone reading:
@kashyap-desai thanks for that, it could be a simple firmware reporting issue
or the kernel code needs to be updated to handle a new case.
megaraid_sas_base.c [1] mentions that it generates the max_sectors limits from
data provided from the firmware.
4096 is defined in a few other places within
@kashyap-desai thanks for checking. AFAICT it's been at 1024 for at
least the 14.04 release as well.
Thanks for noting what FW status 0x3 means, that will help any future
tests we do.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
So assuming the the value max_sectors_kb is changed to 1024 (with the
2048 kernel command line) that means we need to figure out what the
correct value is for the Avago controller. Currently it's set as 4096
in the kernel according to C#28. It appears 1024 works, but if we get
the actual value
Yes it would only be for one boot, to use that as a workaround you want
to add it permanently to GRUB_CMDLINE_LINUX_DEFAULT in
/etc/default/grub. Then run sudo update-grub.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Adi,
Just to confirm my understanding of this bug, did doing so change the
value of max_sectors_kb / max_hw_sectors_kb? I don't believe it would
have survived the reboot after the install, but you could try adding it
to the kernel command line of the installed system and see.
Bryan
--
You
Thanks for the bisect results! We can confirm that this fixes the issue by
manually specifying the max_sectors_kb and seeing if that fixes the issue.
1. Boot the server installation and stop at the partitioning screen (this way
we make sure it has detected everything)
2. Switch to another VT
All that patch appears to do is to remove an artificial limit for all
devices to 1024. I haven't been able to reproduce the option reset on
my systems, so here is what I would try:
Try setting the controller option and see if that sticks [1]:
rmmod megaraid_sas
modprobe megaraid_sas
** Changed in: linux (Ubuntu)
Assignee: Chris J Arges (arges) = Bryan Quigley (bryanquigley)
--
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/1475166
Title:
Ubuntu 15.04 Install
Sorry, I forgot that was also in C#17. I just wanted to minimize the
chance the kernel build/git operations would be affected by the IO
issues. Sticking with 14.10 for the bisection is perfect.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Sorry I misunderstood, I'm guessing if you go back to v3.16 it would be
fine? Perhaps something about the build is wrong at the checkout
preventing that.
There are two ways to try proceeding:
git bisect skip (trys to pick another commit) and see if it builds PPC64LE
checkout v3.18 or 3.17 and
1) I would definitely recommend booting up/checking the logs multiple times on
every leg of the test to ensure that it gets a consistent result.
2) I don't understand how this would have happened. It does occur to me that
if we're dealing with possible IO corruption there could be other
1) I would at least try booting multiple times.
If possible I would try partitioning so you have extra space and can set up a
new ext4 partition on the Controller for every test. Then deleting before
running the next one.
In fact, I'd recommend for the next test to install 15.04 on a SATA
It would be worth trying 4.1 as well built from source as that should
match the other kernel test above. Small fixes do make it after the
release and that should rule that out.
The most likely possibility that I see is that it is an Ubuntu specific kernel
config change.
It could also be
You can also try building 3.19 with the config from Ubuntu - see the
bottom of GitKernelBuild for more. Alternatively you could grab the
config from a 15.04 using step 4 in GitKernelBuild.
[1] http://kernel.ubuntu.com/git/ubuntu/ubuntu-
vivid.git/tree/debian.master/config
--
You received this
Hi Adi,
I would go ahead and proceed with a bisect. The first step would be to
test if you can build[1] the 14.10 (git checkout v3.16) kernel and it
boots fine.
Then confirm the failure of 3.19 before proceeding to a normal bisect
[1].
Which if everything above is expected, would be git bisect
The machine has been running on an external wifi card for a while, and
it's working fine. I've swapped out the RTL8188ee card for an Atheros
(mini pci) and this should let us see if it's really RTL8188ee to blame
or not (or a antenna, location issue).
I did complete a series of wireshark tests
My next plan is to setup a packet dump on both a router (or laptop) and
the laptop with the issue (RTL8188ee) and see if the packets are being
dropped more on the send or receive side. It might be a while, so if
anyone wants to get to it first :).
EMail to list:
Still true in 15.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1311834
Title:
adds crashkernel line during install, but doesn't remove it when it's
purged
Status in
apport information
** Tags added: apport-collected vivid
** Description changed:
Ubuntu 15.04 with 3.19.0-15-generic.
Current status:
System fails to finish booting with Scanning for btrfs. If you wait long
enough you see:
INFO: task exe:208 blocked for more than 120 seconds
** Attachment added: Call trace
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446464/+attachment/4380312/+files/2015-04-21_01-00-19_587.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: JournalErrors.txt
https://bugs.launchpad.net/bugs/1446464/+attachment/4380318/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1446464/+attachment/4380327/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1446464/+attachment/4380315/+files/CRDA.txt
--
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/1446464
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1446464/+attachment/4380323/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1446464/+attachment/4380326/+files/UdevDb.txt
--
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/1446464
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1446464/+attachment/4380320/+files/Lsusb.txt
--
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/1446464
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1446464/+attachment/4380322/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1446464/+attachment/4380321/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1446464/+attachment/4380316/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
All I had to do to recover it was to boot up with a Ubuntu 14.04.2
livecd and mount the drive (I gathered logs looking to debug further).
Upon rebooting it seems to be working again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1446464/+attachment/4380324/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1446464/+attachment/4380317/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1446464/+attachment/4380325/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1446464/+attachment/4380328/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1446464/+attachment/4380319/+files/Lspci.txt
--
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/1446464
Public bug reported:
Ubuntu 15.04 with 3.19.0-15-generic.
Current status:
System fails to finish booting with Scanning for btrfs. If you wait long
enough you see:
INFO: task exe:208 blocked for more than 120 seconds
INFO: task btrfs-transacti:230 blocked for more than 120 seconds
(message
I was doing mount-image-callback at the time to be more specific.
I have no way to reproduce it despite trying the above command a bunch.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 136 matches
Mail list logo
