[1] kvm psci v0.2 patchset
http://comments.gmane.org/gmane.linux.ubuntu.devel.kernel.general/56676
** Attachment added: dmesg log after running 'reboot' 'poweroff' on current
arm64 VM with the kvm psci v0.2 patchset
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455372
Title:
Trausty arm64 VM doesn't support 'reboot' and 'powerdown'
To manage notifications about this bug
** Description changed:
+ Trusty arm64/arm kernel can't support reboot and powerdown function.
- Trusty arm64 kernel can't support reboot and powerdown function.
-
- If user runs 'reboot', then finally the VM hangs in the last step instead of
next booting, and similar problem
- exists about
Public bug reported:
Trusty arm64 kernel can't support reboot and powerdown function.
If user runs 'reboot', then finally the VM hangs in the last step instead of
next booting, and similar problem
exists about powerdown.
** Affects: linux (Ubuntu)
Importance: Undecided
Status:
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) = Ming Lei (tom-leiming)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438585
Title:
no console when starting VM from cloud image
kernel, then utopic
kernel
can choose the console automatically from the 'stdout' DT property which is
setup
from QEMU automatically.
http://kernel.ubuntu.com/git?p=ming/ubuntu-
utopic.git;a=shortlog;h=refs/heads/console-fix_stdout
Thanks,
--
You received this bug notification because you
Public bug reported:
The 'console=' parameter has been removed from grub config file inside utopic
cloud image, so no console
output any more because stdout parameter isn't parsed by utopic kernel yet.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags:
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1430184
Title:
trusty: fail to pass xfstests(generic/324)
To
BTW, the patch in #3 fixes xfstests(ext4/308) at the same time too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1430184
Title:
trusty: fail to pass xfstests(generic/324)
To manage notifications
It is fixed by upstream commit(merged to 3.14):
a9b8241 ext4: merge uninitialized extents
I have sent the patch to ubuntu kernel mail list already.
** Tags removed: needs-reverse-bisect
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug
Public bug reported:
ming@am2:~/git/xfstests$ sudo ./check generic/324
FSTYP -- ext4
PLATFORM -- Linux/aarch64 am2 3.13.0-37-generic
MKFS_OPTIONS -- /dev/loop1
MOUNT_OPTIONS -- -o acl,user_xattr /dev/loop1 /mnt/scratch
generic/324 23s ... [failed, exit status 1] - output mismatch
Fixed in 3.13.0-47-generic #78
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1418284
Title:
trusty: kernel oops during runing
** Tags removed: verification-needed-utopic
** Tags added: vverification-done-utopic
** Tags removed: vverification-done-utopic
** Tags added: verification-done-utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1417339
Title:
utopic kernel can't make ethernet workable on
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Ming Lei (tom-leiming)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1418284
Title:
trusty: kernel oops during runing xfstests(generic
The patch in the following link does fix the problem:
http://git.kernel.org/cgit/linux/kernel/git/stable/stable-
queue.git/tree/queue-3.14/ext4-prevent-bugon-on-race-between-write-
fcntl.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
xfstests generic/036 works fine with 3.18-rc6 kernel.
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1418284
Title:
trusty: kernel oops during runing
The test box is in private environment, and I can't run apport-collect to
collect log automatically.
If you need any specific log, please let me know and I can provide that.
BTW, the bug can be duplicated every time.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You
Public bug reported:
generic/036 11s ...[ 680.213164] Kernel panic - not syncing: BUG!
[ 680.217414] CPU: 4 PID: 16161 Comm: aio-dio-fcntl-r Not tainted
3.13.0-37-generic #64-Ubuntu
[ 680.225807] Call trace:
[ 680.228246] [ffc88490] dump_backtrace+0x0/0x16c
[ 680.233616]
xfstests config(local.config):
export TEST_DEV=/dev/loop0
export TEST_DIR=/mnt/test
export SCRATCH_DEV=/dev/loop1
export SCRATCH_MNT=/mnt/scratch
ming@am2:~/git/xfstests$ sudo losetup -a
/dev/loop0: [0802]:25306845 (/home/ming/git/xfstests/loop0.img)
/dev/loop1: [0802]:25306843
in stmmac
and changes the fixed link description into current standard binding:
git://kernel.ubuntu.com/ming/ubuntu-utopic.git exynos5440-net-fix
72bf502 UBUNTU: SAUCE: (no-up) net: stmmac: add fixed_phy support via
fixed-link DT binding
65a6d09 UBUNTU: SAUCE: (no-up) ARM: exynos5440-sd5v1
Public bug reported:
I found the utopic kernel can't boot on Samsung exynos5440, finally
figured out at least the following three patches are needed:
1) [PATCH] ARM: EXYNOS: do not try to map PMU for exynos5440
http://marc.info/?l=linux-arm-kernelm=141950370711871w=2
2) ARM: SAMSUNG: fix the
** Description changed:
I found the utopic kernel can't boot on Samsung exynos5440, finally
figured out at least the following three patches are needed:
- 1) [PATCH] ARM: EXYNOS: do not try to map PMU for exynos5440
- http://marc.info/?l=linux-arm-kernelm=141950370711871w=2
-
- 2) ARM:
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1400349
Title:
[SRU] new arm64 optimized copy_to_user and
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1400349
Title:
[SRU] new arm64 optimized copy_to_user and
ubuntu@ms10-42-mcdivittA3:~$ uname -a
Linux ms10-42-mcdivittA3 3.16.0-29-generic #39-Ubuntu SMP Mon Dec 15 22:31:48
UTC 2014 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@ms10-42-mcdivittA3:~$ ping kernel.ubuntu.com
PING kernel.ubuntu.com (91.189.94.216) 56(84) bytes of data.
64 bytes from
Turns out that grub isn't installed completely in the cloud image:
[ming@download]$ls -l ./tt/boot/grub/
total 2368
-rw-r--r-- 1 root root 191 Dec 12 11:37 default
-rw-r--r-- 1 root root5366 Dec 12 12:05 grub.cfg
-rw-r--r-- 1 root root4322 Dec 12 11:38 menu.lst
-rw-r--r-- 1 root root
the
backup to the
end (and removing the old backup)?
Fix/Ignore/Cancel? I
Warning: Not all of the space available to /home/ming/git/kvm/ts.img appears to
be used, you
can fix the GPT to use all of the space (an extra 1527884 blocks) or continue
the
backup to the
end (and removing the old backup)?
Fix/Ignore/Cancel? I
Warning: Not all of the space available to /home/ming/git/kvm/ts.img appears to
be used, you
can fix the GPT to use all of the space (an extra 1527884 blocks) or continue
vivid-server-cloudimg-arm64-uefi1.img has the same problem. and during VM
kernel booting,
following message can be found:
[0.823861] GPT:Primary header thinks Alt. header is not at the end of the
disk.
[0.825451] GPT:3084211 != 4612095
[0.826195] GPT:Alternate GPT header not at the
On Tue, Dec 2, 2014 at 2:49 AM, dann frazier dann.fraz...@canonical.com wrote:
On Thu, Nov 27, 2014 at 8:17 PM, Ming Lei 1386...@bugs.launchpad.net wrote:
From ARM64 maintainer's viewpoint:
http://marc.info/?l=linux-arm-kernelm=141708838404470w=2
Either way, I don't think
On Fri, Nov 28, 2014 at 11:18 PM, Chuck Short chuck.sh...@canonical.com wrote:
Which version of nova?
ubuntu@ms01a:~$ nova --version
2.17.0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
On Fri, Nov 28, 2014 at 11:18 PM, Chuck Short chuck.sh...@canonical.com wrote:
Which version of nova?
ubuntu@ms01a:~$ nova --version
2.17.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389938
I have sent out one patch to fix the problem for upstream:
http://marc.info/?t=14170671845r=1w=2
Let's see the further discussion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386490
in: linux (Ubuntu Utopic)
Assignee: (unassigned) = Ming Lei (tom-leiming)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386490
Title:
HP ProLiant m400 nic doesn't work after trusty
To manage
Public bug reported:
1, version
ubuntu@ms01a:~/ming$ uname -a
Linux ms01a 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:10:54 UTC 2014
aarch64 aarch64 aarch64 GNU/Linux
2, kvm instance can't be launched, and see below failure log in
/var/log/nova/nova-compute.log:
2014-11-05 21:58:58.480
Public bug reported:
1, version
ubuntu@ms01a:~/ming$ uname -a
Linux ms01a 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:10:54 UTC 2014
aarch64 aarch64 aarch64 GNU/Linux
2, kvm instance can't be launched, and see below failure log in
/var/log/nova/nova-compute.log:
2014-11-05 21:58:58.480
Colin,
HP has marked it as critical in the private entry, and I have verified that
netcfg_1.119 does fix the issue
on trusty, could you merge it to trusty ?
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
merged to upstream as commit:
https://github.com/torvalds/linux/commit/0738854939e6ec9b9111a8cfc0ca1dfa3cff6b2e
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1359146
Title:
Kernel crash when
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1360140
Title:
trusty still uses APM's out-of-tree xgene-enet
** Description changed:
After investigation, looks VTOP() works mistakenly in current trusty
crash on arm64.
With the commit below, crash starts to working on arm64, and it can be
applied cleanly on trusty crash, so could you guys merge it?
https://github.com/crash-
It should be a block-core problem introduced by this commit 05f1dd531521,
anyone care to test the
attached patch?
** Patch added: block: merge segment in need
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359146/+attachment/4192437/+files/blk-no-sg-merge.patch
--
You received this
Public bug reported:
Now all APM's xgene-enet patches are merged to linus tree already, so it is time
to replace these out-of-tree patches with upstreamed xgene-enet commits.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: trusty
--
You received
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354242
Title:
mellanox driver crash fix in leagcy EQ mode
To manage notifications about this bug go to:
Public bug reported:
After investigation, looks VTOP() works mistakenly in current trusty
crash on arm64.
With the commit below, crash starts to working on arm64, and it can be
applied cleanly on trusty crash, so could you guys merge it?
https://github.com/crash-
** Summary changed:
- trusty crash(7.0.3 cased) can't support arm64
+ trusty crash(7.0.3 based) can't support arm64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354349
Title:
trusty crash(7.0.3
*** This bug is a duplicate of bug 1354349 ***
https://bugs.launchpad.net/bugs/1354349
** This bug has been marked a duplicate of bug 1354349
trusty crash(7.0.3 based) can't support arm64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
1, reproduction steps:
- ethtool eth0 rx 128
- iperf -s
- in iperf client side, run below:
iperf -c IP_SRV -P128 -t 120
- then mellanox driver crash:
[ cut here ]
WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:264 dev_watchdog+0x2a8/0x2b4()
With upstream 92df54ee3dde385 ( net/mlx4_en: Don't use irq_affinity_notifier to
track changes
in IRQ affinity map), the issue is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354242
Title:
Public bug reported:
# crash
crash 7.0.3
Copyright (C) 2002-2013 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited
Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
Copyright (C)
I upgraded to the latest kernel package, and looks the problem is still
there, is it really released?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308183
Title:
make_kpkg runs postinst scripts
** Changed in: libvirt (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1266677
Title:
Doesn't parse cpu model for arm64
To manage notifications about this
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265425
Title:
Doesn't support arm64
To manage notifications about this bug
, that is the problem, and I think you are using the libvirt with my
workaround, :-)
Even '-cpu host' isn't needed for previous qemy from openvirtualsystem
git tree, but for current upstream qemu(1.7.XX), it is required for aarch64,
and the related qemu code is in hw/arm/virt.c
Thanks,
--
Ming Lei
--
You
testcase tweaking?
Sorry, I didn't understand this stuff, and I just remember without the patch,
we can't bring up a VM on arm64 with qemu...
Thanks for your comment.
Thanks
--
Ming Lei
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Serge,
I need to downgrade python-webob to 1.2.3 manually for working around
the problem.
Thanks,
** Changed in: nova (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Looks the upstreamed commit mentioned in #5 includes most of the patch we are
using, and that is great
really, :-)
But maybe below part is needed too:
diff --git a/src/qemu/qemu_domain.c b/src/qemu/qemu_domain.c
index e964c75..c947e2e 100644
--- a/src/qemu/qemu_domain.c
+++
Serge,
I need to downgrade python-webob to 1.2.3 manually for working around
the problem.
Thanks,
** Changed in: nova (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The upstream qemu[1] needs to pass '-cpu host' for aarch64, but current libvirt
doesn't
support to parse the parameter for aarch64, so we can see below failure when
running
the command:
ming@arm64:~/vm-new/virt$ virsh create host.xml
error: Failed to create domain from
Hi Andrew,
On Tue, Jan 7, 2014 at 6:33 PM, Andrew Cloke andrew.cl...@canonical.com wrote:
Does this patch need to be cherrypicked from the upstream project into
the Ubuntu archive?
Yes, I think it need absolutely.
Thanks,
--
Ming Lei
--
You received this bug notification because you
Public bug reported:
The upstream qemu[1] needs to pass '-cpu host' for aarch64, but current libvirt
doesn't
support to parse the parameter for aarch64, so we can see below failure when
running
the command:
ming@arm64:~/vm-new/virt$ virsh create host.xml
error: Failed to create domain from
Currently for enabling openstack on aarch64, I have to work around the problem
by below patch,
which is surely not good for merging.
diff --git a/src/qemu/qemu_command.c b/src/qemu/qemu_command.c
index 63e235d..ac67b14 100644
--- a/src/qemu/qemu_command.c
+++ b/src/qemu/qemu_command.c
@@
Hi Andrew,
On Tue, Jan 7, 2014 at 6:33 PM, Andrew Cloke andrew.cl...@canonical.com wrote:
Does this patch need to be cherrypicked from the upstream project into
the Ubuntu archive?
Yes, I think it need absolutely.
Thanks,
--
Ming Lei
--
You received this bug notification because you
Hi Tim,
Looks I still don't see it is common for all ARCHs, see below please:
[ubuntu@ubuntu-trusty]$git config -l
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
Public bug reported:
Without attached patch, we can't create VM on arm64 with KVM.
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: libvirt-fix-arm64.patch
Public bug reported:
The patch(lxc: Fix a bug of baselineCPU parse failure ) in the below link is
needed for starting nova-compute service successfully:
https://review.openstack.org/gitweb?p=openstack%2Fnova.git;a=commitdiff;h=3afa01611923168da349aa542a2b39301840c414
Otherwise, we may meet
Public bug reported:
debian.master/config/arm64/config.common.arm64:74:# CONFIG_VIRTIO_NET is
not set
On ubuntu-trusty, CONFIG_VIRTIO_NET isn't set, so it is not good to enable
ubuntu-trusty
kernel for arm64 VM.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
**
Public bug reported:
Without attached patch, we can't create VM on arm64 with KVM.
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: libvirt-fix-arm64.patch
Public bug reported:
The patch(lxc: Fix a bug of baselineCPU parse failure ) in the below link is
needed for starting nova-compute service successfully:
https://review.openstack.org/gitweb?p=openstack%2Fnova.git;a=commitdiff;h=3afa01611923168da349aa542a2b39301840c414
Otherwise, we may meet
Public bug reported:
1, The problem can be observed on both nova controller node and nova-
compute node
2, the bug should be introduced recently, and looks the nova-compute
package 2 weeks ago looks fine.
3, error log from nova-compute.log:
2013-12-28 11:30:01.697 1222 ERROR object
status 1
Setting up nova-compute-kvm (1:2014.1~b1-0ubuntu2) ...
Errors were encountered while processing:
nova-compute
E: Sub-process /usr/bin/dpkg returned an error code (1)
2, the system is latest trusty:
ming@arm64:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency
Public bug reported:
1, The problem can be observed on both nova controller node and nova-
compute node
2, the bug should be introduced recently, and looks the nova-compute
package 2 weeks ago looks fine.
3, error log from nova-compute.log:
2013-12-28 11:30:01.697 1222 ERROR object
status 1
Setting up nova-compute-kvm (1:2014.1~b1-0ubuntu2) ...
Errors were encountered while processing:
nova-compute
E: Sub-process /usr/bin/dpkg returned an error code (1)
2, the system is latest trusty:
ming@arm64:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency
Public bug reported:
Many filesystems support discard feature, and lots of SSD disks(even some usb
storages)
support TRIM feature, but unfortunately Ubuntu does not enable it automatically.
With trim/discard enabled, SSD's lifetime can be increased and write performance
may be improved.
For
Looks the log isn't needed, see below:
ubuntu@h4c:~$ mount | grep ext4
/dev/sda2 on / type ext4 (rw,errors=remount-ro)
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
the firmware loading bug?
http://kernel.ubuntu.com/~ming/bugs/1197616/v1/usermodehelper-
enable.patch
Thanks
--
Ming Lei
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197616
Title:
Bluetooth sometimes
On Mon, Jul 29, 2013 at 5:56 PM, chris 1159...@bugs.launchpad.net wrote:
I try my best to understand (though I don't really understand :)) the
command(s) that I should execute.
Hope following result helps (I ran it while printer unplugged) :
$ dmesg | grep usb
No, it is wrong, and the
search utility(find, grep, ls, ...) can be used to do this searching.
Thanks,
--
Ming Lei
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159358
Title:
USB Printer HDD external can't wake up after
On Tue, Jul 23, 2013 at 5:17 PM, chris 1159...@bugs.launchpad.net wrote:
Hi Ming Lei,
I'm sorry if I don't understand. Could you please explain how to do
that?
You should understand that there is one process named as 'usb' which
disconnects your printer, shouldn't you?
But I am sure how
On Thu, Jul 25, 2013 at 9:11 AM, Ming Lei ming@canonical.com wrote:
On Tue, Jul 23, 2013 at 5:17 PM, chris 1159...@bugs.launchpad.net wrote:
But I am sure how to find it in distribution, and looks no such utility in
my desktop.
Sorry, s/am/am not
Thanks,
--
Ming Lei
--
You received
Chris,
So suggest you to check if there is 'usb' utility in udev or other system
component in your system,
and definately the warning is from the user space utility.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1166745
Title:
usb modem module crash
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197616
Title:
Bluetooth sometimes does not work after resuming from suspend
To
As vorlorn mentoned, this seems to be a heat related issue. It started
when my office's air conditioning stopped working in the tropical heat.
One way I found to solve the problem is to remove the device from the
PCI bus and rescan. This seems to re-initialize it to a working state.
1) Wait for
Hi,
Please try the images on the below link:
http://kernel.ubuntu.com/~ming/bugs/1197616/v1/
Also the kernel patch can be found on the link.
Thanks,
--
Ming Lei
On Thu, Jul 4, 2013 at 11:41 AM, Launchpad Bug Tracker
1197...@bugs.launchpad.net wrote:
You have been subscribed
switched over.
Could you do the test and post the log in LP?
Thanks,
--
Ming Lei
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172908
Title:
USB 2.0 Ports Dont Work on Sony Vaio Laptop
done the tests below?
- plug one 2.0 devices to 2.0 port, then power on machine to see
if they can be found in 2.0 bus
If not, I suggest you to give it a try.
Thanks,
--
Ming Lei
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
on the bug, and reported it on linux-usb list already.
Thanks,
--
Ming Lei
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172908
Title:
USB 2.0 Ports Dont Work on Sony Vaio Laptop
To manage
'rmmod ath9k'
to see if new devices can be recognized on usb3.
Or if you can build kernel by yourself, you can enable 'CONFIG_USB_DEBUG'
'CONFIG_DEBUG_DRIVER' and post out 'dmesg' info. If you can't, I'd like to
build one kernel with these debug options for your test.
Thanks,
--
Ming Lei
; do
echo on ${LINE}; done
Thanks,
--
Ming Lei
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172908
Title:
USB 2.0 Ports Dont Work on Sony Vaio Laptop
To manage notifications about this bug go
work at all. However, they work fine under
Windows.
Sorry, it is hard to guess what is issue without any 'dmesg' log.
Thanks,
--
Ming Lei
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172908
Title
On Fri, Jun 14, 2013 at 2:49 PM, mikewhatever 852...@bugs.launchpad.net wrote:
There is a slew of the 8192cu related changes with the 3.2.0-48-generic
update for Precise, and that seems to provide a fix, and a happy end for
this bug report. I've un-blacklisted the module, rebooted, and was glad
Hi Barry and ATIpro,
Could you plug the devices into USB 2.0 port first and run below command
to see if your devices can be found in USB 2.0 bus?
find /sys/bus/usb/devices/*/port*/power/control | while read LINE; do
echo on ${LINE}; done
Thanks,
--
Ming Lei
--
You received this bug
ehci interrupts(/proc/interrupts)(see #35)
after plugging the device, I guess that there is no power from the port. And
you can connect your cell phone to the port and check if it is capable of
becoming in charging state.
Thanks,
--
Ming Lei
--
You received this bug notification because you
On Wed, Jun 5, 2013 at 8:42 AM, Barry Bulls 1172...@bugs.launchpad.net wrote:
ubuntu@ubuntu:~$ dmesg
[ 384.022264] usb 3-1: USB disconnect, device number 2
Why aren't you so generous to post more logs of 'dmesg' under USB 2.0
case?
Thanks,
--
Ming Lei
--
You received this bug notification
On Wed, Jun 5, 2013 at 1:42 AM, Jeff Marcom jeff.mar...@canonical.com wrote:
marking as invalid. I was able to get this cpu stress to pass multiple
subsequent attempts.
That is very normal since result of 'stress' depends on actual running
activity of
system very much.
Thanks,
--
Ming Lei
- if 'vm' child tasks exited abnormally or can't be exited,
the problem might
be in swap/vm/or disk performance.
Then corresponding tests can be proposed to narrow down the problem
further.
Thanks,
--
Ming Lei
--
You received this bug notification because you are a member of Ubuntu
Bugs
On Tue, Jun 4, 2013 at 12:04 PM, Ming Lei ming@canonical.com wrote:
On Tue, Jun 4, 2013 at 10:21 AM, Launchpad Bug Tracker
1187...@bugs.launchpad.net wrote:
Anthony Wong (anthonywong) has assigned this bug to you for linux-lts-raring
in Ubuntu:
[Lenovo L530]: Fails cpu stress test
Hi,
Could you provide 'dmesg' just after your plug your usb mass storage
device into the 2.0 port?
Also could you try to plug other devices(hub, uvc camera, ...) into the 2.0
port to see if it works?
From the 'lsusb' log, there are many devices found in the 2.0 bus, so it
is a bit confused that
.
Thanks,
--
Ming Lei
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1176355
Title:
Can't access USB external disk
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
201 - 300 of 1314 matches
Mail list logo
