Bug 5041 - Encountered this kernel Panic on system boot up
Summary: Encountered this kernel Panic on system boot up
Status: CLOSED CODE_FIX
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: SCSI (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: Stephanie Glass
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-10 03:52 UTC by Sharyathi
Modified: 2005-10-11 04:58 UTC (History)
4 users (show)

See Also:
Kernel Version: 2.6.13-rc5-mm1
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
Serial Console output while boot up (22.97 KB, text/plain)
2005-08-10 03:55 UTC, Sharyathi
Details
Configuration file used to build the kernel (27.40 KB, text/plain)
2005-08-10 04:01 UTC, Sharyathi
Details
Kernel Panic with CONFIG_PREEMPT disabled (24.09 KB, text/plain)
2005-08-11 07:48 UTC, Sharyathi
Details

Description Sharyathi 2005-08-10 03:52:35 UTC
Distribution:
SLES 9 SP1
----------------------------------
Hardware Environment:
2 way, Intel(R) XEON(TM) CPU 2.00GHz, 4 GB RAM
Network driver Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet
SCSi Driver:
SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual
Ultra320 )
----------------------------------
Software Environment:
Linux Kernel: 2.6.13-rc5 + 2.6.13-rc5-mm1 
----------------------------------
Problem Description:

On building kernel 2.6.13-rc5-mm1 with the existing config file[worked with
earlier kernels]. Encountered this Kernel Panic with the message " Unable to
handle kernel paging request at virtual address 00000010.

I will attachi the Serial Console and Config file please have a look
Comment 1 Sharyathi 2005-08-10 03:55:18 UTC
Created attachment 5578 [details]
Serial Console output while boot up

Grub Entry
----------------------
###Don't change this comment - YaST2 identifier: Original name: linux###
title Linux-2.6.13-rc5-mm1
    kernel (hd0,0)/tmp/bzImage-2.6.13-rc5-mm1  root=/dev/sda5 vga=0x31a
selinux=
0 splash=silent acpi=oldboot resume=/dev/sda2 elevator=cfq showopts
crashkernel=
64M@16M nmi_watchdog=2 console=tty0 console=ttyS0,38400n1
Comment 2 Sharyathi 2005-08-10 04:01:10 UTC
Created attachment 5579 [details]
Configuration file used to build the kernel
Comment 3 Andrew Morton 2005-08-10 09:48:33 UTC
Hm, that's bad.

It might be caused by the scsi changes in -mm.  I assume that
2.6.12-rc6 does not exhibit this bug?

I'm about to disappear for 3-4 days - please remind me to
look at this if it seems that I've forgotten ;)

If you can do a bisection search through the patches in -mm that
would help.  I'd amek the first pivot point be around git-scsi-misc.patch.
Comment 4 Greg Kroah-Hartman 2005-08-10 13:41:13 UTC
If you disable preempt, does that help?

And this doesn't occur on 2.6.13-rc6, right?
Comment 5 Sharyathi 2005-08-11 07:47:17 UTC
   I looked for 2.6.13-rc6 and this panic doesn't occur for this.
But for 2.6.13-rc5-mm1 I tried to build with CONFIG_PREEMPT disabled still it
gets into panic.
  I will attach the Console output with preempt disabled 
Comment 6 Sharyathi 2005-08-11 07:48:28 UTC
Created attachment 5601 [details]
Kernel Panic with CONFIG_PREEMPT disabled
Comment 7 Badari Pulavarty 2005-10-10 10:12:02 UTC
Is this still an issue with latest -mm tree ?
Otherwise, can we close it ?
Comment 8 Sharyathi 2005-10-10 22:43:56 UTC
Its not observed in the latest kernel 2.6.14-rc2-mm1 and  2.6.14-rc2-mm2 kernels
Comment 9 Stephanie Glass 2005-10-11 04:58:00 UTC
Closing bug since you no longer can reproduce.

Note You need to log in before you can comment on or make changes to this bug.