Re: bug report: Sun Blade 100 kernel panics during boot under 3.0.3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Aug 24, 2011 at 03:50:53PM -0400, Jim Faulkner wrote:
> On Mon, Aug 22, 2011 at 05:36:02PM -0700, David Miller wrote:
> 
> > Unfortunately we need the very first crash message that happens, but
> > even your first snapshot is after other crashes have occurred.
> > 
> > You'll need to build a kernel with CONFIG_BOOT_PRINTK_DELAYED enabled
> > and then you can boot with boot_delay=xxx (where "xxx" is something
> > like 100, it's in milliseconds) to slow down the message printing so
> > that you can capture the first message cleanly.
> 
> OK, I've attached several images of the kernel panic w/ boot_delay to
> the bug:
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=41522

>From image 3 it looks like you hit some issues with the ALI7101.

>From your config I can see you have:
CONFIG_I2C_ALI1535=m
CONFIG_I2C_ALI1563=m

They both mention ALI7101 in their help text.

Just to give a hint if this is the casue could you try to disable one
or both of these to see if this has any effect.

	Sam
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite Help]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux