Thanks randy's comments, I will modifiy it.
On Sun, 2012-12-23 at 19:37 -0800, Randy Dunlap wrote:
> On 12/23/12 18:31, he, bo wrote:
> > From: "he, bo"
> >
> > We often hit kernel panic issues on SMP machines because processes race
> > on multiple cpu. By adding a new parameter printk.cpu,
On 12/23/12 18:31, he, bo wrote:
> From: "he, bo"
>
> We often hit kernel panic issues on SMP machines because processes race
> on multiple cpu. By adding a new parameter printk.cpu, kernel prints
> cpu number at printk information line. It’s useful to debug what cpus
> are racing.
>
>
From: "he, bo"
We often hit kernel panic issues on SMP machines because processes race
on multiple cpu. By adding a new parameter printk.cpu, kernel prints
cpu number at printk information line. It’s useful to debug what cpus
are racing.
Signed-off-by: he, bo
---
From: he, bo bo...@intel.com
We often hit kernel panic issues on SMP machines because processes race
on multiple cpu. By adding a new parameter printk.cpu, kernel prints
cpu number at printk information line. It’s useful to debug what cpus
are racing.
Signed-off-by: he, bo bo...@intel.com
---
On 12/23/12 18:31, he, bo wrote:
From: he, bo bo...@intel.com
We often hit kernel panic issues on SMP machines because processes race
on multiple cpu. By adding a new parameter printk.cpu, kernel prints
cpu number at printk information line. It’s useful to debug what cpus
are racing.
Thanks randy's comments, I will modifiy it.
On Sun, 2012-12-23 at 19:37 -0800, Randy Dunlap wrote:
On 12/23/12 18:31, he, bo wrote:
From: he, bo bo...@intel.com
We often hit kernel panic issues on SMP machines because processes race
on multiple cpu. By adding a new parameter printk.cpu,
6 matches
Mail list logo
