-Original Post
Weathers, Norman R. wrote:
>To all whom it may concern:
>
>
>I am having trouble with several of the 2.6 kernels. The last one is
>the one that is perhaps most annoying.
>
>I have a dual Opteron based NFS server that keeps crashing when I try
to
>boot up with 2.6.11-rc4.
>
>The node is trying to boot from an mptbase device, and it is also
>loading modules for a qlogic fiber card (module is qla2300, qla2xxx,
and
>the scsi_transport_fc). Now, as it is scanning the drives, it does a
>perfect impersonation of a dying duck and crashes.
>
>Here is the output from the crash:'
>
>Fusion MPT base driver 3.01.18
>Loading scsi_modCopyright (c) 1999-2004 LSI Logic Corporation
>.ko module
>Loadmptbase: Initiating ioc0 bringup
>ing sd_mod.ko module
>Loading mptbase.ko module
>ioc0: 53C1030: Capabilities={Initiator}
>Unable to handle kernel paging request at 25b0 RIP:
>{vmalloc_fault+557}
>PGD 821ad067 PUD 2c50067 PMD 0
>Oops: [1] SMP
>CPU 0
>Modules linked in: mptbase sd_mod scsi_mod
>Pid: 0, comm: swapper Not tainted 2.6.11-rc4
>RIP: 0010:[] {vmalloc_fault+557}
>RSP: :80455230 EFLAGS: 00010212
>RAX: 000fe050 RBX: 0001 RCX: 0018
>RDX: RSI: 03fff000 RDI: 3fff
>RBP: R08: 8100fba3c000 R09: fba3c000
>R10: 0008 R11: 810081b44760 R12: 80455338
>R13: 0003 R14: c244 R15:
>FS: () GS:804c1800()
>knlGS:
>CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b
>CR2: 25b0 CR3: 02c58000 CR4: 06e0
>Process swapper (pid: 0, threadinfo 804c8000, task
>80358380)
>Stack: 801207ce 0001 0001
>80455278
> 80358380 80455338 80317933
>
> 000b000e 0082
>Call Trace: {do_page_fault+238}
>{autoremove
>_wake_function+9}
> {__wake_up_common+67}
>{error_exit+0}
> {:mptbase:mpt_interrupt+45}
>{update_wall_
>time+9}
> {handle_IRQ_event+44}
>{__do_IRQ+222}
> {do_IRQ+66}
{ret_from_intr+0}
>
> {thread_return+42}
>{default_idle+0
>}
> {default_idle+36}
>{cpu_idle+58}
> {start_kernel+416}
>{x86_64_start_kernel+4
>04}
>
>
>Code: 48 2b 82 b0 25 00 00 48 8d 34 c5 00 00 00 00 48 29 c6 48 8b
>RIP {vmalloc_fault+557} RSP
>CR2: 25b0
> <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
>
>Has anyone seen this in this kernel? 2.6.7 - 2.6.10 has not had a
>problem booting, but there has been other problems that are forcing us
>to move up to a newer kernel (2.6.7 has stability issues, 2.6.9 had
some
>interesting issues with our IBM servers and USB keyboards (complete
>lockups), and I had problems with kswapd on 2.6.7 - 2.6.10).
>
>Thanks for any help you may be able to shed on this problem. Please CC
>me. I was on the kernel list, but I think my company has blocked that
>email due to the volume of the traffic.
>
>Norman Weathers
>
>-
>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/
>
>
>
---End Original Post--
---Response from Original
Post---
Hi!
Did you change some configuration options or did add/remove hardware?
Matthias-Christian Ott
---End Response
>> My Response <
No, nothing has changed on the box outside of trying to get the OS up
and running stable.
I forgot to mention last time that the OS is Fedora Core2, and the
kernel was compiled on that box using the GCC on that box. I can get
the config and anything else that anyone may need to help solve this
problem. In the mean time, I am trying to download 2.6.11-rc3 to see if
it will boot correctly on this box. If it does, than there is some
change between rc3 and rc4 that may have caused the problem.
Norman Weathers
-
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/