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

2007-12-04 Thread Ingo Molnar 

* 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
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

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

2007-12-04 Thread 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.
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

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

2007-12-04 Thread Ingo Molnar 

* Kamalesh Babulal [EMAIL PROTECTED] wrote:

 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.

do you know whether there's any true delay when this happens, or is it a 
pure softlockup-detector false positive?

Ingo
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

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

2007-12-03 Thread Andrew Morton 
On Fri, 30 Nov 2007 12:58:06 +0530
Kamalesh Babulal [EMAIL PROTECTED] wrote:

 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_BIT0
   #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.
 

There are effectively no drivers/scsi/ changes after 2.6.24-rc3 and we
don't (I believe) have a clue what caused this regression.

Can you please do a bisection search on this?

Thanks.
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

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

2007-11-29 Thread Andrew Morton 
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

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

2007-11-29 Thread 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-git2 softlockup detected

2007-11-29 Thread Kyle McMartin 
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
 
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

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

2007-11-29 Thread Andrew Morton 
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?
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

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

2007-11-29 Thread 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.
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

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

2007-11-28 Thread 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.
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

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

2007-11-28 Thread Andrew Morton 
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

- Enable CONFIG_DEBUG_INFO

- gdb sym53c8xx.o

(gdb) p sym_hcb_attach
prints 0xsomething
(gdb) p/x 0xsomething + 0x1194
prints 0xsomethingelse
(gdb) l *0xsomethingelse

___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev