Re: [linux-sunxi] Re: [PATCH v2 1/5] ARM: dts: sun8i: Add SID node

2015-11-24 Thread Shuge
On Monday, November 23, 2015 at 17:32 UTC+8, Maxime Ripard wrote: > On Mon, Nov 23, 2015 at 10:51:15PM -0800, Sugar Wu wrote: >> On Monday, November 23, 2015 at 8:43:59 PM UTC+8, Maxime Ripard wrote: >>> >>> Hi, >>> >>> On Mon, Nov 23, 2015 at 09:02:48AM +0100, Josef Gajdusek wrote: Add a

Re: [linux-sunxi] Re: [PATCH v2 1/5] ARM: dts: sun8i: Add SID node

2015-11-24 Thread Shuge
On Monday, November 23, 2015 at 17:32 UTC+8, Maxime Ripard wrote: > On Mon, Nov 23, 2015 at 10:51:15PM -0800, Sugar Wu wrote: >> On Monday, November 23, 2015 at 8:43:59 PM UTC+8, Maxime Ripard wrote: >>> >>> Hi, >>> >>> On Mon, Nov 23, 2015 at 09:02:48AM +0100, Josef Gajdusek wrote: Add a

Re: [BUG]: when printk too more through serial, cpu up is failed.

2013-03-14 Thread Shuge
于 2013年03月14日 22:05, Greg KH 写道: On Thu, Mar 14, 2013 at 09:51:34PM +0800, Shuge wrote: Hi all, When the kernel printk too many log, the cpu is failed to come online. The problem is this: For example, cpu0 bring up cpu1: a. cpu0 call cpu_up: cpu_up() ->_cpu

[BUG]: when printk too more through serial, cpu up is failed.

2013-03-14 Thread Shuge
Hi all, When the kernel printk too many log, the cpu is failed to come online. The problem is this: For example, cpu0 bring up cpu1: a. cpu0 call cpu_up: cpu_up() ->_cpu_up() ->__cpu_notify(CPU_UP_PREPARE) ->__cpu_up()

[BUG]: when printk too more through serial, cpu up is failed.

2013-03-14 Thread Shuge
Hi all, When the kernel printk too many log, the cpu is failed to come online. The problem is this: For example, cpu0 bring up cpu1: a. cpu0 call cpu_up: cpu_up() -_cpu_up() -__cpu_notify(CPU_UP_PREPARE) -__cpu_up()

Re: [BUG]: when printk too more through serial, cpu up is failed.

2013-03-14 Thread Shuge
于 2013年03月14日 22:05, Greg KH 写道: On Thu, Mar 14, 2013 at 09:51:34PM +0800, Shuge wrote: Hi all, When the kernel printk too many log, the cpu is failed to come online. The problem is this: For example, cpu0 bring up cpu1: a. cpu0 call cpu_up: cpu_up() -_cpu_up

Re: [PATCH] bounce:fix bug, avoid to flush dcache on slab page from jbd2.

2013-03-12 Thread Shuge
Hi all The bounce accept slab pages from jbd2, and flush dcache on them. When enabling VM_DEBUG, it will tigger VM_BUG_ON in page_mapping(). So, check PageSlab to avoid it in __blk_queue_bounce(). Bug URL: http://lkml.org/lkml/2013/3/7/56 ... .. That sure is strange. I didn't see any

Re: [PATCH] bounce:fix bug, avoid to flush dcache on slab page from jbd2.

2013-03-12 Thread Shuge
Hi all The bounce accept slab pages from jbd2, and flush dcache on them. When enabling VM_DEBUG, it will tigger VM_BUG_ON in page_mapping(). So, check PageSlab to avoid it in __blk_queue_bounce(). Bug URL: http://lkml.org/lkml/2013/3/7/56 ... .. That sure is strange. I didn't see any

[PATCH] bounce:fix bug, avoid to flush dcache on slab page from jbd2.

2013-03-08 Thread Shuge
The bounce accept slab pages from jbd2, and flush dcache on them. When enabling VM_DEBUG, it will tigger VM_BUG_ON in page_mapping(). So, check PageSlab to avoid it in __blk_queue_bounce(). Bug URL: http://lkml.org/lkml/2013/3/7/56 Signed-off-by: shuge --- mm/bounce.c |3 ++- 1 file

[PATCH] bounce:fix bug, avoid to flush dcache on slab page from jbd2.

2013-03-08 Thread Shuge
The bounce accept slab pages from jbd2, and flush dcache on them. When enabling VM_DEBUG, it will tigger VM_BUG_ON in page_mapping(). So, check PageSlab to avoid it in __blk_queue_bounce(). Bug URL: http://lkml.org/lkml/2013/3/7/56 Signed-off-by: shuge sh...@allwinnertech.com --- mm/bounce.c

[jbd2 or mm BUG]: crash while flush JBD2's the pages, that owned Slab flag.

2013-03-07 Thread Shuge
m->bv_page); vto = page_address(to->bv_page) + to->bv_offset; vfrom = kmap(from->bv_page) + from->bv_offset; memcpy(vto, vfrom, to->bv_len); Who can give some suggestions to me. Thanks Shuge NOTICE: This e-mail an

[jbd2 or mm BUG]: crash while flush JBD2's the pages, that owned Slab flag.

2013-03-07 Thread Shuge
Shuge NOTICE: This e-mail and any included attachments are intended only for the sole use of named and intended recipient (s) only. If you are the named and intended recipient, please note that the information contained in this email and its embedded files are confidential and privileged. If you