Re: 2.6.24-rc8-mm1 Kernel oops will running kernbench

[Kamalesh Babulal]

Paul Mackerras wrote:
> Andrew Morton writes:
> 
>> On Fri, 18 Jan 2008 14:06:00 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> 
>> wrote:
>>
>>> Hi Andrew,
>>>
>>> Following oops was seen while running kernbench on one of test machine
>>> (power4+ box). I tried reproducing the oops but was unsuccessful. 
>>> I will try to reproduce the oops with debug info compiled.
>>>
>>>
>>> Oops: Kernel access of bad area, sig: 11 [#1]
>>> SMP NR_CPUS=32 NUMA pSeries
>>> Modules linked in:
>>> NIP: 4570 LR: 0fc42dc0 CTR: 
>>> REGS: c0077b6bf8c0 TRAP: 0300   Not tainted  (2.6.24-rc8-mm1-autotest)
>>> MSR: 80001000   CR: 28022422  XER: 
>>> DAR: c0077b6bfce0, DSISR: 0a00
>>> TASK = c00773164c40[19588] 'as' THREAD: c0077b6bc000 CPU: 1
>>> GPR00: 4000 c0077b6bfb40 7346 d032 
>>> GPR04: 043a  000c 0004 
>>> GPR08: 0fd278c8 48022424 c0077b6bfe30 998be2321500 
>>> GPR12: 80001030 c05f6280 1003 1003 
>>> GPR16: 1003 1005 1006aac0 10053cd0 
>>> GPR20:  0fe0 1005 1005 
>>> GPR24: 0ff8 0fe8 0062 0fd27490 
>>> GPR28: 0fd274c8 10099420 0fd25ff4 1009a400 
>>> NIP [4570] 0x4570
>>> LR [0fc42dc0] 0xfc42dc0
>>> Call Trace:
>>> [c0077b6bfb40] [c0077b292000] 0xc0077b292000 (unreliable)
>>> Instruction dump:
>>> 4800    41820008    
>>> 4810    f92101a0    
>>>
>> odd.  Where did the stack trace go?

Only this much was captured in the serial console.
> 
> It's there, it's just really really short (one line).  The link
> register is in userspace and the stack pointer looks to be right at
> the top of a kernel stack area.
> 
> The trap was a data access exception which is very odd given that the
> machine is in real mode (MMU off) with the pc at 0x4570.  Actually it
> looks like the machine probably got a data access exception somewhere
> (probably in userspace, probably a page fault or similar) and then got
> another exception before it had finished saving the state from the
> first exception.
> 
> Kamalesh, do you still have the vmlinux?  If so could you disassemble
> the area from say 0x4500 to 0x4600, and find out what is the closest
> symbol before 0xc0004570 from System.map, and show us those?
> 
> Paul.
> --
I tried reproducing the problem and was successful with following trace
in which the pc is at 0x4570 as the above one

 Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=32 NUMA pSeries
Modules linked in:
NIP: 4570 LR: 0ff0288c CTR: 0ff013e0
REGS: c0077e61f8c0 TRAP: 0300   Not tainted  (2.6.24-rc8-mm1-autotest)
MSR: 80001000   CR: 28000422  XER: 
DAR: c0077e61fce0, DSISR: 0a00
TASK = c0077207f880[23480] 'cc1' THREAD: c0077e61c000 CPU: 3
GPR00: 4000 c0077e61fb40 0088 d032 
GPR04: 0088 030c fefefeff 7f7f7f7f 
GPR08: 8000 44000428 c0077e61fe30 998be2321500 
GPR12: 80001030 c05f6680 1003 1003 
GPR16: 105b 105b 1044 105b 
GPR20: 105b 105b 105b 105b 
GPR24: 105b 105b 105b ffa11b24 
GPR28:   0ffebff4 0ffec408 
NIP [4570] 0x4570
LR [0ff0288c] 0xff0288c
Call Trace:
[c0077e61fb40] [c0077e61fcf0] 0xc0077e61fcf0 (unreliable)
[c0077e61fbd0] [1044] 0x1044
Instruction dump:
4800    41820008    
4810    f92101a0    

The disassembled vmlinux from 0x4500 to 0x4600 

c0004500:   f9 4d 01 68 std r10,360(r13)
c0004504:   48 02 89 f9 bl  c002cefc 
<.slb_allocate_realmode>
c0004508:   e9 4d 01 68 ld  r10,360(r13)
c000450c:   e8 6d 01 60 ld  r3,352(r13)
c0004510:   81 2d 01 5c lwz r9,348(r13)
c0004514:   7d 48 03 a6 mtlrr10
c0004518:   71 8a 00 02

Re: 2.6.24-rc8-mm1 Kernel oops will running kernbench

[Kamalesh Babulal]

Hi Andrew,

Following oops was seen while running kernbench on one of test machine
(power4+ box). I tried reproducing the oops but was unsuccessful. 
I will try to reproduce the oops with debug info compiled.


Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=32 NUMA pSeries
Modules linked in:
NIP: 4570 LR: 0fc42dc0 CTR: 
REGS: c0077b6bf8c0 TRAP: 0300   Not tainted  (2.6.24-rc8-mm1-autotest)
MSR: 80001000   CR: 28022422  XER: 
DAR: c0077b6bfce0, DSISR: 0a00
TASK = c00773164c40[19588] 'as' THREAD: c0077b6bc000 CPU: 1
GPR00: 4000 c0077b6bfb40 7346 d032 
GPR04: 043a  000c 0004 
GPR08: 0fd278c8 48022424 c0077b6bfe30 998be2321500 
GPR12: 80001030 c05f6280 1003 1003 
GPR16: 1003 1005 1006aac0 10053cd0 
GPR20:  0fe0 1005 1005 
GPR24: 0ff8 0fe8 0062 0fd27490 
GPR28: 0fd274c8 10099420 0fd25ff4 1009a400 
NIP [4570] 0x4570
LR [0fc42dc0] 0xfc42dc0
Call Trace:
[c0077b6bfb40] [c0077b292000] 0xc0077b292000 (unreliable)
Instruction dump:
4800    41820008    
4810    f92101a0    

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc8-mm1 Kernel oops will running kernbench

[Kamalesh Babulal]

Hi Andrew,

Following oops was seen while running kernbench on one of test machine
(power4+ box). I tried reproducing the oops but was unsuccessful. 
I will try to reproduce the oops with debug info compiled.


Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=32 NUMA pSeries
Modules linked in:
NIP: 4570 LR: 0fc42dc0 CTR: 
REGS: c0077b6bf8c0 TRAP: 0300   Not tainted  (2.6.24-rc8-mm1-autotest)
MSR: 80001000 ME  CR: 28022422  XER: 
DAR: c0077b6bfce0, DSISR: 0a00
TASK = c00773164c40[19588] 'as' THREAD: c0077b6bc000 CPU: 1
GPR00: 4000 c0077b6bfb40 7346 d032 
GPR04: 043a  000c 0004 
GPR08: 0fd278c8 48022424 c0077b6bfe30 998be2321500 
GPR12: 80001030 c05f6280 1003 1003 
GPR16: 1003 1005 1006aac0 10053cd0 
GPR20:  0fe0 1005 1005 
GPR24: 0ff8 0fe8 0062 0fd27490 
GPR28: 0fd274c8 10099420 0fd25ff4 1009a400 
NIP [4570] 0x4570
LR [0fc42dc0] 0xfc42dc0
Call Trace:
[c0077b6bfb40] [c0077b292000] 0xc0077b292000 (unreliable)
Instruction dump:
4800    41820008    
4810    f92101a0    

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc8-mm1 Kernel oops will running kernbench

[Kamalesh Babulal]

Paul Mackerras wrote:
 Andrew Morton writes:
 
 On Fri, 18 Jan 2008 14:06:00 +0530 Kamalesh Babulal [EMAIL PROTECTED] 
 wrote:

 Hi Andrew,

 Following oops was seen while running kernbench on one of test machine
 (power4+ box). I tried reproducing the oops but was unsuccessful. 
 I will try to reproduce the oops with debug info compiled.


 Oops: Kernel access of bad area, sig: 11 [#1]
 SMP NR_CPUS=32 NUMA pSeries
 Modules linked in:
 NIP: 4570 LR: 0fc42dc0 CTR: 
 REGS: c0077b6bf8c0 TRAP: 0300   Not tainted  (2.6.24-rc8-mm1-autotest)
 MSR: 80001000 ME  CR: 28022422  XER: 
 DAR: c0077b6bfce0, DSISR: 0a00
 TASK = c00773164c40[19588] 'as' THREAD: c0077b6bc000 CPU: 1
 GPR00: 4000 c0077b6bfb40 7346 d032 
 GPR04: 043a  000c 0004 
 GPR08: 0fd278c8 48022424 c0077b6bfe30 998be2321500 
 GPR12: 80001030 c05f6280 1003 1003 
 GPR16: 1003 1005 1006aac0 10053cd0 
 GPR20:  0fe0 1005 1005 
 GPR24: 0ff8 0fe8 0062 0fd27490 
 GPR28: 0fd274c8 10099420 0fd25ff4 1009a400 
 NIP [4570] 0x4570
 LR [0fc42dc0] 0xfc42dc0
 Call Trace:
 [c0077b6bfb40] [c0077b292000] 0xc0077b292000 (unreliable)
 Instruction dump:
 4800    41820008    
 4810    f92101a0    

 odd.  Where did the stack trace go?

Only this much was captured in the serial console.
 
 It's there, it's just really really short (one line).  The link
 register is in userspace and the stack pointer looks to be right at
 the top of a kernel stack area.
 
 The trap was a data access exception which is very odd given that the
 machine is in real mode (MMU off) with the pc at 0x4570.  Actually it
 looks like the machine probably got a data access exception somewhere
 (probably in userspace, probably a page fault or similar) and then got
 another exception before it had finished saving the state from the
 first exception.
 
 Kamalesh, do you still have the vmlinux?  If so could you disassemble
 the area from say 0x4500 to 0x4600, and find out what is the closest
 symbol before 0xc0004570 from System.map, and show us those?
 
 Paul.
 --
I tried reproducing the problem and was successful with following trace
in which the pc is at 0x4570 as the above one

 Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=32 NUMA pSeries
Modules linked in:
NIP: 4570 LR: 0ff0288c CTR: 0ff013e0
REGS: c0077e61f8c0 TRAP: 0300   Not tainted  (2.6.24-rc8-mm1-autotest)
MSR: 80001000 ME  CR: 28000422  XER: 
DAR: c0077e61fce0, DSISR: 0a00
TASK = c0077207f880[23480] 'cc1' THREAD: c0077e61c000 CPU: 3
GPR00: 4000 c0077e61fb40 0088 d032 
GPR04: 0088 030c fefefeff 7f7f7f7f 
GPR08: 8000 44000428 c0077e61fe30 998be2321500 
GPR12: 80001030 c05f6680 1003 1003 
GPR16: 105b 105b 1044 105b 
GPR20: 105b 105b 105b 105b 
GPR24: 105b 105b 105b ffa11b24 
GPR28:   0ffebff4 0ffec408 
NIP [4570] 0x4570
LR [0ff0288c] 0xff0288c
Call Trace:
[c0077e61fb40] [c0077e61fcf0] 0xc0077e61fcf0 (unreliable)
[c0077e61fbd0] [1044] 0x1044
Instruction dump:
4800    41820008    
4810    f92101a0    

The disassembled vmlinux from 0x4500 to 0x4600 

c0004500:   f9 4d 01 68 std r10,360(r13)
c0004504:   48 02 89 f9 bl  c002cefc 
.slb_allocate_realmode
c0004508:   e9 4d 01 68 ld  r10,360(r13)
c000450c:   e8 6d 01 60 ld  r3,352(r13)
c0004510:   81 2d 01 5c lwz r9,348(r13)
c0004514:   7d 48 03 a6 mtlrr10
c0004518:   71 8a 00 02 andi.   r10,r12,2
c000451c:   41 82 00 28 beq-c0004544 unrecov_slb
c0004520:   7d 38 01 20 mtocrf  128,r9  
c0004524:   7d 30 11 20 mtocrf  1,r9
c0004528:   e9 2d 01 20 ld  r9,288(r13)
c000452c:   e9 4d 01 28 ld  r10,296(r13)
c0004530:   e9 6d 01 30 ld  r11,304(r13)
c0004534:   e9 8d 01 38 ld  r12,312(r13)
c0004538:   e9 ad 01 40 ld

Re: 2.6.24-rc8-mm1 Kernel oops will running kernbench

[Kamalesh Babulal]

Paul Mackerras wrote:
 Kamalesh Babulal writes:
 
 NIP: 4570 LR: 0fc42dc0 CTR: 
 REGS: c0077b6bf8c0 TRAP: 0300   Not tainted  (2.6.24-rc8-mm1-autotest)
 MSR: 80001000 ME  CR: 28022422  XER: 
 DAR: c0077b6bfce0, DSISR: 0a00
 
 Actually, how much RAM does this machine have?  If it has less than
 32GB, then the problem is that the kernel stack pointer is bogus.
 (How it got to be bogus is the interesting question, of course. :)
 
 Paul.
 
Hi Paul,

The machine has around 30GB of RAM, do you want me to try, by taking 
the git-powerpc.patch out of the series and try reproducing the oops.

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] SCSI: fix isa/pcmcia compile problem

[Kamalesh Babulal]

On Fri, Jan 18, 2008 at 04:20:40PM +0900, Tejun Heo wrote:
> aha152x.c and fdomain are built twice - once for the isa driver and
> once for the PCMCIA one.  Through #ifdefs, the compiled codes are
> slightly different; thus, global symbols need to be given different
> names depending on which flavor is being built.  This patch adds
> GLOBAL() macro to aha152x.h and fdomain.h which change the symbol
> depending on PCMCIA.
> 
> This bug has always existed but has been masked by the fact the
> drivers/scsi/pcmcia used subdir-(y|m) instead of obj-(y|m) which made
> drivers/scsi/pcmcia/built_in.o not linked into the kernel and thus
> avoided the duplicate symbols during compilation.
> 
Hi Tejun Heo,

Thanks, I have tested the patch, it fixes both build failures.

Tested-by: Kamalesh Babulal <[EMAIL PROTECTED]>
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
---
Ah... missed that one.  Here's the updated version.

 drivers/scsi/aha152x.c |   12 ++--
 drivers/scsi/aha152x.h |   20 +---
 drivers/scsi/fdomain.c |   20 ++--
 drivers/scsi/fdomain.h |   21 +
 drivers/scsi/pcmcia/aha152x_stub.c |   10 ++
 drivers/scsi/pcmcia/fdomain_stub.c |   10 ++
 6 files changed, 62 insertions(+), 31 deletions(-)

diff --git a/drivers/scsi/aha152x.c b/drivers/scsi/aha152x.c
index ea8c699..0204f44 100644
--- a/drivers/scsi/aha152x.c
+++ b/drivers/scsi/aha152x.c
@@ -769,7 +769,7 @@ static irqreturn_t swintr(int irqno, void *dev_id)
return IRQ_HANDLED;
 }

-struct Scsi_Host *aha152x_probe_one(struct aha152x_setup *setup)
+struct Scsi_Host *GLOBAL(aha152x_probe_one)(struct aha152x_setup *setup)
 {
struct Scsi_Host *shpnt;

@@ -905,7 +905,7 @@ out_host_put:
return NULL;
 }

-void aha152x_release(struct Scsi_Host *shpnt)
+void GLOBAL(aha152x_release)(struct Scsi_Host *shpnt)
 {
if (!shpnt)
return;
@@ -1327,7 +1327,7 @@ static void reset_ports(struct Scsi_Host *shpnt)
  * Reset the host (bus and controller)
  *
  */
-int aha152x_host_reset_host(struct Scsi_Host *shpnt)
+int GLOBAL(aha152x_host_reset_host)(struct Scsi_Host *shpnt)
 {
DPRINTK(debug_eh, KERN_DEBUG "scsi%d: host reset\n", shpnt->host_no);

@@ -1345,7 +1345,7 @@ int aha152x_host_reset_host(struct Scsi_Host *shpnt)
  */
 static int aha152x_host_reset(Scsi_Cmnd *SCpnt)
 {
-   return aha152x_host_reset_host(SCpnt->device->host);
+   return GLOBAL(aha152x_host_reset_host)(SCpnt->device->host);
 }

 /*
@@ -3916,7 +3916,7 @@ static int __init aha152x_init(void)

for (i=0; i
-#include "aha152x.h"

 #include 
 #include 
 #include 
 #include 

+#define PCMCIA 1
+#include "aha152x.h"
+
 #ifdef PCMCIA_DEBUG
 static int pc_debug = PCMCIA_DEBUG;
 module_param(pc_debug, int, 0644);
@@ -194,7 +196,7 @@ static int aha152x_config_cs(struct pcmcia_device *link)
 if (ext_trans)
 s.ext_trans = ext_trans;

-host = aha152x_probe_one();
+host = GLOBAL(aha152x_probe_one)();
 if (host == NULL) {
printk(KERN_INFO "aha152x_cs: no SCSI devices found\n");
goto cs_failed;
@@ -216,7 +218,7 @@ static void aha152x_release_cs(struct pcmcia_device *link)
 {
scsi_info_t *info = link->priv;

-   aha152x_release(info->host);
+   GLOBAL(aha152x_release)(info->host);
pcmcia_disable_device(link);
 }

@@ -224,7 +226,7 @@ static int aha152x_resume(struct pcmcia_device *link)
 {
scsi_info_t *info = link->priv;

-   aha152x_host_reset_host(info->host);
+   GLOBAL(aha152x_host_reset_host)(info->host);

return 0;
 }
diff --git a/drivers/scsi/pcmcia/fdomain_stub.c 
b/drivers/scsi/pcmcia/fdomain_stub.c
index 4b82b20..b075576 100644
--- a/drivers/scsi/pcmcia/fdomain_stub.c
+++ b/drivers/scsi/pcmcia/fdomain_stub.c
@@ -44,13 +44,15 @@

 #include "scsi.h"
 #include 
-#include "fdomain.h"

 #include 
 #include 
 #include 
 #include 

+#define PCMCIA 1
+#include "fdomain.h"
+
 /**/

 /* Module parameters */
@@ -161,9 +163,9 @@ static int fdomain_config(struct pcmcia_device *link)

 /* Set configuration options for the fdomain driver */
 sprintf(str, "%d,%d", link->io.BasePort1, link->irq.AssignedIRQ);
-fdomain_setup(str);
+GLOBAL(fdomain_setup)(str);

-host = __fdomain_16x0_detect(_driver_template);
+host = GLOBAL(__fdomain_16x0_detect)((fdomain_driver_template));
 if (!host) {
 printk(KERN_INFO "fdomain_cs: no SCSI devices found\n");
goto cs_failed;
@@ -202,7 +204,7 @@ static void fdomain_release(struct pcmcia_device *link)

 static int fdomain_resume(struct pcmcia_device *link)
 {
-   fdomain_16x0_bus_reset(NULL);
+   GLOBAL(fdomain_16x0_bus_reset)(NULL);

 

Re: 2.6.24-rc8-mm1 build failure on headers_check

[Kamalesh Babulal]

Hi Andrew,

The kernel build fails during the headers_check on power box

  CHECK   include/asm/nvram.h
/usr/local/autobench/autotest/tmp/build/linux/usr/include/asm/nvram.h requires 
linux/list.h, which does not exist in exported headers
make[3]: *** 
[/usr/local/autobench/autotest/tmp/build/linux/usr/include/asm/.check.nvram.h] 
Error 1
make[2]: *** [asm-powerpc] Error 2
make[1]: *** [headers_check] Error 2
make: *** [vmlinux] Error 2

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc8-mm1 Build Failure on scsi driver

[Kamalesh Babulal]

Andrew Morton wrote:
> On Thu, 17 Jan 2008 21:45:39 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> 
>> Hi Andrew,
>>
>> The kernel build fails with following error
>>
>> drivers/scsi/aha152x.o: In function `aha152x_host_reset_host':
>> /home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:1324: multiple 
>> definition of `aha152x_host_reset_host'
>> drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:1324:
>>  first defined here
>> drivers/scsi/aha152x.o: In function `aha152x_release':
>> /home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:908: multiple 
>> definition of `aha152x_release'
>> drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:908:
>>  first defined here
>> ld: Warning: size of symbol `aha152x_release' changed from 68 in 
>> drivers/scsi/pcmcia/built-in.o to 100 in drivers/scsi/aha152x.o
>> drivers/scsi/aha152x.o: In function `aha152x_probe_one':
> 
> Neat.  Seems that the scsi build system is linking together two copies of
> drivers/scsi/aha152x.o.  One via drivers/scsi/aha152x.o directly and the
> other via drivers/scsi/pcmcia/built-in.o.
> 
> Please send the .config.
> 
> I'm looking suspiciously at this, from git-scsi-misc:
> 
> commit 8ae732a91df051aba6820068a47b631a06599d84
> Author: Tejun Heo <[EMAIL PROTECTED]>
> Date:   Fri Dec 7 22:36:23 2007 +0900
> 
> [SCSI] make pcmcia directory use obj-y|m instead of subdir-y|m
> 
> subdir-y|m isn't supposed to contain modules or built-in components.
> Change subdir-$(CONFIG_PCMCIA) to obj-$(CONFIG_PCMCIA).
> 
> Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
> Acked-by: Sam Ravnborg <[EMAIL PROTECTED]>
> Signed-off-by: James Bottomley <[EMAIL PROTECTED]>
> 
> diff --git a/drivers/scsi/Makefile b/drivers/scsi/Makefile
> index b5441f5..93e1428 100644
> --- a/drivers/scsi/Makefile
> +++ b/drivers/scsi/Makefile
> @@ -17,7 +17,7 @@
>  CFLAGS_aha152x.o =   -DAHA152X_STAT -DAUTOCONF
>  CFLAGS_gdth.o= # -DDEBUG_GDTH=2 -D__SERIAL__ -D__COM2__ -DGDTH_STATISTICS
> 
> -subdir-$(CONFIG_PCMCIA)  += pcmcia
> +obj-$(CONFIG_PCMCIA) += pcmcia/
> 
>  obj-$(CONFIG_SCSI)   += scsi_mod.o
>  obj-$(CONFIG_SCSI_TGT)   += scsi_tgt.o

Hi Andrew,

Patch from Tejun Heo fixes the aha152x.c build failure, and following second 
part
of the build failure, is still occurring.

drivers/scsi/fdomain.o:(.data+0x0): multiple definition of 
`fdomain_driver_template'
drivers/scsi/pcmcia/built-in.o:(.data+0x5a0): first defined here
drivers/scsi/fdomain.o: In function `fdomain_16x0_bus_reset':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:1568: multiple 
definition of `fdomain_16x0_bus_reset'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:1568:
 first defined here
drivers/scsi/fdomain.o: In function `__fdomain_16x0_detect':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:894: multiple 
definition of `__fdomain_16x0_detect'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:894:
 first defined here
ld: Warning: size of symbol `__fdomain_16x0_detect' changed from 1206 in 
drivers/scsi/pcmcia/built-in.o to 1700 in drivers/scsi/fdomain.o
drivers/scsi/fdomain.o: In function `fdomain_setup':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:554: multiple 
definition of `fdomain_setup'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:554:
 first defined here
make[2]: *** [drivers/scsi/built-in.o] Error 1
make[1]: *** [drivers/scsi] Error 2
make: *** [drivers] Error 2

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] aha152x: fix isa/pcmcia compile problem

[Kamalesh Babulal]

c_debug = PCMCIA_DEBUG;
>  module_param(pc_debug, int, 0644);
> @@ -194,7 +196,7 @@ static int aha152x_config_cs(struct pcmcia_device *link)
>  if (ext_trans)
>  s.ext_trans = ext_trans;
> 
> -host = aha152x_probe_one();
> +host = GLOBAL(aha152x_probe_one)();
>  if (host == NULL) {
>   printk(KERN_INFO "aha152x_cs: no SCSI devices found\n");
>   goto cs_failed;
> @@ -216,7 +218,7 @@ static void aha152x_release_cs(struct pcmcia_device *link)
>  {
>   scsi_info_t *info = link->priv;
> 
> - aha152x_release(info->host);
> + GLOBAL(aha152x_release)(info->host);
>   pcmcia_disable_device(link);
>  }
> 
> @@ -224,7 +226,7 @@ static int aha152x_resume(struct pcmcia_device *link)
>  {
>   scsi_info_t *info = link->priv;
> 
> - aha152x_host_reset_host(info->host);
> + GLOBAL(aha152x_host_reset_host)(info->host);
> 
>   return 0;
>  }
> diff --git a/fs/sysfs/dir.c b/fs/sysfs/dir.c
> --
Hi Tejun Heo,

Thanks, I have tested the patch fixes the build failure on aha152x.c.
Tested-By: Kamalesh Babulal <[EMAIL PROTECTED]>

Thanks & Regards,
Kamalesh Babulal.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc8-mm1 Build Failure at scripts/mkubooting/crc32.c

[Kamalesh Babulal]

Hi Andrew,

The kernel build fails with following error message

scripts/mkubootimg/crc32.c:15:18: error: zlib.h: No such file or directory
scripts/mkubootimg/crc32.c:77: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before 'crc_table'
scripts/mkubootimg/crc32.c:153: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before 'crc32'
make[2]: *** [scripts/mkubootimg/crc32.o] Error 1
make[1]: *** [scripts/mkubootimg] Error 2
make: *** [scripts] Error 2

The patch causing this build failure may be git-kbuild.patch.

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc8-mm1 Build Failure on scsi driver

[Kamalesh Babulal]

Hi Andrew,

The kernel build fails with following error

drivers/scsi/aha152x.o: In function `aha152x_host_reset_host':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:1324: multiple 
definition of `aha152x_host_reset_host'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:1324:
 first defined here
drivers/scsi/aha152x.o: In function `aha152x_release':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:908: multiple 
definition of `aha152x_release'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:908:
 first defined here
ld: Warning: size of symbol `aha152x_release' changed from 68 in 
drivers/scsi/pcmcia/built-in.o to 100 in drivers/scsi/aha152x.o
drivers/scsi/aha152x.o: In function `aha152x_probe_one':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:772: multiple 
definition of `aha152x_probe_one'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:772:
 first defined here
drivers/scsi/fdomain.o:(.data+0x0): multiple definition of 
`fdomain_driver_template'
drivers/scsi/pcmcia/built-in.o:(.data+0x5a0): first defined here
drivers/scsi/fdomain.o: In function `fdomain_16x0_bus_reset':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:1568: multiple 
definition of `fdomain_16x0_bus_reset'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:1568:
 first defined here
drivers/scsi/fdomain.o: In function `__fdomain_16x0_detect':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:894: multiple 
definition of `__fdomain_16x0_detect'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:894:
 first defined here
ld: Warning: size of symbol `__fdomain_16x0_detect' changed from 1206 in 
drivers/scsi/pcmcia/built-in.o to 1700 in drivers/scsi/fdomain.o
drivers/scsi/fdomain.o: In function `fdomain_setup':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:554: multiple 
definition of `fdomain_setup'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:554:
 first defined here
make[2]: *** [drivers/scsi/built-in.o] Error 1
make[1]: *** [drivers/scsi] Error 2
make: *** [drivers] Error 2


-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc8-mm1 kernel panic while bootup

[Kamalesh Babulal]

Hi Andrew,

The 2.6.24-rc8-mm1 kernel panic while bootup with bootup message

Dual Core AMD Opteron(tm) Processor 270 stepping 02
Unable to handle kernel paging request at 4a78 RIP: 
 [] __alloc_pages+0x40/0x31e
PGD 0 
Oops:  [1] SMP 
last sysfs file: 
CPU 0 
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.24-rc8-mm1-autotest #1
RIP: 0010:[]  [] __alloc_pages+0x40/0x31e
RSP: :81003f9b9c60  EFLAGS: 00010246
RAX:  RBX:  RCX: 0002
RDX: 4a70 RSI: 0605 RDI: 805a6f66
RBP: 00d0 R08: 003808c0 R09: 0003db89
R10: e2fe6880 R11: 806287b0 R12: 4a70
R13:  R14: 0286 R15: 81003f9b6000
FS:  () GS:80664000() knlGS:
CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
CR2: 4a78 CR3: 00201000 CR4: 06e0
DR0:  DR1:  DR2: 
DR3:  DR6: 0ff0 DR7: 0400
Process swapper (pid: 1, threadinfo 81003f9b8000, task 81003f9b6000)
Stack:  c0d0 0010 8027574f 8100e5c8
 c0d0 8026f320 81003f9b9c88 
  807fac90 807fac90 0286
Call Trace:
 [] ? zone_statistics+0x3f/0x97
 [] ? get_page_from_freelist+0x463/0x5b5
 [] ? new_slab+0x10e/0x261
 [] ? get_new_slab+0x20/0xaa
 [] ? __slab_alloc+0x123/0x182
 [] ? process_zones+0x79/0x15e
 [] ? kmem_cache_alloc_node+0x3c/0x70
 [] ? process_zones+0x79/0x15e
 [] ? _spin_lock_irqsave+0x9/0xe
 [] ? pageset_cpuup_callback+0x33/0x91
 [] ? notifier_call_chain+0x29/0x56
 [] ? _cpu_up+0x68/0x101
 [] ? cpu_up+0x54/0x61
 [] ? kernel_init+0xbf/0x2ef
 [] ? _spin_unlock_irq+0x9/0xc
 [] ? child_rip+0xa/0x12
 [] ? kernel_init+0x0/0x2ef
 [] ? child_rip+0x0/0x12


Code: 83 ec 38 65 4c 8b 3c 25 00 00 00 00 83 e0 10 89 44 24 0c 74 16 be 05 06 
00 00 48 c7 c7 66 6f 5a 80 e8 a9 f4 fb ff e8 20 05 28 00 <49> 83 7c 24 08 00 49 
8d 44 24 08 48 89 44 24 18 75 1a 48 c7 44 
RIP  [] __alloc_pages+0x40/0x31e
 RSP 
CR2: 4a78

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc8-mm1

[Kamalesh Babulal]

Hi Andrew,

The kernel build fails with following error

arch/x86/kernel/mpparse_32.c: In function `smp_read_mpc_oem':
arch/x86/kernel/mpparse_32.c:318: error: `oemtable' undeclared (first use in 
this function)
arch/x86/kernel/mpparse_32.c:318: error: (Each undeclared identifier is 
reported only once
arch/x86/kernel/mpparse_32.c:318: error: for each function it appears in.)
arch/x86/kernel/mpparse_32.c:332: error: `mpc_phys' undeclared (first use in 
this function)


This patch is build tested only.


Signed-off-by: Kamalesh Babulal <[EMAIL PROTECTED]>
---
--- linux-2.6.24-rc8/arch/x86/kernel/mpparse_32.c   2008-01-17 
18:02:45.0 +0530
+++ linux-2.6.24-rc8/arch/x86/kernel/~mpparse_32.c  2008-01-17 
18:17:29.0 +0530
@@ -32,6 +32,7 @@
 #include 
 #include 
 #include 
+#include 
 
 /* Have we found an MP table */
 int smp_found_config;
@@ -329,7 +330,7 @@ static void __init smp_read_mpc_oem(unsi
oem_length = oemtable->oem_length;
/* Unmap header and map full base table */
early_iounmap(oemtable, sizeof(struct mp_config_oemtable));
-   oemtable = (struct mp_config_oemtable *)early_ioremap(mpc_phys,
+   oemtable = (struct mp_config_oemtable *)early_ioremap(oemtable_phys,
oem_length);
if (!oemtable) {
printk("MPTABLE: full oemtable map error!\n");
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc8-mm1 Build Failure on S390x

[Kamalesh Babulal]

 of 'dump_fcp_attrs'
arch/s390/kernel/ipl.c:675: error: previous definition of 'dump_fcp_attrs' was 
here
arch/s390/kernel/ipl.c:1078: error: redefinition of 'dump_fcp_attr_group'
arch/s390/kernel/ipl.c:684: error: previous definition of 'dump_fcp_attr_group' 
was here
arch/s390/kernel/ipl.c:1085: error: redefinition of 'sys_dump_ccw_device_show'
arch/s390/kernel/ipl.c:691: error: previous definition of 
'sys_dump_ccw_device_show' was here
arch/s390/kernel/ipl.c:1085: error: redefinition of 'sys_dump_ccw_device_store'
arch/s390/kernel/ipl.c:691: error: previous definition of 
'sys_dump_ccw_device_store' was here
arch/s390/kernel/ipl.c:1085: error: redefinition of 'sys_dump_ccw_device_attr'
arch/s390/kernel/ipl.c:691: error: previous definition of 
'sys_dump_ccw_device_attr' was here
arch/s390/kernel/ipl.c:1088: error: redefinition of 'dump_ccw_attrs'
arch/s390/kernel/ipl.c:694: error: previous definition of 'dump_ccw_attrs' was 
here
arch/s390/kernel/ipl.c:1093: error: redefinition of 'dump_ccw_attr_group'
arch/s390/kernel/ipl.c:699: error: previous definition of 'dump_ccw_attr_group' 
was here
arch/s390/kernel/ipl.c:1101: error: redefinition of 'dump_set_type'
arch/s390/kernel/ipl.c:707: error: previous definition of 'dump_set_type' was 
here
arch/s390/kernel/ipl.c:1124: error: conflicting types for 'dump_type_show'
arch/s390/kernel/ipl.c:731: error: previous definition of 'dump_type_show' was 
here
arch/s390/kernel/ipl.c:1130: error: conflicting types for 'dump_type_store'
arch/s390/kernel/ipl.c:738: error: previous definition of 'dump_type_store' was 
here
arch/s390/kernel/ipl.c:1142: error: variable `dump_type_attr' has initializer 
but incomplete type
arch/s390/kernel/ipl.c:1142: error: conflicting types for 'dump_type_attr'
arch/s390/kernel/ipl.c:750: error: previous definition of 'dump_type_attr' was 
here
arch/s390/kernel/ipl.c:1143: error: unknown field `attr' specified in 
initializer
arch/s390/kernel/ipl.c:1143: error: extra brace group at end of initializer
arch/s390/kernel/ipl.c:1143: error: (near initialization for `dump_type_attr')
arch/s390/kernel/ipl.c:1143: warning: excess elements in struct initializer
arch/s390/kernel/ipl.c:1143: warning: (near initialization for `dump_type_attr')
arch/s390/kernel/ipl.c:1143: error: unknown field `show' specified in 
initializer
arch/s390/kernel/ipl.c:1143: warning: excess elements in struct initializer
arch/s390/kernel/ipl.c:1143: warning: (near initialization for `dump_type_attr')
arch/s390/kernel/ipl.c:1143: error: unknown field `store' specified in 
initializer
arch/s390/kernel/ipl.c:1143: warning: excess elements in struct initializer
arch/s390/kernel/ipl.c:1143: warning: (near initialization for `dump_type_attr')
arch/s390/kernel/ipl.c:1145: error: syntax error before '(' token
arch/s390/kernel/ipl.c: In function `dump_init':
arch/s390/kernel/ipl.c:1233: warning: passing arg 2 of `sysfs_create_file' from 
incompatible pointer type
arch/s390/kernel/ipl.c: In function `shutdown_actions_init':
arch/s390/kernel/ipl.c:1256: warning: passing arg 2 of `sysfs_create_file' from 
incompatible pointer type
arch/s390/kernel/ipl.c:1262: error: `shutdown_on_panic_nb' undeclared (first 
use in this function)
arch/s390/kernel/ipl.c: At top level:
arch/s390/kernel/ipl.c:237: warning: 'get_ipl_type' defined but not used
arch/s390/kernel/ipl.c:477: warning: 'ipl_action' defined but not used
arch/s390/kernel/ipl.c:684: warning: 'dump_fcp_attr_group' defined but not used
arch/s390/kernel/ipl.c:699: warning: 'dump_ccw_attr_group' defined but not used
arch/s390/kernel/ipl.c:750: warning: 'dump_type_attr' defined but not used
arch/s390/kernel/ipl.c:843: warning: 'do_dump' defined but not used
arch/s390/kernel/ipl.c:1049: warning: 'reipl_action' defined but not used
arch/s390/kernel/ipl.c:1148: warning: 'dump_run' defined but not used
make[1]: *** [arch/s390/kernel/ipl.o] Error 1
make[1]: *** Waiting for unfinished jobs

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc8-mm1 Build Failure on S390x

[Kamalesh Babulal]

 of 'dump_fcp_attrs'
arch/s390/kernel/ipl.c:675: error: previous definition of 'dump_fcp_attrs' was 
here
arch/s390/kernel/ipl.c:1078: error: redefinition of 'dump_fcp_attr_group'
arch/s390/kernel/ipl.c:684: error: previous definition of 'dump_fcp_attr_group' 
was here
arch/s390/kernel/ipl.c:1085: error: redefinition of 'sys_dump_ccw_device_show'
arch/s390/kernel/ipl.c:691: error: previous definition of 
'sys_dump_ccw_device_show' was here
arch/s390/kernel/ipl.c:1085: error: redefinition of 'sys_dump_ccw_device_store'
arch/s390/kernel/ipl.c:691: error: previous definition of 
'sys_dump_ccw_device_store' was here
arch/s390/kernel/ipl.c:1085: error: redefinition of 'sys_dump_ccw_device_attr'
arch/s390/kernel/ipl.c:691: error: previous definition of 
'sys_dump_ccw_device_attr' was here
arch/s390/kernel/ipl.c:1088: error: redefinition of 'dump_ccw_attrs'
arch/s390/kernel/ipl.c:694: error: previous definition of 'dump_ccw_attrs' was 
here
arch/s390/kernel/ipl.c:1093: error: redefinition of 'dump_ccw_attr_group'
arch/s390/kernel/ipl.c:699: error: previous definition of 'dump_ccw_attr_group' 
was here
arch/s390/kernel/ipl.c:1101: error: redefinition of 'dump_set_type'
arch/s390/kernel/ipl.c:707: error: previous definition of 'dump_set_type' was 
here
arch/s390/kernel/ipl.c:1124: error: conflicting types for 'dump_type_show'
arch/s390/kernel/ipl.c:731: error: previous definition of 'dump_type_show' was 
here
arch/s390/kernel/ipl.c:1130: error: conflicting types for 'dump_type_store'
arch/s390/kernel/ipl.c:738: error: previous definition of 'dump_type_store' was 
here
arch/s390/kernel/ipl.c:1142: error: variable `dump_type_attr' has initializer 
but incomplete type
arch/s390/kernel/ipl.c:1142: error: conflicting types for 'dump_type_attr'
arch/s390/kernel/ipl.c:750: error: previous definition of 'dump_type_attr' was 
here
arch/s390/kernel/ipl.c:1143: error: unknown field `attr' specified in 
initializer
arch/s390/kernel/ipl.c:1143: error: extra brace group at end of initializer
arch/s390/kernel/ipl.c:1143: error: (near initialization for `dump_type_attr')
arch/s390/kernel/ipl.c:1143: warning: excess elements in struct initializer
arch/s390/kernel/ipl.c:1143: warning: (near initialization for `dump_type_attr')
arch/s390/kernel/ipl.c:1143: error: unknown field `show' specified in 
initializer
arch/s390/kernel/ipl.c:1143: warning: excess elements in struct initializer
arch/s390/kernel/ipl.c:1143: warning: (near initialization for `dump_type_attr')
arch/s390/kernel/ipl.c:1143: error: unknown field `store' specified in 
initializer
arch/s390/kernel/ipl.c:1143: warning: excess elements in struct initializer
arch/s390/kernel/ipl.c:1143: warning: (near initialization for `dump_type_attr')
arch/s390/kernel/ipl.c:1145: error: syntax error before '(' token
arch/s390/kernel/ipl.c: In function `dump_init':
arch/s390/kernel/ipl.c:1233: warning: passing arg 2 of `sysfs_create_file' from 
incompatible pointer type
arch/s390/kernel/ipl.c: In function `shutdown_actions_init':
arch/s390/kernel/ipl.c:1256: warning: passing arg 2 of `sysfs_create_file' from 
incompatible pointer type
arch/s390/kernel/ipl.c:1262: error: `shutdown_on_panic_nb' undeclared (first 
use in this function)
arch/s390/kernel/ipl.c: At top level:
arch/s390/kernel/ipl.c:237: warning: 'get_ipl_type' defined but not used
arch/s390/kernel/ipl.c:477: warning: 'ipl_action' defined but not used
arch/s390/kernel/ipl.c:684: warning: 'dump_fcp_attr_group' defined but not used
arch/s390/kernel/ipl.c:699: warning: 'dump_ccw_attr_group' defined but not used
arch/s390/kernel/ipl.c:750: warning: 'dump_type_attr' defined but not used
arch/s390/kernel/ipl.c:843: warning: 'do_dump' defined but not used
arch/s390/kernel/ipl.c:1049: warning: 'reipl_action' defined but not used
arch/s390/kernel/ipl.c:1148: warning: 'dump_run' defined but not used
make[1]: *** [arch/s390/kernel/ipl.o] Error 1
make[1]: *** Waiting for unfinished jobs

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc8-mm1 kernel panic while bootup

[Kamalesh Babulal]

Hi Andrew,

The 2.6.24-rc8-mm1 kernel panic while bootup with bootup message

Dual Core AMD Opteron(tm) Processor 270 stepping 02
Unable to handle kernel paging request at 4a78 RIP: 
 [8026f966] __alloc_pages+0x40/0x31e
PGD 0 
Oops:  [1] SMP 
last sysfs file: 
CPU 0 
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.24-rc8-mm1-autotest #1
RIP: 0010:[8026f966]  [8026f966] __alloc_pages+0x40/0x31e
RSP: :81003f9b9c60  EFLAGS: 00010246
RAX:  RBX:  RCX: 0002
RDX: 4a70 RSI: 0605 RDI: 805a6f66
RBP: 00d0 R08: 003808c0 R09: 0003db89
R10: e2fe6880 R11: 806287b0 R12: 4a70
R13:  R14: 0286 R15: 81003f9b6000
FS:  () GS:80664000() knlGS:
CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
CR2: 4a78 CR3: 00201000 CR4: 06e0
DR0:  DR1:  DR2: 
DR3:  DR6: 0ff0 DR7: 0400
Process swapper (pid: 1, threadinfo 81003f9b8000, task 81003f9b6000)
Stack:  c0d0 0010 8027574f 8100e5c8
 c0d0 8026f320 81003f9b9c88 
  807fac90 807fac90 0286
Call Trace:
 [8027574f] ? zone_statistics+0x3f/0x97
 [8026f320] ? get_page_from_freelist+0x463/0x5b5
 [8028d7b8] ? new_slab+0x10e/0x261
 [8028d92b] ? get_new_slab+0x20/0xaa
 [8028dad8] ? __slab_alloc+0x123/0x182
 [8026e5a1] ? process_zones+0x79/0x15e
 [8028db73] ? kmem_cache_alloc_node+0x3c/0x70
 [8026e5a1] ? process_zones+0x79/0x15e
 [804f15b9] ? _spin_lock_irqsave+0x9/0xe
 [8026e6b9] ? pageset_cpuup_callback+0x33/0x91
 [804f37b9] ? notifier_call_chain+0x29/0x56
 [80254b09] ? _cpu_up+0x68/0x101
 [80254bf6] ? cpu_up+0x54/0x61
 [808a4581] ? kernel_init+0xbf/0x2ef
 [804f15a1] ? _spin_unlock_irq+0x9/0xc
 [8020cc08] ? child_rip+0xa/0x12
 [808a44c2] ? kernel_init+0x0/0x2ef
 [8020cbfe] ? child_rip+0x0/0x12


Code: 83 ec 38 65 4c 8b 3c 25 00 00 00 00 83 e0 10 89 44 24 0c 74 16 be 05 06 
00 00 48 c7 c7 66 6f 5a 80 e8 a9 f4 fb ff e8 20 05 28 00 49 83 7c 24 08 00 49 
8d 44 24 08 48 89 44 24 18 75 1a 48 c7 44 
RIP  [8026f966] __alloc_pages+0x40/0x31e
 RSP 81003f9b9c60
CR2: 4a78

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc8-mm1

[Kamalesh Babulal]

Hi Andrew,

The kernel build fails with following error

arch/x86/kernel/mpparse_32.c: In function `smp_read_mpc_oem':
arch/x86/kernel/mpparse_32.c:318: error: `oemtable' undeclared (first use in 
this function)
arch/x86/kernel/mpparse_32.c:318: error: (Each undeclared identifier is 
reported only once
arch/x86/kernel/mpparse_32.c:318: error: for each function it appears in.)
arch/x86/kernel/mpparse_32.c:332: error: `mpc_phys' undeclared (first use in 
this function)


This patch is build tested only.


Signed-off-by: Kamalesh Babulal [EMAIL PROTECTED]
---
--- linux-2.6.24-rc8/arch/x86/kernel/mpparse_32.c   2008-01-17 
18:02:45.0 +0530
+++ linux-2.6.24-rc8/arch/x86/kernel/~mpparse_32.c  2008-01-17 
18:17:29.0 +0530
@@ -32,6 +32,7 @@
 #include mach_apic.h
 #include mach_apicdef.h
 #include mach_mpparse.h
+#include asm/mpspec_def.h
 
 /* Have we found an MP table */
 int smp_found_config;
@@ -329,7 +330,7 @@ static void __init smp_read_mpc_oem(unsi
oem_length = oemtable-oem_length;
/* Unmap header and map full base table */
early_iounmap(oemtable, sizeof(struct mp_config_oemtable));
-   oemtable = (struct mp_config_oemtable *)early_ioremap(mpc_phys,
+   oemtable = (struct mp_config_oemtable *)early_ioremap(oemtable_phys,
oem_length);
if (!oemtable) {
printk(MPTABLE: full oemtable map error!\n);
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc8-mm1 Build Failure on scsi driver

[Kamalesh Babulal]

Hi Andrew,

The kernel build fails with following error

drivers/scsi/aha152x.o: In function `aha152x_host_reset_host':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:1324: multiple 
definition of `aha152x_host_reset_host'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:1324:
 first defined here
drivers/scsi/aha152x.o: In function `aha152x_release':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:908: multiple 
definition of `aha152x_release'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:908:
 first defined here
ld: Warning: size of symbol `aha152x_release' changed from 68 in 
drivers/scsi/pcmcia/built-in.o to 100 in drivers/scsi/aha152x.o
drivers/scsi/aha152x.o: In function `aha152x_probe_one':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:772: multiple 
definition of `aha152x_probe_one'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:772:
 first defined here
drivers/scsi/fdomain.o:(.data+0x0): multiple definition of 
`fdomain_driver_template'
drivers/scsi/pcmcia/built-in.o:(.data+0x5a0): first defined here
drivers/scsi/fdomain.o: In function `fdomain_16x0_bus_reset':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:1568: multiple 
definition of `fdomain_16x0_bus_reset'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:1568:
 first defined here
drivers/scsi/fdomain.o: In function `__fdomain_16x0_detect':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:894: multiple 
definition of `__fdomain_16x0_detect'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:894:
 first defined here
ld: Warning: size of symbol `__fdomain_16x0_detect' changed from 1206 in 
drivers/scsi/pcmcia/built-in.o to 1700 in drivers/scsi/fdomain.o
drivers/scsi/fdomain.o: In function `fdomain_setup':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:554: multiple 
definition of `fdomain_setup'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:554:
 first defined here
make[2]: *** [drivers/scsi/built-in.o] Error 1
make[1]: *** [drivers/scsi] Error 2
make: *** [drivers] Error 2


-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc8-mm1 Build Failure at scripts/mkubooting/crc32.c

[Kamalesh Babulal]

Hi Andrew,

The kernel build fails with following error message

scripts/mkubootimg/crc32.c:15:18: error: zlib.h: No such file or directory
scripts/mkubootimg/crc32.c:77: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before 'crc_table'
scripts/mkubootimg/crc32.c:153: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before 'crc32'
make[2]: *** [scripts/mkubootimg/crc32.o] Error 1
make[1]: *** [scripts/mkubootimg] Error 2
make: *** [scripts] Error 2

The patch causing this build failure may be git-kbuild.patch.

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] aha152x: fix isa/pcmcia compile problem

[Kamalesh Babulal]

 *info = link-priv;
 
 - aha152x_release(info-host);
 + GLOBAL(aha152x_release)(info-host);
   pcmcia_disable_device(link);
  }
 
 @@ -224,7 +226,7 @@ static int aha152x_resume(struct pcmcia_device *link)
  {
   scsi_info_t *info = link-priv;
 
 - aha152x_host_reset_host(info-host);
 + GLOBAL(aha152x_host_reset_host)(info-host);
 
   return 0;
  }
 diff --git a/fs/sysfs/dir.c b/fs/sysfs/dir.c
 --
Hi Tejun Heo,

Thanks, I have tested the patch fixes the build failure on aha152x.c.
Tested-By: Kamalesh Babulal [EMAIL PROTECTED]

Thanks  Regards,
Kamalesh Babulal.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc8-mm1 Build Failure on scsi driver

[Kamalesh Babulal]

Andrew Morton wrote:
 On Thu, 17 Jan 2008 21:45:39 +0530 Kamalesh Babulal [EMAIL PROTECTED] wrote:
 
 Hi Andrew,

 The kernel build fails with following error

 drivers/scsi/aha152x.o: In function `aha152x_host_reset_host':
 /home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:1324: multiple 
 definition of `aha152x_host_reset_host'
 drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:1324:
  first defined here
 drivers/scsi/aha152x.o: In function `aha152x_release':
 /home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:908: multiple 
 definition of `aha152x_release'
 drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:908:
  first defined here
 ld: Warning: size of symbol `aha152x_release' changed from 68 in 
 drivers/scsi/pcmcia/built-in.o to 100 in drivers/scsi/aha152x.o
 drivers/scsi/aha152x.o: In function `aha152x_probe_one':
 
 Neat.  Seems that the scsi build system is linking together two copies of
 drivers/scsi/aha152x.o.  One via drivers/scsi/aha152x.o directly and the
 other via drivers/scsi/pcmcia/built-in.o.
 
 Please send the .config.
 
 I'm looking suspiciously at this, from git-scsi-misc:
 
 commit 8ae732a91df051aba6820068a47b631a06599d84
 Author: Tejun Heo [EMAIL PROTECTED]
 Date:   Fri Dec 7 22:36:23 2007 +0900
 
 [SCSI] make pcmcia directory use obj-y|m instead of subdir-y|m
 
 subdir-y|m isn't supposed to contain modules or built-in components.
 Change subdir-$(CONFIG_PCMCIA) to obj-$(CONFIG_PCMCIA).
 
 Signed-off-by: Tejun Heo [EMAIL PROTECTED]
 Acked-by: Sam Ravnborg [EMAIL PROTECTED]
 Signed-off-by: James Bottomley [EMAIL PROTECTED]
 
 diff --git a/drivers/scsi/Makefile b/drivers/scsi/Makefile
 index b5441f5..93e1428 100644
 --- a/drivers/scsi/Makefile
 +++ b/drivers/scsi/Makefile
 @@ -17,7 +17,7 @@
  CFLAGS_aha152x.o =   -DAHA152X_STAT -DAUTOCONF
  CFLAGS_gdth.o= # -DDEBUG_GDTH=2 -D__SERIAL__ -D__COM2__ -DGDTH_STATISTICS
 
 -subdir-$(CONFIG_PCMCIA)  += pcmcia
 +obj-$(CONFIG_PCMCIA) += pcmcia/
 
  obj-$(CONFIG_SCSI)   += scsi_mod.o
  obj-$(CONFIG_SCSI_TGT)   += scsi_tgt.o

Hi Andrew,

Patch from Tejun Heo fixes the aha152x.c build failure, and following second 
part
of the build failure, is still occurring.

drivers/scsi/fdomain.o:(.data+0x0): multiple definition of 
`fdomain_driver_template'
drivers/scsi/pcmcia/built-in.o:(.data+0x5a0): first defined here
drivers/scsi/fdomain.o: In function `fdomain_16x0_bus_reset':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:1568: multiple 
definition of `fdomain_16x0_bus_reset'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:1568:
 first defined here
drivers/scsi/fdomain.o: In function `__fdomain_16x0_detect':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:894: multiple 
definition of `__fdomain_16x0_detect'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:894:
 first defined here
ld: Warning: size of symbol `__fdomain_16x0_detect' changed from 1206 in 
drivers/scsi/pcmcia/built-in.o to 1700 in drivers/scsi/fdomain.o
drivers/scsi/fdomain.o: In function `fdomain_setup':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:554: multiple 
definition of `fdomain_setup'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/fdomain.c:554:
 first defined here
make[2]: *** [drivers/scsi/built-in.o] Error 1
make[1]: *** [drivers/scsi] Error 2
make: *** [drivers] Error 2

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc8-mm1 build failure on headers_check

[Kamalesh Babulal]

Hi Andrew,

The kernel build fails during the headers_check on power box

  CHECK   include/asm/nvram.h
/usr/local/autobench/autotest/tmp/build/linux/usr/include/asm/nvram.h requires 
linux/list.h, which does not exist in exported headers
make[3]: *** 
[/usr/local/autobench/autotest/tmp/build/linux/usr/include/asm/.check.nvram.h] 
Error 1
make[2]: *** [asm-powerpc] Error 2
make[1]: *** [headers_check] Error 2
make: *** [vmlinux] Error 2

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] SCSI: fix isa/pcmcia compile problem

[Kamalesh Babulal]

On Fri, Jan 18, 2008 at 04:20:40PM +0900, Tejun Heo wrote:
 aha152x.c and fdomain are built twice - once for the isa driver and
 once for the PCMCIA one.  Through #ifdefs, the compiled codes are
 slightly different; thus, global symbols need to be given different
 names depending on which flavor is being built.  This patch adds
 GLOBAL() macro to aha152x.h and fdomain.h which change the symbol
 depending on PCMCIA.
 
 This bug has always existed but has been masked by the fact the
 drivers/scsi/pcmcia used subdir-(y|m) instead of obj-(y|m) which made
 drivers/scsi/pcmcia/built_in.o not linked into the kernel and thus
 avoided the duplicate symbols during compilation.
 
Hi Tejun Heo,

Thanks, I have tested the patch, it fixes both build failures.

Tested-by: Kamalesh Babulal [EMAIL PROTECTED]
Signed-off-by: Tejun Heo [EMAIL PROTECTED]
---
Ah... missed that one.  Here's the updated version.

 drivers/scsi/aha152x.c |   12 ++--
 drivers/scsi/aha152x.h |   20 +---
 drivers/scsi/fdomain.c |   20 ++--
 drivers/scsi/fdomain.h |   21 +
 drivers/scsi/pcmcia/aha152x_stub.c |   10 ++
 drivers/scsi/pcmcia/fdomain_stub.c |   10 ++
 6 files changed, 62 insertions(+), 31 deletions(-)

diff --git a/drivers/scsi/aha152x.c b/drivers/scsi/aha152x.c
index ea8c699..0204f44 100644
--- a/drivers/scsi/aha152x.c
+++ b/drivers/scsi/aha152x.c
@@ -769,7 +769,7 @@ static irqreturn_t swintr(int irqno, void *dev_id)
return IRQ_HANDLED;
 }

-struct Scsi_Host *aha152x_probe_one(struct aha152x_setup *setup)
+struct Scsi_Host *GLOBAL(aha152x_probe_one)(struct aha152x_setup *setup)
 {
struct Scsi_Host *shpnt;

@@ -905,7 +905,7 @@ out_host_put:
return NULL;
 }

-void aha152x_release(struct Scsi_Host *shpnt)
+void GLOBAL(aha152x_release)(struct Scsi_Host *shpnt)
 {
if (!shpnt)
return;
@@ -1327,7 +1327,7 @@ static void reset_ports(struct Scsi_Host *shpnt)
  * Reset the host (bus and controller)
  *
  */
-int aha152x_host_reset_host(struct Scsi_Host *shpnt)
+int GLOBAL(aha152x_host_reset_host)(struct Scsi_Host *shpnt)
 {
DPRINTK(debug_eh, KERN_DEBUG scsi%d: host reset\n, shpnt-host_no);

@@ -1345,7 +1345,7 @@ int aha152x_host_reset_host(struct Scsi_Host *shpnt)
  */
 static int aha152x_host_reset(Scsi_Cmnd *SCpnt)
 {
-   return aha152x_host_reset_host(SCpnt-device-host);
+   return GLOBAL(aha152x_host_reset_host)(SCpnt-device-host);
 }

 /*
@@ -3916,7 +3916,7 @@ static int __init aha152x_init(void)

for (i=0; isetup_count; i++) {
if ( request_region(setup[i].io_port, IO_RANGE, aha152x) ) {
-   struct Scsi_Host *shpnt = aha152x_probe_one(setup[i]);
+   struct Scsi_Host *shpnt = 
GLOBAL(aha152x_probe_one)(setup[i]);

if( !shpnt ) {
release_region(setup[i].io_port, IO_RANGE);
@@ -3946,7 +3946,7 @@ static void __exit aha152x_exit(void)
list_for_each_entry(hd, aha152x_host_list, host_list) {
struct Scsi_Host *shost = container_of((void *)hd, struct 
Scsi_Host, hostdata);

-   aha152x_release(shost);
+   GLOBAL(aha152x_release)(shost);
}
 }

diff --git a/drivers/scsi/aha152x.h b/drivers/scsi/aha152x.h
index ac4bfa4..f441e54 100644
--- a/drivers/scsi/aha152x.h
+++ b/drivers/scsi/aha152x.h
@@ -330,8 +330,22 @@ struct aha152x_setup {
char *conf;
 };

-struct Scsi_Host *aha152x_probe_one(struct aha152x_setup *);
-void aha152x_release(struct Scsi_Host *);
-int aha152x_host_reset_host(struct Scsi_Host *);
+/*
+ * This file and aha152x.c are compiled in two different ways - for
+ * the isa driver and pcmcia one.  When building the pcmcia one, the
+ * file is slightly modified, so they can't share the same object
+ * file.  The following macro alters a symbol depending on whether
+ * pcmcia driver is being built or not and should be used for any
+ * global symbol.
+ */
+#if defined(PCMCIA)
+#define GLOBAL(x)  CS_##x
+#else
+#define GLOBAL(x)  ISA_##x
+#endif
+
+struct Scsi_Host *GLOBAL(aha152x_probe_one)(struct aha152x_setup *);
+void GLOBAL(aha152x_release)(struct Scsi_Host *);
+int GLOBAL(aha152x_host_reset_host)(struct Scsi_Host *);

 #endif /* _AHA152X_H */
diff --git a/drivers/scsi/fdomain.c b/drivers/scsi/fdomain.c
index 2cd6b49..e14c59b 100644
--- a/drivers/scsi/fdomain.c
+++ b/drivers/scsi/fdomain.c
@@ -550,7 +550,7 @@ static void print_banner( struct Scsi_Host *shpnt )
printk( \n );
 }

-int fdomain_setup(char *str)
+int GLOBAL(fdomain_setup)(char *str)
 {
int ints[4];

@@ -571,7 +571,7 @@ int fdomain_setup(char *str)
return 1;
 }

-__setup(fdomain=, fdomain_setup);
+__setup(fdomain=, GLOBAL(fdomain_setup));


 static void do_pause(unsigned amount)  /* Pause for amount*10 milliseconds */
@@ -890,7 +890,7 @@ fail:

 #endif

-struct Scsi_Host

Re: Linux 2.6.24-rc7 Build Failure on headers_install

[Kamalesh Babulal]

Sam Ravnborg wrote:
> On Mon, Jan 07, 2008 at 02:18:27PM +0530, Kamalesh Babulal wrote:
>> Hi,
>>
>> The make allyesconfig build fails on x86_64 (AMD box) with the following
>> error
>>
>>   CHK include/linux/version.h
>>   CHK include/linux/utsrelease.h
>>   CALLscripts/checksyscalls.sh
>>   CHK include/linux/compile.h
>>   CHK include/linux/version.h
>> make[2]: `scripts/unifdef' is up to date.
>> make[2]: *** No rule to make target `|', needed by `asm-generic'.  Stop.
>> make[1]: *** [headers_install] Error 2
>> make: *** [vmlinux] Error 2
> 
> Which make version are you using - it looks like a make bug.
> Did this occur with an older kernel or has this behaviour just started?
> 
> To get further you can disable "headers check" in kernel hacking menu
> but we need to find out why it fails for you.
> 
> Note: '|' is used to say that a prerequisite is 'order only' in
> scripts/Makefile.headersinst
> 
>   Sam
Hi Sam,

After disabling the headers_check, the build failure is not seen,
i tried compiling 2.6.24-rc{2,3,4,5,6,7} all of these have this failure.
And when i tried compiling 2.6.23 with allyesconfig i got the following
error

  SYSCALL arch/x86_64/vdso/vdso.so
/usr/bin/ld: section .data [ff700900 -> ff700917] overlaps 
section .plt [ff7008e4 -> ff700903]
collect2: ld returned 1 exit status
make[1]: *** [arch/x86_64/vdso/vdso.so] Error 1
make: *** [arch/x86_64/vdso] Error 2

# make --version
GNU Make version 3.79.1

# ld -v
GNU ld version 2.14.90.0.4 20030523

# gcc --version
gcc (GCC) 3.2.3 20030502 

let me know if, i could help you with more information.
-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.6.24-rc7 Build-Failure at __you_cannot_kmalloc_that_much

[Kamalesh Babulal]

On Tue, Jan 08, 2008 at 10:56:09AM +0100, Jean Delvare wrote:
> Hi Andrew, hi Chritoph,
> 
> On Mon, 7 Jan 2008 11:38:31 -0800, Andrew Morton wrote:
> > On Mon, 7 Jan 2008 10:31:53 -0800 (PST)
> > Christoph Lameter <[EMAIL PROTECTED]> wrote:
> > 
> > > On Mon, 7 Jan 2008, Andrew Morton wrote:
> > > 
> > > > > : undefined reference to `__you_cannot_kmalloc_that_much'
> > > 
> > > There is also a kernel.org bugzilla for this at
> > > 
> > > http://bugzilla.kernel.org/show_bug.cgi?id=9669
> > > For some reason my adds to this do not show up.
> > > 
> > > In both cases we have a 
> > > 
> > > k(z/m)alloc(sizeof(*pointer), ...)
> > > 
> > > that is for some reason failing. I guess what happens is that the 
> > > function 
> > > in which this occurs is too complex for gcc 3.2. Thus it stops constant 
> > > folding the sizeof(*pointer) in the complex inline-if-cascade that SLAB 
> > > needs to determine the cache and does not eliminate the 
> > > __you_cannot_kmalloc_that_much branch().
> 
> Interesting theory... So I tried to split half of the code of
> dmi_id_init() to a subfunction and bingo! gcc 3.2.3 is now able to
> build it properly. Thanks for the hint!
> 
> > > SLUB in that case just puts a series of if comparisions in the code. This 
> > > means compilation does not fail but a large amount of code is generated.
> > 
> > ug.  Silent and nasty.
> > 
> > > We could replace the __you_cannot_kmalloc_that_much() with a BUG() 
> > > statement so we have the same effect in SLAB?
> > 
> > I think it'd be better to just put suitable workarounds at the offending
> > callsites.  We've only seen three or four of them in several months.
> 
> Here's a workaround for dmi-id.
> 
> Subject: Fix for __you_cannot_kmalloc_that_much failure in dmi-id
> 
> gcc 3.2 has a hard time coping with the code in dmi_id_init():
> 
> drivers/built-in.o(.init.text+0x789e): In function `dmi_id_init':
> : undefined reference to `__you_cannot_kmalloc_that_much'
> make: *** [.tmp_vmlinux1] Error 1
> 
> Moving half of the code to a separate function seems to help. This is
> a no-op for gcc 4.1 which will successfully inline the code anyway.

Hi Jean,

Thank you, I have tested the patch, it fixes the build failure.


 Tested-by: Kamalesh Babulal <[EMAIL PROTECTED]>
 Signed-off-by: Jean Delvare <[EMAIL PROTECTED]>
 ---
 drivers/firmware/dmi-id.c |   19 ++-
 1 file changed, 14 insertions(+), 5 deletions(-)
 
--- linux-2.6.24-rc7.orig/drivers/firmware/dmi-id.c 2007-10-24 
09:59:28.0 +0200
+++ linux-2.6.24-rc7/drivers/firmware/dmi-id.c  2008-01-08 10:32:00.0 
+0100
@@ -175,12 +175,11 @@ static struct device *dmi_dev;

 extern int dmi_available;

-static int __init dmi_id_init(void)
+/* In a separate function to keep gcc 3.2 happy - do NOT merge this in
+   dmi_id_init! */
+static void __init dmi_id_init_attr_table(void)
 {
-   int ret, i;
-
-   if (!dmi_available)
-   return -ENODEV;
+   int i;
 
/* Not necessarily all DMI fields are available on all
 * systems, hence let's built an attribute table of just
@@ -205,6 +204,16 @@ static int __init dmi_id_init(void)
ADD_DMI_ATTR(chassis_serial,DMI_CHASSIS_SERIAL);
ADD_DMI_ATTR(chassis_asset_tag, DMI_CHASSIS_ASSET_TAG);
sys_dmi_attributes[i++] = _dmi_modalias_attr.attr;
+}
+
+static int __init dmi_id_init(void)
+{
+   int ret;
+
+   if (!dmi_available)
+   return -ENODEV;
+
+   dmi_id_init_attr_table();

ret = class_register(_class);
if (ret)

I'll now check if I can do something similar for snd-mixer-oss.
 
-- 
Jean Delvare
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.6.24-rc7 Build-Failure at __you_cannot_kmalloc_that_much

[Kamalesh Babulal]

Andrew Morton wrote:
> On Mon, 07 Jan 2008 16:06:20 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> 
>> The defconfig make fails on x86_64 (AMD box) with following error
>>
>>   CHK include/linux/utsrelease.h
>>   CALLscripts/checksyscalls.sh
>>   CHK include/linux/compile.h
>>   GEN .version
>>   CHK include/linux/compile.h
>>   UPD include/linux/compile.h
>>   CC  init/version.o
>>   LD  init/built-in.o
>>   LD  .tmp_vmlinux1
>> drivers/built-in.o(.init.text+0x8d76): In function `dmi_id_init':
>> : undefined reference to `__you_cannot_kmalloc_that_much'
>> make: *** [.tmp_vmlinux1] Error 1
>>
>>
>> # gcc --version
>> gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-59)
>>
>> This was reported by Adrian Bunk http://lkml.org/lkml/2007/12/1/39
> 
> That's odd.  afacit the only kmalloc in dmi_id_init() is
> 
> dmi_dev = kzalloc(sizeof(*dmi_dev), GFP_KERNEL);
> 
> and even gcc-3.2.3 should be able to get that right.
> 
> Could you please a) verify that simply removing that line fixes the build
> error and then b) try to find some way of fixing it?
> 
> Try replacing `sizeof(*dmi_dev)' with `sizeof(struct dmi_device_attribute)'
> and any other tricks you can think of to try to make the compiler process
> the code differently.
> 

removing the line fixes the issue, but changing the sizeof(*dmi_dev) to
sizeof(struct device) is not helping.

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.6.24-rc7 Build-Failure at __you_cannot_kmalloc_that_much

[Kamalesh Babulal]

Andrew Morton wrote:
 On Mon, 07 Jan 2008 16:06:20 +0530 Kamalesh Babulal [EMAIL PROTECTED] wrote:
 
 The defconfig make fails on x86_64 (AMD box) with following error

   CHK include/linux/utsrelease.h
   CALLscripts/checksyscalls.sh
   CHK include/linux/compile.h
   GEN .version
   CHK include/linux/compile.h
   UPD include/linux/compile.h
   CC  init/version.o
   LD  init/built-in.o
   LD  .tmp_vmlinux1
 drivers/built-in.o(.init.text+0x8d76): In function `dmi_id_init':
 : undefined reference to `__you_cannot_kmalloc_that_much'
 make: *** [.tmp_vmlinux1] Error 1


 # gcc --version
 gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-59)

 This was reported by Adrian Bunk http://lkml.org/lkml/2007/12/1/39
 
 That's odd.  afacit the only kmalloc in dmi_id_init() is
 
 dmi_dev = kzalloc(sizeof(*dmi_dev), GFP_KERNEL);
 
 and even gcc-3.2.3 should be able to get that right.
 
 Could you please a) verify that simply removing that line fixes the build
 error and then b) try to find some way of fixing it?
 
 Try replacing `sizeof(*dmi_dev)' with `sizeof(struct dmi_device_attribute)'
 and any other tricks you can think of to try to make the compiler process
 the code differently.
 

removing the line fixes the issue, but changing the sizeof(*dmi_dev) to
sizeof(struct device) is not helping.

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.6.24-rc7 Build-Failure at __you_cannot_kmalloc_that_much

[Kamalesh Babulal]

On Tue, Jan 08, 2008 at 10:56:09AM +0100, Jean Delvare wrote:
 Hi Andrew, hi Chritoph,
 
 On Mon, 7 Jan 2008 11:38:31 -0800, Andrew Morton wrote:
  On Mon, 7 Jan 2008 10:31:53 -0800 (PST)
  Christoph Lameter [EMAIL PROTECTED] wrote:
  
   On Mon, 7 Jan 2008, Andrew Morton wrote:
   
 : undefined reference to `__you_cannot_kmalloc_that_much'
   
   There is also a kernel.org bugzilla for this at
   
   http://bugzilla.kernel.org/show_bug.cgi?id=9669
   For some reason my adds to this do not show up.
   
   In both cases we have a 
   
   k(z/m)alloc(sizeof(*pointer), ...)
   
   that is for some reason failing. I guess what happens is that the 
   function 
   in which this occurs is too complex for gcc 3.2. Thus it stops constant 
   folding the sizeof(*pointer) in the complex inline-if-cascade that SLAB 
   needs to determine the cache and does not eliminate the 
   __you_cannot_kmalloc_that_much branch().
 
 Interesting theory... So I tried to split half of the code of
 dmi_id_init() to a subfunction and bingo! gcc 3.2.3 is now able to
 build it properly. Thanks for the hint!
 
   SLUB in that case just puts a series of if comparisions in the code. This 
   means compilation does not fail but a large amount of code is generated.
  
  ug.  Silent and nasty.
  
   We could replace the __you_cannot_kmalloc_that_much() with a BUG() 
   statement so we have the same effect in SLAB?
  
  I think it'd be better to just put suitable workarounds at the offending
  callsites.  We've only seen three or four of them in several months.
 
 Here's a workaround for dmi-id.
 
 Subject: Fix for __you_cannot_kmalloc_that_much failure in dmi-id
 
 gcc 3.2 has a hard time coping with the code in dmi_id_init():
 
 drivers/built-in.o(.init.text+0x789e): In function `dmi_id_init':
 : undefined reference to `__you_cannot_kmalloc_that_much'
 make: *** [.tmp_vmlinux1] Error 1
 
 Moving half of the code to a separate function seems to help. This is
 a no-op for gcc 4.1 which will successfully inline the code anyway.

Hi Jean,

Thank you, I have tested the patch, it fixes the build failure.


 Tested-by: Kamalesh Babulal [EMAIL PROTECTED]
 Signed-off-by: Jean Delvare [EMAIL PROTECTED]
 ---
 drivers/firmware/dmi-id.c |   19 ++-
 1 file changed, 14 insertions(+), 5 deletions(-)
 
--- linux-2.6.24-rc7.orig/drivers/firmware/dmi-id.c 2007-10-24 
09:59:28.0 +0200
+++ linux-2.6.24-rc7/drivers/firmware/dmi-id.c  2008-01-08 10:32:00.0 
+0100
@@ -175,12 +175,11 @@ static struct device *dmi_dev;

 extern int dmi_available;

-static int __init dmi_id_init(void)
+/* In a separate function to keep gcc 3.2 happy - do NOT merge this in
+   dmi_id_init! */
+static void __init dmi_id_init_attr_table(void)
 {
-   int ret, i;
-
-   if (!dmi_available)
-   return -ENODEV;
+   int i;
 
/* Not necessarily all DMI fields are available on all
 * systems, hence let's built an attribute table of just
@@ -205,6 +204,16 @@ static int __init dmi_id_init(void)
ADD_DMI_ATTR(chassis_serial,DMI_CHASSIS_SERIAL);
ADD_DMI_ATTR(chassis_asset_tag, DMI_CHASSIS_ASSET_TAG);
sys_dmi_attributes[i++] = sys_dmi_modalias_attr.attr;
+}
+
+static int __init dmi_id_init(void)
+{
+   int ret;
+
+   if (!dmi_available)
+   return -ENODEV;
+
+   dmi_id_init_attr_table();

ret = class_register(dmi_class);
if (ret)

I'll now check if I can do something similar for snd-mixer-oss.
 
-- 
Jean Delvare
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.6.24-rc7 Build Failure on headers_install

[Kamalesh Babulal]

Sam Ravnborg wrote:
 On Mon, Jan 07, 2008 at 02:18:27PM +0530, Kamalesh Babulal wrote:
 Hi,

 The make allyesconfig build fails on x86_64 (AMD box) with the following
 error

   CHK include/linux/version.h
   CHK include/linux/utsrelease.h
   CALLscripts/checksyscalls.sh
   CHK include/linux/compile.h
   CHK include/linux/version.h
 make[2]: `scripts/unifdef' is up to date.
 make[2]: *** No rule to make target `|', needed by `asm-generic'.  Stop.
 make[1]: *** [headers_install] Error 2
 make: *** [vmlinux] Error 2
 
 Which make version are you using - it looks like a make bug.
 Did this occur with an older kernel or has this behaviour just started?
 
 To get further you can disable headers check in kernel hacking menu
 but we need to find out why it fails for you.
 
 Note: '|' is used to say that a prerequisite is 'order only' in
 scripts/Makefile.headersinst
 
   Sam
Hi Sam,

After disabling the headers_check, the build failure is not seen,
i tried compiling 2.6.24-rc{2,3,4,5,6,7} all of these have this failure.
And when i tried compiling 2.6.23 with allyesconfig i got the following
error

  SYSCALL arch/x86_64/vdso/vdso.so
/usr/bin/ld: section .data [ff700900 - ff700917] overlaps 
section .plt [ff7008e4 - ff700903]
collect2: ld returned 1 exit status
make[1]: *** [arch/x86_64/vdso/vdso.so] Error 1
make: *** [arch/x86_64/vdso] Error 2

# make --version
GNU Make version 3.79.1

# ld -v
GNU ld version 2.14.90.0.4 20030523

# gcc --version
gcc (GCC) 3.2.3 20030502 

let me know if, i could help you with more information.
-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.6.24-rc7 kernel BUG at kernel/sched.c:5156!

[Kamalesh Babulal]

Hi,

When booting the 2.6.24-rc7 kernel on the powerpc, kernel bug at
kernel.sched.c is triggered

[0.00] Kernel command line: ro console=hvc0 rhgb quiet root=LABEL=/ 
[0.149567] BUG: scheduling while atomic: kthreadd/2/0x0006f34c
[0.149655] BUG: scheduling while atomic: kthreadd/3/0xbe0d8168
[0.149714] [ cut here ]
[0.149722] kernel BUG at kernel/sched.c:5156!
cpu 0x0: Vector: 700 (Program Check) at [c001be0dbd70]
pc: c006c090: .migration_thread+0x64/0x31c
lr: c008e348: .kthread+0x78/0xc4
sp: c001be0dbff0
   msr: 80029032
  current = 0xc000ee11ccc0
  paca= 0xc0532d00
pid   = 3, comm = kthreadd
kernel BUG at kernel/sched.c:5156!
enter ? for help
[c001be0dc0b0] c008e348 .kthread+0x78/0xc4
[c001be0dc140] c002a550 .kernel_thread+0x4c/0x68

0:mon> t
[c001be0dc0b0] c008e348 .kthread+0x78/0xc4
[c001be0dc140] c002a550 .kernel_thread+0x4c/0x68
0:mon> r
R00 = 0001   R16 = 41c0
R01 = c001be0dbff0   R17 = c0403920
R02 = c06072f8   R18 = 
R03 =    R19 = 0019b000
R04 = c000ee11ccc0   R20 = c04c9550
R05 =    R21 = 020c9550
R06 = c0532d00   R22 = 020c97c0
R07 = c001be0d81b0   R23 = c04c97c0
R08 =    R24 = 018bf8d0
R09 = c000ee11ccbf   R25 = 
R10 = fffc   R26 = c06a4968
R11 = c0532d00   R27 = c06a00b0
R12 = c002a550   R28 = c000ee143c98
R13 = c0532d00   R29 = c0f35b80
R14 =    R30 = c05b4190
R15 = c04050a0   R31 = c05cf910
pc  = c006c090 .migration_thread+0x64/0x31c
lr  = c008e348 .kthread+0x78/0xc4
msr = 80029032   cr  = 2824
ctr = c006c02c   xer = 2004   trap =  700

(gdb) p kthread
$1 = {int (void *)} 0xc008e2d0 
(gdb) p/x 0xc008e2d0+0x78
$2 = 0xc008e348
(gdb) l *0xc008e348
0xc008e348 is in kthread (kernel/kthread.c:78).
73  __set_current_state(TASK_UNINTERRUPTIBLE);
74  complete(>started);
75  schedule();
76
77  if (!kthread_should_stop())
78  ret = threadfn(data);
79
80  /* It might have exited on its own, w/o kthread_stop.  Check. */
81  if (kthread_should_stop()) {
82  kthread_stop_info.err = ret;


-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.6.24-rc7 Build-Failure at __you_cannot_kmalloc_that_much

[Kamalesh Babulal]

Hi,

The defconfig make fails on x86_64 (AMD box) with following error

  CHK include/linux/utsrelease.h
  CALLscripts/checksyscalls.sh
  CHK include/linux/compile.h
  GEN .version
  CHK include/linux/compile.h
  UPD include/linux/compile.h
  CC  init/version.o
  LD  init/built-in.o
  LD  .tmp_vmlinux1
drivers/built-in.o(.init.text+0x8d76): In function `dmi_id_init':
: undefined reference to `__you_cannot_kmalloc_that_much'
make: *** [.tmp_vmlinux1] Error 1


# gcc --version
gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-59)

This was reported by Adrian Bunk http://lkml.org/lkml/2007/12/1/39

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.24-rc7
# Mon Jan  7 16:47:07 2008
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
# CONFIG_QUICKLIST is not set
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_RWSEM_XCHGADD_ALGORITHM is not set
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ARCH_SUPPORTS_OPROFILE=y
CONFIG_ZONE_DMA32=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_AUDIT_ARCH=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_HT=y
# CONFIG_KTIME_SCALAR is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=18
# CONFIG_CGROUPS is not set
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_FAIR_USER_SCHED=y
# CONFIG_FAIR_CGROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_RELAY=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_KMOD is not set
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_BLK_DEV_BSG is not set
CONFIG_BLOCK_COMPAT=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_AS is not set
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"

#
# Processor type and features
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_NO_HZ is not set
# CONFIG_HIGH_RES_TIMERS is not set
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_X86_VSMP is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
CONFIG_GENERIC_CPU=y
CONFIG_X86_L1_CACHE_BYTES=128
CONFIG_X86_INTERNODE_CACHE_BYTES=128
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_GOOD_APIC=y
CONFI

Re: Linux 2.6.24-rc7 Build Failure on headers_install

[Kamalesh Babulal]

Hi,

The make allyesconfig build fails on x86_64 (AMD box) with the following
error

  CHK include/linux/version.h
  CHK include/linux/utsrelease.h
  CALLscripts/checksyscalls.sh
  CHK include/linux/compile.h
  CHK include/linux/version.h
make[2]: `scripts/unifdef' is up to date.
make[2]: *** No rule to make target `|', needed by `asm-generic'.  Stop.
make[1]: *** [headers_install] Error 2
make: *** [vmlinux] Error 2

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.6.24-rc7 Build Failure on headers_install

[Kamalesh Babulal]

Hi,

The make allyesconfig build fails on x86_64 (AMD box) with the following
error

  CHK include/linux/version.h
  CHK include/linux/utsrelease.h
  CALLscripts/checksyscalls.sh
  CHK include/linux/compile.h
  CHK include/linux/version.h
make[2]: `scripts/unifdef' is up to date.
make[2]: *** No rule to make target `|', needed by `asm-generic'.  Stop.
make[1]: *** [headers_install] Error 2
make: *** [vmlinux] Error 2

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.6.24-rc7 Build-Failure at __you_cannot_kmalloc_that_much

[Kamalesh Babulal]

Hi,

The defconfig make fails on x86_64 (AMD box) with following error

  CHK include/linux/utsrelease.h
  CALLscripts/checksyscalls.sh
  CHK include/linux/compile.h
  GEN .version
  CHK include/linux/compile.h
  UPD include/linux/compile.h
  CC  init/version.o
  LD  init/built-in.o
  LD  .tmp_vmlinux1
drivers/built-in.o(.init.text+0x8d76): In function `dmi_id_init':
: undefined reference to `__you_cannot_kmalloc_that_much'
make: *** [.tmp_vmlinux1] Error 1


# gcc --version
gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-59)

This was reported by Adrian Bunk http://lkml.org/lkml/2007/12/1/39

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.24-rc7
# Mon Jan  7 16:47:07 2008
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
# CONFIG_QUICKLIST is not set
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_RWSEM_XCHGADD_ALGORITHM is not set
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ARCH_SUPPORTS_OPROFILE=y
CONFIG_ZONE_DMA32=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_AUDIT_ARCH=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_HT=y
# CONFIG_KTIME_SCALAR is not set
CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=18
# CONFIG_CGROUPS is not set
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_FAIR_USER_SCHED=y
# CONFIG_FAIR_CGROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_RELAY=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_KMOD is not set
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_BLK_DEV_BSG is not set
CONFIG_BLOCK_COMPAT=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_AS is not set
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED=cfq

#
# Processor type and features
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_NO_HZ is not set
# CONFIG_HIGH_RES_TIMERS is not set
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_X86_VSMP is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
CONFIG_GENERIC_CPU=y
CONFIG_X86_L1_CACHE_BYTES=128
CONFIG_X86_INTERNODE_CACHE_BYTES=128
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_HPET_TIMER

Re: Linux 2.6.24-rc7 kernel BUG at kernel/sched.c:5156!

[Kamalesh Babulal]

Hi,

When booting the 2.6.24-rc7 kernel on the powerpc, kernel bug at
kernel.sched.c is triggered

[0.00] Kernel command line: ro console=hvc0 rhgb quiet root=LABEL=/ 
[0.149567] BUG: scheduling while atomic: kthreadd/2/0x0006f34c
[0.149655] BUG: scheduling while atomic: kthreadd/3/0xbe0d8168
[0.149714] [ cut here ]
[0.149722] kernel BUG at kernel/sched.c:5156!
cpu 0x0: Vector: 700 (Program Check) at [c001be0dbd70]
pc: c006c090: .migration_thread+0x64/0x31c
lr: c008e348: .kthread+0x78/0xc4
sp: c001be0dbff0
   msr: 80029032
  current = 0xc000ee11ccc0
  paca= 0xc0532d00
pid   = 3, comm = kthreadd
kernel BUG at kernel/sched.c:5156!
enter ? for help
[c001be0dc0b0] c008e348 .kthread+0x78/0xc4
[c001be0dc140] c002a550 .kernel_thread+0x4c/0x68

0:mon t
[c001be0dc0b0] c008e348 .kthread+0x78/0xc4
[c001be0dc140] c002a550 .kernel_thread+0x4c/0x68
0:mon r
R00 = 0001   R16 = 41c0
R01 = c001be0dbff0   R17 = c0403920
R02 = c06072f8   R18 = 
R03 =    R19 = 0019b000
R04 = c000ee11ccc0   R20 = c04c9550
R05 =    R21 = 020c9550
R06 = c0532d00   R22 = 020c97c0
R07 = c001be0d81b0   R23 = c04c97c0
R08 =    R24 = 018bf8d0
R09 = c000ee11ccbf   R25 = 
R10 = fffc   R26 = c06a4968
R11 = c0532d00   R27 = c06a00b0
R12 = c002a550   R28 = c000ee143c98
R13 = c0532d00   R29 = c0f35b80
R14 =    R30 = c05b4190
R15 = c04050a0   R31 = c05cf910
pc  = c006c090 .migration_thread+0x64/0x31c
lr  = c008e348 .kthread+0x78/0xc4
msr = 80029032   cr  = 2824
ctr = c006c02c   xer = 2004   trap =  700

(gdb) p kthread
$1 = {int (void *)} 0xc008e2d0 kthread
(gdb) p/x 0xc008e2d0+0x78
$2 = 0xc008e348
(gdb) l *0xc008e348
0xc008e348 is in kthread (kernel/kthread.c:78).
73  __set_current_state(TASK_UNINTERRUPTIBLE);
74  complete(create-started);
75  schedule();
76
77  if (!kthread_should_stop())
78  ret = threadfn(data);
79
80  /* It might have exited on its own, w/o kthread_stop.  Check. */
81  if (kthread_should_stop()) {
82  kthread_stop_info.err = ret;


-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc6-mm1 Kernel panics at different functions ()

[Kamalesh Babulal]

Andrew Morton wrote:
> On Thu, 27 Dec 2007 14:19:54 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> 
>> Hi Andrew,
>>
>> The 2.6.24-rc6-mm1 kernel with hotfix 
>> x86-fix-system-gate-related-crash.patch applied
>> panics while booting on a x86_64 box
>>
>> Unable to handle kernel NULL pointer dereference at 0046 RIP: 
>>  [] rb_erase+0xe7/0x2a3
>> PGD 17ff65067 PUD 17f1c7067 PMD 0 
>> Oops:  [1] SMP 
>> last sysfs file: 
>> /sys/devices/pci:00/:00:0a.0/:02:04.0/host0/target0:0:6/0:0:6:0/type
>> CPU 0 
>> Modules linked in:
>> Pid: 0, comm: swapper Not tainted 2.6.24-rc6-mm1-autokern1 #1
>> RIP: 0010:[]  [] rb_erase+0xe7/0x2a3
>> RSP: :80650e00  EFLAGS: 00010002
>> RAX: 8101fe9568c8 RBX: 8100010062a8 RCX: 8101fe9568b0
>> RDX: 8101fe9568c8 RSI: 0046 RDI: 
>> RBP: 80650e10 R08: 8101fe9568c8 R09: 0086
>> R10:  R11: 01e8 R12: 8100010062b8
>> R13: 0002 R14: 810001006260 R15: 0001
>> FS:  () GS:805dc000() knlGS:f31ffbb0
>> CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
>> CR2: 0046 CR3: 00017f0ab000 CR4: 06e0
>> DR0:  DR1:  DR2: 
>> DR3:  DR6: 0ff0 DR7: 0400
>> Process swapper (pid: 0, threadinfo 805f6000, task 805a2080)
>> Stack:  8100010062a8 8101fe9568b0 80650e40 8024be16
>>  80369d65 80369d65 8101fe9568b0 8100010062a8
>>  80650eb0 8024c1d5 b88cc28e 06e73eff
>> Call Trace:
>>[] __remove_hrtimer+0x2e/0x3c
>>  [] __down_read_trylock+0x16/0x42
>>  [] __down_read_trylock+0x16/0x42
>>  [] hrtimer_run_queues+0x130/0x191
>>  [] run_timer_softirq+0x28/0x1a7
>>  [] __do_softirq+0x55/0xc2
>>  [] call_softirq+0x1c/0x28
>>  [] do_softirq+0x32/0x9d
>>  [] irq_exit+0x3f/0x41
>>  [] smp_apic_timer_interrupt+0x92/0xa7
>>  [] apic_timer_interrupt+0x66/0x70
>>[] default_idle+0x36/0x5e
>>  [] default_idle+0x31/0x5e
>>  [] default_idle+0x0/0x5e
>>  [] cpu_idle+0x90/0xb2
>>  [] rest_init+0x5a/0x5c
>>  [] start_kernel+0x2b8/0x2c4
>>  [] _sinittext+0x12b/0x132
>>
>>
> 
> It does seem to be mostly hrtimer-related.  But surely the hrtimer system
> is initialised by the time tis happens.
> 
> The usual refrain: is it possible to run a bisection search?
Hi Andrew,

While doing the git bisect, following panic was seen

Unable to handle kernel paging request at 401e RIP: 
 [] load_balance_monitor+0x15e/0x2a4
PGD 0 
Oops:  [1] SMP 
last sysfs file: 
/devices/pci:00/:00:0a.0/:02:04.0/host0/target0:0:6/0:0:6:0/type
CPU 1 
Modules linked in:
Pid: 15, comm: load_balance_mo Not tainted 2.6.24-rc6-mm1-autokern1 #1
RIP: 0010:[]  [] 
load_balance_monitor+0x15e/0x2a4
RSP: :81007ffb7eb0  EFLAGS: 00010297
RAX:  RBX: 0001 RCX: 
RDX: 401e RSI: 81007ffb7ed8 RDI: 
RBP: 81007ffb7f20 R08: 81007ffb6000 R09: 81007ffb6000
R10: 81007ffb6000 R11:  R12: 
R13: 0003 R14: 0800 R15: 8101fe997f00
FS:  () GS:8100e3b1() knlGS:f73e1bb0
CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
CR2: 401e CR3: 00201000 CR4: 06e0
DR0:  DR1:  DR2: 
DR3:  DR6: 0ff0 DR7: 0400
Process load_balance_mo (pid: 15, threadinfo 81007ffb6000, task 
81007ff94790)
Stack:  2000  810001009cc0 0001e3b29d90
 0080 000f 81007f0be780 000f
 00017ffb7f20  fffc 
Call Trace:
 [] load_balance_monitor+0x0/0x2a4
 [] kthread+0x3d/0x63
 [] child_rip+0xa/0x12
 [] kthread+0x0/0x63
 [] child_rip+0x0/0x12


Code: 48 8b 04 c2 48 8b 10 48 01 55 98 e8 ce 40 12 00 83 f8 07 41 
RIP  [] load_balance_monitor+0x15e/0x2a4
 RSP 
CR2: 401e


The git-sched.patch is causing this panic, and i am searching for the patch 
causing the
hrtimer-related panic.
 
-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc6-mm1 Kernel panics at different functions ()

[Kamalesh Babulal]

Andrew Morton wrote:
 On Thu, 27 Dec 2007 14:19:54 +0530 Kamalesh Babulal [EMAIL PROTECTED] wrote:
 
 Hi Andrew,

 The 2.6.24-rc6-mm1 kernel with hotfix 
 x86-fix-system-gate-related-crash.patch applied
 panics while booting on a x86_64 box

 Unable to handle kernel NULL pointer dereference at 0046 RIP: 
  [80369a0b] rb_erase+0xe7/0x2a3
 PGD 17ff65067 PUD 17f1c7067 PMD 0 
 Oops:  [1] SMP 
 last sysfs file: 
 /sys/devices/pci:00/:00:0a.0/:02:04.0/host0/target0:0:6/0:0:6:0/type
 CPU 0 
 Modules linked in:
 Pid: 0, comm: swapper Not tainted 2.6.24-rc6-mm1-autokern1 #1
 RIP: 0010:[80369a0b]  [80369a0b] rb_erase+0xe7/0x2a3
 RSP: :80650e00  EFLAGS: 00010002
 RAX: 8101fe9568c8 RBX: 8100010062a8 RCX: 8101fe9568b0
 RDX: 8101fe9568c8 RSI: 0046 RDI: 
 RBP: 80650e10 R08: 8101fe9568c8 R09: 0086
 R10:  R11: 01e8 R12: 8100010062b8
 R13: 0002 R14: 810001006260 R15: 0001
 FS:  () GS:805dc000() knlGS:f31ffbb0
 CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
 CR2: 0046 CR3: 00017f0ab000 CR4: 06e0
 DR0:  DR1:  DR2: 
 DR3:  DR6: 0ff0 DR7: 0400
 Process swapper (pid: 0, threadinfo 805f6000, task 805a2080)
 Stack:  8100010062a8 8101fe9568b0 80650e40 8024be16
  80369d65 80369d65 8101fe9568b0 8100010062a8
  80650eb0 8024c1d5 b88cc28e 06e73eff
 Call Trace:
  IRQ  [8024be16] __remove_hrtimer+0x2e/0x3c
  [80369d65] __down_read_trylock+0x16/0x42
  [80369d65] __down_read_trylock+0x16/0x42
  [8024c1d5] hrtimer_run_queues+0x130/0x191
  [8023fd09] run_timer_softirq+0x28/0x1a7
  [8023c018] __do_softirq+0x55/0xc2
  [8020c73c] call_softirq+0x1c/0x28
  [8020e719] do_softirq+0x32/0x9d
  [8023c0dd] irq_exit+0x3f/0x41
  [8021ff85] smp_apic_timer_interrupt+0x92/0xa7
  [8020c1e6] apic_timer_interrupt+0x66/0x70
  EOI  [802095f5] default_idle+0x36/0x5e
  [802095f0] default_idle+0x31/0x5e
  [802095bf] default_idle+0x0/0x5e
  [802096b6] cpu_idle+0x90/0xb2
  [804b0126] rest_init+0x5a/0x5c
  [806017ee] start_kernel+0x2b8/0x2c4
  [8060112b] _sinittext+0x12b/0x132


 
 It does seem to be mostly hrtimer-related.  But surely the hrtimer system
 is initialised by the time tis happens.
 
 The usual refrain: is it possible to run a bisection search?
Hi Andrew,

While doing the git bisect, following panic was seen

Unable to handle kernel paging request at 401e RIP: 
 [80232ec8] load_balance_monitor+0x15e/0x2a4
PGD 0 
Oops:  [1] SMP 
last sysfs file: 
/devices/pci:00/:00:0a.0/:02:04.0/host0/target0:0:6/0:0:6:0/type
CPU 1 
Modules linked in:
Pid: 15, comm: load_balance_mo Not tainted 2.6.24-rc6-mm1-autokern1 #1
RIP: 0010:[80232ec8]  [80232ec8] 
load_balance_monitor+0x15e/0x2a4
RSP: :81007ffb7eb0  EFLAGS: 00010297
RAX:  RBX: 0001 RCX: 
RDX: 401e RSI: 81007ffb7ed8 RDI: 
RBP: 81007ffb7f20 R08: 81007ffb6000 R09: 81007ffb6000
R10: 81007ffb6000 R11:  R12: 
R13: 0003 R14: 0800 R15: 8101fe997f00
FS:  () GS:8100e3b1() knlGS:f73e1bb0
CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
CR2: 401e CR3: 00201000 CR4: 06e0
DR0:  DR1:  DR2: 
DR3:  DR6: 0ff0 DR7: 0400
Process load_balance_mo (pid: 15, threadinfo 81007ffb6000, task 
81007ff94790)
Stack:  2000  810001009cc0 0001e3b29d90
 0080 000f 81007f0be780 000f
 00017ffb7f20  fffc 
Call Trace:
 [80232d6a] load_balance_monitor+0x0/0x2a4
 [80247830] kthread+0x3d/0x63
 [8020c2b8] child_rip+0xa/0x12
 [802477f3] kthread+0x0/0x63
 [8020c2ae] child_rip+0x0/0x12


Code: 48 8b 04 c2 48 8b 10 48 01 55 98 e8 ce 40 12 00 83 f8 07 41 
RIP  [80232ec8] load_balance_monitor+0x15e/0x2a4
 RSP 81007ffb7eb0
CR2: 401e


The git-sched.patch is causing this panic, and i am searching for the patch 
causing the
hrtimer-related panic.
 
-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ

Re: 2.6.24-rc6-mm1 Kernel panics at different functions ()

[Kamalesh Babulal]

Andrew Morton wrote:
> On Thu, 27 Dec 2007 14:19:54 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> 
>> Hi Andrew,
>>
>> The 2.6.24-rc6-mm1 kernel with hotfix 
>> x86-fix-system-gate-related-crash.patch applied
>> panics while booting on a x86_64 box
>>
>> Unable to handle kernel NULL pointer dereference at 0046 RIP: 
>>  [] rb_erase+0xe7/0x2a3
>> PGD 17ff65067 PUD 17f1c7067 PMD 0 
>> Oops:  [1] SMP 
>> last sysfs file: 
>> /sys/devices/pci:00/:00:0a.0/:02:04.0/host0/target0:0:6/0:0:6:0/type
>> CPU 0 
>> Modules linked in:
>> Pid: 0, comm: swapper Not tainted 2.6.24-rc6-mm1-autokern1 #1
>> RIP: 0010:[]  [] rb_erase+0xe7/0x2a3
>> RSP: :80650e00  EFLAGS: 00010002
>> RAX: 8101fe9568c8 RBX: 8100010062a8 RCX: 8101fe9568b0
>> RDX: 8101fe9568c8 RSI: 0046 RDI: 
>> RBP: 80650e10 R08: 8101fe9568c8 R09: 0086
>> R10:  R11: 01e8 R12: 8100010062b8
>> R13: 0002 R14: 810001006260 R15: 0001
>> FS:  () GS:805dc000() knlGS:f31ffbb0
>> CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
>> CR2: 0046 CR3: 00017f0ab000 CR4: 06e0
>> DR0:  DR1:  DR2: 
>> DR3:  DR6: 0ff0 DR7: 0400
>> Process swapper (pid: 0, threadinfo 805f6000, task 805a2080)
>> Stack:  8100010062a8 8101fe9568b0 80650e40 8024be16
>>  80369d65 80369d65 8101fe9568b0 8100010062a8
>>  80650eb0 8024c1d5 b88cc28e 06e73eff
>> Call Trace:
>>[] __remove_hrtimer+0x2e/0x3c
>>  [] __down_read_trylock+0x16/0x42
>>  [] __down_read_trylock+0x16/0x42
>>  [] hrtimer_run_queues+0x130/0x191
>>  [] run_timer_softirq+0x28/0x1a7
>>  [] __do_softirq+0x55/0xc2
>>  [] call_softirq+0x1c/0x28
>>  [] do_softirq+0x32/0x9d
>>  [] irq_exit+0x3f/0x41
>>  [] smp_apic_timer_interrupt+0x92/0xa7
>>  [] apic_timer_interrupt+0x66/0x70
>>[] default_idle+0x36/0x5e
>>  [] default_idle+0x31/0x5e
>>  [] default_idle+0x0/0x5e
>>  [] cpu_idle+0x90/0xb2
>>  [] rest_init+0x5a/0x5c
>>  [] start_kernel+0x2b8/0x2c4
>>  [] _sinittext+0x12b/0x132
>>
>>
> 
> It does seem to be mostly hrtimer-related.  But surely the hrtimer system
> is initialised by the time tis happens.
> 
> The usual refrain: is it possible to run a bisection search?
I will do the bisect and update.

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc6-mm1 Kernel panics at different functions ()

[Kamalesh Babulal]

0\n\t"
79  "je 2f\n\t"

PGD 0 
Oops:  [3] SMP 
last sysfs file: 
/sys/devices/pci:00/:00:0a.0/:02:04.0/host0/target0:0:6/0:0:6:0/type
CPU 2 
Modules linked in:
Pid: 0, comm: swapper Tainted: G   M  D 2.6.24-rc6-mm1-autokern1 #1
RIP: 0010:[]  [] rb_next+0x1e/0x4f
RSP: :81017ff3be10  EFLAGS: 00010002
RAX: 0002 RBX: 8101000332a8 RCX: 
RDX:  RSI: 8101000332a8 RDI: 0002
RBP: 81017ff3be10 R08: 01e8 R09: 0086
R10: 0001 R11: 01e8 R12: 8101fe71dec8
R13: 0002 R14: 810100033260 R15: 0001
FS:  () GS:81017ff0e000() knlGS:f7ea3b80
CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
CR2: 0012 CR3: 00201000 CR4: 06e0
DR0:  DR1:  DR2: 
DR3:  DR6: 0ff0 DR7: 0400
Process swapper (pid: 0, threadinfo 8100e3b4a000, task 81007ff6c000)
Stack:  81017ff3be40 8024be06 8020bb29 8020bb29
 8101fe71dec8 8101000332a8 81017ff3beb0 8024c1d5
 b88cc1cc 0848661b b88cc1cc 0848661b
Call Trace:
   [] __remove_hrtimer+0x1e/0x3c
 [] hrtimer_run_queues+0x130/0x191
 [] run_timer_softirq+0x28/0x1a7
 [] __do_softirq+0x55/0xc2
 [] call_softirq+0x1c/0x28
 [] do_softirq+0x32/0x9d
 [] irq_exit+0x3f/0x41
 [] smp_apic_timer_interrupt+0x92/0xa7
 [] apic_timer_interrupt+0x66/0x70
   [] default_idle+0x36/0x5e
 [] default_idle+0x31/0x5e
 [] default_idle+0x0/0x5e
 [] cpu_idle+0x90/0xb2
 [] start_secondary+0x3ad/0x3b9


Code: 48 83 7f 10 00 74 06 48 8b 7f 10 eb f3 48 89 f8 eb 1d 48 89 
RIP  [] rb_next+0x1e/0x4f
 RSP 
CR2: 0012


0x80369c2b is in rb_next (lib/rbtree.c:333).
328 /* If we have a right-hand child, go down and then left as far
329as we can. */
330 if (node->rb_right) {
331 node = node->rb_right; 
332 while (node->rb_left)
333 node=node->rb_left;
334 return node;
335 }
336
337 /* No right-hand children.  Everything down and left is

Unable to handle kernel paging request at 8020bb81 RIP: 
 [] exit_signals+0x27/0x10a
PGD 1ff102067 PUD 0 
Oops:  [5] SMP 
last sysfs file: 
/sys/devices/pci:00/:00:0a.0/:02:04.0/host0/target0:0:6/0:0:6:0/type
CPU 3 
Modules linked in:
Pid: 16511, comm: ,@ Tainted: G   M  D 2.6.24-rc6-mm1-autokern1 #1
RIP: 0010:[]  [] exit_signals+0x27/0x10a
RSP: :8101fe6e3cf8  EFLAGS: 00010003
RAX: 8020bb29 RBX: 0046 RCX: 
RDX: 8101fe6e4000 RSI:  RDI: 8101fe6e4000
RBP: 8101fe6e3d18 R08:  R09: 80662540
R10: 80662540 R11: 810004ab9740 R12: 8101fe6e4000
R13:  R14: 8101fe6e4000 R15: 8101fe6e3e88
FS:  () GS:8101fff13000(0063) knlGS:f7d4a080
CS:  0010 DS: 002b ES: 002b CR0: 8005003b
CR2: 8020bb81 CR3: 0001ff1f2000 CR4: 06e0
DR0:  DR1:  DR2: 
DR3:  DR6: 0ff0 DR7: 0400
Process ,@ (pid: 16511, threadinfo , task 8101fe6e4000)
Stack:  8101fe6e4000 0046 8101fe6e4000 0009
 8101fe6e3d68 80239b8c 8101fe6e3d48 803c241d
 0046 0046 8101fe6e3e88 0009
Call Trace:


Code: f6 40 58 08 75 07 48 83 78 48 00 74 0b 41 83 4c 24 14 04 e9 
RIP  [] exit_signals+0x27/0x10a
 RSP 
CR2: 8020bb81

0x80242abd is in exit_signals (include/linux/sched.h:555).
550 #define SIGNAL_GROUP_EXIT   0x0008 /* group exit in progress */
551
552 /* If true, all threads except ->group_exit_task have pending SIGKILL */
553 static inline int signal_group_exit(const struct signal_struct *sig)
554 {
555 return  (sig->flags & SIGNAL_GROUP_EXIT) ||
556     (sig->group_exit_task != NULL);
557 }
558
559 /*

 
-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc6-mm1 Kernel panics at different functions ()

[Kamalesh Babulal]

);
557 }
558
559 /*

 
-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc6-mm1 Kernel panics at different functions ()

[Kamalesh Babulal]

Andrew Morton wrote:
 On Thu, 27 Dec 2007 14:19:54 +0530 Kamalesh Babulal [EMAIL PROTECTED] wrote:
 
 Hi Andrew,

 The 2.6.24-rc6-mm1 kernel with hotfix 
 x86-fix-system-gate-related-crash.patch applied
 panics while booting on a x86_64 box

 Unable to handle kernel NULL pointer dereference at 0046 RIP: 
  [80369a0b] rb_erase+0xe7/0x2a3
 PGD 17ff65067 PUD 17f1c7067 PMD 0 
 Oops:  [1] SMP 
 last sysfs file: 
 /sys/devices/pci:00/:00:0a.0/:02:04.0/host0/target0:0:6/0:0:6:0/type
 CPU 0 
 Modules linked in:
 Pid: 0, comm: swapper Not tainted 2.6.24-rc6-mm1-autokern1 #1
 RIP: 0010:[80369a0b]  [80369a0b] rb_erase+0xe7/0x2a3
 RSP: :80650e00  EFLAGS: 00010002
 RAX: 8101fe9568c8 RBX: 8100010062a8 RCX: 8101fe9568b0
 RDX: 8101fe9568c8 RSI: 0046 RDI: 
 RBP: 80650e10 R08: 8101fe9568c8 R09: 0086
 R10:  R11: 01e8 R12: 8100010062b8
 R13: 0002 R14: 810001006260 R15: 0001
 FS:  () GS:805dc000() knlGS:f31ffbb0
 CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
 CR2: 0046 CR3: 00017f0ab000 CR4: 06e0
 DR0:  DR1:  DR2: 
 DR3:  DR6: 0ff0 DR7: 0400
 Process swapper (pid: 0, threadinfo 805f6000, task 805a2080)
 Stack:  8100010062a8 8101fe9568b0 80650e40 8024be16
  80369d65 80369d65 8101fe9568b0 8100010062a8
  80650eb0 8024c1d5 b88cc28e 06e73eff
 Call Trace:
  IRQ  [8024be16] __remove_hrtimer+0x2e/0x3c
  [80369d65] __down_read_trylock+0x16/0x42
  [80369d65] __down_read_trylock+0x16/0x42
  [8024c1d5] hrtimer_run_queues+0x130/0x191
  [8023fd09] run_timer_softirq+0x28/0x1a7
  [8023c018] __do_softirq+0x55/0xc2
  [8020c73c] call_softirq+0x1c/0x28
  [8020e719] do_softirq+0x32/0x9d
  [8023c0dd] irq_exit+0x3f/0x41
  [8021ff85] smp_apic_timer_interrupt+0x92/0xa7
  [8020c1e6] apic_timer_interrupt+0x66/0x70
  EOI  [802095f5] default_idle+0x36/0x5e
  [802095f0] default_idle+0x31/0x5e
  [802095bf] default_idle+0x0/0x5e
  [802096b6] cpu_idle+0x90/0xb2
  [804b0126] rest_init+0x5a/0x5c
  [806017ee] start_kernel+0x2b8/0x2c4
  [8060112b] _sinittext+0x12b/0x132


 
 It does seem to be mostly hrtimer-related.  But surely the hrtimer system
 is initialised by the time tis happens.
 
 The usual refrain: is it possible to run a bisection search?
I will do the bisect and update.

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc5-mm1 - build failures due to kobject changes

[Kamalesh Babulal]

Hi Andrew,

The kernel build fails, due to kobjects changes

drivers/infiniband/hw/ehca/ehca_main.c: In function ‘ehca_module_init’:
drivers/infiniband/hw/ehca/ehca_main.c:947: error: ‘struct device_driver’ has 
no member named ‘kobj’
drivers/infiniband/hw/ehca/ehca_main.c: In function ‘ehca_module_exit’:
drivers/infiniband/hw/ehca/ehca_main.c:976: error: ‘struct device_driver’ has 
no member named ‘kobj’
make[3]: *** [drivers/infiniband/hw/ehca/ehca_main.o] Error 1
make[2]: *** [drivers/infiniband/hw/ehca] Error 2
make[1]: *** [drivers/infiniband] Error 2
make: *** [drivers] Error 2


drivers/net/ehea/ehea_main.c: In function ‘ehea_driver_sysfs_add’:
drivers/net/ehea/ehea_main.c:2812: error: ‘struct device_driver’ has no member 
named ‘kobj’
drivers/net/ehea/ehea_main.c:2815: error: ‘struct device_driver’ has no member 
named ‘kobj’
drivers/net/ehea/ehea_main.c:2818: error: ‘struct device_driver’ has no member 
named ‘kobj’
drivers/net/ehea/ehea_main.c: In function ‘ehea_driver_sysfs_remove’:
drivers/net/ehea/ehea_main.c:2830: error: ‘struct device_driver’ has no member 
named ‘kobj’
make[3]: *** [drivers/net/ehea/ehea_main.o] Error 1
make[2]: *** [drivers/net/ehea] Error 2
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2


  CC  drivers/net/iseries_veth.o
drivers/net/iseries_veth.c: In function ‘veth_module_init’:
drivers/net/iseries_veth.c:1714: error: ‘struct device_driver’ has no member 
named ‘kobj’
make[2]: *** [drivers/net/iseries_veth.o] Error 1
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2


-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc5-mm1 regression - kernel warning on tcp_fastretrans_alert()

[Kamalesh Babulal]

Hi Andrew,

Following call trace is seen in 2.6.24-rc5-mm1 kernel also,it was reported
for 2.6.24-rc4-mm1 kernel http://lkml.org/lkml/2007/12/6/22

ls21b kernel: [ 7530.313408] WARNING: at net/ipv4/tcp_input.c:2533 
tcp_fastretrans_alert()
ls21b kernel: [ 7530.354051] Pid: 0, comm: swapper Not tainted 2.6.24-rc5-mm1 #1
ls21b kernel: [ 7530.389487]
ls21b kernel: [ 7530.389488] Call Trace:
ls21b kernel: [ 7530.413030][] 
tcp_fastretrans_alert+0x127/0xdaf
ls21b kernel: [ 7530.454295]  [] tcp_ack+0xf2f/0x10fe
ls21b kernel: [ 7530.485066]  [] 
tcp_rcv_established+0x695/0x79a
ls21b kernel: [ 7530.521542]  [] trace_hardirqs_off+0x39/0xdc
ls21b kernel: [ 7530.556468]  [] tcp_v4_do_rcv+0x37/0x3e1
ls21b kernel: [ 7530.589317]  [] tcp_v4_rcv+0xac7/0xb93
ls21b kernel: [ 7530.621126]  [] 
ip_local_deliver_finish+0x54/0x20f
ls21b kernel: [ 7530.659168]  [] 
ip_local_deliver_finish+0x134/0x20f
ls21b kernel: [ 7530.697724]  [] ip_local_deliver+0x72/0x7a
ls21b kernel: [ 7530.731609]  [] ip_rcv_finish+0x3c0/0x430
ls21b kernel: [ 7530.764977]  [] netif_receive_skb+0x10e/0x44d
ls21b kernel: [ 7530.800422]  [] ip_rcv+0x326/0x35d
ls21b kernel: [ 7530.830148]  [] netif_receive_skb+0x3df/0x44d
ls21b kernel: [ 7530.865603]  [] :bnx2:bnx2_poll+0x1262/0x14a4
ls21b kernel: [ 7530.901039]  [] __next_cpu+0x19/0x28
ls21b kernel: [ 7530.931805]  [] 
find_busiest_group+0x252/0x6da
ls21b kernel: [ 7530.967768]  [] trace_hardirqs_off+0x39/0xdc
ls21b kernel: [ 7531.002693]  [] trace_hardirqs_off+0x39/0xdc
ls21b kernel: [ 7531.037612]  [] check_chain_key+0x9c/0x15f
ls21b kernel: [ 7531.071501]  [] __lock_acquire+0xdee/0xf06
ls21b kernel: [ 7531.105386]  [] net_rx_action+0x75/0x234
ls21b kernel: [ 7531.138233]  [] net_rx_action+0x75/0x234
ls21b kernel: [ 7531.171074]  [] net_rx_action+0xec/0x234
ls21b kernel: [ 7531.203920]  [] __do_softirq+0x5f/0xe3
ls21b kernel: [ 7531.235721]  [] call_softirq+0x1c/0x28
ls21b kernel: [ 7531.267528]  [] do_softirq+0x45/0x108
ls21b kernel: [ 7531.298811]  [] irq_exit+0x4e/0x50
ls21b kernel: [ 7531.328540]  [] do_IRQ+0x171/0x194
ls21b kernel: [ 7531.358267]  [] ret_from_intr+0x0/0xf
ls21b kernel: [ 7531.389549][] default_idle+0x58/0x8a
ls21b kernel: [ 7531.425096]  [] default_idle+0x56/0x8a
ls21b kernel: [ 7531.456900]  [] default_idle+0x0/0x8a
ls21b kernel: [ 7531.488186]  [] cpu_idle+0xb5/0xec
ls21b kernel: [ 7531.517913]  [] start_secondary+0x3ca/0x3da


-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc5-mm1 kobject changes broken with hvcs driver on powerpc - regression

[Kamalesh Babulal]

Hi,

The kernel build fails with following error message

drivers/char/hvcs.c: In function 'hvcs_open':
drivers/char/hvcs.c:1180: error: wrong type argument to unary exclamation mark
make[2]: *** [drivers/char/hvcs.o] Error 1
make[2]: *** Waiting for unfinished jobs

This driver was broken in 2.6.24-rc4-mm1 either on powerpc, and the discussion
has been going on at

http://lkml.org/lkml/2007/12/5/141
http://lkml.org/lkml/2007/12/7/280
-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc5-mm1 kobject changes broken with hvcs driver on powerpc - regression

[Kamalesh Babulal]

Hi,

The kernel build fails with following error message

drivers/char/hvcs.c: In function 'hvcs_open':
drivers/char/hvcs.c:1180: error: wrong type argument to unary exclamation mark
make[2]: *** [drivers/char/hvcs.o] Error 1
make[2]: *** Waiting for unfinished jobs

This driver was broken in 2.6.24-rc4-mm1 either on powerpc, and the discussion
has been going on at

http://lkml.org/lkml/2007/12/5/141
http://lkml.org/lkml/2007/12/7/280
-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc5-mm1 regression - kernel warning on tcp_fastretrans_alert()

[Kamalesh Babulal]

Hi Andrew,

Following call trace is seen in 2.6.24-rc5-mm1 kernel also,it was reported
for 2.6.24-rc4-mm1 kernel http://lkml.org/lkml/2007/12/6/22

ls21b kernel: [ 7530.313408] WARNING: at net/ipv4/tcp_input.c:2533 
tcp_fastretrans_alert()
ls21b kernel: [ 7530.354051] Pid: 0, comm: swapper Not tainted 2.6.24-rc5-mm1 #1
ls21b kernel: [ 7530.389487]
ls21b kernel: [ 7530.389488] Call Trace:
ls21b kernel: [ 7530.413030]  IRQ  [80482374] 
tcp_fastretrans_alert+0x127/0xdaf
ls21b kernel: [ 7530.454295]  [804850cd] tcp_ack+0xf2f/0x10fe
ls21b kernel: [ 7530.485066]  [80488503] 
tcp_rcv_established+0x695/0x79a
ls21b kernel: [ 7530.521542]  [8025c46a] trace_hardirqs_off+0x39/0xdc
ls21b kernel: [ 7530.556468]  [8048eb70] tcp_v4_do_rcv+0x37/0x3e1
ls21b kernel: [ 7530.589317]  [80491764] tcp_v4_rcv+0xac7/0xb93
ls21b kernel: [ 7530.621126]  [80472c40] 
ip_local_deliver_finish+0x54/0x20f
ls21b kernel: [ 7530.659168]  [80472d20] 
ip_local_deliver_finish+0x134/0x20f
ls21b kernel: [ 7530.697724]  [804732cc] ip_local_deliver+0x72/0x7a
ls21b kernel: [ 7530.731609]  [80472b7c] ip_rcv_finish+0x3c0/0x430
ls21b kernel: [ 7530.764977]  [8044d9a6] netif_receive_skb+0x10e/0x44d
ls21b kernel: [ 7530.800422]  [80473223] ip_rcv+0x326/0x35d
ls21b kernel: [ 7530.830148]  [8044dc77] netif_receive_skb+0x3df/0x44d
ls21b kernel: [ 7530.865603]  [8814d44a] :bnx2:bnx2_poll+0x1262/0x14a4
ls21b kernel: [ 7530.901039]  [8034817d] __next_cpu+0x19/0x28
ls21b kernel: [ 7530.931805]  [802323a1] 
find_busiest_group+0x252/0x6da
ls21b kernel: [ 7530.967768]  [8025c46a] trace_hardirqs_off+0x39/0xdc
ls21b kernel: [ 7531.002693]  [8025c46a] trace_hardirqs_off+0x39/0xdc
ls21b kernel: [ 7531.037612]  [8025c21f] check_chain_key+0x9c/0x15f
ls21b kernel: [ 7531.071501]  [8026012b] __lock_acquire+0xdee/0xf06
ls21b kernel: [ 7531.105386]  [80450476] net_rx_action+0x75/0x234
ls21b kernel: [ 7531.138233]  [80450476] net_rx_action+0x75/0x234
ls21b kernel: [ 7531.171074]  [804504ed] net_rx_action+0xec/0x234
ls21b kernel: [ 7531.203920]  [80243f02] __do_softirq+0x5f/0xe3
ls21b kernel: [ 7531.235721]  [8020d5cc] call_softirq+0x1c/0x28
ls21b kernel: [ 7531.267528]  [8020ecdf] do_softirq+0x45/0x108
ls21b kernel: [ 7531.298811]  [80243ea1] irq_exit+0x4e/0x50
ls21b kernel: [ 7531.328540]  [8020ef3d] do_IRQ+0x171/0x194
ls21b kernel: [ 7531.358267]  [8020c8c6] ret_from_intr+0x0/0xf
ls21b kernel: [ 7531.389549]  EOI  [8020b1ec] default_idle+0x58/0x8a
ls21b kernel: [ 7531.425096]  [8020b1ea] default_idle+0x56/0x8a
ls21b kernel: [ 7531.456900]  [8020b194] default_idle+0x0/0x8a
ls21b kernel: [ 7531.488186]  [8020b2d3] cpu_idle+0xb5/0xec
ls21b kernel: [ 7531.517913]  [802226f4] start_secondary+0x3ca/0x3da


-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc5-mm1 - build failures due to kobject changes

[Kamalesh Babulal]

Hi Andrew,

The kernel build fails, due to kobjects changes

drivers/infiniband/hw/ehca/ehca_main.c: In function ‘ehca_module_init’:
drivers/infiniband/hw/ehca/ehca_main.c:947: error: ‘struct device_driver’ has 
no member named ‘kobj’
drivers/infiniband/hw/ehca/ehca_main.c: In function ‘ehca_module_exit’:
drivers/infiniband/hw/ehca/ehca_main.c:976: error: ‘struct device_driver’ has 
no member named ‘kobj’
make[3]: *** [drivers/infiniband/hw/ehca/ehca_main.o] Error 1
make[2]: *** [drivers/infiniband/hw/ehca] Error 2
make[1]: *** [drivers/infiniband] Error 2
make: *** [drivers] Error 2


drivers/net/ehea/ehea_main.c: In function ‘ehea_driver_sysfs_add’:
drivers/net/ehea/ehea_main.c:2812: error: ‘struct device_driver’ has no member 
named ‘kobj’
drivers/net/ehea/ehea_main.c:2815: error: ‘struct device_driver’ has no member 
named ‘kobj’
drivers/net/ehea/ehea_main.c:2818: error: ‘struct device_driver’ has no member 
named ‘kobj’
drivers/net/ehea/ehea_main.c: In function ‘ehea_driver_sysfs_remove’:
drivers/net/ehea/ehea_main.c:2830: error: ‘struct device_driver’ has no member 
named ‘kobj’
make[3]: *** [drivers/net/ehea/ehea_main.o] Error 1
make[2]: *** [drivers/net/ehea] Error 2
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2


  CC  drivers/net/iseries_veth.o
drivers/net/iseries_veth.c: In function ‘veth_module_init’:
drivers/net/iseries_veth.c:1714: error: ‘struct device_driver’ has no member 
named ‘kobj’
make[2]: *** [drivers/net/iseries_veth.o] Error 1
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2


-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc4-mm1 kobject changes broken with hvcs driver on powerpc

[Kamalesh Babulal]

: c0217b88 CTR: c029b71c
REGS: c0003c066fc0 TRAP: 0700   Not tainted  (2.6.24-rc4-mm1-autokern1)
MSR: 80029032   CR: 88002022  XER: 0001
TASK = c0003ef4c840[339] 'insmod' THREAD: c0003c064000 CPU: 0
GPR00:  c0003c067240 c05d32c0 c0003e0101a0 
GPR04: fff2 fffe 000a 0002 
GPR08:  c0003ef8ae50  c0449269 
GPR12: 24002084 c0515980   
GPR16:   0024  
GPR20: 1290 0002 c0003ef3f970 c0003ef3f970 
GPR24: 0001  c0003c039958 c0003c039918 
GPR28:  c0003ef3fa60 c058e588 c0003e010198 
NIP [c021908c] .kref_get+0x10/0x2c
LR [c0217b88] .kobject_get+0x20/0x3c
Call Trace:
[c0003c067240] [c0217a48] .kobject_set_name_vargs+0x38/0x60 
(unreliable)
[c0003c0672c0] [c0217ffc] .kobject_add+0x88/0x20c
[c0003c067350] [c029b7ec] .device_add+0xd0/0x648
[c0003c067410] [d0613c84] .scsi_alloc_target+0x238/0x414 [scsi_mod]
[c0003c0674e0] [d0614e70] .__scsi_scan_target+0xac/0x718 [scsi_mod]
[c0003c067630] [d061566c] .scsi_scan_channel+0x78/0xdc [scsi_mod]
[c0003c0676d0] [d06157f0] .scsi_scan_host_selected+0x120/0x194 
[scsi_mod]
[c0003c067780] [d0682148] .ibmvscsi_probe+0x450/0x4fc [ibmvscsic]
[c0003c067870] [c0025fe8] .vio_bus_probe+0x74/0x9c
[c0003c067900] [c029f2c8] .driver_probe_device+0x110/0x1ec
[c0003c067990] [c029f57c] .__driver_attach+0xd0/0x160
[c0003c067a20] [c0000029da58] .bus_for_each_dev+0x7c/0xcc
[c0003c067ad0] [c029f634] .driver_attach+0x28/0x40
[c0003c067b50] [c029e6a4] .bus_add_driver+0xe8/0x2b4
[c0003c067c00] [c029fd80] .driver_register+0x80/0x9c
[c0003c067c80] [c00260b0] .vio_register_driver+0x40/0x5c
[c0003c067d10] [d0682c04] .init_module+0x68/0xa4 [ibmvscsic]
[c0003c067da0] [c009301c] .sys_init_module+0xf4/0x1ac
[c0003c067e30] [c000872c] syscall_exit+0x0/0x40
Instruction dump:
7d808120 4e800020 38a0 4bfffad0 3801 9003 7c0004ac 4e800020 
8003 7c0007b4 2f80 40be0008 <0fe0> 7c001828 3001 7c00192d



-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc4-mm1 kobject changes broken with hvcs driver on powerpc

[Kamalesh Babulal]

Greg KH wrote:
> On Thu, Dec 06, 2007 at 11:49:59PM +0530, Balbir Singh wrote:
>> Kamalesh Babulal wrote:
>>> Hi Andrew,
>>>
>>> The 2.6.24-rc4-mm1 kernel build fails with build failure,
>>>
>>>   CC  drivers/char/hvcs.o
>>> drivers/char/hvcs.c: In function ‘hvcs_open’:
>>> drivers/char/hvcs.c:1180: error: wrong type argument to unary exclamation 
>>> mark
>>> make[2]: *** [drivers/char/hvcs.o] Error 1
>>> make[1]: *** [drivers/char] Error 2
>>> make: *** [drivers] Error 2
>>>
>>> The kref_get begin void return type, check for the kobject return type
>>> as in the previous kobject_get()
>>>
>>> if (!kref_get(>kref)) {
>>> spin_unlock_irqrestore(>lock, flags); 
>>> printk(KERN_ERR "HVCS: Kobject of open"
>>> " hvcs doesn't exist.\n");
>>> return -EFAULT; /* Is this the right return value? */
>>> }
>>>
>>> I have tested for the build failure only.
>>>
>>> Signed-off-by: Kamalesh Babulal <[EMAIL PROTECTED]>
>>> --
>>> --- linux-2.6.24-rc4/drivers/char/hvcs.c2007-12-05 12:17:37.0 
>>> +0530
>>> +++ linux-2.6.24-rc4/drivers/char/~hvcs.c   2007-12-05 19:17:12.0 
>>> +0530
>>> @@ -1177,12 +1177,8 @@ fast_open:
>>> hvcsd = tty->driver_data;
>>>
>>> spin_lock_irqsave(>lock, flags);
>>> -   if (!kref_get(>kref)) {
>>> -   spin_unlock_irqrestore(>lock, flags);
>>> -   printk(KERN_ERR "HVCS: Kobject of open"
>>> -   " hvcs doesn't exist.\n");
>>> -   return -EFAULT; /* Is this the right return value? */
>>> -   }
>>> +   kref_get(>kref);
>>> +   spin_unlock_irqrestore(>lock, flags);
>>>
>> Why release the spinlock here? It's done after the count is incremented.
>> This patch does not seem correct.
> 
> Doh, you are correct, I'll make sure that I fix this up before applying
> it.
> 
> thanks,
> 
> greg k-h

Sorry, my fault for overlooking that, thanks greg.

-- 
Thanks & Regards,
Kamalesh Babulal,

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc4-mm1 kobject changes broken with hvcs driver on powerpc

[Kamalesh Babulal]

Greg KH wrote:
 On Thu, Dec 06, 2007 at 11:49:59PM +0530, Balbir Singh wrote:
 Kamalesh Babulal wrote:
 Hi Andrew,

 The 2.6.24-rc4-mm1 kernel build fails with build failure,

   CC  drivers/char/hvcs.o
 drivers/char/hvcs.c: In function ‘hvcs_open’:
 drivers/char/hvcs.c:1180: error: wrong type argument to unary exclamation 
 mark
 make[2]: *** [drivers/char/hvcs.o] Error 1
 make[1]: *** [drivers/char] Error 2
 make: *** [drivers] Error 2

 The kref_get begin void return type, check for the kobject return type
 as in the previous kobject_get()

 if (!kref_get(hvcsd-kref)) {
 spin_unlock_irqrestore(hvcsd-lock, flags); 
 printk(KERN_ERR HVCS: Kobject of open
  hvcs doesn't exist.\n);
 return -EFAULT; /* Is this the right return value? */
 }

 I have tested for the build failure only.

 Signed-off-by: Kamalesh Babulal [EMAIL PROTECTED]
 --
 --- linux-2.6.24-rc4/drivers/char/hvcs.c2007-12-05 12:17:37.0 
 +0530
 +++ linux-2.6.24-rc4/drivers/char/~hvcs.c   2007-12-05 19:17:12.0 
 +0530
 @@ -1177,12 +1177,8 @@ fast_open:
 hvcsd = tty-driver_data;

 spin_lock_irqsave(hvcsd-lock, flags);
 -   if (!kref_get(hvcsd-kref)) {
 -   spin_unlock_irqrestore(hvcsd-lock, flags);
 -   printk(KERN_ERR HVCS: Kobject of open
 -hvcs doesn't exist.\n);
 -   return -EFAULT; /* Is this the right return value? */
 -   }
 +   kref_get(hvcsd-kref);
 +   spin_unlock_irqrestore(hvcsd-lock, flags);

 Why release the spinlock here? It's done after the count is incremented.
 This patch does not seem correct.
 
 Doh, you are correct, I'll make sure that I fix this up before applying
 it.
 
 thanks,
 
 greg k-h

Sorry, my fault for overlooking that, thanks greg.

-- 
Thanks  Regards,
Kamalesh Babulal,

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc4-mm1 kobject changes broken with hvcs driver on powerpc

[Kamalesh Babulal]

 [c0217b88] .kobject_get+0x20/0x3c
Call Trace:
[c0003c067240] [c0217a48] .kobject_set_name_vargs+0x38/0x60 
(unreliable)
[c0003c0672c0] [c0217ffc] .kobject_add+0x88/0x20c
[c0003c067350] [c029b7ec] .device_add+0xd0/0x648
[c0003c067410] [d0613c84] .scsi_alloc_target+0x238/0x414 [scsi_mod]
[c0003c0674e0] [d0614e70] .__scsi_scan_target+0xac/0x718 [scsi_mod]
[c0003c067630] [d061566c] .scsi_scan_channel+0x78/0xdc [scsi_mod]
[c0003c0676d0] [d06157f0] .scsi_scan_host_selected+0x120/0x194 
[scsi_mod]
[c0003c067780] [d0682148] .ibmvscsi_probe+0x450/0x4fc [ibmvscsic]
[c0003c067870] [c0025fe8] .vio_bus_probe+0x74/0x9c
[c0003c067900] [c029f2c8] .driver_probe_device+0x110/0x1ec
[c0003c067990] [c029f57c] .__driver_attach+0xd0/0x160
[c0003c067a20] [c029da58] .bus_for_each_dev+0x7c/0xcc
[c0003c067ad0] [c029f634] .driver_attach+0x28/0x40
[c0003c067b50] [c029e6a4] .bus_add_driver+0xe8/0x2b4
[c0003c067c00] [c029fd80] .driver_register+0x80/0x9c
[c0003c067c80] [c00260b0] .vio_register_driver+0x40/0x5c
[c0003c067d10] [d0682c04] .init_module+0x68/0xa4 [ibmvscsic]
[c0003c067da0] [c009301c] .sys_init_module+0xf4/0x1ac
[c0003c067e30] [c000872c] syscall_exit+0x0/0x40
Instruction dump:
7d808120 4e800020 38a0 4bfffad0 3801 9003 7c0004ac 4e800020 
8003 7c0007b4 2f80 40be0008 0fe0 7c001828 3001 7c00192d



-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc4-mm1 Kernel build fails on S390x

[Kamalesh Babulal]

Hi Andrew,

The 2.6.24-rc4-mm1 kernel build fails on s390x,

  CC  arch/s390/kernel/traps.o
In file included from include/asm/thread_info.h:39,
 from include/linux/thread_info.h:21,
 from include/linux/preempt.h:9,
 from include/linux/spinlock.h:49,
 from include/linux/seqlock.h:29,
 from include/linux/time.h:8,
 from include/linux/timex.h:57,
 from include/linux/sched.h:53,
 from arch/s390/kernel/traps.c:17:
include/asm/processor.h:191: warning: "struct seq_file" declared inside 
parameter list
include/asm/processor.h:191: warning: its scope is only this definition or 
declaration, which is probably not what you want
arch/s390/kernel/traps.c: In function `task_show_regs':
arch/s390/kernel/traps.c:226: error: implicit declaration of function 
`seq_printf'
make[1]: *** [arch/s390/kernel/traps.o] Error 1
make: *** [arch/s390/kernel] Error 2

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc4-mm1 kobject changes broken with hvcs driver on powerpc

[Kamalesh Babulal]

Hi Andrew,

The 2.6.24-rc4-mm1 kernel build fails with build failure,

  CC  drivers/char/hvcs.o
drivers/char/hvcs.c: In function ‘hvcs_open’:
drivers/char/hvcs.c:1180: error: wrong type argument to unary exclamation mark
make[2]: *** [drivers/char/hvcs.o] Error 1
make[1]: *** [drivers/char] Error 2
make: *** [drivers] Error 2

The kref_get begin void return type, check for the kobject return type
as in the previous kobject_get()
 
if (!kref_get(>kref)) {
spin_unlock_irqrestore(>lock, flags); 
printk(KERN_ERR "HVCS: Kobject of open"
" hvcs doesn't exist.\n");
return -EFAULT; /* Is this the right return value? */
}

I have tested for the build failure only.

Signed-off-by: Kamalesh Babulal <[EMAIL PROTECTED]>
--
--- linux-2.6.24-rc4/drivers/char/hvcs.c2007-12-05 12:17:37.0 
+0530
+++ linux-2.6.24-rc4/drivers/char/~hvcs.c   2007-12-05 19:17:12.0 
+0530
@@ -1177,12 +1177,8 @@ fast_open:
hvcsd = tty->driver_data;
 
spin_lock_irqsave(>lock, flags);
-   if (!kref_get(>kref)) {
-   spin_unlock_irqrestore(>lock, flags);
-   printk(KERN_ERR "HVCS: Kobject of open"
-   " hvcs doesn't exist.\n");
-   return -EFAULT; /* Is this the right return value? */
-   }
+   kref_get(>kref);
+   spin_unlock_irqrestore(>lock, flags);
 
hvcsd->open_count++;
 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc4-mm1: kobj changes fallout on powerpc

[Kamalesh Babulal]

On Wed, Dec 05, 2007 at 03:15:15AM -0600, Olof Johansson wrote:
> powerpc allyesconfig fails on the following two drivers (iseries_defconfig
> fails for the veth one):
> 
> drivers/net/ehea/ehea_main.c: In function 'ehea_driver_sysfs_add':
> drivers/net/ehea/ehea_main.c:2812: error: 'struct device_driver' has no 
> member named 'kobj'
> drivers/net/ehea/ehea_main.c:2815: error: 'struct device_driver' has no 
> member named 'kobj'
> drivers/net/ehea/ehea_main.c:2818: error: 'struct device_driver' has no 
> member named 'kobj'
> drivers/net/ehea/ehea_main.c: In function 'ehea_driver_sysfs_remove':
> drivers/net/ehea/ehea_main.c:2830: error: 'struct device_driver' has no 
> member named 'kobj'
> drivers/net/iseries_veth.c: In function 'veth_module_init':
> drivers/net/iseries_veth.c:1714: error: 'struct device_driver' has no member 
> named 'kobj'
> 
> I'm guessing it's some of Greg's kobj/driver patches that missed to
> change this, but it's not obvious to me how it should be fixed.
> 
> 
> -Olof
Hi,

Probably this patch should fix the build failure (The kobject related
structure have been moved to driver_private struct).

Signed-off-by: Kamalesh Babulal <[EMAIL PROTECTED]>
--
--- linux-2.6.24-rc4/drivers/net/ehea/ehea_main.c   2007-12-04 
09:56:10.0 +0530
+++ linux-2.6.24-rc4/drivers/net/ehea/~ehea_main.c  2007-12-05 
18:01:31.0 +0530
@@ -2809,7 +2809,7 @@ static int ehea_driver_sysfs_add(struct 
 {
int ret;
 
-   ret = sysfs_create_link(>kobj, >kobj,
+   ret = sysfs_create_link(>driver_private->kobj, >kobj,
kobject_name(>kobj));
if (ret == 0) {
ret = sysfs_create_link(>kobj, >kobj,
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc4-mm1: kobj changes fallout on powerpc

[Kamalesh Babulal]

On Wed, Dec 05, 2007 at 03:15:15AM -0600, Olof Johansson wrote:
 powerpc allyesconfig fails on the following two drivers (iseries_defconfig
 fails for the veth one):
 
 drivers/net/ehea/ehea_main.c: In function 'ehea_driver_sysfs_add':
 drivers/net/ehea/ehea_main.c:2812: error: 'struct device_driver' has no 
 member named 'kobj'
 drivers/net/ehea/ehea_main.c:2815: error: 'struct device_driver' has no 
 member named 'kobj'
 drivers/net/ehea/ehea_main.c:2818: error: 'struct device_driver' has no 
 member named 'kobj'
 drivers/net/ehea/ehea_main.c: In function 'ehea_driver_sysfs_remove':
 drivers/net/ehea/ehea_main.c:2830: error: 'struct device_driver' has no 
 member named 'kobj'
 drivers/net/iseries_veth.c: In function 'veth_module_init':
 drivers/net/iseries_veth.c:1714: error: 'struct device_driver' has no member 
 named 'kobj'
 
 I'm guessing it's some of Greg's kobj/driver patches that missed to
 change this, but it's not obvious to me how it should be fixed.
 
 
 -Olof
Hi,

Probably this patch should fix the build failure (The kobject related
structure have been moved to driver_private struct).

Signed-off-by: Kamalesh Babulal [EMAIL PROTECTED]
--
--- linux-2.6.24-rc4/drivers/net/ehea/ehea_main.c   2007-12-04 
09:56:10.0 +0530
+++ linux-2.6.24-rc4/drivers/net/ehea/~ehea_main.c  2007-12-05 
18:01:31.0 +0530
@@ -2809,7 +2809,7 @@ static int ehea_driver_sysfs_add(struct 
 {
int ret;
 
-   ret = sysfs_create_link(driver-kobj, dev-kobj,
+   ret = sysfs_create_link(driver-driver_private-kobj, dev-kobj,
kobject_name(dev-kobj));
if (ret == 0) {
ret = sysfs_create_link(dev-kobj, driver-kobj,
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc4-mm1 kobject changes broken with hvcs driver on powerpc

[Kamalesh Babulal]

Hi Andrew,

The 2.6.24-rc4-mm1 kernel build fails with build failure,

  CC  drivers/char/hvcs.o
drivers/char/hvcs.c: In function ‘hvcs_open’:
drivers/char/hvcs.c:1180: error: wrong type argument to unary exclamation mark
make[2]: *** [drivers/char/hvcs.o] Error 1
make[1]: *** [drivers/char] Error 2
make: *** [drivers] Error 2

The kref_get begin void return type, check for the kobject return type
as in the previous kobject_get()
 
if (!kref_get(hvcsd-kref)) {
spin_unlock_irqrestore(hvcsd-lock, flags); 
printk(KERN_ERR HVCS: Kobject of open
 hvcs doesn't exist.\n);
return -EFAULT; /* Is this the right return value? */
}

I have tested for the build failure only.

Signed-off-by: Kamalesh Babulal [EMAIL PROTECTED]
--
--- linux-2.6.24-rc4/drivers/char/hvcs.c2007-12-05 12:17:37.0 
+0530
+++ linux-2.6.24-rc4/drivers/char/~hvcs.c   2007-12-05 19:17:12.0 
+0530
@@ -1177,12 +1177,8 @@ fast_open:
hvcsd = tty-driver_data;
 
spin_lock_irqsave(hvcsd-lock, flags);
-   if (!kref_get(hvcsd-kref)) {
-   spin_unlock_irqrestore(hvcsd-lock, flags);
-   printk(KERN_ERR HVCS: Kobject of open
-hvcs doesn't exist.\n);
-   return -EFAULT; /* Is this the right return value? */
-   }
+   kref_get(hvcsd-kref);
+   spin_unlock_irqrestore(hvcsd-lock, flags);
 
hvcsd-open_count++;
 
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc4-mm1 Kernel build fails on S390x

[Kamalesh Babulal]

Hi Andrew,

The 2.6.24-rc4-mm1 kernel build fails on s390x,

  CC  arch/s390/kernel/traps.o
In file included from include/asm/thread_info.h:39,
 from include/linux/thread_info.h:21,
 from include/linux/preempt.h:9,
 from include/linux/spinlock.h:49,
 from include/linux/seqlock.h:29,
 from include/linux/time.h:8,
 from include/linux/timex.h:57,
 from include/linux/sched.h:53,
 from arch/s390/kernel/traps.c:17:
include/asm/processor.h:191: warning: struct seq_file declared inside 
parameter list
include/asm/processor.h:191: warning: its scope is only this definition or 
declaration, which is probably not what you want
arch/s390/kernel/traps.c: In function `task_show_regs':
arch/s390/kernel/traps.c:226: error: implicit declaration of function 
`seq_printf'
make[1]: *** [arch/s390/kernel/traps.o] Error 1
make: *** [arch/s390/kernel] Error 2

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] 2.6.24-rc3-git2 softlockup detected

[Kamalesh Babulal]

Ingo Molnar wrote:
> * Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> 
>>> So 2.6.24-rc3 was OK and 2.6.24-rc3-git2 is not?
>> Yes, the 2.6.24-rc3 was Ok and this is seen from 2.6.24-rc3-git2/3/4.
> 
> just to make sure: this is a real lockup and failed bootup (or device 
> init), not just a message, right?
> 
>   Ingo
> --

Hi Ingo,

This softlockup is seen in the 2.6.24-rc4 either and looks like a message 
because 
this is seen while running tbench and machine continues running other test's 
after 
the softlockup messages and some times seen with the bootup, but the machines 
reaches the 
login prompt and able to continue running tests.

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[build failure] Re: Linux 2.6.24-rc4 on S390x

[Kamalesh Babulal]

Hi,

The patch ctc: make use of alloc_netdev() (commit 
1c1478859017452a1179dbbdf7b9eb5b48438746)
introduces the build failure

  CC [M]  drivers/s390/net/fsm.o
  CC [M]  drivers/s390/net/smsgiucv.o
  CC [M]  drivers/s390/net/ctcmain.o
drivers/s390/net/ctcmain.c: In function `ctc_init_netdevice':
drivers/s390/net/ctcmain.c:2805: error: implicit declaration of function 
`SET_MODULE_OWNER'
make[2]: *** [drivers/s390/net/ctcmain.o] Error 1
make[1]: *** [drivers/s390/net] Error 2
make: *** [drivers/s390] Error 2

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[build failure] Re: Linux 2.6.24-rc4 on S390x

[Kamalesh Babulal]

Hi,

The patch ctc: make use of alloc_netdev() (commit 
1c1478859017452a1179dbbdf7b9eb5b48438746)
introduces the build failure

  CC [M]  drivers/s390/net/fsm.o
  CC [M]  drivers/s390/net/smsgiucv.o
  CC [M]  drivers/s390/net/ctcmain.o
drivers/s390/net/ctcmain.c: In function `ctc_init_netdevice':
drivers/s390/net/ctcmain.c:2805: error: implicit declaration of function 
`SET_MODULE_OWNER'
make[2]: *** [drivers/s390/net/ctcmain.o] Error 1
make[1]: *** [drivers/s390/net] Error 2
make: *** [drivers/s390] Error 2

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] 2.6.24-rc3-git2 softlockup detected

[Kamalesh Babulal]

Ingo Molnar wrote:
 * Kamalesh Babulal [EMAIL PROTECTED] wrote:
 
 So 2.6.24-rc3 was OK and 2.6.24-rc3-git2 is not?
 Yes, the 2.6.24-rc3 was Ok and this is seen from 2.6.24-rc3-git2/3/4.
 
 just to make sure: this is a real lockup and failed bootup (or device 
 init), not just a message, right?
 
   Ingo
 --

Hi Ingo,

This softlockup is seen in the 2.6.24-rc4 either and looks like a message 
because 
this is seen while running tbench and machine continues running other test's 
after 
the softlockup messages and some times seen with the bootup, but the machines 
reaches the 
login prompt and able to continue running tests.

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] 2.6.24-rc3-mm2 kernel bug on nfs & cifs mounted partitions

[Kamalesh Babulal]

Jan Kara wrote:
> On Thu 29-11-07 17:27:08, Kamalesh Babulal wrote:
>> Andrew Morton wrote:
>>> On Thu, 29 Nov 2007 14:30:14 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> 
>>> wrote:
>>>
>>>> Hi Andrew,
>>>>
>>>> While running file system stress on nfs and cifs mounted partitions, the 
>>>> machine
>>>> drops to xmon
>>>>
>>>> 1:mon> e
>>>> cpu 0x1: Vector: 300 (Data Access) at [c00080a9f880]
>>>> pc: c01392c8: .inotify_inode_queue_event+0x50/0x158
>>>> lr: c01074d0: .vfs_link+0x204/0x298
>>>> sp: c00080a9fb00
>>>>msr: 80009032
>>>>dar: 280 
>>>>  dsisr: 4001
>>>>   current = 0xc000c8e6f670
>>>>   paca= 0xc0512c00
>>>> pid   = 2848, comm = fsstress
>>>> 1:mon> t
>>>> [c00080a9fbd0] c01074d0 .vfs_link+0x204/0x298
>>>> [c00080a9fc70] c010b6e0 .sys_linkat+0x134/0x1b4
>>>> [c00080a9fe30] c000872c syscall_exit+0x0/0x40
>>>> --- Exception: c00 (System Call) at 0ff1bdfc
>>>> SP (ffeaed10) is in userspace
>>>> 1:mon> r
>>>> R00 = c01074d0   R16 = 
>>>> R01 = c00080a9fb00   R17 = 
>>>> R02 = c060c380   R18 = 
>>>> R03 =    R19 = 
>>>> R04 = 0004   R20 = 
>>>> R05 =    R21 = 
>>>> R06 =    R22 = 
>>>> R07 =    R23 = 0004
>>>> R08 =    R24 = 0280
>>>> R09 =    R25 = f000
>>>> R10 = 0001   R26 = c00082827790
>>>> R11 = c03963e8   R27 = c000828275a0
>>>> R12 = d0deec78   R28 = 
>>>> R13 = c0512c00   R29 = c0007b18fcf0
>>>> R14 =    R30 = c05bc088
>>>> R15 =    R31 = 
>>>> pc  = c01392c8 .inotify_inode_queue_event+0x50/0x158
>>>> lr  = c01074d0 .vfs_link+0x204/0x298
>>>> msr = 80009032   cr  = 24000882
>>>> ctr = c03963e8   xer =    trap =  300 
>>>> dar = 0280   dsisr = 4001
>>>>
>>>>
>>>> The gdb output shows 
>>>>
>>>> 0xc01076d4 is in vfs_symlink (include/linux/fsnotify.h:108).
>>>> 103  * fsnotify_create - 'name' was linked in
>>>> 104  */  
>>>> 105 static inline void fsnotify_create(struct inode *inode, struct 
>>>> dentry *dentry)
>>>> 106 {   
>>>> 107 inode_dir_notify(inode, DN_CREATE);
>>>> 108 inotify_inode_queue_event(inode, IN_CREATE, 0, 
>>>> dentry->d_name.name,
>>>> 109   dentry->d_inode);
>>>> 110 audit_inode_child(dentry->d_name.name, dentry, inode);
>>>> 111 }   
>>>> 112
>>>>
>>> If it is reproducible can you please try reverting
>>> inotify-send-in_attrib-events-when-link-count-changes.patch?
>> Hi Andrew,
>>
>> reverting the patch 
>> inotify-send-in_attrib-events-when-link-count-changes.patch, the 
>> bug is not reproduced.
>   OK, it's a problem with CIFS. Its cifs_hardlink() function doesn't call
> d_instantiate() and thus returns a dentry with d_inode set to NULL. I'm not
> sure if such behavior is really correct but anyway, attached is a new
> version of the patch which should handle it gracefully. Kamalesh, can you
> please give it a try? Thanks.
> 
>   Honza
Hi Jan,

Thanks, the patch fixes the bug.

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] 2.6.24-rc3-mm2 kernel bug on nfs cifs mounted partitions

[Kamalesh Babulal]

Jan Kara wrote:
 On Thu 29-11-07 17:27:08, Kamalesh Babulal wrote:
 Andrew Morton wrote:
 On Thu, 29 Nov 2007 14:30:14 +0530 Kamalesh Babulal [EMAIL PROTECTED] 
 wrote:

 Hi Andrew,

 While running file system stress on nfs and cifs mounted partitions, the 
 machine
 drops to xmon

 1:mon e
 cpu 0x1: Vector: 300 (Data Access) at [c00080a9f880]
 pc: c01392c8: .inotify_inode_queue_event+0x50/0x158
 lr: c01074d0: .vfs_link+0x204/0x298
 sp: c00080a9fb00
msr: 80009032
dar: 280 
  dsisr: 4001
   current = 0xc000c8e6f670
   paca= 0xc0512c00
 pid   = 2848, comm = fsstress
 1:mon t
 [c00080a9fbd0] c01074d0 .vfs_link+0x204/0x298
 [c00080a9fc70] c010b6e0 .sys_linkat+0x134/0x1b4
 [c00080a9fe30] c000872c syscall_exit+0x0/0x40
 --- Exception: c00 (System Call) at 0ff1bdfc
 SP (ffeaed10) is in userspace
 1:mon r
 R00 = c01074d0   R16 = 
 R01 = c00080a9fb00   R17 = 
 R02 = c060c380   R18 = 
 R03 =    R19 = 
 R04 = 0004   R20 = 
 R05 =    R21 = 
 R06 =    R22 = 
 R07 =    R23 = 0004
 R08 =    R24 = 0280
 R09 =    R25 = f000
 R10 = 0001   R26 = c00082827790
 R11 = c03963e8   R27 = c000828275a0
 R12 = d0deec78   R28 = 
 R13 = c0512c00   R29 = c0007b18fcf0
 R14 =    R30 = c05bc088
 R15 =    R31 = 
 pc  = c01392c8 .inotify_inode_queue_event+0x50/0x158
 lr  = c01074d0 .vfs_link+0x204/0x298
 msr = 80009032   cr  = 24000882
 ctr = c03963e8   xer =    trap =  300 
 dar = 0280   dsisr = 4001


 The gdb output shows 

 0xc01076d4 is in vfs_symlink (include/linux/fsnotify.h:108).
 103  * fsnotify_create - 'name' was linked in
 104  */  
 105 static inline void fsnotify_create(struct inode *inode, struct 
 dentry *dentry)
 106 {   
 107 inode_dir_notify(inode, DN_CREATE);
 108 inotify_inode_queue_event(inode, IN_CREATE, 0, 
 dentry-d_name.name,
 109   dentry-d_inode);
 110 audit_inode_child(dentry-d_name.name, dentry, inode);
 111 }   
 112

 If it is reproducible can you please try reverting
 inotify-send-in_attrib-events-when-link-count-changes.patch?
 Hi Andrew,

 reverting the patch 
 inotify-send-in_attrib-events-when-link-count-changes.patch, the 
 bug is not reproduced.
   OK, it's a problem with CIFS. Its cifs_hardlink() function doesn't call
 d_instantiate() and thus returns a dentry with d_inode set to NULL. I'm not
 sure if such behavior is really correct but anyway, attached is a new
 version of the patch which should handle it gracefully. Kamalesh, can you
 please give it a try? Thanks.
 
   Honza
Hi Jan,

Thanks, the patch fixes the bug.

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] 2.6.24-rc3-git2 softlockup detected

[Kamalesh Babulal]

Andrew Morton wrote:
> On Thu, 29 Nov 2007 23:00:47 -0800 Andrew Morton <[EMAIL PROTECTED]> wrote:
> 
>> On Fri, 30 Nov 2007 01:39:29 -0500 Kyle McMartin <[EMAIL PROTECTED]> wrote:
>>
>>> On Thu, Nov 29, 2007 at 12:35:33AM -0800, Andrew Morton wrote:
>>>> ten million is close enough to infinity for me to assume that we broke the
>>>> driver and that's never going to terminate.
>>>>
>>> how about this? doesn't break things on my pa8800:
>>>
>>> diff --git a/drivers/scsi/sym53c8xx_2/sym_hipd.c 
>>> b/drivers/scsi/sym53c8xx_2/sym_hipd.c
>>> index 463f119..ef01cb1 100644
>>> --- a/drivers/scsi/sym53c8xx_2/sym_hipd.c
>>> +++ b/drivers/scsi/sym53c8xx_2/sym_hipd.c
>>> @@ -1037,10 +1037,13 @@ restart_test:
>>> /*
>>>  *  Wait 'til done (with timeout)
>>>  */
>>> -   for (i=0; i>> +   do {
>>> if (INB(np, nc_istat) & (INTF|SIP|DIP))
>>> break;
>>> -   if (i>=SYM_SNOOP_TIMEOUT) {
>>> +   msleep(10);
>>> +   } while (i++ < SYM_SNOOP_TIMEOUT);
>>> +
>>> +   if (i >= SYM_SNOOP_TIMEOUT) {
>>> printf ("CACHE TEST FAILED: timeout.\n");
>>> return (0x20);
>>> }
>>> diff --git a/drivers/scsi/sym53c8xx_2/sym_hipd.h 
>>> b/drivers/scsi/sym53c8xx_2/sym_hipd.h
>>> index ad07880..85c483b 100644
>>> --- a/drivers/scsi/sym53c8xx_2/sym_hipd.h
>>> +++ b/drivers/scsi/sym53c8xx_2/sym_hipd.h
>>> @@ -339,7 +339,7 @@
>>>  /*
>>>   *  Misc.
>>>   */
>>> -#define SYM_SNOOP_TIMEOUT (1000)
>>> +#define SYM_SNOOP_TIMEOUT (1000)
>>>  #define BUS_8_BIT  0
>>>  #define BUS_16_BIT 1
>>>  
>> That might be the fix, but do we know what we're actually fixing?  afaik
>> 2.6.24-rc3 doesn't get this timeout, 2.6.24-rc3-mm2 does get it and we
>> don't know why?
>>
> 
> 
> 
> 
> 
> So 2.6.24-rc3 was OK and 2.6.24-rc3-git2 is not?

Yes, the 2.6.24-rc3 was Ok and this is seen from 2.6.24-rc3-git2/3/4.

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] 2.6.24-rc3-mm2 soft lockup while running tbench

[Kamalesh Babulal]

Andrew Morton wrote:
> On Wed, 28 Nov 2007 20:03:22 +0530
> Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> 
>> Hi Andrew,
>>
>> while running tbench on the powerpc with 2.6.24-rc3-mm2 softlock up occurs
>>
>> BUG: soft lockup - CPU#0 stuck for 11s! [tbench:12183]
>> NIP: c00ac978 LR: c00acff0 CTR: c005c648
>> REGS: C0076F0F3200 TRAP: 0901   Not tainted  (2.6.24-rc3-mm2-autotest)
>> MSR: 80009032   CR: 44000482  XER: 
>> TASK = C0076F4BC000[12183] 'tbench' THREAD: C0076F0F CPU: 0
>> NIP [c00ac978] .get_page_from_freelist+0x1cc/0x754
>> LR [c00acff0] .__alloc_pages+0xb0/0x3a8
>> Call Trace:
>> [c0076f0f3480] [c0076f0f3560] 0xc0076f0f3560 (unreliable)
>> [c0076f0f3590] [c00acff0] .__alloc_pages+0xb0/0x3a8
>> [c0076f0f3680] [c00ce2e4] .alloc_pages_current+0xa8/0xc8
>> [c0076f0f3710] [c00ac6ec] .__get_free_pages+0x20/0x70
>> [c0076f0f3790] [c00d75c8] .__kmalloc_node_track_caller+0x60/0x148
>> [c0076f0f3840] [c02c22b0] .__alloc_skb+0x98/0x184
>> [c0076f0f38f0] [c0306cd8] .tcp_sendmsg+0x1fc/0xe24
>> [c0076f0f3a10] [c02b963c] .sock_sendmsg+0xe4/0x128
>> [c0076f0f3c10] [c02ba4ec] .sys_sendto+0xd4/0x120
>> [c0076f0f3d90] [c02df2f8] .compat_sys_socketcall+0x148/0x214
>> [c0076f0f3e30] [c000872c] syscall_exit+0x0/0x40
>> Instruction dump:
>> 720b0001 eb97 40820070 7202 4182000c e8bc 4818 72080004 
>> 4182000c e8bc0008 4808 e8bc0010  7f83e378 7de407b4 7e078378 
>>
> 
> hm.  Beats me.  Does the machine recover OK?
> -
Hi Andrew,

In the set of test cases ran serially, the softlockup in seen in tbench,
then the remaining test cases get to run successfully after the softlockup.

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] 2.6.24-rc3-mm2 kernel bug on nfs & cifs mounted partitions

[Kamalesh Babulal]

Jan Kara wrote:
> On Thu 29-11-07 17:27:08, Kamalesh Babulal wrote:
>> Andrew Morton wrote:
>>> On Thu, 29 Nov 2007 14:30:14 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> 
>>> wrote:
>>>
>>>> Hi Andrew,
>>>>
>>>> While running file system stress on nfs and cifs mounted partitions, the 
>>>> machine
>>>> drops to xmon
>>>>
>>>> 1:mon> e
>>>> cpu 0x1: Vector: 300 (Data Access) at [c00080a9f880]
>>>> pc: c01392c8: .inotify_inode_queue_event+0x50/0x158
>>>> lr: c01074d0: .vfs_link+0x204/0x298
>>>> sp: c00080a9fb00
>>>>msr: 80009032
>>>>dar: 280 
>>>>  dsisr: 4001
>>>>   current = 0xc000c8e6f670
>>>>   paca= 0xc0512c00
>>>> pid   = 2848, comm = fsstress
>>>> 1:mon> t
>>>> [c00080a9fbd0] c01074d0 .vfs_link+0x204/0x298
>>>> [c00080a9fc70] c010b6e0 .sys_linkat+0x134/0x1b4
>>>> [c00080a9fe30] c000872c syscall_exit+0x0/0x40
>>>> --- Exception: c00 (System Call) at 0ff1bdfc
>>>> SP (ffeaed10) is in userspace
>>>> 1:mon> r
>>>> R00 = c01074d0   R16 = 
>>>> R01 = c00080a9fb00   R17 = 
>>>> R02 = c060c380   R18 = 
>>>> R03 =    R19 = 
>>>> R04 = 0004   R20 = 
>>>> R05 =    R21 = 
>>>> R06 =    R22 = 
>>>> R07 =    R23 = 0004
>>>> R08 =    R24 = 0280
>>>> R09 =    R25 = f000
>>>> R10 = 0001   R26 = c00082827790
>>>> R11 = c03963e8   R27 = c000828275a0
>>>> R12 = d0deec78   R28 = 
>>>> R13 = c0512c00   R29 = c0007b18fcf0
>>>> R14 =    R30 = c05bc088
>>>> R15 =    R31 = 
>>>> pc  = c01392c8 .inotify_inode_queue_event+0x50/0x158
>>>> lr  = c01074d0 .vfs_link+0x204/0x298
>>>> msr = 80009032   cr  = 24000882
>>>> ctr = c03963e8   xer =    trap =  300 
>>>> dar = 0280   dsisr = 4001
>>>>
>>>>
>>>> The gdb output shows 
>>>>
>>>> 0xc01076d4 is in vfs_symlink (include/linux/fsnotify.h:108).
>>>> 103  * fsnotify_create - 'name' was linked in
>>>> 104  */  
>>>> 105 static inline void fsnotify_create(struct inode *inode, struct 
>>>> dentry *dentry)
>>>> 106 {   
>>>> 107 inode_dir_notify(inode, DN_CREATE);
>>>> 108 inotify_inode_queue_event(inode, IN_CREATE, 0, 
>>>> dentry->d_name.name,
>>>> 109   dentry->d_inode);
>>>> 110 audit_inode_child(dentry->d_name.name, dentry, inode);
>>>> 111 }   
>>>> 112
>>>>
>>> If it is reproducible can you please try reverting
>>> inotify-send-in_attrib-events-when-link-count-changes.patch?
>> Hi Andrew,
>>
>> reverting the patch 
>> inotify-send-in_attrib-events-when-link-count-changes.patch, the 
>> bug is not reproduced.
>   OK, thanks for testing. I was trying to reproduce the problem locally but
> without success so far - I guess it's either NFS or CIFS which makes the
> problem appear. I'll investigate more.
> 
>   Honza

Hi Jan,

I was running file system stress parallely on NFS and CIFS mounted partitions.
  

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] 2.6.24-rc3-mm2 kernel bug on nfs & cifs mounted partitions

[Kamalesh Babulal]

Andrew Morton wrote:
> On Thu, 29 Nov 2007 14:30:14 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> 
>> Hi Andrew,
>>
>> While running file system stress on nfs and cifs mounted partitions, the 
>> machine
>> drops to xmon
>>
>> 1:mon> e
>> cpu 0x1: Vector: 300 (Data Access) at [c00080a9f880]
>> pc: c01392c8: .inotify_inode_queue_event+0x50/0x158
>> lr: c01074d0: .vfs_link+0x204/0x298
>> sp: c00080a9fb00
>>msr: 80009032
>>dar: 280 
>>  dsisr: 4001
>>   current = 0xc000c8e6f670
>>   paca= 0xc0512c00
>> pid   = 2848, comm = fsstress
>> 1:mon> t
>> [c00080a9fbd0] c01074d0 .vfs_link+0x204/0x298
>> [c00080a9fc70] c010b6e0 .sys_linkat+0x134/0x1b4
>> [c00080a9fe30] c000872c syscall_exit+0x0/0x40
>> --- Exception: c00 (System Call) at 0ff1bdfc
>> SP (ffeaed10) is in userspace
>> 1:mon> r
>> R00 = c01074d0   R16 = 
>> R01 = c00080a9fb00   R17 = 
>> R02 = c060c380   R18 = 
>> R03 =    R19 = 
>> R04 = 0004   R20 = 
>> R05 =    R21 = 
>> R06 =    R22 = 
>> R07 =    R23 = 0004
>> R08 =    R24 = 0280
>> R09 =    R25 = f000
>> R10 = 0001   R26 = c00082827790
>> R11 = c03963e8   R27 = c000828275a0
>> R12 = d0deec78   R28 = 
>> R13 = c0512c00   R29 = c0007b18fcf0
>> R14 =    R30 = c05bc088
>> R15 =    R31 = 
>> pc  = c01392c8 .inotify_inode_queue_event+0x50/0x158
>> lr  = c01074d0 .vfs_link+0x204/0x298
>> msr = 80009032   cr  = 24000882
>> ctr = c03963e8   xer =    trap =  300 
>> dar = 0280   dsisr = 4001
>>
>>
>> The gdb output shows 
>>
>> 0xc01076d4 is in vfs_symlink (include/linux/fsnotify.h:108).
>> 103  * fsnotify_create - 'name' was linked in
>> 104  */  
>> 105 static inline void fsnotify_create(struct inode *inode, struct 
>> dentry *dentry)
>> 106 {   
>> 107 inode_dir_notify(inode, DN_CREATE);
>> 108 inotify_inode_queue_event(inode, IN_CREATE, 0, 
>> dentry->d_name.name,
>> 109   dentry->d_inode);
>> 110 audit_inode_child(dentry->d_name.name, dentry, inode);
>> 111 }   
>> 112
>>
> 
> If it is reproducible can you please try reverting
> inotify-send-in_attrib-events-when-link-count-changes.patch?

Hi Andrew,

reverting the patch 
inotify-send-in_attrib-events-when-link-count-changes.patch, the 
bug is not reproduced.

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] 2.6.24-rc3-git2 softlockup detected

[Kamalesh Babulal]

Andrew Morton wrote:
> On Thu, 29 Nov 2007 12:01:08 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> 
>> Andrew Morton wrote:
>>> On Wed, 28 Nov 2007 12:47:19 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> 
>>> wrote:
>>>
>>>> Andrew Morton wrote:
>>>>> On Wed, 28 Nov 2007 11:59:00 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> 
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>> (cc linux-scsi, for sym53c8xx)
>>>>>
>>>>>> Soft lockup is detected while bootup with 2.6.24-rc3-git2 on powerbox
>>>>> I assume this is a post-2.6.23 regression?
>>>>>
>>>>>> BUG: soft lockup - CPU#1 stuck for 11s! [insmod:375]
>>>>>> NIP: c002f02c LR: d01414fc CTR: c002f018
>>>>>> REGS: c0077cbef0b0 TRAP: 0901   Not tainted  
>>>>>> (2.6.24-rc3-git2-autotest)
>>>>>> MSR: 80009032   CR: 24022088  XER: 
>>>>>> TASK = c0077cbd8000[375] 'insmod' THREAD: c0077cbec000 CPU: 1
>>>>>> GPR00: d01414fc c0077cbef330 c052b930 
>>>>>> d80080002014 
>>>>>> GPR04: d8008000202c  c0077ca1cb00 
>>>>>> d014ce54 
>>>>>> GPR08: c0077ca1c63c  002a 
>>>>>> c002f018 
>>>>>> GPR12: d0143610 c0473d00 
>>>>>> NIP [c002f02c] .ioread8+0x14/0x60
>>>>>> LR [d01414fc] .sym_hcb_attach+0x1188/0x1378 [sym53c8xx]
>>>>>> Call Trace:
>>>>>> [c0077cbef330] [c0077cbef3c0] 0xc0077cbef3c0 (unreliable)
>>>>>> [c0077cbef3a0] [d01414fc] .sym_hcb_attach+0x1188/0x1378 
>>>>>> [sym53c8xx]
>>>>>> [c0077cbef470] [d01395f8] .sym2_probe+0x700/0x99c [sym53c8xx]
>>>>>> [c0077cbef710] [c01bc118] .pci_device_probe+0x124/0x1b0
>>>>>> [c0077cbef7b0] [c0221138] .driver_probe_device+0x144/0x20c
>>>>>> [c0077cbef850] [c0221450] .__driver_attach+0xcc/0x154
>>>>>> [c0077cbef8e0] [c021ff94] .bus_for_each_dev+0x7c/0xd4
>>>>>> [c0077cbef9a0] [c0220e9c] .driver_attach+0x28/0x40
>>>>>> [c0077cbefa20] [c02204d8] .bus_add_driver+0x90/0x228
>>>>>> [c0077cbefac0] [c0221858] .driver_register+0x94/0xb0
>>>>>> [c0077cbefb40] [c01bc430] .__pci_register_driver+0x6c/0xcc
>>>>>> [c0077cbefbe0] [d0143428] .sym2_init+0x108/0x15b0 [sym53c8xx]
>>>>>> [c0077cbefc80] [c008ce80] .sys_init_module+0x17c4/0x1958
>>>>>> [c0077cbefe30] [c000872c] syscall_exit+0x0/0x40
>>>>>> Instruction dump:
>>>>>> 6000 786b0420 38210070 7d635b78 e8010010 7c0803a6 4e800020 7c0802a6 
>>>>>> f8010010 f821ff91 7c0004ac 8923 <0c09> 4c00012c 79290620 
>>>>>> 2f8900ff 
>>>>> I see no obvious lockup sites near the end of sym_hcb_attach().  Maybe 
>>>>> it's
>>>>> being called lots of times from a higher level..  Do the traces all look
>>>>> the same?
>>>> Hi Andrew,
>>>>
>>>> I see this call trace twice and both looks similar and on another reboot
>>>> the following trace is seen twice in different cpu
>>>>
>>>> BUG: soft lockup detected on CPU#3!
>>>> Call Trace:
>>>> [C0003FEDEDA0] [C0010220] .show_stack+0x68/0x1b0 (unreliable)
>>>> [C0003FEDEE40] [C00A061C] .softlockup_tick+0xf0/0x13c
>>>> [C0003FEDEEF0] [C0072E2C] .run_local_timers+0x1c/0x30
>>>> [C0003FEDEF70] [C0022FA0] .timer_interrupt+0xa8/0x488
>>>> [C0003FEDF050] [C00034EC] decrementer_common+0xec/0x100
>>>> --- Exception: 901 at .ioread8+0x14/0x60
>>>> LR = .sym_hcb_attach+0x1194/0x1384 [sym53c8xx]
>>>> [C0003FEDF340] [D02B3BC0] 0xd02b3bc0 (unreliable)
>>>> [C0003FEDF3B0] [D029A3C0] .sym_hcb_attach+0x1194/0x1384 
>>>> [sym53c8xx]
>>>> [C0003FEDF480] [D0291D30] .sym2_probe+0x75c/0x9f8 [sym53c8xx]
>>>> [C0003FEDF710] [C01B65A4] .pci_device_probe+0x13c/0x1dc
>>>> [C0003FEDF7D0] [C0219A0C] .driver

[BUG] 2.6.24-rc3-mm2 kernel bug on nfs & cifs mounted partitions

[Kamalesh Babulal]

Hi Andrew,

While running file system stress on nfs and cifs mounted partitions, the machine
drops to xmon

1:mon> e
cpu 0x1: Vector: 300 (Data Access) at [c00080a9f880]
pc: c01392c8: .inotify_inode_queue_event+0x50/0x158
lr: c01074d0: .vfs_link+0x204/0x298
sp: c00080a9fb00
   msr: 80009032
   dar: 280 
 dsisr: 4001
  current = 0xc000c8e6f670
  paca= 0xc0512c00
pid   = 2848, comm = fsstress
1:mon> t
[c00080a9fbd0] c01074d0 .vfs_link+0x204/0x298
[c00080a9fc70] c010b6e0 .sys_linkat+0x134/0x1b4
[c00080a9fe30] c000872c syscall_exit+0x0/0x40
--- Exception: c00 (System Call) at 0ff1bdfc
SP (ffeaed10) is in userspace
1:mon> r
R00 = c01074d0   R16 = 
R01 = c00080a9fb00   R17 = 
R02 = c060c380   R18 = 
R03 =    R19 = 
R04 = 0004   R20 = 
R05 =    R21 = 
R06 =    R22 = 
R07 =    R23 = 0004
R08 =    R24 = 0280
R09 =    R25 = f000
R10 = 0001   R26 = c00082827790
R11 = c03963e8   R27 = c000828275a0
R12 = d0deec78   R28 = 
R13 = c0512c00   R29 = c0007b18fcf0
R14 =    R30 = c05bc088
R15 =    R31 = 
pc  = c01392c8 .inotify_inode_queue_event+0x50/0x158
lr  = c01074d0 .vfs_link+0x204/0x298
msr = 80009032   cr  = 24000882
ctr = c03963e8   xer =    trap =  300 
dar = 0280   dsisr = 4001


The gdb output shows 

0xc01076d4 is in vfs_symlink (include/linux/fsnotify.h:108).
103  * fsnotify_create - 'name' was linked in
104  */  
105 static inline void fsnotify_create(struct inode *inode, struct dentry 
*dentry)
106 {   
107 inode_dir_notify(inode, DN_CREATE);
108 inotify_inode_queue_event(inode, IN_CREATE, 0, 
dentry->d_name.name,
109   dentry->d_inode);
110 audit_inode_child(dentry->d_name.name, dentry, inode);
111 }   
112



-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[BUG] 2.6.24-rc3-mm2 kernel bug on nfs cifs mounted partitions

[Kamalesh Babulal]

Hi Andrew,

While running file system stress on nfs and cifs mounted partitions, the machine
drops to xmon

1:mon e
cpu 0x1: Vector: 300 (Data Access) at [c00080a9f880]
pc: c01392c8: .inotify_inode_queue_event+0x50/0x158
lr: c01074d0: .vfs_link+0x204/0x298
sp: c00080a9fb00
   msr: 80009032
   dar: 280 
 dsisr: 4001
  current = 0xc000c8e6f670
  paca= 0xc0512c00
pid   = 2848, comm = fsstress
1:mon t
[c00080a9fbd0] c01074d0 .vfs_link+0x204/0x298
[c00080a9fc70] c010b6e0 .sys_linkat+0x134/0x1b4
[c00080a9fe30] c000872c syscall_exit+0x0/0x40
--- Exception: c00 (System Call) at 0ff1bdfc
SP (ffeaed10) is in userspace
1:mon r
R00 = c01074d0   R16 = 
R01 = c00080a9fb00   R17 = 
R02 = c060c380   R18 = 
R03 =    R19 = 
R04 = 0004   R20 = 
R05 =    R21 = 
R06 =    R22 = 
R07 =    R23 = 0004
R08 =    R24 = 0280
R09 =    R25 = f000
R10 = 0001   R26 = c00082827790
R11 = c03963e8   R27 = c000828275a0
R12 = d0deec78   R28 = 
R13 = c0512c00   R29 = c0007b18fcf0
R14 =    R30 = c05bc088
R15 =    R31 = 
pc  = c01392c8 .inotify_inode_queue_event+0x50/0x158
lr  = c01074d0 .vfs_link+0x204/0x298
msr = 80009032   cr  = 24000882
ctr = c03963e8   xer =    trap =  300 
dar = 0280   dsisr = 4001


The gdb output shows 

0xc01076d4 is in vfs_symlink (include/linux/fsnotify.h:108).
103  * fsnotify_create - 'name' was linked in
104  */  
105 static inline void fsnotify_create(struct inode *inode, struct dentry 
*dentry)
106 {   
107 inode_dir_notify(inode, DN_CREATE);
108 inotify_inode_queue_event(inode, IN_CREATE, 0, 
dentry-d_name.name,
109   dentry-d_inode);
110 audit_inode_child(dentry-d_name.name, dentry, inode);
111 }   
112



-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] 2.6.24-rc3-git2 softlockup detected

[Kamalesh Babulal]

Andrew Morton wrote:
 On Thu, 29 Nov 2007 12:01:08 +0530 Kamalesh Babulal [EMAIL PROTECTED] wrote:
 
 Andrew Morton wrote:
 On Wed, 28 Nov 2007 12:47:19 +0530 Kamalesh Babulal [EMAIL PROTECTED] 
 wrote:

 Andrew Morton wrote:
 On Wed, 28 Nov 2007 11:59:00 +0530 Kamalesh Babulal [EMAIL PROTECTED] 
 wrote:

 Hi,
 (cc linux-scsi, for sym53c8xx)

 Soft lockup is detected while bootup with 2.6.24-rc3-git2 on powerbox
 I assume this is a post-2.6.23 regression?

 BUG: soft lockup - CPU#1 stuck for 11s! [insmod:375]
 NIP: c002f02c LR: d01414fc CTR: c002f018
 REGS: c0077cbef0b0 TRAP: 0901   Not tainted  
 (2.6.24-rc3-git2-autotest)
 MSR: 80009032 EE,ME,IR,DR  CR: 24022088  XER: 
 TASK = c0077cbd8000[375] 'insmod' THREAD: c0077cbec000 CPU: 1
 GPR00: d01414fc c0077cbef330 c052b930 
 d80080002014 
 GPR04: d8008000202c  c0077ca1cb00 
 d014ce54 
 GPR08: c0077ca1c63c  002a 
 c002f018 
 GPR12: d0143610 c0473d00 
 NIP [c002f02c] .ioread8+0x14/0x60
 LR [d01414fc] .sym_hcb_attach+0x1188/0x1378 [sym53c8xx]
 Call Trace:
 [c0077cbef330] [c0077cbef3c0] 0xc0077cbef3c0 (unreliable)
 [c0077cbef3a0] [d01414fc] .sym_hcb_attach+0x1188/0x1378 
 [sym53c8xx]
 [c0077cbef470] [d01395f8] .sym2_probe+0x700/0x99c [sym53c8xx]
 [c0077cbef710] [c01bc118] .pci_device_probe+0x124/0x1b0
 [c0077cbef7b0] [c0221138] .driver_probe_device+0x144/0x20c
 [c0077cbef850] [c0221450] .__driver_attach+0xcc/0x154
 [c0077cbef8e0] [c021ff94] .bus_for_each_dev+0x7c/0xd4
 [c0077cbef9a0] [c0220e9c] .driver_attach+0x28/0x40
 [c0077cbefa20] [c02204d8] .bus_add_driver+0x90/0x228
 [c0077cbefac0] [c0221858] .driver_register+0x94/0xb0
 [c0077cbefb40] [c01bc430] .__pci_register_driver+0x6c/0xcc
 [c0077cbefbe0] [d0143428] .sym2_init+0x108/0x15b0 [sym53c8xx]
 [c0077cbefc80] [c008ce80] .sys_init_module+0x17c4/0x1958
 [c0077cbefe30] [c000872c] syscall_exit+0x0/0x40
 Instruction dump:
 6000 786b0420 38210070 7d635b78 e8010010 7c0803a6 4e800020 7c0802a6 
 f8010010 f821ff91 7c0004ac 8923 0c09 4c00012c 79290620 
 2f8900ff 
 I see no obvious lockup sites near the end of sym_hcb_attach().  Maybe 
 it's
 being called lots of times from a higher level..  Do the traces all look
 the same?
 Hi Andrew,

 I see this call trace twice and both looks similar and on another reboot
 the following trace is seen twice in different cpu

 BUG: soft lockup detected on CPU#3!
 Call Trace:
 [C0003FEDEDA0] [C0010220] .show_stack+0x68/0x1b0 (unreliable)
 [C0003FEDEE40] [C00A061C] .softlockup_tick+0xf0/0x13c
 [C0003FEDEEF0] [C0072E2C] .run_local_timers+0x1c/0x30
 [C0003FEDEF70] [C0022FA0] .timer_interrupt+0xa8/0x488
 [C0003FEDF050] [C00034EC] decrementer_common+0xec/0x100
 --- Exception: 901 at .ioread8+0x14/0x60
 LR = .sym_hcb_attach+0x1194/0x1384 [sym53c8xx]
 [C0003FEDF340] [D02B3BC0] 0xd02b3bc0 (unreliable)
 [C0003FEDF3B0] [D029A3C0] .sym_hcb_attach+0x1194/0x1384 
 [sym53c8xx]
 [C0003FEDF480] [D0291D30] .sym2_probe+0x75c/0x9f8 [sym53c8xx]
 [C0003FEDF710] [C01B65A4] .pci_device_probe+0x13c/0x1dc
 [C0003FEDF7D0] [C0219A0C] .driver_probe_device+0xa0/0x15c
 [C0003FEDF870] [C0219C64] .__driver_attach+0xb4/0x138
 [C0003FEDF900] [C021913C] .bus_for_each_dev+0x7c/0xd4
 [C0003FEDF9C0] [C02198B0] .driver_attach+0x28/0x40
 [C0003FEDFA40] [C0218BA4] .bus_add_driver+0x98/0x18c
 [C0003FEDFAE0] [C021A064] .driver_register+0xa8/0xc4
 [C0003FEDFB60] [C01B68AC] .__pci_register_driver+0x5c/0xa4
 [C0003FEDFBF0] [D029C204] .sym2_init+0x104/0x1550 [sym53c8xx]
 [C0003FEDFC90] [C008D1F4] .sys_init_module+0x1764/0x1998
 [C0003FEDFE30] [C000869C] syscall_exit+0x0/0x40

 hm, odd.

 Can you look up sym_hcb_attach+0x1194/0x1384 in gdb?  Something like

 Hi Andrew,

 I tried with 2.6.24-rc3-git3 and got the following trace

 BUG: soft lockup - CPU#2 stuck for 11s! [insmod:375]
 NIP: c002f02c LR: d01414fc CTR: c002f018
 REGS: c0077ca3b0b0 TRAP: 0901   Not tainted  (2.6.24-rc3-git3-autokern1)
 MSR: 80009032 EE,ME,IR,DR  CR: 24022088  XER: 
 TASK = c0077cc58000[375] 'insmod' THREAD: c0077ca38000 CPU: 2
 GPR00: d01414fc c0077ca3b330 c052b880 d80080002014 
 GPR04: d8008000202c  c0077c82eb00 d014ce54 
 GPR08: c0077c82e63c  002a c002f018 
 GPR12: d0143610 c0473f80 
 NIP [c002f02c] .ioread8+0x14/0x60
 LR [d01414fc] .sym_hcb_attach+0x1188/0x1378 [sym53c8xx]

 Call Trace

Re: [BUG] 2.6.24-rc3-mm2 kernel bug on nfs cifs mounted partitions

[Kamalesh Babulal]

Andrew Morton wrote:
 On Thu, 29 Nov 2007 14:30:14 +0530 Kamalesh Babulal [EMAIL PROTECTED] wrote:
 
 Hi Andrew,

 While running file system stress on nfs and cifs mounted partitions, the 
 machine
 drops to xmon

 1:mon e
 cpu 0x1: Vector: 300 (Data Access) at [c00080a9f880]
 pc: c01392c8: .inotify_inode_queue_event+0x50/0x158
 lr: c01074d0: .vfs_link+0x204/0x298
 sp: c00080a9fb00
msr: 80009032
dar: 280 
  dsisr: 4001
   current = 0xc000c8e6f670
   paca= 0xc0512c00
 pid   = 2848, comm = fsstress
 1:mon t
 [c00080a9fbd0] c01074d0 .vfs_link+0x204/0x298
 [c00080a9fc70] c010b6e0 .sys_linkat+0x134/0x1b4
 [c00080a9fe30] c000872c syscall_exit+0x0/0x40
 --- Exception: c00 (System Call) at 0ff1bdfc
 SP (ffeaed10) is in userspace
 1:mon r
 R00 = c01074d0   R16 = 
 R01 = c00080a9fb00   R17 = 
 R02 = c060c380   R18 = 
 R03 =    R19 = 
 R04 = 0004   R20 = 
 R05 =    R21 = 
 R06 =    R22 = 
 R07 =    R23 = 0004
 R08 =    R24 = 0280
 R09 =    R25 = f000
 R10 = 0001   R26 = c00082827790
 R11 = c03963e8   R27 = c000828275a0
 R12 = d0deec78   R28 = 
 R13 = c0512c00   R29 = c0007b18fcf0
 R14 =    R30 = c05bc088
 R15 =    R31 = 
 pc  = c01392c8 .inotify_inode_queue_event+0x50/0x158
 lr  = c01074d0 .vfs_link+0x204/0x298
 msr = 80009032   cr  = 24000882
 ctr = c03963e8   xer =    trap =  300 
 dar = 0280   dsisr = 4001


 The gdb output shows 

 0xc01076d4 is in vfs_symlink (include/linux/fsnotify.h:108).
 103  * fsnotify_create - 'name' was linked in
 104  */  
 105 static inline void fsnotify_create(struct inode *inode, struct 
 dentry *dentry)
 106 {   
 107 inode_dir_notify(inode, DN_CREATE);
 108 inotify_inode_queue_event(inode, IN_CREATE, 0, 
 dentry-d_name.name,
 109   dentry-d_inode);
 110 audit_inode_child(dentry-d_name.name, dentry, inode);
 111 }   
 112

 
 If it is reproducible can you please try reverting
 inotify-send-in_attrib-events-when-link-count-changes.patch?

Hi Andrew,

reverting the patch 
inotify-send-in_attrib-events-when-link-count-changes.patch, the 
bug is not reproduced.

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] 2.6.24-rc3-mm2 kernel bug on nfs cifs mounted partitions

[Kamalesh Babulal]

Jan Kara wrote:
 On Thu 29-11-07 17:27:08, Kamalesh Babulal wrote:
 Andrew Morton wrote:
 On Thu, 29 Nov 2007 14:30:14 +0530 Kamalesh Babulal [EMAIL PROTECTED] 
 wrote:

 Hi Andrew,

 While running file system stress on nfs and cifs mounted partitions, the 
 machine
 drops to xmon

 1:mon e
 cpu 0x1: Vector: 300 (Data Access) at [c00080a9f880]
 pc: c01392c8: .inotify_inode_queue_event+0x50/0x158
 lr: c01074d0: .vfs_link+0x204/0x298
 sp: c00080a9fb00
msr: 80009032
dar: 280 
  dsisr: 4001
   current = 0xc000c8e6f670
   paca= 0xc0512c00
 pid   = 2848, comm = fsstress
 1:mon t
 [c00080a9fbd0] c01074d0 .vfs_link+0x204/0x298
 [c00080a9fc70] c010b6e0 .sys_linkat+0x134/0x1b4
 [c00080a9fe30] c000872c syscall_exit+0x0/0x40
 --- Exception: c00 (System Call) at 0ff1bdfc
 SP (ffeaed10) is in userspace
 1:mon r
 R00 = c01074d0   R16 = 
 R01 = c00080a9fb00   R17 = 
 R02 = c060c380   R18 = 
 R03 =    R19 = 
 R04 = 0004   R20 = 
 R05 =    R21 = 
 R06 =    R22 = 
 R07 =    R23 = 0004
 R08 =    R24 = 0280
 R09 =    R25 = f000
 R10 = 0001   R26 = c00082827790
 R11 = c03963e8   R27 = c000828275a0
 R12 = d0deec78   R28 = 
 R13 = c0512c00   R29 = c0007b18fcf0
 R14 =    R30 = c05bc088
 R15 =    R31 = 
 pc  = c01392c8 .inotify_inode_queue_event+0x50/0x158
 lr  = c01074d0 .vfs_link+0x204/0x298
 msr = 80009032   cr  = 24000882
 ctr = c03963e8   xer =    trap =  300 
 dar = 0280   dsisr = 4001


 The gdb output shows 

 0xc01076d4 is in vfs_symlink (include/linux/fsnotify.h:108).
 103  * fsnotify_create - 'name' was linked in
 104  */  
 105 static inline void fsnotify_create(struct inode *inode, struct 
 dentry *dentry)
 106 {   
 107 inode_dir_notify(inode, DN_CREATE);
 108 inotify_inode_queue_event(inode, IN_CREATE, 0, 
 dentry-d_name.name,
 109   dentry-d_inode);
 110 audit_inode_child(dentry-d_name.name, dentry, inode);
 111 }   
 112

 If it is reproducible can you please try reverting
 inotify-send-in_attrib-events-when-link-count-changes.patch?
 Hi Andrew,

 reverting the patch 
 inotify-send-in_attrib-events-when-link-count-changes.patch, the 
 bug is not reproduced.
   OK, thanks for testing. I was trying to reproduce the problem locally but
 without success so far - I guess it's either NFS or CIFS which makes the
 problem appear. I'll investigate more.
 
   Honza

Hi Jan,

I was running file system stress parallely on NFS and CIFS mounted partitions.
  

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] 2.6.24-rc3-mm2 soft lockup while running tbench

[Kamalesh Babulal]

Andrew Morton wrote:
 On Wed, 28 Nov 2007 20:03:22 +0530
 Kamalesh Babulal [EMAIL PROTECTED] wrote:
 
 Hi Andrew,

 while running tbench on the powerpc with 2.6.24-rc3-mm2 softlock up occurs

 BUG: soft lockup - CPU#0 stuck for 11s! [tbench:12183]
 NIP: c00ac978 LR: c00acff0 CTR: c005c648
 REGS: C0076F0F3200 TRAP: 0901   Not tainted  (2.6.24-rc3-mm2-autotest)
 MSR: 80009032 EE,ME,IR,DR  CR: 44000482  XER: 
 TASK = C0076F4BC000[12183] 'tbench' THREAD: C0076F0F CPU: 0
 NIP [c00ac978] .get_page_from_freelist+0x1cc/0x754
 LR [c00acff0] .__alloc_pages+0xb0/0x3a8
 Call Trace:
 [c0076f0f3480] [c0076f0f3560] 0xc0076f0f3560 (unreliable)
 [c0076f0f3590] [c00acff0] .__alloc_pages+0xb0/0x3a8
 [c0076f0f3680] [c00ce2e4] .alloc_pages_current+0xa8/0xc8
 [c0076f0f3710] [c00ac6ec] .__get_free_pages+0x20/0x70
 [c0076f0f3790] [c00d75c8] .__kmalloc_node_track_caller+0x60/0x148
 [c0076f0f3840] [c02c22b0] .__alloc_skb+0x98/0x184
 [c0076f0f38f0] [c0306cd8] .tcp_sendmsg+0x1fc/0xe24
 [c0076f0f3a10] [c02b963c] .sock_sendmsg+0xe4/0x128
 [c0076f0f3c10] [c02ba4ec] .sys_sendto+0xd4/0x120
 [c0076f0f3d90] [c02df2f8] .compat_sys_socketcall+0x148/0x214
 [c0076f0f3e30] [c000872c] syscall_exit+0x0/0x40
 Instruction dump:
 720b0001 eb97 40820070 7202 4182000c e8bc 4818 72080004 
 4182000c e8bc0008 4808 e8bc0010 e8c10078 7f83e378 7de407b4 7e078378 

 
 hm.  Beats me.  Does the machine recover OK?
 -
Hi Andrew,

In the set of test cases ran serially, the softlockup in seen in tbench,
then the remaining test cases get to run successfully after the softlockup.

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] 2.6.24-rc3-git2 softlockup detected

[Kamalesh Babulal]

Andrew Morton wrote:
 On Thu, 29 Nov 2007 23:00:47 -0800 Andrew Morton [EMAIL PROTECTED] wrote:
 
 On Fri, 30 Nov 2007 01:39:29 -0500 Kyle McMartin [EMAIL PROTECTED] wrote:

 On Thu, Nov 29, 2007 at 12:35:33AM -0800, Andrew Morton wrote:
 ten million is close enough to infinity for me to assume that we broke the
 driver and that's never going to terminate.

 how about this? doesn't break things on my pa8800:

 diff --git a/drivers/scsi/sym53c8xx_2/sym_hipd.c 
 b/drivers/scsi/sym53c8xx_2/sym_hipd.c
 index 463f119..ef01cb1 100644
 --- a/drivers/scsi/sym53c8xx_2/sym_hipd.c
 +++ b/drivers/scsi/sym53c8xx_2/sym_hipd.c
 @@ -1037,10 +1037,13 @@ restart_test:
 /*
  *  Wait 'til done (with timeout)
  */
 -   for (i=0; iSYM_SNOOP_TIMEOUT; i++)
 +   do {
 if (INB(np, nc_istat)  (INTF|SIP|DIP))
 break;
 -   if (i=SYM_SNOOP_TIMEOUT) {
 +   msleep(10);
 +   } while (i++  SYM_SNOOP_TIMEOUT);
 +
 +   if (i = SYM_SNOOP_TIMEOUT) {
 printf (CACHE TEST FAILED: timeout.\n);
 return (0x20);
 }
 diff --git a/drivers/scsi/sym53c8xx_2/sym_hipd.h 
 b/drivers/scsi/sym53c8xx_2/sym_hipd.h
 index ad07880..85c483b 100644
 --- a/drivers/scsi/sym53c8xx_2/sym_hipd.h
 +++ b/drivers/scsi/sym53c8xx_2/sym_hipd.h
 @@ -339,7 +339,7 @@
  /*
   *  Misc.
   */
 -#define SYM_SNOOP_TIMEOUT (1000)
 +#define SYM_SNOOP_TIMEOUT (1000)
  #define BUS_8_BIT  0
  #define BUS_16_BIT 1
  
 That might be the fix, but do we know what we're actually fixing?  afaik
 2.6.24-rc3 doesn't get this timeout, 2.6.24-rc3-mm2 does get it and we
 don't know why?

 
 looks at Subject:
 
 Checks that Rafael was cc'ed
 
 So 2.6.24-rc3 was OK and 2.6.24-rc3-git2 is not?

Yes, the 2.6.24-rc3 was Ok and this is seen from 2.6.24-rc3-git2/3/4.

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] 2.6.24-rc3-git2 softlockup detected

[Kamalesh Babulal]

Andrew Morton wrote:
> On Wed, 28 Nov 2007 12:47:19 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> 
>> Andrew Morton wrote:
>>> On Wed, 28 Nov 2007 11:59:00 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> 
>>> wrote:
>>>
>>>> Hi,
>>> (cc linux-scsi, for sym53c8xx)
>>>
>>>> Soft lockup is detected while bootup with 2.6.24-rc3-git2 on powerbox
>>> I assume this is a post-2.6.23 regression?
>>>
>>>> BUG: soft lockup - CPU#1 stuck for 11s! [insmod:375]
>>>> NIP: c002f02c LR: d01414fc CTR: c002f018
>>>> REGS: c0077cbef0b0 TRAP: 0901   Not tainted  (2.6.24-rc3-git2-autotest)
>>>> MSR: 80009032   CR: 24022088  XER: 
>>>> TASK = c0077cbd8000[375] 'insmod' THREAD: c0077cbec000 CPU: 1
>>>> GPR00: d01414fc c0077cbef330 c052b930 d80080002014 
>>>> GPR04: d8008000202c  c0077ca1cb00 d014ce54 
>>>> GPR08: c0077ca1c63c  002a c002f018 
>>>> GPR12: d0143610 c0473d00 
>>>> NIP [c002f02c] .ioread8+0x14/0x60
>>>> LR [d01414fc] .sym_hcb_attach+0x1188/0x1378 [sym53c8xx]
>>>> Call Trace:
>>>> [c0077cbef330] [c0077cbef3c0] 0xc0077cbef3c0 (unreliable)
>>>> [c0077cbef3a0] [d01414fc] .sym_hcb_attach+0x1188/0x1378 
>>>> [sym53c8xx]
>>>> [c0077cbef470] [d01395f8] .sym2_probe+0x700/0x99c [sym53c8xx]
>>>> [c0077cbef710] [c01bc118] .pci_device_probe+0x124/0x1b0
>>>> [c0077cbef7b0] [c0221138] .driver_probe_device+0x144/0x20c
>>>> [c0077cbef850] [c0221450] .__driver_attach+0xcc/0x154
>>>> [c0077cbef8e0] [c021ff94] .bus_for_each_dev+0x7c/0xd4
>>>> [c0077cbef9a0] [c0220e9c] .driver_attach+0x28/0x40
>>>> [c0077cbefa20] [c02204d8] .bus_add_driver+0x90/0x228
>>>> [c0077cbefac0] [c0221858] .driver_register+0x94/0xb0
>>>> [c0077cbefb40] [c01bc430] .__pci_register_driver+0x6c/0xcc
>>>> [c0077cbefbe0] [d0143428] .sym2_init+0x108/0x15b0 [sym53c8xx]
>>>> [c0077cbefc80] [c008ce80] .sys_init_module+0x17c4/0x1958
>>>> [c0077cbefe30] [c000872c] syscall_exit+0x0/0x40
>>>> Instruction dump:
>>>> 6000 786b0420 38210070 7d635b78 e8010010 7c0803a6 4e800020 7c0802a6 
>>>> f8010010 f821ff91 7c0004ac 8923 <0c09> 4c00012c 79290620 2f8900ff 
>>> I see no obvious lockup sites near the end of sym_hcb_attach().  Maybe it's
>>> being called lots of times from a higher level..  Do the traces all look
>>> the same?
>> Hi Andrew,
>>
>> I see this call trace twice and both looks similar and on another reboot
>> the following trace is seen twice in different cpu
>>
>> BUG: soft lockup detected on CPU#3!
>> Call Trace:
>> [C0003FEDEDA0] [C0010220] .show_stack+0x68/0x1b0 (unreliable)
>> [C0003FEDEE40] [C00A061C] .softlockup_tick+0xf0/0x13c
>> [C0003FEDEEF0] [C0072E2C] .run_local_timers+0x1c/0x30
>> [C0003FEDEF70] [C0022FA0] .timer_interrupt+0xa8/0x488
>> [C0003FEDF050] [C00034EC] decrementer_common+0xec/0x100
>> --- Exception: 901 at .ioread8+0x14/0x60
>> LR = .sym_hcb_attach+0x1194/0x1384 [sym53c8xx]
>> [C0003FEDF340] [D02B3BC0] 0xd02b3bc0 (unreliable)
>> [C0003FEDF3B0] [D029A3C0] .sym_hcb_attach+0x1194/0x1384 
>> [sym53c8xx]
>> [C0003FEDF480] [D0291D30] .sym2_probe+0x75c/0x9f8 [sym53c8xx]
>> [C0003FEDF710] [C01B65A4] .pci_device_probe+0x13c/0x1dc
>> [C0003FEDF7D0] [C0219A0C] .driver_probe_device+0xa0/0x15c
>> [C0003FEDF870] [C0219C64] .__driver_attach+0xb4/0x138
>> [C0003FEDF900] [C021913C] .bus_for_each_dev+0x7c/0xd4
>> [C0003FEDF9C0] [C02198B0] .driver_attach+0x28/0x40
>> [C0003FEDFA40] [C0218BA4] .bus_add_driver+0x98/0x18c
>> [C0003FEDFAE0] [C021A064] .driver_register+0xa8/0xc4
>> [C0003FEDFB60] [C01B68AC] .__pci_register_driver+0x5c/0xa4
>> [C0003FEDFBF0] [D029C204] .sym2_init+0x104/0x1550 [sym53c8xx]
>> [C0003FEDFC90] [C008D1F4] .sys_init_module+0x1764/0x1998
>> [C0003FEDFE30] [C000869C] syscall_exit+0x0/0x40
>>
> 
> hm, odd.
> 
> Can you look up sym_hcb_attach+0x1194/0x1384 in gdb?  Something 

[BUG] 2.6.24-rc3-mm2 soft lockup while running tbench

[Kamalesh Babulal]

Hi Andrew,

while running tbench on the powerpc with 2.6.24-rc3-mm2 softlock up occurs

BUG: soft lockup - CPU#0 stuck for 11s! [tbench:12183]
NIP: c00ac978 LR: c00acff0 CTR: c005c648
REGS: C0076F0F3200 TRAP: 0901   Not tainted  (2.6.24-rc3-mm2-autotest)
MSR: 80009032   CR: 44000482  XER: 
TASK = C0076F4BC000[12183] 'tbench' THREAD: C0076F0F CPU: 0
NIP [c00ac978] .get_page_from_freelist+0x1cc/0x754
LR [c00acff0] .__alloc_pages+0xb0/0x3a8
Call Trace:
[c0076f0f3480] [c0076f0f3560] 0xc0076f0f3560 (unreliable)
[c0076f0f3590] [c00acff0] .__alloc_pages+0xb0/0x3a8
[c0076f0f3680] [c00ce2e4] .alloc_pages_current+0xa8/0xc8
[c0076f0f3710] [c00ac6ec] .__get_free_pages+0x20/0x70
[c0076f0f3790] [c00d75c8] .__kmalloc_node_track_caller+0x60/0x148
[c0076f0f3840] [c02c22b0] .__alloc_skb+0x98/0x184
[c0076f0f38f0] [c0306cd8] .tcp_sendmsg+0x1fc/0xe24
[c0076f0f3a10] [c02b963c] .sock_sendmsg+0xe4/0x128
[c0076f0f3c10] [c02ba4ec] .sys_sendto+0xd4/0x120
[c0076f0f3d90] [c02df2f8] .compat_sys_socketcall+0x148/0x214
[c0076f0f3e30] [c000872c] syscall_exit+0x0/0x40
Instruction dump:
720b0001 eb97 40820070 7202 4182000c e8bc 4818 72080004 
4182000c e8bc0008 4808 e8bc0010  7f83e378 7de407b4 7e078378 

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] 2.6.24-rc3-mm2 build failure pasemi-rng driver

[Kamalesh Babulal]

Hi Andrew,

The kerne build fails, with message

  CC  drivers/char/hw_random/pasemi-rng.o
drivers/char/hw_random/pasemi-rng.c: In function ‘pasemi_rng_data_present’:
drivers/char/hw_random/pasemi-rng.c:53: error: ‘wait’ undeclared (first use in 
this function)
drivers/char/hw_random/pasemi-rng.c:53: error: (Each undeclared identifier is 
reported only once
drivers/char/hw_random/pasemi-rng.c:53: error: for each function it appears in.)
drivers/char/hw_random/pasemi-rng.c: At top level:
drivers/char/hw_random/pasemi-rng.c:93: warning: initialization from 
incompatible pointer type
make[3]: *** [drivers/char/hw_random/pasemi-rng.o] Error 1
make[2]: *** [drivers/char/hw_random] Error 2
make[1]: *** [drivers/char] Error 2
make: *** [drivers] Error 2

Tested for build failure, only.

Signed-off-by: Kamalesh Babulal <[EMAIL PROTECTED]>
--
--- linux-2.6.24-rc3/drivers/char/hw_random/pasemi-rng.c2007-11-28 
17:47:41.0 +0530
+++ linux-2.6.24-rc3/drivers/char/hw_random/~pasemi-rng.c   2007-11-28 
19:43:10.0 +0530
@@ -42,7 +42,7 @@
 
 #define MODULE_NAME "pasemi_rng"
 
-static int pasemi_rng_data_present(struct hwrng *rng)
+static int pasemi_rng_data_present(struct hwrng *rng, int wait)
 {
void __iomem *rng_regs = (void __iomem *)rng->priv;
int data, i;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc3-mm2 Build Failure at imacfb framebuffer driver

[Kamalesh Babulal]

Hi Andrew,

The kernel build fails, with following error

  CC  drivers/video/imacfb.o
drivers/video/imacfb.c: In function ‘imacfb_probe’:
drivers/video/imacfb.c:238: error: ‘struct screen_info’ has no member named 
‘imacpm_seg’
make[2]: *** [drivers/video/imacfb.o] Error 1
make[1]: *** [drivers/video] Error 2
make: *** [drivers] Error 2


-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc3-mm2 - Build Failure on powerpc timerfd() undeclared

[Kamalesh Babulal]

Hi Andrew,

Kernel build fails, with build error

  CC  arch/powerpc/platforms/cell/spu_callbacks.o
In file included from arch/powerpc/platforms/cell/spu_callbacks.c:49:
include/asm/systbl.h:312: error: ‘sys_timerfd’ undeclared here (not in a 
function)
make[2]: *** [arch/powerpc/platforms/cell/spu_callbacks.o] Error 1
make[1]: *** [arch/powerpc/platforms/cell] Error 2
make: *** [arch/powerpc/platforms] Error 2

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[BUG] 2.6.24-rc3-git3 oom-killer invoked

[Kamalesh Babulal]

Hi,

oom-killer gets invoked while running ltprunall on AMD Opteron box

sleep invoked oom-killer: gfp_mask=0x1201d2, order=0, oomkilladj=0
Pid: 23477, comm: sleep Not tainted 2.6.24-rc3-git3-autokern1 #1

Call Trace:
 [] oom_kill_process+0x4f/0xf5
 [] out_of_memory+0x1bc/0x22d
 [] __alloc_pages+0x282/0x313
 [] __wait_on_bit_lock+0x5b/0x66
 [] __do_page_cache_readahead+0x7c/0x18f
 [] filemap_fault+0x15d/0x317
 [] __do_fault+0x68/0x3bb
 [] _spin_unlock_irq+0x9/0xc
 [] handle_mm_fault+0x325/0x694
 [] do_page_fault+0x3c5/0x764
 [] hrtimer_try_to_cancel+0x5f/0x68
 [] hrtimer_cancel+0xc/0x16
 [] do_nanosleep+0x4e/0x77
 [] hrtimer_nanosleep+0x58/0xf8
 [] hrtimer_wakeup+0x0/0x21
 [] error_exit+0x0/0x51

Mem-info:
Node 0 DMA per-cpu:
CPU0: Hot: hi:0, btch:   1 usd:   0   Cold: hi:0, btch:   1 usd:   0
CPU1: Hot: hi:0, btch:   1 usd:   0   Cold: hi:0, btch:   1 usd:   0
CPU2: Hot: hi:0, btch:   1 usd:   0   Cold: hi:0, btch:   1 usd:   0
CPU3: Hot: hi:0, btch:   1 usd:   0   Cold: hi:0, btch:   1 usd:   0
Node 0 DMA32 per-cpu:
CPU0: Hot: hi:  186, btch:  31 usd:  40   Cold: hi:   62, btch:  15 usd:  50
CPU1: Hot: hi:  186, btch:  31 usd:  24   Cold: hi:   62, btch:  15 usd:  24
CPU2: Hot: hi:  186, btch:  31 usd:   3   Cold: hi:   62, btch:  15 usd:  21
CPU3: Hot: hi:  186, btch:  31 usd: 163   Cold: hi:   62, btch:  15 usd:  45
Active:122323 inactive:122411 dirty:0 writeback:1 unstable:0
 free:1979 slab:2772 mapped:10 pagetables:2062 bounce:0
Node 0 DMA free:3988kB min:28kB low:32kB high:40kB active:2056kB 
inactive:2108kB present:7656kB pages_scanned:7201 all_unreclaimable? yes
lowmem_reserve[]: 0 992 992 992
Node 0 DMA32 free:4228kB min:4012kB low:5012kB high:6016kB active:489852kB 
inactive:485192kB present:1015864kB pages_scanned:70920 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
Node 0 DMA: 3*4kB 5*8kB 2*16kB 0*32kB 1*64kB 2*128kB 2*256kB 0*512kB 1*1024kB 
1*2048kB 0*4096kB = 3988kB
Node 0 DMA32: 117*4kB 16*8kB 5*16kB 1*32kB 1*64kB 1*128kB 1*256kB 0*512kB 
1*1024kB 1*2048kB 0*4096kB = 4228kB
Swap cache: add 815346, delete 815330, find 474/677, race 0+0
Free swap  = 0kB
Total swap = 2031640kB
Free swap:0kB
262093 pages of RAM
6955 reserved pages
288 pages shared
40 pages swap cached
Out of memory: kill process 23475 (mem01) score 46734 or a child
Killed process 23475 (mem01)


(boot log)
---
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009d400 (usable)
 BIOS-e820: 0009d400 - 000a (reserved)
 BIOS-e820: 000e - 0010 (reserved)
 BIOS-e820: 0010 - 3ffcddc0 (usable)
 BIOS-e820: 3ffcddc0 - 3ffd (ACPI data)
 BIOS-e820: 3ffd - 4000 (reserved)
 BIOS-e820: fec0 - 0001 (reserved)
end_pfn_map = 1048576
DMI 2.3 present.
ACPI: RSDP 000FDFC0, 0014 (r0 IBM   )
ACPI: RSDT 3FFCFF80, 0034 (r1 IBMSERBLADE 1000 IBM  45444F43)
ACPI: FACP 3FFCFEC0, 0084 (r2 IBMSERBLADE 1000 IBM  45444F43)
ACPI: DSDT 3FFCDDC0, 1EA6 (r1 IBMSERBLADE 1000 INTL  2002025)
ACPI: FACS 3FFCFCC0, 0040
ACPI: APIC 3FFCFE00, 009C (r1 IBMSERBLADE 1000 IBM  45444F43)
ACPI: SRAT 3FFCFD40, 0098 (r1 IBMSERBLADE 1000 IBM  45444F43)
ACPI: HPET 3FFCFD00, 0038 (r1 IBMSERBLADE 1000 IBM  45444F43)
SRAT: PXM 0 -> APIC 0 -> Node 0
SRAT: PXM 0 -> APIC 1 -> Node 0
SRAT: PXM 1 -> APIC 2 -> Node 1
SRAT: PXM 1 -> APIC 3 -> Node 1
SRAT: Node 0 PXM 0 0-4000
Bootmem setup node 0 -3ffcd000
Zone PFN ranges:
  DMA 0 -> 4096
  DMA324096 ->  1048576
  Normal1048576 ->  1048576
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0:0 ->  157
0:  256 ->   262093

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[BUG] 2.6.24-rc3-git3 oom-killer invoked

[Kamalesh Babulal]

Hi,

oom-killer gets invoked while running ltprunall on AMD Opteron box

sleep invoked oom-killer: gfp_mask=0x1201d2, order=0, oomkilladj=0
Pid: 23477, comm: sleep Not tainted 2.6.24-rc3-git3-autokern1 #1

Call Trace:
 [8026ac6b] oom_kill_process+0x4f/0xf5
 [8026b147] out_of_memory+0x1bc/0x22d
 [8026db44] __alloc_pages+0x282/0x313
 [804e4a5c] __wait_on_bit_lock+0x5b/0x66
 [8026f684] __do_page_cache_readahead+0x7c/0x18f
 [8026a353] filemap_fault+0x15d/0x317
 [80274d06] __do_fault+0x68/0x3bb
 [804e5cb1] _spin_unlock_irq+0x9/0xc
 [8027690a] handle_mm_fault+0x325/0x694
 [804e78c1] do_page_fault+0x3c5/0x764
 [8024c5b9] hrtimer_try_to_cancel+0x5f/0x68
 [8024c5ce] hrtimer_cancel+0xc/0x16
 [804e4e43] do_nanosleep+0x4e/0x77
 [8024c73f] hrtimer_nanosleep+0x58/0xf8
 [8024c301] hrtimer_wakeup+0x0/0x21
 [804e5e59] error_exit+0x0/0x51

Mem-info:
Node 0 DMA per-cpu:
CPU0: Hot: hi:0, btch:   1 usd:   0   Cold: hi:0, btch:   1 usd:   0
CPU1: Hot: hi:0, btch:   1 usd:   0   Cold: hi:0, btch:   1 usd:   0
CPU2: Hot: hi:0, btch:   1 usd:   0   Cold: hi:0, btch:   1 usd:   0
CPU3: Hot: hi:0, btch:   1 usd:   0   Cold: hi:0, btch:   1 usd:   0
Node 0 DMA32 per-cpu:
CPU0: Hot: hi:  186, btch:  31 usd:  40   Cold: hi:   62, btch:  15 usd:  50
CPU1: Hot: hi:  186, btch:  31 usd:  24   Cold: hi:   62, btch:  15 usd:  24
CPU2: Hot: hi:  186, btch:  31 usd:   3   Cold: hi:   62, btch:  15 usd:  21
CPU3: Hot: hi:  186, btch:  31 usd: 163   Cold: hi:   62, btch:  15 usd:  45
Active:122323 inactive:122411 dirty:0 writeback:1 unstable:0
 free:1979 slab:2772 mapped:10 pagetables:2062 bounce:0
Node 0 DMA free:3988kB min:28kB low:32kB high:40kB active:2056kB 
inactive:2108kB present:7656kB pages_scanned:7201 all_unreclaimable? yes
lowmem_reserve[]: 0 992 992 992
Node 0 DMA32 free:4228kB min:4012kB low:5012kB high:6016kB active:489852kB 
inactive:485192kB present:1015864kB pages_scanned:70920 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
Node 0 DMA: 3*4kB 5*8kB 2*16kB 0*32kB 1*64kB 2*128kB 2*256kB 0*512kB 1*1024kB 
1*2048kB 0*4096kB = 3988kB
Node 0 DMA32: 117*4kB 16*8kB 5*16kB 1*32kB 1*64kB 1*128kB 1*256kB 0*512kB 
1*1024kB 1*2048kB 0*4096kB = 4228kB
Swap cache: add 815346, delete 815330, find 474/677, race 0+0
Free swap  = 0kB
Total swap = 2031640kB
Free swap:0kB
262093 pages of RAM
6955 reserved pages
288 pages shared
40 pages swap cached
Out of memory: kill process 23475 (mem01) score 46734 or a child
Killed process 23475 (mem01)


(boot log)
---
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009d400 (usable)
 BIOS-e820: 0009d400 - 000a (reserved)
 BIOS-e820: 000e - 0010 (reserved)
 BIOS-e820: 0010 - 3ffcddc0 (usable)
 BIOS-e820: 3ffcddc0 - 3ffd (ACPI data)
 BIOS-e820: 3ffd - 4000 (reserved)
 BIOS-e820: fec0 - 0001 (reserved)
end_pfn_map = 1048576
DMI 2.3 present.
ACPI: RSDP 000FDFC0, 0014 (r0 IBM   )
ACPI: RSDT 3FFCFF80, 0034 (r1 IBMSERBLADE 1000 IBM  45444F43)
ACPI: FACP 3FFCFEC0, 0084 (r2 IBMSERBLADE 1000 IBM  45444F43)
ACPI: DSDT 3FFCDDC0, 1EA6 (r1 IBMSERBLADE 1000 INTL  2002025)
ACPI: FACS 3FFCFCC0, 0040
ACPI: APIC 3FFCFE00, 009C (r1 IBMSERBLADE 1000 IBM  45444F43)
ACPI: SRAT 3FFCFD40, 0098 (r1 IBMSERBLADE 1000 IBM  45444F43)
ACPI: HPET 3FFCFD00, 0038 (r1 IBMSERBLADE 1000 IBM  45444F43)
SRAT: PXM 0 - APIC 0 - Node 0
SRAT: PXM 0 - APIC 1 - Node 0
SRAT: PXM 1 - APIC 2 - Node 1
SRAT: PXM 1 - APIC 3 - Node 1
SRAT: Node 0 PXM 0 0-4000
Bootmem setup node 0 -3ffcd000
Zone PFN ranges:
  DMA 0 - 4096
  DMA324096 -  1048576
  Normal1048576 -  1048576
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0:0 -  157
0:  256 -   262093

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc3-mm2 - Build Failure on powerpc timerfd() undeclared

[Kamalesh Babulal]

Hi Andrew,

Kernel build fails, with build error

  CC  arch/powerpc/platforms/cell/spu_callbacks.o
In file included from arch/powerpc/platforms/cell/spu_callbacks.c:49:
include/asm/systbl.h:312: error: ‘sys_timerfd’ undeclared here (not in a 
function)
make[2]: *** [arch/powerpc/platforms/cell/spu_callbacks.o] Error 1
make[1]: *** [arch/powerpc/platforms/cell] Error 2
make: *** [arch/powerpc/platforms] Error 2

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc3-mm2 Build Failure at imacfb framebuffer driver

[Kamalesh Babulal]

Hi Andrew,

The kernel build fails, with following error

  CC  drivers/video/imacfb.o
drivers/video/imacfb.c: In function ‘imacfb_probe’:
drivers/video/imacfb.c:238: error: ‘struct screen_info’ has no member named 
‘imacpm_seg’
make[2]: *** [drivers/video/imacfb.o] Error 1
make[1]: *** [drivers/video] Error 2
make: *** [drivers] Error 2


-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] 2.6.24-rc3-mm2 build failure pasemi-rng driver

[Kamalesh Babulal]

Hi Andrew,

The kerne build fails, with message

  CC  drivers/char/hw_random/pasemi-rng.o
drivers/char/hw_random/pasemi-rng.c: In function ‘pasemi_rng_data_present’:
drivers/char/hw_random/pasemi-rng.c:53: error: ‘wait’ undeclared (first use in 
this function)
drivers/char/hw_random/pasemi-rng.c:53: error: (Each undeclared identifier is 
reported only once
drivers/char/hw_random/pasemi-rng.c:53: error: for each function it appears in.)
drivers/char/hw_random/pasemi-rng.c: At top level:
drivers/char/hw_random/pasemi-rng.c:93: warning: initialization from 
incompatible pointer type
make[3]: *** [drivers/char/hw_random/pasemi-rng.o] Error 1
make[2]: *** [drivers/char/hw_random] Error 2
make[1]: *** [drivers/char] Error 2
make: *** [drivers] Error 2

Tested for build failure, only.

Signed-off-by: Kamalesh Babulal [EMAIL PROTECTED]
--
--- linux-2.6.24-rc3/drivers/char/hw_random/pasemi-rng.c2007-11-28 
17:47:41.0 +0530
+++ linux-2.6.24-rc3/drivers/char/hw_random/~pasemi-rng.c   2007-11-28 
19:43:10.0 +0530
@@ -42,7 +42,7 @@
 
 #define MODULE_NAME pasemi_rng
 
-static int pasemi_rng_data_present(struct hwrng *rng)
+static int pasemi_rng_data_present(struct hwrng *rng, int wait)
 {
void __iomem *rng_regs = (void __iomem *)rng-priv;
int data, i;
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[BUG] 2.6.24-rc3-mm2 soft lockup while running tbench

[Kamalesh Babulal]

Hi Andrew,

while running tbench on the powerpc with 2.6.24-rc3-mm2 softlock up occurs

BUG: soft lockup - CPU#0 stuck for 11s! [tbench:12183]
NIP: c00ac978 LR: c00acff0 CTR: c005c648
REGS: C0076F0F3200 TRAP: 0901   Not tainted  (2.6.24-rc3-mm2-autotest)
MSR: 80009032 EE,ME,IR,DR  CR: 44000482  XER: 
TASK = C0076F4BC000[12183] 'tbench' THREAD: C0076F0F CPU: 0
NIP [c00ac978] .get_page_from_freelist+0x1cc/0x754
LR [c00acff0] .__alloc_pages+0xb0/0x3a8
Call Trace:
[c0076f0f3480] [c0076f0f3560] 0xc0076f0f3560 (unreliable)
[c0076f0f3590] [c00acff0] .__alloc_pages+0xb0/0x3a8
[c0076f0f3680] [c00ce2e4] .alloc_pages_current+0xa8/0xc8
[c0076f0f3710] [c00ac6ec] .__get_free_pages+0x20/0x70
[c0076f0f3790] [c00d75c8] .__kmalloc_node_track_caller+0x60/0x148
[c0076f0f3840] [c02c22b0] .__alloc_skb+0x98/0x184
[c0076f0f38f0] [c0306cd8] .tcp_sendmsg+0x1fc/0xe24
[c0076f0f3a10] [c02b963c] .sock_sendmsg+0xe4/0x128
[c0076f0f3c10] [c02ba4ec] .sys_sendto+0xd4/0x120
[c0076f0f3d90] [c02df2f8] .compat_sys_socketcall+0x148/0x214
[c0076f0f3e30] [c000872c] syscall_exit+0x0/0x40
Instruction dump:
720b0001 eb97 40820070 7202 4182000c e8bc 4818 72080004 
4182000c e8bc0008 4808 e8bc0010 e8c10078 7f83e378 7de407b4 7e078378 

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] 2.6.24-rc3-git2 softlockup detected

[Kamalesh Babulal]

Andrew Morton wrote:
 On Wed, 28 Nov 2007 12:47:19 +0530 Kamalesh Babulal [EMAIL PROTECTED] wrote:
 
 Andrew Morton wrote:
 On Wed, 28 Nov 2007 11:59:00 +0530 Kamalesh Babulal [EMAIL PROTECTED] 
 wrote:

 Hi,
 (cc linux-scsi, for sym53c8xx)

 Soft lockup is detected while bootup with 2.6.24-rc3-git2 on powerbox
 I assume this is a post-2.6.23 regression?

 BUG: soft lockup - CPU#1 stuck for 11s! [insmod:375]
 NIP: c002f02c LR: d01414fc CTR: c002f018
 REGS: c0077cbef0b0 TRAP: 0901   Not tainted  (2.6.24-rc3-git2-autotest)
 MSR: 80009032 EE,ME,IR,DR  CR: 24022088  XER: 
 TASK = c0077cbd8000[375] 'insmod' THREAD: c0077cbec000 CPU: 1
 GPR00: d01414fc c0077cbef330 c052b930 d80080002014 
 GPR04: d8008000202c  c0077ca1cb00 d014ce54 
 GPR08: c0077ca1c63c  002a c002f018 
 GPR12: d0143610 c0473d00 
 NIP [c002f02c] .ioread8+0x14/0x60
 LR [d01414fc] .sym_hcb_attach+0x1188/0x1378 [sym53c8xx]
 Call Trace:
 [c0077cbef330] [c0077cbef3c0] 0xc0077cbef3c0 (unreliable)
 [c0077cbef3a0] [d01414fc] .sym_hcb_attach+0x1188/0x1378 
 [sym53c8xx]
 [c0077cbef470] [d01395f8] .sym2_probe+0x700/0x99c [sym53c8xx]
 [c0077cbef710] [c01bc118] .pci_device_probe+0x124/0x1b0
 [c0077cbef7b0] [c0221138] .driver_probe_device+0x144/0x20c
 [c0077cbef850] [c0221450] .__driver_attach+0xcc/0x154
 [c0077cbef8e0] [c021ff94] .bus_for_each_dev+0x7c/0xd4
 [c0077cbef9a0] [c0220e9c] .driver_attach+0x28/0x40
 [c0077cbefa20] [c02204d8] .bus_add_driver+0x90/0x228
 [c0077cbefac0] [c0221858] .driver_register+0x94/0xb0
 [c0077cbefb40] [c01bc430] .__pci_register_driver+0x6c/0xcc
 [c0077cbefbe0] [d0143428] .sym2_init+0x108/0x15b0 [sym53c8xx]
 [c0077cbefc80] [c008ce80] .sys_init_module+0x17c4/0x1958
 [c0077cbefe30] [c000872c] syscall_exit+0x0/0x40
 Instruction dump:
 6000 786b0420 38210070 7d635b78 e8010010 7c0803a6 4e800020 7c0802a6 
 f8010010 f821ff91 7c0004ac 8923 0c09 4c00012c 79290620 2f8900ff 
 I see no obvious lockup sites near the end of sym_hcb_attach().  Maybe it's
 being called lots of times from a higher level..  Do the traces all look
 the same?
 Hi Andrew,

 I see this call trace twice and both looks similar and on another reboot
 the following trace is seen twice in different cpu

 BUG: soft lockup detected on CPU#3!
 Call Trace:
 [C0003FEDEDA0] [C0010220] .show_stack+0x68/0x1b0 (unreliable)
 [C0003FEDEE40] [C00A061C] .softlockup_tick+0xf0/0x13c
 [C0003FEDEEF0] [C0072E2C] .run_local_timers+0x1c/0x30
 [C0003FEDEF70] [C0022FA0] .timer_interrupt+0xa8/0x488
 [C0003FEDF050] [C00034EC] decrementer_common+0xec/0x100
 --- Exception: 901 at .ioread8+0x14/0x60
 LR = .sym_hcb_attach+0x1194/0x1384 [sym53c8xx]
 [C0003FEDF340] [D02B3BC0] 0xd02b3bc0 (unreliable)
 [C0003FEDF3B0] [D029A3C0] .sym_hcb_attach+0x1194/0x1384 
 [sym53c8xx]
 [C0003FEDF480] [D0291D30] .sym2_probe+0x75c/0x9f8 [sym53c8xx]
 [C0003FEDF710] [C01B65A4] .pci_device_probe+0x13c/0x1dc
 [C0003FEDF7D0] [C0219A0C] .driver_probe_device+0xa0/0x15c
 [C0003FEDF870] [C0219C64] .__driver_attach+0xb4/0x138
 [C0003FEDF900] [C021913C] .bus_for_each_dev+0x7c/0xd4
 [C0003FEDF9C0] [C02198B0] .driver_attach+0x28/0x40
 [C0003FEDFA40] [C0218BA4] .bus_add_driver+0x98/0x18c
 [C0003FEDFAE0] [C021A064] .driver_register+0xa8/0xc4
 [C0003FEDFB60] [C01B68AC] .__pci_register_driver+0x5c/0xa4
 [C0003FEDFBF0] [D029C204] .sym2_init+0x104/0x1550 [sym53c8xx]
 [C0003FEDFC90] [C008D1F4] .sys_init_module+0x1764/0x1998
 [C0003FEDFE30] [C000869C] syscall_exit+0x0/0x40

 
 hm, odd.
 
 Can you look up sym_hcb_attach+0x1194/0x1384 in gdb?  Something like
 
Hi Andrew,

I tried with 2.6.24-rc3-git3 and got the following trace

BUG: soft lockup - CPU#2 stuck for 11s! [insmod:375]
NIP: c002f02c LR: d01414fc CTR: c002f018
REGS: c0077ca3b0b0 TRAP: 0901   Not tainted  (2.6.24-rc3-git3-autokern1)
MSR: 80009032 EE,ME,IR,DR  CR: 24022088  XER: 
TASK = c0077cc58000[375] 'insmod' THREAD: c0077ca38000 CPU: 2
GPR00: d01414fc c0077ca3b330 c052b880 d80080002014 
GPR04: d8008000202c  c0077c82eb00 d014ce54 
GPR08: c0077c82e63c  002a c002f018 
GPR12: d0143610 c0473f80 
NIP [c002f02c] .ioread8+0x14/0x60
LR [d01414fc] .sym_hcb_attach+0x1188/0x1378 [sym53c8xx]

Call Trace:
[c0077ca3b330] [c0077ca3b3c0] 0xc0077ca3b3c0 (unreliable)
[c0077ca3b3a0] [d01414fc] .sym_hcb_attach

Re: [BUG] 2.6.24-rc3-git2 softlockup detected

[Kamalesh Babulal]

Andrew Morton wrote:
> On Wed, 28 Nov 2007 11:59:00 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> 
>> Hi,
> 
> (cc linux-scsi, for sym53c8xx)
> 
>> Soft lockup is detected while bootup with 2.6.24-rc3-git2 on powerbox
> 
> I assume this is a post-2.6.23 regression?
> 
>> BUG: soft lockup - CPU#1 stuck for 11s! [insmod:375]
>> NIP: c002f02c LR: d01414fc CTR: c002f018
>> REGS: c0077cbef0b0 TRAP: 0901   Not tainted  (2.6.24-rc3-git2-autotest)
>> MSR: 80009032   CR: 24022088  XER: 
>> TASK = c0077cbd8000[375] 'insmod' THREAD: c0077cbec000 CPU: 1
>> GPR00: d01414fc c0077cbef330 c052b930 d80080002014 
>> GPR04: d8008000202c  c0077ca1cb00 d014ce54 
>> GPR08: c0077ca1c63c  002a c002f018 
>> GPR12: d0143610 c0473d00 
>> NIP [c002f02c] .ioread8+0x14/0x60
>> LR [d01414fc] .sym_hcb_attach+0x1188/0x1378 [sym53c8xx]
>> Call Trace:
>> [c0077cbef330] [c0077cbef3c0] 0xc0077cbef3c0 (unreliable)
>> [c0077cbef3a0] [d01414fc] .sym_hcb_attach+0x1188/0x1378 
>> [sym53c8xx]
>> [c0077cbef470] [d01395f8] .sym2_probe+0x700/0x99c [sym53c8xx]
>> [c0077cbef710] [c01bc118] .pci_device_probe+0x124/0x1b0
>> [c0077cbef7b0] [c0221138] .driver_probe_device+0x144/0x20c
>> [c0077cbef850] [c0221450] .__driver_attach+0xcc/0x154
>> [c0077cbef8e0] [c021ff94] .bus_for_each_dev+0x7c/0xd4
>> [c0077cbef9a0] [c0220e9c] .driver_attach+0x28/0x40
>> [c0077cbefa20] [c02204d8] .bus_add_driver+0x90/0x228
>> [c0077cbefac0] [c0221858] .driver_register+0x94/0xb0
>> [c0077cbefb40] [c01bc430] .__pci_register_driver+0x6c/0xcc
>> [c0077cbefbe0] [d0143428] .sym2_init+0x108/0x15b0 [sym53c8xx]
>> [c0077cbefc80] [c008ce80] .sys_init_module+0x17c4/0x1958
>> [c0077cbefe30] [c000872c] syscall_exit+0x0/0x40
>> Instruction dump:
>> 6000 786b0420 38210070 7d635b78 e8010010 7c0803a6 4e800020 7c0802a6 
>> f8010010 f821ff91 7c0004ac 8923 <0c09> 4c00012c 79290620 2f8900ff 
> 
> I see no obvious lockup sites near the end of sym_hcb_attach().  Maybe it's
> being called lots of times from a higher level..  Do the traces all look
> the same?

Hi Andrew,

I see this call trace twice and both looks similar and on another reboot
the following trace is seen twice in different cpu

BUG: soft lockup detected on CPU#3!
Call Trace:
[C0003FEDEDA0] [C0010220] .show_stack+0x68/0x1b0 (unreliable)
[C0003FEDEE40] [C00A061C] .softlockup_tick+0xf0/0x13c
[C0003FEDEEF0] [C0072E2C] .run_local_timers+0x1c/0x30
[C0003FEDEF70] [C0022FA0] .timer_interrupt+0xa8/0x488
[C0003FEDF050] [C00034EC] decrementer_common+0xec/0x100
--- Exception: 901 at .ioread8+0x14/0x60
LR = .sym_hcb_attach+0x1194/0x1384 [sym53c8xx]
[C0003FEDF340] [D02B3BC0] 0xd02b3bc0 (unreliable)
[C0003FEDF3B0] [D029A3C0] .sym_hcb_attach+0x1194/0x1384 [sym53c8xx]
[C0003FEDF480] [D0291D30] .sym2_probe+0x75c/0x9f8 [sym53c8xx]
[C0003FEDF710] [C01B65A4] .pci_device_probe+0x13c/0x1dc
[C0003FEDF7D0] [C0219A0C] .driver_probe_device+0xa0/0x15c
[C0003FEDF870] [C0219C64] .__driver_attach+0xb4/0x138
[C0003FEDF900] [C021913C] .bus_for_each_dev+0x7c/0xd4
[C0003FEDF9C0] [C02198B0] .driver_attach+0x28/0x40
[C0003FEDFA40] [C0218BA4] .bus_add_driver+0x98/0x18c
[C0003FEDFAE0] [C021A064] .driver_register+0xa8/0xc4
[C0003FEDFB60] [C01B68AC] .__pci_register_driver+0x5c/0xa4
[C0003FEDFBF0] [D029C204] .sym2_init+0x104/0x1550 [sym53c8xx]
[C0003FEDFC90] [C008D1F4] .sys_init_module+0x1764/0x1998
[C0003FEDFE30] [C000869C] syscall_exit+0x0/0x40


-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[BUG] 2.6.24-rc3-git2 softlockup detected

[Kamalesh Babulal]

Hi,

Soft lockup is detected while bootup with 2.6.24-rc3-git2 on powerbox

BUG: soft lockup - CPU#1 stuck for 11s! [insmod:375]
NIP: c002f02c LR: d01414fc CTR: c002f018
REGS: c0077cbef0b0 TRAP: 0901   Not tainted  (2.6.24-rc3-git2-autotest)
MSR: 80009032   CR: 24022088  XER: 
TASK = c0077cbd8000[375] 'insmod' THREAD: c0077cbec000 CPU: 1
GPR00: d01414fc c0077cbef330 c052b930 d80080002014 
GPR04: d8008000202c  c0077ca1cb00 d014ce54 
GPR08: c0077ca1c63c  002a c002f018 
GPR12: d0143610 c0473d00 
NIP [c002f02c] .ioread8+0x14/0x60
LR [d01414fc] .sym_hcb_attach+0x1188/0x1378 [sym53c8xx]
Call Trace:
[c0077cbef330] [c0077cbef3c0] 0xc0077cbef3c0 (unreliable)
[c0077cbef3a0] [d01414fc] .sym_hcb_attach+0x1188/0x1378 [sym53c8xx]
[c0077cbef470] [d01395f8] .sym2_probe+0x700/0x99c [sym53c8xx]
[c0077cbef710] [c01bc118] .pci_device_probe+0x124/0x1b0
[c0077cbef7b0] [c0221138] .driver_probe_device+0x144/0x20c
[c0077cbef850] [c0221450] .__driver_attach+0xcc/0x154
[c0077cbef8e0] [c021ff94] .bus_for_each_dev+0x7c/0xd4
[c0077cbef9a0] [c0220e9c] .driver_attach+0x28/0x40
[c0077cbefa20] [c02204d8] .bus_add_driver+0x90/0x228
[c0077cbefac0] [c0221858] .driver_register+0x94/0xb0
[c0077cbefb40] [c01bc430] .__pci_register_driver+0x6c/0xcc
[c0077cbefbe0] [d0143428] .sym2_init+0x108/0x15b0 [sym53c8xx]
[c0077cbefc80] [c008ce80] .sys_init_module+0x17c4/0x1958
[c0077cbefe30] [c000872c] syscall_exit+0x0/0x40
Instruction dump:
6000 786b0420 38210070 7d635b78 e8010010 7c0803a6 4e800020 7c0802a6 
f8010010 f821ff91 7c0004ac 8923 <0c09> 4c00012c 79290620 2f8900ff 

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[BUG] 2.6.24-rc3-git2 softlockup detected

[Kamalesh Babulal]

Hi,

Soft lockup is detected while bootup with 2.6.24-rc3-git2 on powerbox

BUG: soft lockup - CPU#1 stuck for 11s! [insmod:375]
NIP: c002f02c LR: d01414fc CTR: c002f018
REGS: c0077cbef0b0 TRAP: 0901   Not tainted  (2.6.24-rc3-git2-autotest)
MSR: 80009032 EE,ME,IR,DR  CR: 24022088  XER: 
TASK = c0077cbd8000[375] 'insmod' THREAD: c0077cbec000 CPU: 1
GPR00: d01414fc c0077cbef330 c052b930 d80080002014 
GPR04: d8008000202c  c0077ca1cb00 d014ce54 
GPR08: c0077ca1c63c  002a c002f018 
GPR12: d0143610 c0473d00 
NIP [c002f02c] .ioread8+0x14/0x60
LR [d01414fc] .sym_hcb_attach+0x1188/0x1378 [sym53c8xx]
Call Trace:
[c0077cbef330] [c0077cbef3c0] 0xc0077cbef3c0 (unreliable)
[c0077cbef3a0] [d01414fc] .sym_hcb_attach+0x1188/0x1378 [sym53c8xx]
[c0077cbef470] [d01395f8] .sym2_probe+0x700/0x99c [sym53c8xx]
[c0077cbef710] [c01bc118] .pci_device_probe+0x124/0x1b0
[c0077cbef7b0] [c0221138] .driver_probe_device+0x144/0x20c
[c0077cbef850] [c0221450] .__driver_attach+0xcc/0x154
[c0077cbef8e0] [c021ff94] .bus_for_each_dev+0x7c/0xd4
[c0077cbef9a0] [c0220e9c] .driver_attach+0x28/0x40
[c0077cbefa20] [c02204d8] .bus_add_driver+0x90/0x228
[c0077cbefac0] [c0221858] .driver_register+0x94/0xb0
[c0077cbefb40] [c01bc430] .__pci_register_driver+0x6c/0xcc
[c0077cbefbe0] [d0143428] .sym2_init+0x108/0x15b0 [sym53c8xx]
[c0077cbefc80] [c008ce80] .sys_init_module+0x17c4/0x1958
[c0077cbefe30] [c000872c] syscall_exit+0x0/0x40
Instruction dump:
6000 786b0420 38210070 7d635b78 e8010010 7c0803a6 4e800020 7c0802a6 
f8010010 f821ff91 7c0004ac 8923 0c09 4c00012c 79290620 2f8900ff 

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] 2.6.24-rc3-git2 softlockup detected

[Kamalesh Babulal]

Andrew Morton wrote:
 On Wed, 28 Nov 2007 11:59:00 +0530 Kamalesh Babulal [EMAIL PROTECTED] wrote:
 
 Hi,
 
 (cc linux-scsi, for sym53c8xx)
 
 Soft lockup is detected while bootup with 2.6.24-rc3-git2 on powerbox
 
 I assume this is a post-2.6.23 regression?
 
 BUG: soft lockup - CPU#1 stuck for 11s! [insmod:375]
 NIP: c002f02c LR: d01414fc CTR: c002f018
 REGS: c0077cbef0b0 TRAP: 0901   Not tainted  (2.6.24-rc3-git2-autotest)
 MSR: 80009032 EE,ME,IR,DR  CR: 24022088  XER: 
 TASK = c0077cbd8000[375] 'insmod' THREAD: c0077cbec000 CPU: 1
 GPR00: d01414fc c0077cbef330 c052b930 d80080002014 
 GPR04: d8008000202c  c0077ca1cb00 d014ce54 
 GPR08: c0077ca1c63c  002a c002f018 
 GPR12: d0143610 c0473d00 
 NIP [c002f02c] .ioread8+0x14/0x60
 LR [d01414fc] .sym_hcb_attach+0x1188/0x1378 [sym53c8xx]
 Call Trace:
 [c0077cbef330] [c0077cbef3c0] 0xc0077cbef3c0 (unreliable)
 [c0077cbef3a0] [d01414fc] .sym_hcb_attach+0x1188/0x1378 
 [sym53c8xx]
 [c0077cbef470] [d01395f8] .sym2_probe+0x700/0x99c [sym53c8xx]
 [c0077cbef710] [c01bc118] .pci_device_probe+0x124/0x1b0
 [c0077cbef7b0] [c0221138] .driver_probe_device+0x144/0x20c
 [c0077cbef850] [c0221450] .__driver_attach+0xcc/0x154
 [c0077cbef8e0] [c021ff94] .bus_for_each_dev+0x7c/0xd4
 [c0077cbef9a0] [c0220e9c] .driver_attach+0x28/0x40
 [c0077cbefa20] [c02204d8] .bus_add_driver+0x90/0x228
 [c0077cbefac0] [c0221858] .driver_register+0x94/0xb0
 [c0077cbefb40] [c01bc430] .__pci_register_driver+0x6c/0xcc
 [c0077cbefbe0] [d0143428] .sym2_init+0x108/0x15b0 [sym53c8xx]
 [c0077cbefc80] [c008ce80] .sys_init_module+0x17c4/0x1958
 [c0077cbefe30] [c000872c] syscall_exit+0x0/0x40
 Instruction dump:
 6000 786b0420 38210070 7d635b78 e8010010 7c0803a6 4e800020 7c0802a6 
 f8010010 f821ff91 7c0004ac 8923 0c09 4c00012c 79290620 2f8900ff 
 
 I see no obvious lockup sites near the end of sym_hcb_attach().  Maybe it's
 being called lots of times from a higher level..  Do the traces all look
 the same?

Hi Andrew,

I see this call trace twice and both looks similar and on another reboot
the following trace is seen twice in different cpu

BUG: soft lockup detected on CPU#3!
Call Trace:
[C0003FEDEDA0] [C0010220] .show_stack+0x68/0x1b0 (unreliable)
[C0003FEDEE40] [C00A061C] .softlockup_tick+0xf0/0x13c
[C0003FEDEEF0] [C0072E2C] .run_local_timers+0x1c/0x30
[C0003FEDEF70] [C0022FA0] .timer_interrupt+0xa8/0x488
[C0003FEDF050] [C00034EC] decrementer_common+0xec/0x100
--- Exception: 901 at .ioread8+0x14/0x60
LR = .sym_hcb_attach+0x1194/0x1384 [sym53c8xx]
[C0003FEDF340] [D02B3BC0] 0xd02b3bc0 (unreliable)
[C0003FEDF3B0] [D029A3C0] .sym_hcb_attach+0x1194/0x1384 [sym53c8xx]
[C0003FEDF480] [D0291D30] .sym2_probe+0x75c/0x9f8 [sym53c8xx]
[C0003FEDF710] [C01B65A4] .pci_device_probe+0x13c/0x1dc
[C0003FEDF7D0] [C0219A0C] .driver_probe_device+0xa0/0x15c
[C0003FEDF870] [C0219C64] .__driver_attach+0xb4/0x138
[C0003FEDF900] [C021913C] .bus_for_each_dev+0x7c/0xd4
[C0003FEDF9C0] [C02198B0] .driver_attach+0x28/0x40
[C0003FEDFA40] [C0218BA4] .bus_add_driver+0x98/0x18c
[C0003FEDFAE0] [C021A064] .driver_register+0xa8/0xc4
[C0003FEDFB60] [C01B68AC] .__pci_register_driver+0x5c/0xa4
[C0003FEDFBF0] [D029C204] .sym2_init+0x104/0x1550 [sym53c8xx]
[C0003FEDFC90] [C008D1F4] .sys_init_module+0x1764/0x1998
[C0003FEDFE30] [C000869C] syscall_exit+0x0/0x40


-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: In /proc/cpuinfo, all processor items show "0"

[Kamalesh Babulal]

ssor : 0
> vendor_id : GenuineIntel
> cpu family: 15
> model : 6
> model name:Genuine Intel(R) CPU 3.40GHz
> stepping  : 8
> cpu MHz   : 3391.555
> cache size: 16384 KB
> physical id   : 1
> siblings  : 4
> core id   : 1
> cpu cores : 2
> fpu   : yes
> fpu_exception : yes
> cpuid level   : 6
> wp: yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
> pat
> pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
> constant_tsc pebs bts sync_rdtsc pni monitor ds_cpl vmx est tm2 cid cx16
> xtpr lahf_lm
> bogomips  : 6782.82
> clflush size  : 64
> cache_alignment   : 128
> address sizes : 40 bits physical, 48 bits virtual
> power management:
> 
> processor : 0
> vendor_id : GenuineIntel
> cpu family: 15
> model : 6
> model name:Genuine Intel(R) CPU 3.40GHz
> stepping  : 8
> cpu MHz   : 3391.555
> cache size: 16384 KB
> physical id   : 2
> siblings  : 4
> core id   : 1
> cpu cores : 2
> fpu   : yes
> fpu_exception : yes
> cpuid level   : 6
> wp: yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
> pat
> pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
> constant_tsc pebs bts sync_rdtsc pni monitor ds_cpl vmx est tm2 cid cx16
> xtpr lahf_lm
> bogomips  : 6782.81
> clflush size  : 64
> cache_alignment   : 128
> address sizes : 40 bits physical, 48 bits virtual
> power management:
> 
> processor : 0
> vendor_id : GenuineIntel
> cpu family: 15
> model : 6
> model name:Genuine Intel(R) CPU 3.40GHz
> stepping  : 8
> cpu MHz   : 3391.555
> cache size: 16384 KB
> physical id   : 3
> siblings  : 4
> core id   : 0
> cpu cores : 2
> fpu   : yes
> fpu_exception : yes
> cpuid level   : 6
> wp: yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
> pat
> pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
> constant_tsc pebs bts sync_rdtsc pni monitor ds_cpl vmx est tm2 cid cx16
> xtpr lahf_lm
> bogomips  : 6782.81
> clflush size  : 64
> cache_alignment   : 128
> address sizes : 40 bits physical, 48 bits virtual
> power management:
> 
> processor : 0
> vendor_id : GenuineIntel
> cpu family: 15
> model : 6
> model name:Genuine Intel(R) CPU 3.40GHz
> stepping  : 8
> cpu MHz   : 3391.555
> cache size: 16384 KB
> physical id   : 0
> siblings  : 4
> core id   : 1
> cpu cores : 2
> fpu   : yes
> fpu_exception : yes
> cpuid level   : 6
> wp: yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
> pat
> pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
> constant_tsc pebs bts sync_rdtsc pni monitor ds_cpl vmx est tm2 cid cx16
> xtpr lahf_lm
> bogomips  : 6782.74
> clflush size  : 64
> cache_alignment   : 128
> address sizes : 40 bits physical, 48 bits virtual
> power management:
> 
> processor : 0
> vendor_id : GenuineIntel
> cpu family: 15
> model : 6
> model name:Genuine Intel(R) CPU 3.40GHz
> stepping  : 8
> cpu MHz   : 3391.555
> cache size: 16384 KB
> physical id   : 1
> siblings  : 4
> core id   : 0
> cpu cores : 2
> fpu   : yes
> fpu_exception : yes
> cpuid level   : 6
> wp: yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
> pat
> pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
> constant_tsc pebs bts sync_rdtsc pni monitor ds_cpl vmx est tm2 cid cx16
> xtpr lahf_lm
> bogomips  : 6782.79
> clflush size  : 64
> cache_alignment   : 128
> address sizes : 40 bits physical, 48 bits virtual
> power management:

Hi,

This patch should help you http://marc.info/?l=linux-kernel=119392088227245.

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: In /proc/cpuinfo, all processor items show 0

[Kamalesh Babulal]

 pge mca cmov 
 pat
 pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
 constant_tsc pebs bts sync_rdtsc pni monitor ds_cpl vmx est tm2 cid cx16
 xtpr lahf_lm
 bogomips  : 6782.81
 clflush size  : 64
 cache_alignment   : 128
 address sizes : 40 bits physical, 48 bits virtual
 power management:
 
 processor : 0
 vendor_id : GenuineIntel
 cpu family: 15
 model : 6
 model name:Genuine Intel(R) CPU 3.40GHz
 stepping  : 8
 cpu MHz   : 3391.555
 cache size: 16384 KB
 physical id   : 3
 siblings  : 4
 core id   : 0
 cpu cores : 2
 fpu   : yes
 fpu_exception : yes
 cpuid level   : 6
 wp: yes
 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
 pat
 pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
 constant_tsc pebs bts sync_rdtsc pni monitor ds_cpl vmx est tm2 cid cx16
 xtpr lahf_lm
 bogomips  : 6782.81
 clflush size  : 64
 cache_alignment   : 128
 address sizes : 40 bits physical, 48 bits virtual
 power management:
 
 processor : 0
 vendor_id : GenuineIntel
 cpu family: 15
 model : 6
 model name:Genuine Intel(R) CPU 3.40GHz
 stepping  : 8
 cpu MHz   : 3391.555
 cache size: 16384 KB
 physical id   : 0
 siblings  : 4
 core id   : 1
 cpu cores : 2
 fpu   : yes
 fpu_exception : yes
 cpuid level   : 6
 wp: yes
 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
 pat
 pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
 constant_tsc pebs bts sync_rdtsc pni monitor ds_cpl vmx est tm2 cid cx16
 xtpr lahf_lm
 bogomips  : 6782.74
 clflush size  : 64
 cache_alignment   : 128
 address sizes : 40 bits physical, 48 bits virtual
 power management:
 
 processor : 0
 vendor_id : GenuineIntel
 cpu family: 15
 model : 6
 model name:Genuine Intel(R) CPU 3.40GHz
 stepping  : 8
 cpu MHz   : 3391.555
 cache size: 16384 KB
 physical id   : 1
 siblings  : 4
 core id   : 0
 cpu cores : 2
 fpu   : yes
 fpu_exception : yes
 cpuid level   : 6
 wp: yes
 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
 pat
 pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
 constant_tsc pebs bts sync_rdtsc pni monitor ds_cpl vmx est tm2 cid cx16
 xtpr lahf_lm
 bogomips  : 6782.79
 clflush size  : 64
 cache_alignment   : 128
 address sizes : 40 bits physical, 48 bits virtual
 power management:

Hi,

This patch should help you http://marc.info/?l=linux-kernelm=119392088227245.

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc3-mm1 - Kernel Panic on IO-APIC

[Kamalesh Babulal]

Andrew Morton wrote:
> On Wed, 21 Nov 2007 14:52:26 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> 
>> Andrew Morton wrote:
>>> On Wed, 21 Nov 2007 11:41:23 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> 
>>> wrote:
>>>
>>>> Hi Andrew,
>>>>
>>>> Kernel panic's across different architectures like powerpc, x86_64, 
>>> powerpc complains about IO-APICs??
>>>
>>>> Dentry cache hash table entries: 8388608 (order: 14, 67108864 bytes)
>>>> Inode-cache hash table entries: 4194304 (order: 13, 33554432 bytes)
>>>> Mount-cache hash table entries: 256
>>>> SMP alternatives: switching to UP code
>>>> ACPI: Core revision 20070126
>>>> ..MP-BIOS bug: 8254 timer not connected to IO-APIC
>>>> Kernel panic - not syncing: IO-APIC + timer doesn't work! Try using the 
>>>> 'noapic' kernel parameter
>>> ACPI or x86 breakage, I guess.
>>>
>>> Did 'noapic' work?
>> Hi Andrew,
>>
>> Passing noapic works,
> 
> OK.
> 
>>  but the kernel oops's 
>>
>> [   97.161103] Unable to handle kernel NULL pointer dereference at 
>> 0009 RIP:
>> [   97.193973]  [] cpu_to_allnodes_group+0x69/0x7c
>> [   97.245359] PGD 0
>> [   97.257611] Oops:  [1] SMP
>> [   97.276638] last sysfs file:
>> [   97.294417] CPU 0
>> [   97.306620] Modules linked in:
>> [   97.325066] Pid: 1, comm: swapper Not tainted 2.6.24-rc3-mm1 #1
>> [   97.360514] RIP: 0010:[]  [] 
>> cpu_to_allnodes_group+0x69/0x7c
>> [   97.413287] RSP: :81012fabb650  EFLAGS: 00010286
>> [   97.445363] RAX: 809bb060 RBX: 81012fabb650 RCX: 
>> 00ff
>> [   97.488378] RDX: 0001 RSI: 013e RDI: 
>> 0100
>> [   97.531413] RBP: 81012fabb680 R08: 81012fa88180 R09: 
>> 
>> [   97.574428] R10:  R11:  R12: 
>> 810001005f50
>> [   97.617394] R13:  R14: 81012fa88180 R15: 
>> 810001005f40
>> [   97.660421] FS:  () GS:806c3000() 
>> knlGS:
>> [   97.709327] CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
>> [   97.743995] CR2: 0009 CR3: 00201000 CR4: 
>> 06a0
>> [   97.787021] DR0:  DR1:  DR2: 
>> 
>> [   97.830053] DR3:  DR6: 0ff0 DR7: 
>> 0400
>> [   97.873036] Process swapper (pid: 1, threadinfo 81012FABA000, task 
>> 81012FAB8040)
>> [   97.921993] Stack:     
>> 
>> [   97.971056]  810001005f40 81012fabb700 81012fabbdf0 
>> 80235487
>> [   98.016420]     
>> 
>> [   98.060324] Call Trace:
>> [   98.076657]  [] build_sched_domains+0x1e1/0xc19
>> [   98.113383]  [] __kernel_text_address+0x22/0x30
>> [   98.150173]  [] check_chain_key+0x9c/0x15f
>> [   98.184355]  [] mark_lock+0x3b/0x5b3
>> [   98.215406]  [] mark_held_locks+0x4a/0x6a
>> [   98.249027]  [] get_page_from_freelist+0x42a/0x77d
>> [   98.287362]  [] trace_hardirqs_on+0x198/0x1c3
>> [   98.323123]  [] get_page_from_freelist+0x75a/0x77d
>> [   98.361429]  [] mark_lock+0x3b/0x5b3
>> [   98.392427]  [] check_chain_key+0x9c/0x15f
>> [   98.426621]  [] number+0x115/0x21f
>> [   98.456594]  [] __kernel_text_address+0x22/0x30
>> [   98.493362]  [] dump_trace+0x248/0x25d
>> [   98.525493]  [] check_chain_key+0x9c/0x15f
>> [   98.559678]  [] __lock_acquire+0xdee/0xf06
>> [   98.593868]  [] check_chain_key+0x9c/0x15f
>> [   98.628038]  [] check_chain_key+0x9c/0x15f
>> [   98.662225]  [] check_chain_key+0x9c/0x15f
>> [   98.696370]  [] __lock_acquire+0xdee/0xf06
>> [   98.730563]  [] check_chain_key+0x9c/0x15f
>> [   98.764689]  [] mark_lock+0x3b/0x5b3
>> [   98.795767]  [] mark_held_locks+0x4a/0x6a
>> [   98.829432]  [] number+0x115/0x21f
>> [   98.859460]  [] kprobe_flush_task+0x63/0xa9
>> [   98.894166]  [] vsnprintf+0x58f/0x5d5
>> [   98.925739]  [] sprintf+0x68/0x6a
>> [   98.955257]  [] lock_acquire+0x72/0xe0
>> [   98.987363]  [] lock_acquired+0x57/0x1d4
>> [   99.020446]  [] lock_release+0x67/0x21a
>> [   99.053079]  [] check_chain_key+0x9c/0x15f
>> [   99.087261]  [] mark_lock+0x3b/0x5b3
>> [   99.118328]  [] mark_lock+0x3b/0x5b3
>> [   99.149394]  [] arch_ini

Re: 2.6.24-rc3-mm1 - Kernel Panic on IO-APIC

[Kamalesh Babulal]

Andrew Morton wrote:
> On Wed, 21 Nov 2007 11:41:23 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> 
>> Hi Andrew,
>>
>> Kernel panic's across different architectures like powerpc, x86_64, 
> 
> powerpc complains about IO-APICs??
> 
>> Dentry cache hash table entries: 8388608 (order: 14, 67108864 bytes)
>> Inode-cache hash table entries: 4194304 (order: 13, 33554432 bytes)
>> Mount-cache hash table entries: 256
>> SMP alternatives: switching to UP code
>> ACPI: Core revision 20070126
>> ..MP-BIOS bug: 8254 timer not connected to IO-APIC
>> Kernel panic - not syncing: IO-APIC + timer doesn't work! Try using the 
>> 'noapic' kernel parameter
> 
> ACPI or x86 breakage, I guess.
> 
> Did 'noapic' work?
Hi Andrew,

Passing noapic works, but the kernel oops's 

[   97.161103] Unable to handle kernel NULL pointer dereference at 
0009 RIP:
[   97.193973]  [] cpu_to_allnodes_group+0x69/0x7c
[   97.245359] PGD 0
[   97.257611] Oops:  [1] SMP
[   97.276638] last sysfs file:
[   97.294417] CPU 0
[   97.306620] Modules linked in:
[   97.325066] Pid: 1, comm: swapper Not tainted 2.6.24-rc3-mm1 #1
[   97.360514] RIP: 0010:[]  [] 
cpu_to_allnodes_group+0x69/0x7c
[   97.413287] RSP: :81012fabb650  EFLAGS: 00010286
[   97.445363] RAX: 809bb060 RBX: 81012fabb650 RCX: 00ff
[   97.488378] RDX: 0001 RSI: 013e RDI: 0100
[   97.531413] RBP: 81012fabb680 R08: 81012fa88180 R09: 
[   97.574428] R10:  R11:  R12: 810001005f50
[   97.617394] R13:  R14: 81012fa88180 R15: 810001005f40
[   97.660421] FS:  () GS:806c3000() 
knlGS:
[   97.709327] CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
[   97.743995] CR2: 0009 CR3: 00201000 CR4: 06a0
[   97.787021] DR0:  DR1:  DR2: 
[   97.830053] DR3:  DR6: 0ff0 DR7: 0400
[   97.873036] Process swapper (pid: 1, threadinfo 81012FABA000, task 
81012FAB8040)
[   97.921993] Stack:     

[   97.971056]  810001005f40 81012fabb700 81012fabbdf0 
80235487
[   98.016420]     

[   98.060324] Call Trace:
[   98.076657]  [] build_sched_domains+0x1e1/0xc19
[   98.113383]  [] __kernel_text_address+0x22/0x30
[   98.150173]  [] check_chain_key+0x9c/0x15f
[   98.184355]  [] mark_lock+0x3b/0x5b3
[   98.215406]  [] mark_held_locks+0x4a/0x6a
[   98.249027]  [] get_page_from_freelist+0x42a/0x77d
[   98.287362]  [] trace_hardirqs_on+0x198/0x1c3
[   98.323123]  [] get_page_from_freelist+0x75a/0x77d
[   98.361429]  [] mark_lock+0x3b/0x5b3
[   98.392427]  [] check_chain_key+0x9c/0x15f
[   98.426621]  [] number+0x115/0x21f
[   98.456594]  [] __kernel_text_address+0x22/0x30
[   98.493362]  [] dump_trace+0x248/0x25d
[   98.525493]  [] check_chain_key+0x9c/0x15f
[   98.559678]  [] __lock_acquire+0xdee/0xf06
[   98.593868]  [] check_chain_key+0x9c/0x15f
[   98.628038]  [] check_chain_key+0x9c/0x15f
[   98.662225]  [] check_chain_key+0x9c/0x15f
[   98.696370]  [] __lock_acquire+0xdee/0xf06
[   98.730563]  [] check_chain_key+0x9c/0x15f
[   98.764689]  [] mark_lock+0x3b/0x5b3
[   98.795767]  [] mark_held_locks+0x4a/0x6a
[   98.829432]  [] number+0x115/0x21f
[   98.859460]  [] kprobe_flush_task+0x63/0xa9
[   98.894166]  [] vsnprintf+0x58f/0x5d5
[   98.925739]  [] sprintf+0x68/0x6a
[   98.955257]  [] lock_acquire+0x72/0xe0
[   98.987363]  [] lock_acquired+0x57/0x1d4
[   99.020446]  [] lock_release+0x67/0x21a
[   99.053079]  [] check_chain_key+0x9c/0x15f
[   99.087261]  [] mark_lock+0x3b/0x5b3
[   99.118328]  [] mark_lock+0x3b/0x5b3
[   99.149394]  [] arch_init_sched_domains+0x27/0x69
[   99.187217]  [] dbg_redzone2+0x2a/0x52
[   99.219320]  [] cache_alloc_debugcheck_after+0x16e/0x1cb
[   99.260779]  [] kmem_cache_alloc+0x15e/0x182
[   99.295944]  [] arch_init_sched_domains+0x5c/0x69
[   99.333768]  [] sched_init_smp+0x27/0x113
[   99.367400]  [] __bitmap_weight+0x78/0x8d
[   99.401090]  [] kernel_init+0x12d/0x315
[   99.433718]  [] _spin_unlock_irq+0x2b/0x30
[   99.467842]  [] trace_hardirqs_on+0x198/0x1c3
[   99.503534]  [] trace_hardirqs_on+0x198/0x1c3
[   99.539251]  [] child_rip+0xa/0x12
[   99.569234]  [] restore_args+0x0/0x30
[   99.600845]  [] kernel_init+0x0/0x315
[   99.632426]  [] child_rip+0x0/0x12
[   99.662455]
[   99.671637] INFO: lockdep is turned off.
[   99.695385]
[   99.695385] Code: 48 03 42 08 49 89 04 24 48 83 c4 20 89 c8 5b 41 5c c9 c3 55
[   99.750603] RIP  [] cpu_to_allnodes_group+0x69/0x7c
[   99.789632]  RSP 

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list

Re: 2.6.24-rc3-mm1- powerpc link failure

[Kamalesh Babulal]

Hi Andrew,

The kernel build fails on powerpc while linking,

  AS  .tmp_kallsyms3.o
  LD  vmlinux.o
ld: TOC section size exceeds 64k
make: *** [vmlinux.o] Error 1

The patch posted at http://lkml.org/lkml/2007/11/13/414, solves this 
failure.

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc3-mm1 make headers_check fails

[Kamalesh Babulal]

Andrew Morton wrote:
> On Wed, 21 Nov 2007 13:54:50 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> 
>> The make headers_check fails,
>>
>>   CHECK   include/linux/usb/gadgetfs.h
>>   CHECK   include/linux/usb/ch9.h
>>   CHECK   include/linux/usb/cdc.h
>>   CHECK   include/linux/usb/audio.h
>>   CHECK   include/linux/kvm.h
>> /root/kernels/linux-2.6.24-rc3/usr/include/linux/kvm.h requires asm/kvm.h, 
>> which does not exist in exported headers
> 
> hm, works for me, on i386 and x86_64.  What's different over there?
Hi Andrew,

It fails on the powerpc box, with allyesconfig option.

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc3-mm1 make headers_check fails

[Kamalesh Babulal]

Hi Andrew,

The make headers_check fails,

  CHECK   include/linux/usb/gadgetfs.h
  CHECK   include/linux/usb/ch9.h
  CHECK   include/linux/usb/cdc.h
  CHECK   include/linux/usb/audio.h
  CHECK   include/linux/kvm.h
/root/kernels/linux-2.6.24-rc3/usr/include/linux/kvm.h requires asm/kvm.h, 
which does not exist in exported headers
make[2]: *** [/root/kernels/linux-2.6.24-rc3/usr/include/linux/.check.kvm.h] 
Error 1
make[1]: *** [linux] Error 2
make: *** [headers_check] Error 2


-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc3-mm1 make headers_check fails

[Kamalesh Babulal]

Hi Andrew,

The make headers_check fails,

  CHECK   include/linux/usb/gadgetfs.h
  CHECK   include/linux/usb/ch9.h
  CHECK   include/linux/usb/cdc.h
  CHECK   include/linux/usb/audio.h
  CHECK   include/linux/kvm.h
/root/kernels/linux-2.6.24-rc3/usr/include/linux/kvm.h requires asm/kvm.h, 
which does not exist in exported headers
make[2]: *** [/root/kernels/linux-2.6.24-rc3/usr/include/linux/.check.kvm.h] 
Error 1
make[1]: *** [linux] Error 2
make: *** [headers_check] Error 2


-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.24-rc3-mm1 make headers_check fails

[Kamalesh Babulal]

Andrew Morton wrote:
 On Wed, 21 Nov 2007 13:54:50 +0530 Kamalesh Babulal [EMAIL PROTECTED] wrote:
 
 The make headers_check fails,

   CHECK   include/linux/usb/gadgetfs.h
   CHECK   include/linux/usb/ch9.h
   CHECK   include/linux/usb/cdc.h
   CHECK   include/linux/usb/audio.h
   CHECK   include/linux/kvm.h
 /root/kernels/linux-2.6.24-rc3/usr/include/linux/kvm.h requires asm/kvm.h, 
 which does not exist in exported headers
 
 hm, works for me, on i386 and x86_64.  What's different over there?
Hi Andrew,

It fails on the powerpc box, with allyesconfig option.

-- 
Thanks  Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/