Re: 4.9.0-rc6+ boot problem

2016-11-29 Thread Kui Zhang
03:04-0800, Kui Zhang: >> Looks like my boot issue might be kvm related. System boots fine with >> CONFIG_KVM=m > > v4.9-rc6 has some funny changes around modversion, although your bug > looks even more random ... > > Can you reproduce with v4.9-rc7 built from a clean repo

Re: 4.9.0-rc6+ boot problem

2016-11-29 Thread Kui Zhang
not set On Sun, Nov 27, 2016 at 2:23 PM, Kui Zhang wrote: > Hello, > > I am having problem booting 4.9.0-rc6+ on my laptop. > > 4.9.0-rc5+ works, so not likely hardware issues. > > > Ubuntu Zesty Zapus > > ### > gcc-6 with > > CONFIG_PCI_QUIRKS=y > CONFIG_X8

4.9.0-rc6+ boot problem

2016-11-27 Thread Kui Zhang
Hello, I am having problem booting 4.9.0-rc6+ on my laptop. 4.9.0-rc5+ works, so not likely hardware issues. Ubuntu Zesty Zapus ### gcc-6 with CONFIG_PCI_QUIRKS=y CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y After grub, screen turns off. No pre modeset messages. Then system reboot itself. When

Re: change in xhci result in soft lockup

2016-08-16 Thread Kui Zhang
Thanks. This patch fixed my issue. Kui.Z On Mon, Aug 15, 2016 at 3:52 AM, Mathias Nyman wrote: > On 14.08.2016 01:13, Kui Zhang wrote: >> >> Hello, >> >> System still hangs with 4.8.0-rc1+. There are new info in the logs. >> > > Does Alban Browaeys Patc

Re: change in xhci result in soft lockup

2016-08-14 Thread Kui Zhang
48 89 d1 89 df 4c 89 e2 e8 39 fe ff ff 8b 55 e0 83 e2 01 74 0a f3 90 8b Aug 13 14:49:32 kernel: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [thermald:2511] -- Reboot -- On Sat, Aug 6, 2016 at 3:34 AM, Kui Zhang wrote: > Hello > > After this patch > > # f

change in xhci result in soft lockup

2016-08-06 Thread Kui Zhang
Hello After this patch # first bad commit: [86065c2719a5685cef36945f09def3f0658c7860] xhci: don't rely on precalculated value of needed trbs in the enqueue loop My system would hang while installing android packages over USB adb install -r VLC-Android-2.1.0-ARMv7.apk Log: Aug 01 01:49:17 k

Re: issue when applying ICC profile to display after drm/i915 change

2016-05-31 Thread Kui Zhang
/ > https://patchwork.freedesktop.org/series/5466/ > > Still waiting for review though. > > - > Lionel > > > On 29/05/16 19:20, Kui Zhang wrote: >> >> Hello, >> >> this used to work. >> >> xcalib D6200MTX.icc >> >> >> After this it stopp

Re: WMI driver no longer load after switching to generic UUID library

2016-05-30 Thread Kui Zhang
Thanks guys. keyboard functions are working now. kui.z On Mon, May 30, 2016 at 7:40 AM, Andy Shevchenko wrote: > On Mon, 2016-05-30 at 12:52 +0200, Bjørn Mork wrote: >> How about the untested attached patch? >> > > Facepalm.jpg! > > Good catch! > > The question is how it passed in our internal

Fwd: WMI driver no longer load after switching to generic UUID library

2016-05-29 Thread Kui Zhang
oops, forgot the list. -- Forwarded message -- From: Kui Zhang Date: Sun, May 29, 2016 at 11:35 AM Subject: WMI driver no longer load after switching to generic UUID library To: andriy.shevche...@linux.intel.com, dvh...@linux.intel.com, a...@linux-foundation.org, torva...@linux

issue when applying ICC profile to display after drm/i915 change

2016-05-29 Thread Kui Zhang
Hello, this used to work. xcalib D6200MTX.icc After this it stopped working commit 20a34e78f0d71cab058a943b2e9601b97b761227 drm/i915: Update color management during vblank evasion. Color profile only take effect after the screen if back on. xcalib D6200MTX.icc xrandr --output eDP1 --off xra

Re: connection failure after "tcp: remove max_qlen_log"

2016-02-27 Thread Kui Zhang
;> import socket >>> sock = socket.socket() >>> sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1) >>> sock.bind(('127.0.0.1',42000)) >>> sock.listen(0) >>> s, a= sock.accept() >>> >>> s.send('test') >>&g

Re: connection failure after "tcp: remove max_qlen_log"

2016-01-25 Thread Kui Zhang
I was using 2.7.11. Older version did set backlog to 1 ( http://bugs.python.org/issue8498 ). On Sun, Jan 24, 2016 at 7:18 PM, Eric Dumazet wrote: > On Sun, Jan 24, 2016 at 2:17 AM, Kui Zhang wrote: >> We licensed the java software. As far as I can tell, the connection is >>

Re: connection failure after "tcp: remove max_qlen_log"

2016-01-24 Thread Kui Zhang
{29, 97}) 5539 sendto(5, "b1\n", 7, 0, NULL, 0) = 7 5539 select(7, [3 4 5 6], [], [3 4 5 6], {30, 0}) = 1 (in [4], left {28, 459804}) 5539 recvfrom(4, "c11111\n", 1024, 0, NULL, NULL) = 7 5539 select(7, [3 4 5 6], [4], [3 4 5 6], {30, 0}) = 1 (out [4], left {29, 999

Re: connection failure after "tcp: remove max_qlen_log"

2016-01-23 Thread Kui Zhang
/bin/python import socket sock = socket.socket() sock.bind(('127.0.0.1',42000)) sock.listen(0) s, a= sock.accept() s.send('test') And telnet to it. On Sat, Jan 23, 2016 at 4:11 PM, Eric Dumazet wrote: > On Sat, 2016-01-23 at 15:54 -0800, Kui Zhang wrote: >>

connection failure after "tcp: remove max_qlen_log"

2016-01-23 Thread Kui Zhang
Hello, One of our java software would not start after this: # first bad commit: [ef547f2ac16bd9d77a780a0e7c70857e69e8f23f] tcp: remove max_qlen_log Log from software: STATUS | monitor | 2016/01/23 14:22:55 | Launching a Service... INFO | buserver | 2016/01/23 14:23:00 | WrapperManager class

Re: 3.17.0-rc7 kernel NULL pointer dereference (3ware 9650SE)

2014-10-04 Thread Kui Zhang
Finally got some more useful traces. [ 4629.957226] BUG: unable to handle kernel NULL pointer dereference at 0018 [ 4629.960539] IP: [] swiotlb_unmap_sg_attrs+0x30/0x70 [ 4629.960539] PGD 3e4176067 PUD 3e4177067 PMD 0 [ 4629.960539] Oops: [#1] SMP [ 4629.960539] Modules linked in

3.17.0-rc7 kernel NULL pointer dereference

2014-10-01 Thread Kui Zhang
Hello, We have been getting NULL pointer dereference error, with 3.17.0-rc7, built from commit aad7fb916a10f1065ad23de0c80a4a04bcba8437 I don't know how to reproduce this. It seem to happen during high io load (sometimes). I got follow via usb a serial console, not sure if trace is complete. [1

btrfs kernel trace: btrfs_delayed_qgroup_accounting

2014-09-26 Thread Kui Zhang
Hello, We have been getting some of these in dmesg: [33957.472633] [ cut here ] [33957.472681] WARNING: CPU: 1 PID: 22758 at fs/btrfs/qgroup.c:1408 btrfs_delayed_qgroup_accounting+0x540/0xe40() [33957.472738] Modules linked in: cpuid nf_conntrack_ipv4 nf_defrag_ipv4 xt_con

drm modeset lock traces on boot

2014-06-14 Thread Kui Zhang
Hello, I am getting these on boot. The computer seems to function normally. Some time I can trigger some of the traces with: udevadm trigger [0.248160] [ cut here ] [0.248300] WARNING: CPU: 1 PID: 6 at kernel/time/tick-sched.c:191 can_stop_full_tick+0xb4/0xbf() [

Re: Segmentation fault on all golang executables

2014-06-12 Thread Kui Zhang
Thanks for the patches. The workaround works. Stupid idea, maybe something in dmesg to help spark conversions, when this workaround is hit? Looks like golang people are close. Thanks Kuiz -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majo

Segmentation fault on all golang executables

2014-06-12 Thread Kui Zhang
Hello, This commit seem to cause Segmentation fault on any of my golang executables. commit 6f121e548f83674ab4920a4e60afb58d4f61b829 Author: Andy Lutomirski Date: Mon May 5 12:19:34 2014 -0700 x86, vdso: Reimplement vdso.so preparation in build-time C golang-go 2:

Re: rmmod thermal, unable to handle kernel NULL pointer dereference

2014-05-21 Thread Kui Zhang
Thanks, that fixed it. On Wed, May 21, 2014 at 1:22 AM, Aaron Lu wrote: > On 05/21/2014 01:57 PM, Kui Zhang wrote: >> Hello, >> >> I get following error when rmmod thermal. >> >> rmmod thermal >> Killed > > Thanks for the report. Here is a fix pat

rmmod thermal, unable to handle kernel NULL pointer dereference

2014-05-20 Thread Kui Zhang
Hello, I get following error when rmmod thermal. rmmod thermal Killed [ 1207.313060] BUG: unable to handle kernel NULL pointer dereference at (null) [ 1207.313460] IP: [] _raw_spin_lock_irq+0x6/0x30 [ 1207.313858] PGD 0 [ 1207.314256] Oops: 0002 [#1] SMP [ 1207.314658] Modules linked

nouveau init unknown opcode error, when CONFIG_DRM_NOUVEAU=y

2014-02-12 Thread Kui Zhang
Hello, When CONFIG_DRM_NOUVEAU=y, I get following error. Blank screen after initrd. This was in the dmesg. [0.282559] [drm] hdmi device not found 1 0 1 [0.282688] nouveau [ DEVICE][:01:00.0] BOOT0 : 0x046800a3 [0.282693] nouveau [ DEVICE][:01:00.0] Chipset: G72 (NV46) [

Re: nouveau - BUG: unable to handle kernel NULL pointer dereference

2014-01-15 Thread Kui Zhang
yap, that fixed it. thanks kuiz On Wed, Jan 15, 2014 at 12:34 AM, Ilia Mirkin wrote: > On Wed, Jan 15, 2014 at 3:28 AM, Kui Zhang wrote: >> Hello, >> >> I am getting a blank screen after loading initrd, with nouveau. >> >> the laptop seem to boot o

nouveau - BUG: unable to handle kernel NULL pointer dereference

2014-01-15 Thread Kui Zhang
Hello, I am getting a blank screen after loading initrd, with nouveau. the laptop seem to boot ok, just no video.This is in dmesg. Sorry if dupes, html version bounced. [0.855961] nouveau [ VBIOS][:01:00.0] ... checksum invalid [0.856120] nouveau [ VBIOS][:01:00.0] BIT sig