Re: [PATCH v3] printk: Have printk() never buffer its data

2012-07-06 Thread Kay Sievers
On Fri, Jul 6, 2012 at 5:47 AM, Michael Neuling wrote: >> 4,89,24561;NIP: c0048164 LR: c0048160 CTR: >> 4,90,24576;REGS: c0007e59fb50 TRAP: 0700 Tainted: GW >> (3.5.0-rc4-mikey) >> 4,91,24583;MSR: 90021032 >> 4,92,24586;< >> 4,93,24591;S

Re: [PATCH v3] printk: Have printk() never buffer its data

2012-07-06 Thread Kay Sievers
On Fri, Jul 6, 2012 at 12:46 PM, Kay Sievers wrote: > On Fri, Jul 6, 2012 at 5:47 AM, Michael Neuling wrote: > >>> 4,89,24561;NIP: c0048164 LR: c0048160 CTR: >>> 4,90,24576;REGS: c0007e59fb50 TRAP: 0700 Tainted: GW

Re: [PATCH v3] printk: Have printk() never buffer its data

2012-07-08 Thread Kay Sievers
On Sat, 2012-07-07 at 07:04 +1000, Michael Neuling wrote: > Whole kmsg below. I guess I have an idea now what's going on. > 4,47,0;WARNING: at > /scratch/mikey/src/linux-ozlabs/arch/powerpc/sysdev/xics/xics-common.c:105 > 4,51,0;MSR: 90021032 CR: 2442 XER: 2200 > 4,54,0;TASK =

Re: [PATCH v3] printk: Have printk() never buffer its data

2012-07-09 Thread Kay Sievers
On Mon, Jul 9, 2012 at 11:42 PM, Joe Perches wrote: > On Sun, 2012-07-08 at 19:55 +0200, Kay Sievers wrote: > >> At the same time the CPU#2 prints the same warning with a continuation >> line, but the buffer from CPU#1 can not be flushed to the console, nor >> can the con

Re: [PATCH v3] printk: Have printk() never buffer its data

2012-07-09 Thread Kay Sievers
On Tue, Jul 10, 2012 at 12:29 AM, Joe Perches wrote: > On Tue, 2012-07-10 at 00:10 +0200, Kay Sievers wrote: >> On Mon, Jul 9, 2012 at 11:42 PM, Joe Perches wrote: >> > On Sun, 2012-07-08 at 19:55 +0200, Kay Sievers wrote: >> > >> >> At the same time t

Re: [PATCH v3] printk: Have printk() never buffer its data

2012-07-05 Thread Kay Sievers
On Thu, Jul 5, 2012 at 9:03 AM, Michael Neuling wrote: >> On Mon, 2012-06-25 at 18:40 -0700, Linus Torvalds wrote: >> > I think it might be a great idea to buffer for logging in order to >> > generate one individual buffer record there. >> > >> > But it needs to be printed as it is generated. >>

Re: [PATCH v3] printk: Have printk() never buffer its data

2012-07-05 Thread Kay Sievers
On Thu, Jul 5, 2012 at 10:39 AM, Kay Sievers wrote: > On Thu, Jul 5, 2012 at 9:03 AM, Michael Neuling wrote: >>> On Mon, 2012-06-25 at 18:40 -0700, Linus Torvalds wrote: > >>> > I think it might be a great idea to buffer for logging in order to >>> > gene

Re: [PATCH v3] printk: Have printk() never buffer its data

2012-07-05 Thread Kay Sievers
On Thu, Jul 5, 2012 at 12:20 PM, Michael Neuling wrote: > I can only make 2) happen on SMP. It's when the second CPU is coming up > and it's printing something. The first CPU isn't printing anything at > this stage (there is no garbled console here) so I don't think it's a > race. I see it con

Re: [PATCH v3] printk: Have printk() never buffer its data

2012-07-05 Thread Kay Sievers
On Thu, 2012-07-05 at 13:47 +0200, Kay Sievers wrote: > On Thu, Jul 5, 2012 at 12:20 PM, Michael Neuling wrote: > > > I can only make 2) happen on SMP. It's when the second CPU is coming up > > and it's printing something. The first CPU isn't printing anythi

Re: [PATCH v3] printk: Have printk() never buffer its data

2012-07-05 Thread Kay Sievers
On Fri, Jul 6, 2012 at 2:41 AM, Michael Neuling wrote: >> > Does this happen only very early during bootup, or also later when the >> > box fully initialized? > > I'm seeing during boot but not later (xmon (ppc kernel debugger) doesn't > see it if I do 'echo x > /proc/sysrq-trigger') . I wouldn'

Re: [PATCH 0/8] v2 De-Couple sysfs memory directories from memory sections

2010-09-29 Thread Kay Sievers
On Wed, Sep 29, 2010 at 14:37, Greg KH wrote: > On Wed, Sep 29, 2010 at 10:32:34AM +0200, Avi Kivity wrote: >>  On 09/29/2010 04:50 AM, Greg KH wrote: >>> > >>> >  Because the old ABI creates 129,000+ entries inside >>> >  /sys/devices/system/memory with their associated links from >>> >  /sys/dev

BUS_ID_SIZE is going away

2009-03-28 Thread Kay Sievers
Hey, care to replace: bus_id[BUS_ID_SIZE]; in: include/linux/fsl_devices.h with a locally defined limit, or whatever fits your needs? Or let me know how you like it to be converted, and I can make a patch, and we can push it through the driver-core tree. The driver core and kobjects have no lo

Re: [i2c] [PATCH] update module-init-tools to support the i2c subsystem

2008-01-14 Thread Kay Sievers
On Jan 14, 2008 6:50 PM, Jean Delvare <[EMAIL PROTECTED]> wrote: > On Mon, 14 Jan 2008 18:08:16 +0100 (CET), Geert Uytterhoeven wrote: > > On Mon, 14 Jan 2008, Jean Delvare wrote: > > > I thought that the module aliases were generated by > > > scripts/mod/modpost? As a matter of fact, I did not app

Re: Fix Firmware class name collision

2007-12-15 Thread Kay Sievers
On Fri, 2007-12-14 at 22:39 -0800, Greg KH wrote: > On Sat, Dec 15, 2007 at 05:14:29PM +1100, Benjamin Herrenschmidt wrote: > > > > On Fri, 2007-12-14 at 14:40 -0800, Greg KH wrote: > > > On Tue, Dec 04, 2007 at 07:28:00PM -0600, Timur Tabi wrote: > > > > Scott Wood wrote: > > > > > > > >> The phy

Re: [PATCH 1/2] i2c: Add support for device alias names

2008-04-28 Thread Kay Sievers
driver binding scheme (driver_name/type) is still > supported. > > Signed-off-by: Jean Delvare <[EMAIL PROTECTED]> > Cc: Jochen Friedrich <[EMAIL PROTECTED]> > Cc: Jon Smirl <[EMAIL PROTECTED]> > Cc: Kay Sievers <[EMAIL PROTECTED]> > --- > One thi

Re: [PATCH 1/2] i2c: Add support for device alias names

2008-04-28 Thread Kay Sievers
On Mon, 2008-04-28 at 17:40 +0200, Jean Delvare wrote: > On Mon, 28 Apr 2008 17:07:25 +0200, Kay Sievers wrote: > > On Mon, 2008-04-28 at 11:39 +0200, Jean Delvare wrote: > > > One thing I am still not happy with is that the aliases created have a > > > trailing "

Re: [PATCH 1/2] i2c: Add support for device alias names

2008-05-01 Thread Kay Sievers
On Thu, 2008-05-01 at 10:04 +0200, Jean Delvare wrote: > On Mon, 28 Apr 2008 18:16:17 +0200, Kay Sievers wrote: > > On Mon, 2008-04-28 at 17:40 +0200, Jean Delvare wrote: > > > Why would i2c device modaliases ever contain multiple strings? A device > > > can&#x