2.6.13-rc5-mm1 doesnt boot on x86_64

2.6.13-rc5-mm1 doesnt boot on x86_64

[Ashok Raj]

Folks,

Iam getting this on the recent 2.6.12-rc5-mm1 kernel built with defconfig. 

Cheers,
Ashok Raj

----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at "include/linux/list.h":165
invalid operand: 0000 [1] SMP
CPU 2
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.13-rc5-mm1
RIP: 0010:[<ffffffff802b9ef4>] <ffffffff802b9ef4>{attribute_container_unregist}RSP: 0018:ffff8100bfb63f00  EFLAGS: 00010283
RAX: ffff8100bfbd4c58 RBX: ffff8100bfbd4c00 RCX: ffffffff804e6600
RDX: 0000000000200200 RSI: 0000000000000000 RDI: ffffffff804e6600
RBP: 0000000000000000 R08: ffff8100bfbd4c48 R09: 0000000000000020
R10: 0000000000000000 R11: ffffffff8019baa0 R12: ffffffff80100190
R13: 00000000ffffffff R14: 0000ffffffff8010 R15: ffffffff80627fb0
FS:  0000000000000000(0000) GS:ffffffff80616980(0000) knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 0000000000101000 CR4: 00000000000006e0
Process swapper (pid: 1, threadinfo ffff8100bfb62000, task ffff8100bfb614d0)
Stack: ffffffff8032643d 0000000000000000 ffffffff8064499f ffffffff80100190
       ffffffff80651288 0000000000000000 ffffffff8010b249 0000000000000246
       0000000000020800 ffffffff804ae180
Call Trace:<ffffffff8032643d>{spi_release_transport+13} <ffffffff8064499f>{ahd}       <ffffffff8010b249>{init+505} <ffffffff8010e896>{child_rip+8}
       <ffffffff8010b050>{init+0} <ffffffff8010e88e>{child_rip+0}


Code: 0f 0b a3 e1 d9 44 80 ff ff ff ff c2 a5 00 49 8b 00 4c 39 40
RIP <ffffffff802b9ef4>{attribute_container_unregister+52} RSP <ffff8100bfb63f0> <0>Kernel panic - not syncing: Attempted to kill init!

Re: 2.6.13-rc5-mm1 doesnt boot on x86_64

[Andi Kleen]

On Mon, Aug 08, 2005 at 09:48:19AM -0700, Ashok Raj wrote:
> Folks,
> 
> Iam getting this on the recent 2.6.12-rc5-mm1 kernel built with defconfig. 
> 
> Cheers,
> Ashok Raj
> 
> ----------- [cut here ] --------- [please bite here ] ---------
> Kernel BUG at "include/linux/list.h":165
> invalid operand: 0000 [1] SMP
> CPU 2
> Modules linked in:
> Pid: 1, comm: swapper Not tainted 2.6.13-rc5-mm1
> RIP: 0010:[<ffffffff802b9ef4>] <ffffffff802b9ef4>{attribute_container_unregist}RSP: 0018:ffff8100bfb63f00  EFLAGS: 00010283
> RAX: ffff8100bfbd4c58 RBX: ffff8100bfbd4c00 RCX: ffffffff804e6600
> RDX: 0000000000200200 RSI: 0000000000000000 RDI: ffffffff804e6600
> RBP: 0000000000000000 R08: ffff8100bfbd4c48 R09: 0000000000000020
> R10: 0000000000000000 R11: ffffffff8019baa0 R12: ffffffff80100190
> R13: 00000000ffffffff R14: 0000ffffffff8010 R15: ffffffff80627fb0
> FS:  0000000000000000(0000) GS:ffffffff80616980(0000) knlGS:0000000000000000
> CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> CR2: 0000000000000000 CR3: 0000000000101000 CR4: 00000000000006e0
> Process swapper (pid: 1, threadinfo ffff8100bfb62000, task ffff8100bfb614d0)
> Stack: ffffffff8032643d 0000000000000000 ffffffff8064499f ffffffff80100190
>        ffffffff80651288 0000000000000000 ffffffff8010b249 0000000000000246
>        0000000000020800 ffffffff804ae180
> Call Trace:<ffffffff8032643d>{spi_release_transport+13} <ffffffff8064499f>{ahd}       <ffffffff8010b249>{init+505} <ffffffff8010e896>{child_rip+8}
>        <ffffffff8010b050>{init+0} <ffffffff8010e88e>{child_rip+0}

Looks like a SCSI problem. The machine has an Adaptec SCSI adapter, right?

-AndI
> 
> 
> Code: 0f 0b a3 e1 d9 44 80 ff ff ff ff c2 a5 00 49 8b 00 4c 39 40
> RIP <ffffffff802b9ef4>{attribute_container_unregister+52} RSP <ffff8100bfb63f0> <0>Kernel panic - not syncing: Attempted to kill init!
> 

Re: 2.6.13-rc5-mm1 doesnt boot on x86_64

[Ashok Raj]

On Mon, Aug 08, 2005 at 07:11:26PM +0200, Andi Kleen wrote:
> On Mon, Aug 08, 2005 at 09:48:19AM -0700, Ashok Raj wrote:
> > Folks,
> > 
> > Iam getting this on the recent 2.6.12-rc5-mm1 kernel built with defconfig. 
> > 
> > Cheers,
> > Ashok Raj
> > 
> > ----------- [cut here ] --------- [please bite here ] ---------
> > Kernel BUG at "include/linux/list.h":165
> > invalid operand: 0000 [1] SMP
> > CPU 2
> > Modules linked in:
> > Pid: 1, comm: swapper Not tainted 2.6.13-rc5-mm1
> > RIP: 0010:[<ffffffff802b9ef4>] <ffffffff802b9ef4>{attribute_container_unregist}RSP: 0018:ffff8100bfb63f00  EFLAGS: 00010283
> > RAX: ffff8100bfbd4c58 RBX: ffff8100bfbd4c00 RCX: ffffffff804e6600
> > RDX: 0000000000200200 RSI: 0000000000000000 RDI: ffffffff804e6600
> > RBP: 0000000000000000 R08: ffff8100bfbd4c48 R09: 0000000000000020
> > R10: 0000000000000000 R11: ffffffff8019baa0 R12: ffffffff80100190
> > R13: 00000000ffffffff R14: 0000ffffffff8010 R15: ffffffff80627fb0
> > FS:  0000000000000000(0000) GS:ffffffff80616980(0000) knlGS:0000000000000000
> > CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> > CR2: 0000000000000000 CR3: 0000000000101000 CR4: 00000000000006e0
> > Process swapper (pid: 1, threadinfo ffff8100bfb62000, task ffff8100bfb614d0)
> > Stack: ffffffff8032643d 0000000000000000 ffffffff8064499f ffffffff80100190
> >        ffffffff80651288 0000000000000000 ffffffff8010b249 0000000000000246
> >        0000000000020800 ffffffff804ae180
> > Call Trace:<ffffffff8032643d>{spi_release_transport+13} <ffffffff8064499f>{ahd}       <ffffffff8010b249>{init+505} <ffffffff8010e896>{child_rip+8}
> >        <ffffffff8010b050>{init+0} <ffffffff8010e88e>{child_rip+0}
> 
> Looks like a SCSI problem. The machine has an Adaptec SCSI adapter, right?

Yep, its adaptec problem

Actually i dont need AIX7XXX, since my system requires only CONFIG_FUSION.
I turned that option off, and it seems to boot fine now.

Ashok


> 
> -AndI
> > 
> > 
> > Code: 0f 0b a3 e1 d9 44 80 ff ff ff ff c2 a5 00 49 8b 00 4c 39 40
> > RIP <ffffffff802b9ef4>{attribute_container_unregister+52} RSP <ffff8100bfb63f0> <0>Kernel panic - not syncing: Attempted to kill init!
> > 

-- 
Cheers,
Ashok Raj
- Open Source Technology Center

Re: 2.6.13-rc5-mm1 doesnt boot on x86_64

[James Bottomley]

On Mon, 2005-08-08 at 19:11 +0200, Andi Kleen wrote:
> Looks like a SCSI problem. The machine has an Adaptec SCSI adapter, right?

The traceback looks pretty meaningless.

What was happening on the machine before this.  i.e. was it booting up,
in which case can we have the prior dmesg file; or was the aic79xxx
driver being removed?

James

Re: 2.6.13-rc5-mm1 doesnt boot on x86_64

[Ashok Raj]

On Mon, Aug 08, 2005 at 12:33:29PM -0500, James Bottomley wrote:
> On Mon, 2005-08-08 at 19:11 +0200, Andi Kleen wrote:
> > Looks like a SCSI problem. The machine has an Adaptec SCSI adapter, right?
> 
> The traceback looks pretty meaningless.
> 
> What was happening on the machine before this.  i.e. was it booting up,
> in which case can we have the prior dmesg file; or was the aic79xxx
> driver being removed?

I can get the trace again, but basically the system was booting. 

AIC_7XXX was defined in defconfig, but my system doesnt have it. Seems like
the senario was the driver tried to probe, found nothing, and tries
to de-reg resulting in the BUG().

I will try to get the recompile and entire dmesg log in the meantime.
> 
> James
> 
> 

-- 
Cheers,
Ashok Raj
- Open Source Technology Center

Re: 2.6.13-rc5-mm1 doesnt boot on x86_64

[Andrew Morton]

James Bottomley <James.Bottomley@SteelEye.com> wrote:
>
> On Mon, 2005-08-08 at 19:11 +0200, Andi Kleen wrote:
> > Looks like a SCSI problem. The machine has an Adaptec SCSI adapter, right?
> 
> The traceback looks pretty meaningless.
> 
> What was happening on the machine before this.  i.e. was it booting up,
> in which case can we have the prior dmesg file; or was the aic79xxx
> driver being removed?
> 

-mm has extra list_head debugging goodies.  I'd be suspecting a list_head
corruption detected somewhere under spi_release_transport().


--- 25/include/linux/list.h~list_del-debug	2005-03-08 11:40:27.000000000 -0800
+++ 25-akpm/include/linux/list.h	2005-03-08 11:40:49.000000000 -0800
@@ -5,7 +5,9 @@
 
 #include <linux/stddef.h>
 #include <linux/prefetch.h>
+#include <linux/kernel.h>
 #include <asm/system.h>
+#include <asm/bug.h>
 
 /*
  * These are non-NULL pointers that will result in page faults
@@ -160,6 +162,8 @@ static inline void __list_del(struct lis
  */
 static inline void list_del(struct list_head *entry)
 {
+	BUG_ON(entry->prev->next != entry);
+	BUG_ON(entry->next->prev != entry);
 	__list_del(entry->prev, entry->next);
 	entry->next = LIST_POISON1;
 	entry->prev = LIST_POISON2;
_

Re: 2.6.13-rc5-mm1 doesnt boot on x86_64

[James Bottomley]

On Mon, 2005-08-08 at 10:42 -0700, Andrew Morton wrote:
> -mm has extra list_head debugging goodies.  I'd be suspecting a list_head
> corruption detected somewhere under spi_release_transport().

Aha, looking in wrong driver ... the problem actually appears to be a
double release of the transport template in aic79xx.  Try this patch

James

diff --git a/drivers/scsi/aic7xxx/aic79xx_osm.c b/drivers/scsi/aic7xxx/aic79xx_osm.c
--- a/drivers/scsi/aic7xxx/aic79xx_osm.c
+++ b/drivers/scsi/aic7xxx/aic79xx_osm.c
@@ -2326,8 +2326,6 @@ done:
 	return (retval);
 }
 
-static void ahd_linux_exit(void);
-
 static void ahd_linux_set_width(struct scsi_target *starget, int width)
 {
 	struct Scsi_Host *shost = dev_to_shost(starget->dev.parent);
@@ -2772,7 +2770,7 @@ ahd_linux_init(void)
 	if (ahd_linux_detect(&aic79xx_driver_template) > 0)
 		return 0;
 	spi_release_transport(ahd_linux_transport_template);
-	ahd_linux_exit();
+
 	return -ENODEV;
 }
 
diff --git a/drivers/scsi/aic7xxx/aic7xxx_osm.c b/drivers/scsi/aic7xxx/aic7xxx_osm.c
--- a/drivers/scsi/aic7xxx/aic7xxx_osm.c
+++ b/drivers/scsi/aic7xxx/aic7xxx_osm.c
@@ -2331,8 +2331,6 @@ ahc_platform_dump_card_state(struct ahc_
 {
 }
 
-static void ahc_linux_exit(void);
-
 static void ahc_linux_set_width(struct scsi_target *starget, int width)
 {
 	struct Scsi_Host *shost = dev_to_shost(starget->dev.parent);

Re: 2.6.13-rc5-mm1 doesnt boot on x86_64

[Ashok Raj]

On Mon, Aug 08, 2005 at 07:06:50PM -0500, James Bottomley wrote:
> On Mon, 2005-08-08 at 10:42 -0700, Andrew Morton wrote:
> > -mm has extra list_head debugging goodies.  I'd be suspecting a list_head
> > corruption detected somewhere under spi_release_transport().
> 
> Aha, looking in wrong driver ... the problem actually appears to be a
> double release of the transport template in aic79xx.  Try this patch

Hi James

Sorry for the delay...

This patch works like a charm!.....

Cheers,
ashok
> 
> James
> 
> diff --git a/drivers/scsi/aic7xxx/aic79xx_osm.c b/drivers/scsi/aic7xxx/aic79xx_osm.c
> --- a/drivers/scsi/aic7xxx/aic79xx_osm.c
> +++ b/drivers/scsi/aic7xxx/aic79xx_osm.c
> @@ -2326,8 +2326,6 @@ done:
>  	return (retval);
>  }
>  
> -static void ahd_linux_exit(void);
> -
>  static void ahd_linux_set_width(struct scsi_target *starget, int width)
>  {
>  	struct Scsi_Host *shost = dev_to_shost(starget->dev.parent);
> @@ -2772,7 +2770,7 @@ ahd_linux_init(void)
>  	if (ahd_linux_detect(&aic79xx_driver_template) > 0)
>  		return 0;
>  	spi_release_transport(ahd_linux_transport_template);
> -	ahd_linux_exit();
> +
>  	return -ENODEV;
>  }
>  
> diff --git a/drivers/scsi/aic7xxx/aic7xxx_osm.c b/drivers/scsi/aic7xxx/aic7xxx_osm.c
> --- a/drivers/scsi/aic7xxx/aic7xxx_osm.c
> +++ b/drivers/scsi/aic7xxx/aic7xxx_osm.c
> @@ -2331,8 +2331,6 @@ ahc_platform_dump_card_state(struct ahc_
>  {
>  }
>  
> -static void ahc_linux_exit(void);
> -
>  static void ahc_linux_set_width(struct scsi_target *starget, int width)
>  {
>  	struct Scsi_Host *shost = dev_to_shost(starget->dev.parent);
> 
> 

-- 
Cheers,
Ashok Raj
- Open Source Technology Center