Want to mention that I am hit by this problem too.
HP-ProBook-430-G2 3.19.0-42-generic x86_64
Downgraded to 3.13.0-74 did not work out because hit by another
different problem which shows up in 3.13.0-74, ie when wake up from
suspend, the display got messed up. The display will not be restored
c
Hey, I've been following the instruction in comment #115. I've got up to step 5
and when I run the command make -jX, I get the following output.
scripts/kconfig/conf --silentoldconfig Kconfig
drivers/media/rc/Kconfig:346: can't open file "drivers/media/rc/img-ir/Kconfig"
make[2]: *** [silentoldco
Hey, I figured out my problem. Turns out that some of the header files
and code were broken (had a padlock on the icon) or were missing
altogether. I made new copies of the file with the same code and
formatting. After that, there were no problems running the command: make
-jX
@Jane Doe, Isaiah:
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
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/1647793
Title:
Yakkety: arm64: CONFIG_ARM64_ERRATUM_8
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
Finally figured out that the 'msi_irqs' directory can't show once the tg3
interface is down.
When I make it up manually, the directory can appear.
So looks an invalide report.
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Invalid
--
You received this bug notification becaus
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
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
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-
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
*** 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 Kernel
Packages, which is subscribed to linux
** 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/1548207
Title:
xenial 4.4.0-7-generic: kernel oops during load module
Public bug reported:
When running 'stress-ng --all 64 -t 800 -v' on Xenial/ARM64, the following
kernel oops is triggered.
[ 93.309158] Unable to handle kernel NULL pointer dereference at virtual
address 0038
[ 93.309160] pgd = 8007a5914000
[ 93.309163] [0038] *pgd=0047a5
The issue can be reproduced on '4.4.0-22-generic #38' too
--
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/1575506
Title:
Xenial: ARM64: Unable to handle kernel NULL pointer dereference at
** 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/1575506
Title:
Xenial: ARM64: Unable to handle kernel NULL pointer der
Upstream 4.6-rc6 hasn't this problem
--
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/1575506
Title:
Xenial: ARM64: Unable to handle kernel NULL pointer dereference at
virtual address 00
On Wed, Apr 27, 2016 at 4:31 PM, Ming Lei <1575...@bugs.launchpad.net> wrote:
> Upstream 4.6-rc6 hasn't this problem
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1575506
>
> Title:
On Thu, Apr 28, 2016 at 9:55 PM, Tim Gardner wrote:
> Ming - please try the kernel at
> http://people.canonical.com/~rtg/lp1575506/ - I've updated AUFS to the
> latest stable branch. Source at git://kernel.ubuntu.com/rtg/ubuntu-
> xenial.git aufs
Looks no difference by installi
It can be triggered 100% by running 'tcpdump -I ethX'.
--
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/1574814
Title:
ThunderX: soft lockup in cursor_timer_handler() Edit
Status in linux
On Tue, May 3, 2016 at 10:35 AM, dann frazier
wrote:
> On Fri, Apr 29, 2016 at 2:06 AM, Ming Lei <1574...@bugs.launchpad.net> wrote:
>> It can be triggered 100% by running 'tcpdump -I ethX'.
>
> Thanks Ming. I let that run for a few hours, but was unable to
>
On Tue, May 3, 2016 at 1:14 PM, Radha Mohan Chintakuntla
wrote:
> Ming,
> The "-I" option of tcpdump is monitoring mode typically applicable only to
> wifi interfaces. So even if you run it on Thunder's NIC interfaces it will
> return saying that this is not support
On Fri, May 13, 2016 at 7:22 AM, dann frazier
wrote:
> I used ftrace to do some duration measuring of the timer function
> fb_flashcursor(). I noticed several places where this timer takes around
> 98 ms to complete. This time seems to be due to multiple calls to
> __memcpy_toio() in ast_dirty_upd
On Mon, May 16, 2016 at 5:25 PM, Ming Lei wrote:
> On Fri, May 13, 2016 at 7:22 AM, dann frazier
> wrote:
>> I used ftrace to do some duration measuring of the timer function
>> fb_flashcursor(). I noticed several places where this timer takes around
>> 98 ms to complet
On Tue, May 17, 2016 at 12:12 PM, Ming Lei wrote:
> On Mon, May 16, 2016 at 5:25 PM, Ming Lei wrote:
>> On Fri, May 13, 2016 at 7:22 AM, dann frazier
>> wrote:
>>> I used ftrace to do some duration measuring of the timer function
>>> fb_flashcursor(). I notice
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1533009
Title:
arm64: "unsupported RELA relocation"
Status in gcc-5 pac
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
** Tags added: verification-done-trusty
--
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/1354242
Title:
mellanox driver crash fix in leagcy EQ mode
Status in “linux” package in Ubuntu:
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 thi
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 thi
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 zinc.canonic
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
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/1400349
Title:
[SRU] new arm64 optimized copy_to_user a
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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/1400349
Title:
[SRU] new arm64 optimized copy_to_user a
I have sent out one patch to fix the problem for upstream:
http://marc.info/?t=14170671845&r=1&w=2
Let's see the further discussion.
--
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
what do you think about it?
Thanks,
** Changed in: linux (Ubuntu Utopic)
Assignee: (unassigned) => Ming Lei (tom-leiming)
--
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/1386490
Title:
On Tue, Dec 2, 2014 at 2:49 AM, dann frazier 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-kernel&m=141708838404470&w=2
>
** 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-
utility/crash
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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/1360140
Title:
trusty still uses APM's out-of-tree xgen
merged to upstream as commit:
https://github.com/torvalds/linux/commit/0738854939e6ec9b9111a8cfc0ca1dfa3cff6b2e
--
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/1359146
Title:
Kernel cras
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()
NET
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/13542
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) 20
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-
utility/crash/commit/0f6d989aa09
** 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 Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1354349
Title:
trusty
*** 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 Kernel
Packages, which is subscribe
** Tags added: kernel-fixed-upstream
--
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/1455372
Title:
Trausty arm64 VM doesn't support 'reboot' and 'powerdown'
Status in linux package in U
** 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 Kernel
Packages
[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
[tom@vm-test]$vim arm64-qemu
[tom@vm-test]$./arm64-qemu
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.13.11-ckt20+ (tom@tom-T450) (gcc version 4.8.2
20140110 (prerelease) [ibm/gcc-4_8-branch merged from gcc-4_8-branch, revision
205847] (Ubuntu/Linaro 4.8.2-13ubuntu1
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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/1438585
Title:
no console when starting VM from cloud
The issue can be fixed by the following upstream commit:
commit 7623eee9046015b65a1f63f6bf07ab7805c36eb4
Author: Dave Anderson
Date: Tue May 19 10:20:04 2015 -0400
Fix for the ARM64 page size determination on Linux 4.1 and later
kernels. Without the patch, the crash session fails duri
Public bug reported:
After running crash from trusty, the failure log in [1] can be observed.
Then I built crash from wily directly, the similar failure[2] can be
observed too.
[1] failure log
ubuntu@am2:~/git/crash-wily$ sudo crash ~/vmlinux
crash 7.0.3
Copyright (C) 2002-2013 Red Hat, Inc
Public bug reported:
When I build crash from wily, the failure in [1] can be
triggered if the kernel is 4.0+.
[1] failure log
ubuntu@am2:~/git/crash-wily$ sudo ./crash ~/vmlinux
crash 7.0.8
Copyright (C) 2002-2014 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
Copyright
The problem can be fixed by applying the following commit:
commit db07dbf5a7e19806b1629bd4125e6643978c6f9f
Author: Dave Anderson
Date: Thu Feb 19 16:16:33 2015 -0500
Prepare for the future increment of Linux 3.x to 4.x.
(ander...@redhat.com)
--
You received this bug notification beca
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Ming Lei (tom-leiming)
--
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/1438585
Title:
no console when starting VM f
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
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 Kernel
Packages, which is subscribed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ming Lei (tom-leiming)
--
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/1418284
Title:
trusty: kernel oops during run
inding, also the ethernet driver of stmmac doesn't parse
fixed link binding, so cause ethernet not workable at all on utopic.
The two patches in below tree can add the fixed link support in stmmac
and changes the fixed link description into current standard binding:
git://kernel.u
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https
/324)
Status in linux package in Ubuntu:
Fix Committed
Bug description:
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
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
x27; DT patches to utopic 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 th
** Attachment added: "dmesg log of 'poweroff'"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455372/+attachment/4411589/+files/dmesg.log
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member
Looks there was similar report from upstream:
http://marc.info/?l=linux-fsdevel&m=142865378923064&w=2
but still don't have resolution or further report.
Also I tried to use fbench to create lots of files, list dirs concurently for
reproducing
the issue, but can't reproduce it yet.
--
You rec
BTW, looks it isn't related with specific filesystem, and from the recent
triger, it happened when
walking path inside proc filesystem:
[24993.562923] Call trace:
[24993.565357] [] __d_lookup+0x88/0x194
[24993.570467] [] d_lookup+0x38/0x64
[24993.575319] [] d_hash_and_lookup+0x54/0x6c
[24993.5809
>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 Kernel
Packages, which is subscribed to linux in Ubunt
** 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
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
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-
backpor
** 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
arch: function not implemented
[Regression Potential]
These changes are to code that only gets compiled on arm64, so
there's no risk to other architectures. Also the proposed change is
merged to upstream alread.
The patches in below link can make them workable:
http://kernel.ubuntu.com/git/ming/c
** Changed in: linux (Ubuntu Vivid)
Assignee: (unassigned) => Ming Lei (tom-leiming)
--
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/1458042
Title:
[SRU] xgene-enet: add SGMII ba
ot implemented
[Regression Potential]
These changes are to code that only gets compiled on arm64, so
there's no risk to other architectures. Also the proposed change is
merged to upstream alread.
The patches in below link can make them workable:
http://kernel.ubuntu.com/git/
Verification on trusty:
ubuntu@am2:~$ sudo crash vmlinux
[sudo] password for ubuntu:
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
Copyrigh
verification on vivid:
ubuntu@ubuntu:~/test$ sudo dpkg -l crash
sudo: unable to resolve host ubuntu
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
Verification on utopic:
ubuntu@am6:~$ sudo crash vmlinux
[sudo] password for ubuntu:
crash 7.0.8
Copyright (C) 2002-2014 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
Copyrigh
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
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/1458042
Title:
[SRU] xgene-enet: add SGMII based 1GbE s
ubuntu@am6:~$ uname -a
Linux am6 3.16.0-43-generic #58-Ubuntu SMP Fri Jun 19 11:04:11 UTC 2015 aarch64
aarch64 aarch64 GNU/Linux
ubuntu@am6:~$ sudo ethtool eth2
Settings for eth2:
Supported ports: [ MII ]
Supported link modes: 1000baseT/Full
Supported pause frame use: No
Public bug reported:
1, upgrade to vivid from trysty
2, boot the server, then the following log in [1] can be observed
[1] kernel booting log
Starting kernel ...
L3C: 8MB
[0.00] Booting Linux on physical CPU 0x0
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializ
Turns out the firmware on this server is a bit old(U-Boot 2013.04 (Oct 01 2014
- 15:18:17)), and the problem
doesn't exit on another server which firmware is U-Boot 2013.04 (Mar 26 2015 -
11:31:01).
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug not
I can't reproduce it after running half a day on ms10-36, and OOM is often
triggered .
--
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/1469214
Title:
HP ProLiant m400 Server crashes with
Oops, the test result in #4 is for LP1469218 instead of this one.
--
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/1469214
Title:
HP ProLiant m400 Server crashes with unhandled level 3 tra
I can't reproduce it after running half a day on ms10-36, and OOM is
often triggered .
--
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/1469218
Title:
HP ProLiant m400 Server sda timeout c
BTW, it can't be reproduced on mustang when running vivid too.
--
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/1469218
Title:
HP ProLiant m400 Server sda timeout causes file system hang
But another kernel oops is just found on one mustang with vivid:
Call trace:
Unable to handle kernel NULL pointer dereference at virtual address 0018
pgd = ffc105652000
[0018] *pgd=00432d9dc003Unable to handle kernel NULL pointer
dereference at virtual address 0030
pgd = f
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1418284
Title:
trusty: kernel oops
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
linux package in Ubuntu:
Confirmed
Bug description:
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
bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1430184
Title:
trusty: fail to pass xfstests(generic/324)
Status in linux package in Ubuntu:
Confirmed
Bug description:
ming@am2:~/git/xfstests$ sudo ./check gene
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
1 - 100 of 166 matches
Mail list logo
