From: Steve Wise <swise@opengridcomputing.com>
To: Dave Jones <davej@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Oops mystery
Date: Fri, 12 Jul 2013 14:24:14 -0500 [thread overview]
Message-ID: <51E057DE.5050909@opengridcomputing.com> (raw)
In-Reply-To: <20130712171422.GC1537@redhat.com>
On 7/12/2013 12:14 PM, Dave Jones wrote:
> On Fri, Jul 12, 2013 at 12:08:25PM -0500, Steve Wise wrote:
>
> > There is no 'Code:' line in the log. I thought about that that too, but
> > I don't see it dumping the code. The kernel is a SLES11sp1 kernel,
> > 1.6.32.54-0.3-default.
>
> "Ask suse" is probably your best bet in that case.
>
> > [ 1054.392502] Modules linked in: smb2(N) smb(N) smb_manager(N)
> > nas_netlink(N) af_packet nfsd nfs_common(N) lockd auth_rpcgss nas_acl(N)
> > nas_proto_vfs(N) sunrpc snas_ts(N) ipmi_devintf snas_cafs(PN) snas_ca(N)
> > ipmi_si ipmi_msghandler snas_mds(PN) snas_ds(N) nm(PN) snas_nvcache(PN)
> > snas_dlm(PN) snas_trns(PN) snas_cm_sdd(PN) snas_cm_pma(PN)
> > disk_online_diagnostic(N) snas_monc(N) snas_fc(N) snas_mml(PN) cstl(PN)
> > ptlrpc(N) ko2iblnd(N) ksocklnd(N) obdclass(N) lnet(N) lvfs(PN) libcfs(N)
> > snas_base(PN) nofs(N) usos(N) zlib_deflate cpufreq_conservative
> > cpufreq_userspace cpufreq_powersave acpi_cpufreq t3k_mpt2sas_vdl(N)
> > raidrepair(N) ib_ipoib ib_umad iw_nes crc32c libcrc32c iw_cxgb3 cxgb3
> > ib_qib(N) dca mlx4_ib mlx4_en mlx4_core ib_mthca nvdimm_mapping(N)
> > smbuspci(N) microcode t4_tom(N) toecore(N) rdma_ucm ib_uverbs rdma_cm
> > ib_cm iw_cm ib_sa ib_mad ib_addr ipv6 iw_cxgb4(N) ib_core
> > soft_watchdog(PN) kbox(PN) fuse loop dm_mod tpm_tis tpm iTCO_wdt
> > rtc_cmos tpm_bios i2c_i801 cxgb4(N) pcspkr iTCO_vendor_support i2c_core
> > rtc_core ses sg rtc_lib bnx2 enclosure wmi button container usbhid hid
> > ehci_hcd usbcore sd_mod crc_t10dif edd ext3 mbcache jbd fan processor
> > mpt2sas scsi_transport_sas raid_class scsi_mod thermal thermal_sys hwmon
>
> Or maybe one of the proprietary module vendors. Who knows.
>
>
I was hoping someone could verify that my analysis is correct, or if
I've come to the wrong conclusion due to some mistake in my analysis.
Steve.
prev parent reply other threads:[~2013-07-12 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 15:48 Oops mystery Steve Wise
2013-07-12 16:48 ` Dave Jones
2013-07-12 16:53 ` Steve Wise
2013-07-12 17:00 ` Dave Jones
2013-07-12 17:08 ` Steve Wise
2013-07-12 17:14 ` Dave Jones
2013-07-12 19:24 ` Steve Wise [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51E057DE.5050909@opengridcomputing.com \
--to=swise@opengridcomputing.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox