On Mon, Jul 13, 2015 at 9:27 AM, Ming Lei <1469...@bugs.launchpad.net> wrote:
> Dann,
>
> Please follow the steps in #12, in which you should trigger the crash in
> 4 minutes.
> I've been running that in a loop and I'm currently on iteration #76
> w/o a crash :
> I prepared a wily package w/ the proposed upstream backport for testing:
> lp:~dannf/ubuntu/wily/irqbalance/lp1469214
> Unfortunately, I'm still seeing irqbalance crash even with this
backport:
I guess you still test irqbalance on c33, looks that upgrade from trusty isn't
good, and
I can see
>From upstrem kernel, v4.0 is same with wily(4.0 kernel), but there isn't the
>issue in v4.1 and v4.2 kernel.
And it can't be found by reverse 'git bisect', because some pci change can
cause no mellanox nic found
in pci bus.
--
You received this bug notification because you are a member of Ubu
** Package changed: irqbalance (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1474171
Title:
Wily boot failure on HP proliant m400 server
To manage notifications about thi
Finally, I figured out it is the following patchset which can fix the issue.
That is said
the issue disappears if these patches are applied to v4.0 kernel:
9a6d729 of: Calculate device DMA masks based on DT dma-range size
22b3c18 arm: dma-mapping: limit IOMMU mapping size
de335bb4 PCI: Update DMA
Dann,
I have figured out patches for fixing wily kernel, see following link:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1474171/comments/4
so you can reproduce the issue on a totally clean wily distribution, :-)
--
You received this bug notification because you are a member of Ubuntu
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-kernel&m=141950370711871&w=2
2) ARM: SAMSUNG: fix the C
** 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-kernel&m=141950370711871&w=2
-
- 2) ARM: S
** 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 im
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: Ne
** 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 p
** 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 go
** Attachment added: "dmesg log after running 'reboot' & 'poweroff' on current
arm64 VM"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455372/+attachment/4400723/+files/dmesg-before-applying-patches.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
[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"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455372/+attachmen
.po files have not been updated
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375598
Title:
Some options have not been translated in system setting- safety and
privacy
To manage notifications ab
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
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
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 notificat
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 a
** 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 manage
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: u
The following LP entry is the one which has removed 'console=' parameter from
grub in
the utopic cloud image.
http://bugs.launchpad.net/bugs/1419952
The direct effect is that there isn't console any more when booting utopic VM
via
grub.
The fix is to backport the 'stdout' DT patches to utopic
zh_CN trans suggested; waiting for trans team member to review it.
** Changed in: ubuntukylin
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231437
Title:
快捷关机界面汉化
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 com
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.
ht
Would you like...
有更合适的翻译没，不是说“您打算...”过于口语吗？
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231437
Title:
快捷关机界面汉化不全
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntuk
kuaipan4uk amd 64 version is on progress
** Changed in: ubuntu
Status: New => In Progress
** Changed in: ubuntu
Assignee: (unassigned) => Luo Lei (robert165)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The following should fix the issue of flash-kernel, could anyone give a test in
MAAS?
diff --git a/functions b/functions
index 97bbdd9..e753054 100644
--- a/functions
+++ b/functions
@@ -429,6 +429,10 @@ fi
kfile_suffix=$(get_kfile_suffix "$kfile")
if ! check_supported "$machine"; then
+
Public bug reported:
1, Wily kernel crashed with attached log on APM mustang(ARM64)
2, how to reproduce
2.1 start iperf first
- run 'iperf -s' on mustang board
- run 'iperf -c IP_OF_MUSTANG' on another machine, and make the client point to
mustang
2.2 run the following 'ifconfig eth0 up/down' t
Public bug reported:
[0.00] [ cut here ]
[0.00] WARNING: CPU: 0 PID: 0 at
/build/linux-vmnY7Y/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
[0.00] Modules linked in:
[0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-16-gener
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509221
Title:
wily: arm64: warning in numa_init() during booting
To manage notification
Today I have applied this patch(efinet: open Simple Network Protocol
exclusively) against grub on wily, looks it
does fix the issue on mustang/merlin.
Dann, could you build one upstrem grub and test it on thunder to see if
there is the synchronous exception issue?
--
You received this bug notif
Dann, I just run a quick test on cvm0 and looks the grub.efi built from wily
plug the patch just works fine, and
attached my build commandline.
./autogen.sh
./configure --host=x86_64-linux-gnu --target=aarch64-linux-gnu
--build=x86_64-linux-gnu --with-platform=efi
--prefix=/tmp/grub64-efi_insta
Riku,
Did you reproduce the issue with UEFI booting or U-boot booting? And it
is on Mustang?
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440536
Title:
Oops __d_lookup+0x88/0x194
To man
>From reading [1] [2] and [3], I don't believe a CVE has been assigned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492124
Title:
infinite loop in parse_encoding (t1load.c)
To manage notificatio
Thanks for pushing out the update! I verified it fixed the infinite loop
for Google Chrome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492124
Title:
infinite loop in parse_encoding (t1load.c)
T
Public bug reported:
ubuntu@ubuntu:~/stress-ng$ stress-ng --numa 1
stress-ng: info: [3191] defaulting to a 86400 second run per st[ 1722.813407]
stress-ng-numa[3192]: unhandled level 2 translation fault (11) at 0x,
esr 0x9206
ressor
stress-ng: info: [3191] dispatching hogs: 1 numa
On Tue, Sep 1, 2015 at 11:27 PM, dann frazier
wrote:
> Sorry, I missed the request for more information. I retested yesterday,
> and it is still possible to crash the system with the above stress-ng
> command 4.2.0-6.6 from ppa:canonical-kernel-team/ppa. In fact, it seems
> to be 100% reproducible
Looks there are other translation fault issue on arm64, and the following fault
is triggered when I run
a stress-ng built from your tree just before, and kernel is v4.2.
ubuntu@ubuntu:~/stress-ng$ ./stress-ng --all 8 -t 10
[90392.210285] stress-ng[2513]: unhandled level 3 translation fault (11) a
This one should be same with LP1508738, and can anyone to try to use the
customerised grub to see if it
can fix the issue?
http://kernel.ubuntu.com/~ming/bugs/1508893/bootnetaa64.efi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
On Tue, Nov 3, 2015 at 11:48 PM, Newell Jensen
wrote:
> Ming,
>
> Trying to use your bootnetaa64.efi file from
> http://kernel.ubuntu.com/~ming/bugs/1508893/bootnetaa64.efi
>
> I am not able to test this because I cannot PXE boot:
>
> TianoCore 2.0.0 UEFI 2.4.0 Sep 1 2015 12:48:07
> CPU: APM ARM
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509221
Title:
wily: arm64: warning in numa_init() during booting
To manage notifi
The issue can be fixed by disabling 'ARM64_DT_NUMA', so it is definitley caused
by the following commit:
commit ecbd5d083f9d668436cd0cc18f06094233c1c336
Author: Ganapatrao Kulkarni
Date: Fri Sep 18 15:44:40 2015 -0600
UBUNTU: SAUCE: arm64, numa, dt: adding dt based numa support using
dt n
> A build from upstream git shows this problem as well.
Looks it is thought as one AMI firmware's issue, so the patch should be merged
to grub, otherwise
grub can't run on APM's UEFI firmware.
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
On Tue, Oct 27, 2015 at 11:03 PM, Fathi Boudra wrote:
> Ming Lei,
>
> yes, on Mustang. We're using U-Boot.
OK, we found the issue is triggered during booting, and finally
APM's fix on firmware can make the issue disappeared, but
it isn't released yet.
>
> --
> Y
Public bug reported:
1, grub boot log
TianoCore 2.0.0 UEFI 2.4.0 Sep 1 2015 12:48:07
CPU: APM ARM 64-bit Strega Rev A2 2400MHz PCP 2400MHz
32 KB ICACHE, 32 KB DCACHE
SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 66MHz
Board: X-Gene Merlin Board
Slimpro FW:
Ver: 3.4 (build
The issue can be work around by commenting 'recordfail' in the boot entry of
'Ubuntu'.
And it can be reproduced on upstrem grub too.
Looks the sectors wroten to hd0 is out of range in the partition, and it
should be bug in grub.
--
You received this bug notification because you are a member of
That can be reproduced by running 'save_env' command in grub shell:
grub> save_env 123
error: failure writing sector 0xe14d800 to `hd0'.
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
1) write environment failure
grub> save_env 123
error: failure writing sector 0xe153800 to `hd0'.
2) LBA of grub environment variable file
ubuntu@ubuntu:~$ sudo hdparm --fibmap /boot/grub/grubenv
[sudo] password for ubuntu:
/boot/grub/grubenv:
filesystem blocksize 4096, begins at LBA
>From dann's reports:
1) system1
Code: 1412 f9400273 b4000213 d1002274 (b9402280)
2) system2
Code: 1412 f9400273 b4000213 d1002274 (b9402280)
And the upstem report in #15,
Code: 1403 f9400273 b4000213 d1002274 (b9402282)
The code snippet should be the following in __d_lookup(): fs/d
*** This bug is a duplicate of bug 1440536 ***
https://bugs.launchpad.net/bugs/1440536
** This bug has been marked a duplicate of bug 1440536
Oops __d_lookup+0x88/0x194
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
** Description changed:
+
+ [Impact]
+
+ crash can't be used on ubuntu trusty, utopic and vivid
+
+ [Test Case]
+
+ sudo crash ~/vmlinux
+
+ [Regression Potential]
+
+ The proposed patch has been merged upstream, so there shouldn't be
+ potential regression
+
+ [Other Info]
+
+
Aft
** Description changed:
+
+ [Impact]
+
+ crash can't be used on ubuntu trusty, utopic and vivid
+
+ [Test Case]
+
+ sudo crash ~/vmlinux
+
+ [Regression Potential]
+
+ The proposed patch has been merged upstream, so there shouldn't be
+ potential regression
+
+ [Other Info]
+
+
Whe
>From the original report, the issue happened since 3.17, so close it on trysty
>because we can't reproduce it
on trusty too.
I've seen this with mainline since somewhere in v3.17 and on several
hardware boards stress testing KVM by running workloads in VMs.
** Changed in: lin
Finally I figured out one approach to reproduce it quickly, see the
attachment log.
** Attachment added: "crash log in trusty"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1425576/+attachment/4416913/+files/dmesg-trusty.log
--
You received this bug notification because you are a mem
And the patches in below links can fix the above crashs(#14, #15)
http://kernel.ubuntu.com/git/ming/ubuntu-trusty.git/commit/?h=apm-enet-
fix&id=a19b2c0bdd12e59a482717664312b18407284ee5
http://kernel.ubuntu.com/git/ming/ubuntu-utopic.git/commit/?h=arm64-net-
backport&id=d46456e3ed9153e743f2add6e0
** Attachment added: "crash log in utopic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1425576/+attachment/4416914/+files/dmesg-utopic.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/142
** Description changed:
+ [Impact]
- [Impact]
-
- crash can't be used on ubuntu trusty, utopic and vivid
+ crash in ARM64 can't be used on ubuntu trusty, utopic and vivid when
+ debugging a new kernel like 4.1-rc+
[Test Case]
sudo crash ~/vmlinux
+ crash will exit with failure log o
Public bug reported:
On trusty, some BT commands are missed for ARM64.
[Impact]
some BT commands aren't usable, such as bt -e, bt -l, ...
[Test Case]
- start crash
- run bt -e
crash> bt -e
PID: 2113 TASK: ffc3e3446180 CPU: 5 COMMAND: "crash"
bt: arm64_eframe_search: function not implem
** Changed in: linux (Ubuntu Vivid)
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/1458042
Title:
[SRU] xgene-enet: add SGMII based 1GbE supp
I have discussed with David privately, and has confirmed that his problem
is different with that of eGalaxis.
For eGalaxis devices, its MT_CLS_EGALAX info is not added into current
-precise driver, so it work badly.
For Quanta touchscreen device, the problem is that its driver has changed
recent
@ashindeed,
Sorry for missing your 'dmesg'.
I found your device is same with David, and it is Quanta touchscreen
3008.
So could you test the images in the link below to see if they can fix your
problem?
http://kernel.ubuntu.com/~ming/bugs/Quanta-hid/
Thanks,
--
Ming Lei
On Thu, Ap
re are still the problems, please post the 'dmesg' here.
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/913164
Title:
REGRESSION: eGalaxis Touchscreen Driver does no
On Thu, Apr 12, 2012 at 9:53 AM, teh603 <913...@bugs.launchpad.net> wrote:
> Quote: For eGalaxis devices, its MT_CLS_EGALAX info is not added into current
> -precise driver, so it work badly.
>
> @Ling Mei- Is there any way we can get the correct info added or
> backported into the driver before re
On Sun, May 20, 2012 at 2:07 AM, Torsten Bronger
wrote:
> I copied very large files with rsync. rsync prints the transfer rate on
> the screen, and in case of NTFS, it was the expected 10 MByte/s (I
> copied though 100MBit Ethernet on the USB disk), and in case of FAT32 it
> was 900 kByte/s. So,
Hi Andrew,
On Tue, May 22, 2012 at 1:44 AM, Andrew Yurkov
<901...@bugs.launchpad.net> wrote:
> So now I can view some files from console (watching videos via mplayer).
> But opening nautilus in /media/LaCie gives me errors - after it I can't use
> the device.
>
>
> dmesg now gives such output:
>
>
buntu/+source/linux/+bug/1002697/+attachment/3157247/+files/resume.log
Could you try the upstream kernel in the below link to see if it can
fix your problem?
http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.4-precise/
Thanks,
--
Ming Lei
--
You received this bug notification be
rding to my experiences, the step 7 of 'Kernel Build and
Installation' is not needed.
But even I did it, I still can not build main line kernel on precise.
thanks,
--
Ming Lei
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
fakeroot: line 178: make-kpkg: command not found
BTW, make-kpkg is provided by 'kernel-package' package.
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/942391
Title:
upstre
tc/kernel/postrm.d/zz-update-grub
3.3.0-030300rc4-generic /boot/vmlinuz-3.3.0-030300rc4-generic
Errors were encountered while processing:
/home/tom/temp/test/linux-image-3.3.0-030300rc4-generic_3.3.0-030300rc4.201202221601_amd64.deb
thanks
--
Ming Lei
--
You received this bug notification becaus
*** This bug is a duplicate of bug 914319 ***
https://bugs.launchpad.net/bugs/914319
** This bug has been marked a duplicate of bug 914319
NULL pointer dereference at sd_revalidate_disk+0x30/0x2a0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
*** This bug is a duplicate of bug 914319 ***
https://bugs.launchpad.net/bugs/914319
** This bug has been marked a duplicate of bug 914319
NULL pointer dereference at sd_revalidate_disk+0x30/0x2a0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
and looks
modules are not built into.
>
> Can you possible revert back to the rc4 tree and see if you have an
> issue compiling it?
I am sure I have built 3.3-rc3 upstream kernel on early precise ubuntu, but now
I can't do it, so looks it is nothing to do with upstream kernel versio
m back at a computer Friday.
I have tried the kernel-package from your PPA, looks same result with
it in precise.
Thanks for your response.
thanks
--
Ming Lei
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
On Tue, Apr 17, 2012 at 10:48 AM, cnbiz850 <960...@bugs.launchpad.net> wrote:
> Correction to my commet above. The described apply only to reboots.
> Cold startups seem not affected.
Care to post the output of dmesg on both reboot and cold startup cases?
--
You received this bug notification be
Could you check if your panic message is same with LP 921944?
I reported the issue on 3.2.0-12.18~3.2.0-12.21 when I was using WIFI, but the
problem
is a bit difficult to reproduce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
On Thu, May 10, 2012 at 12:25 PM, JOTADEATH wrote:
> I have the exactly same problem, nautilus and unity...
ashindeed, JOTADEATH, as the comment #40 said, there are some problems
about double click function, which should be caused by X.org, maybe you should
recreate a new bug entry for it.
Than
ew high speed USB device number 5 using ehci_hcd
Could you plug your usb HD. into USB3 and see if it can work well?
> [ 610.688466] scsi7 : uas
> [ 610.884197] scsi 7:0:0:0: Direct-Access LaCie Rugged FW USB3
Thanks,
--
Ming Lei
--
You received this bug notification because you are
On Thu, May 10, 2012 at 5:14 AM, Stephen Zimmerman
<872...@bugs.launchpad.net> wrote:
> Having this happen on Xubuntu 12.04 as well -- can transfer files from
> phone to computer file (drag and drop, you name it), but computer to
> phone is not happening. 11.04 (what I was on previously) worked.
>
@ashindeed
Could you try to enable "Two-finger scrolling" in
System Setting->Mouse and Touchpad->Touchpad->Two-finger scrolling
to see if double click can work?
Looks single/double click function is nothing to do with low level usb
hid driver.
Also for X freeze, not sure if it is a X bug
Hi Ding,
Could you help to verify 3.2.0-24.38 to see the UAS problem can be fixed
if you have time?
Thanks,
--
Ming Lei
On Fri, May 4, 2012 at 1:05 AM, Luis Henriques
wrote:
> This bug is awaiting verification that the kernel for Precise in
> -proposed solves the problem (3.2.0-24.38).
Public bug reported:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...
L3c Cache: 8MB
[0.587986] kernel BUG at /build/linux-RKt9qy/linux-4.4.0/mm/memory.c:1887!
[0.594918] Internal error: Oop
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548207
Title:
xenial 4.4.0-7-generic: kernel oops during load module
To manage no
When this commit c8d73ebfe19daac81b7cb5c8d1dd(module: clean up RO/NX handling)
is reverted, the issue disappeares.
So the above commit should be the cause.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Looks it is enough to just revert
'e96e20134729121689a0089537c6ed(module: clean up RO/NX handling)'
for fixing the issue.
But the interesting thing is that there isn't the problem in upstream kernel
4.5-rc5, and the commit(module: clean up RO/NX handling) isn't reverted
in upstream yet.
So looks
*** This bug is a duplicate of bug 1547718 ***
https://bugs.launchpad.net/bugs/1547718
** This bug has been marked a duplicate of bug 1547718
4.4.0-7.22 no longer boots on arm64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
On Mon, Feb 22, 2016 at 4:37 PM, Ming Lei wrote:
> Looks it is enough to just revert
> 'e96e20134729121689a0089537c6ed(module: clean up RO/NX handling)'
> for fixing the issue.
>
> But the interesting thing is that there isn't the problem in upstream kernel
> 4.5-
Looks there isn't crash during the ifconfig up/down test any more after applying
the patch in the following link, but ifconfig still may hang during the test:
https://www.mail-archive.com/netdev@vger.kernel.org/msg88060.html
See test log in the attachment.
** Attachment added: "ifconfig hangs d
On HP ProLiant m400 Server, when booting via UEFI, TFTP still may timeout when
loading kernel by
netboot.
Looks only the commit 49426e9fd2( efinet: open Simple Network Protocol
exclusively) isn't enough, and the
following three commits are required too for grub working well on HP m400 ARM64
ser
Public bug reported:
Inside VM wily kernel which is installed via wily d-i installer, reboot hangs,
see the following message:
[ 40.294727] reboot: Restarting system
And never return to UEFI UI.
The issue can be observed too in d-i installing too.
** Affects: edk2 (Ubuntu)
Importance
The three grub changes have been tested fine on both APM arm64 board and HP
m400, looks
all works fine.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Hi Dann,
On Mon, Dec 21, 2015 at 11:59 PM, dann frazier
wrote:
> @Ming can you clarify which build(s) you tested (trusty, vivid, and/or
> wily)? It isn't clear to me if "three grub changes" means you tested all
All three have been tested on both two kinds of arm64.
thanks,
> 3 builds, or if yo
When I built 4.3.0-7-generic on arm64(mustang) Wily with the following
steps,
fakeroot debian/rules clean
fakeroot debian/rules binary-generic
by this compiler:
ubuntu@ubuntu:~$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/aarch64-linux-gnu/5/lt
0108 (Ubuntu/Linaro 5.3.1-5ubuntu2)
On Wed, Jan 13, 2016 at 9:11 AM, Ming Lei wrote:
> When I built 4.3.0-7-generic on arm64(mustang) Wily with the following steps,
>
> fakeroot debian/rules clean
> fakeroot debian/rules binary-generic
>
> by this compiler:
&
Hi,
Wrt. the build environment, the built kernel/modules can work fine just after
switching gcc from gcc-5 to gcc-4.9 and keep other things not changed
in Xenial.
So I am sure the issue is in Xenial gcc-5, and the bug should be introduced
after 5.2.1-22ubuntu2 because Wily gcc-5 hasn't this probl
Looks the latest proposed gcc-5.3.1-6ubuntu1 has the problem too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533009
Title:
arm64: "unsupported RELA relocation"
To manage notifications about th
On Fri, Jan 15, 2016 at 6:29 PM, Matthias Klose wrote:
> please attach the preprocessed source and the exact command line options
> to build the libahci module.
Not only libahci modules, all built modules has the problem.
Follows the command line for building libahci.ko:
1) apt-get source linux
Dann,
In my test, the issue is nothing to do with kernel, and only related
with modules built by the affected gcc 5.3.
For example, the kernel running is built from gcc 5.2, then I rebuilt some
modules by gcc 5.3, the issue comes
when I try to load the just built module.
BTW, '-mcmodel=large' i
Public bug reported:
When I test xenial kernel about PCI function on one ARM64 box, I see
the PCI device does work, and this device is shown with MSI capability.
But the msi_irqs directory can't be found under:
./platform/soc/1f2b.pcie/pci:00/:00:00.0/:01:00.0/
When I trace the
Now grub2 for Xenial just works fine on mcdivitt in case of netboot, especially
during loading kernel image
via tftp.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521612
Title:
Continued TFTP tim
201 - 300 of 813 matches
Mail list logo
