From: Christian Boehme <Christian.Boehme@gwdg.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel BUG at objrmap:325 in 2.6.5-7.151-smp (SuSE, x86_64)
Date: Wed, 13 Jul 2005 11:52:18 +0200 [thread overview]
Message-ID: <42D4E452.9090407@gwdg.de> (raw)
In-Reply-To: <4pLzx-1KX-23@gated-at.bofh.it>
Arjan van de Ven schrieb:
> you really should call SuSE support for this... after all that's what
> you're paying them for ;)
We use SLES because it is a requiremnet for getting support for some
vendor-supplied MPI-libraries... but you are of course still right. I
file a bug report to them as well.
>>kernel: Kernel BUG at objrmap:325
>>kernel: invalid operand: 0000 [1] SMP
>>kernel: CPU 0
>>kernel: Pid: 4752, comm: mhd3d.opteron Tainted: G U (2.6.5-7.151-smp SLES9_SP1_BRANCH-200503181131210000)
>
>
> which modules do you use ?
Here's the list:
joydev 19584 0
sg 51000 0
st 51236 0
sr_mod 26788 0
thermal 22668 0
processor 28352 1 thermal
fan 12808 0
button 15648 0
battery 17928 0
ac 13832 0
ipv6 317304 21
tg3 88324 0
ohci_hcd 29700 0
evdev 18944 0
usbcore 131824 3 ohci_hcd
ib_sdp 136000 0
ib_useraccess_cm 28320 0
ib_cm 59000 2 ib_sdp,ib_useraccess_cm
ib_udapl 49852 0
ib_ip2pr 38200 3 ib_sdp,ib_useraccess_cm,ib_udapl
ib_ipoib 75160 2 ib_udapl,ib_ip2pr
ib_useraccess 21540 0
ib_sa_client 41232 3 ib_udapl,ib_ip2pr,ib_ipoib
ib_client_query 27040 4 ib_udapl,ib_ip2pr,ib_ipoib,ib_sa_client
ib_tavor 40964 7 ib_useraccess_cm
mod_vapi 169824 3 ib_useraccess_cm,ib_udapl,ib_tavor
mod_vipkl 262520 1 mod_vapi
mod_thh 258272 1 mod_vapi
mod_hh 31888 2 mod_vipkl,mod_thh
mod_mpga 35200 1 mod_vapi
mod_vapi_common 103296 6 ib_useraccess_cm,ib_udapl,ib_tavor,mod_vapi,mod_vipkl,mod_thh
mosal 155340 5 mod_vapi,mod_vipkl,mod_thh,mod_mpga,mod_vapi_common
ib_mad 34200 4 ib_cm,ib_useraccess,ib_client_query,ib_tavor
ib_core 286744 10 ib_sdp,ib_useraccess_cm,ib_cm,ib_udapl,ib_ip2pr,ib_ipoib,ib_useraccess,ib_sa_client,ib_tavor,ib_mad
ib_poll 34768 4 ib_sdp,ib_cm,ib_ip2pr,ib_client_query
ib_services 28484 13 ib_sdp,ib_useraccess_cm,ib_cm,ib_udapl,ib_ip2pr,ib_ipoib,ib_useraccess,ib_sa_client,ib_client_query,ib_tavor,ib_mad,ib_core,ib_poll
mst_pciconf 95488 0
mst_pci 93312 2
w83627hf 39172 0
lm85 34052 0
i2c_sensor 11520 2 w83627hf,lm85
i2c_isa 11008 0
i2c_amd756 15620 0
i2c_core 35716 5 w83627hf,lm85,i2c_sensor,i2c_isa,i2c_amd756
dm_mod 67776 0
ext3 133104 3
jbd 83144 1 ext3
sata_sil 17284 4
libata 51200 1 sata_sil,[permanent]
sd_mod 29568 5
scsi_mod 140800 5 sg,st,sr_mod,libata,sd_mod
The ib_* modules are for the Infiniband network connections. Thanks for
your help!
Best wishes
Christian Boehme
--
Dr. Christian Boehme
GWDG Private:
Am Fassberg Wilhelm-Raabe-Str. 15
37077 Göttingen 37083 Göttingen
email: Christian.Boehme@gwdg.de ChristianBoehme@web.de
phone: +49 (0)551 201-1839 +49 (0)551 3077000
fax: +49 (0)551 201-2150 +49 (0)551 3077077
next parent reply other threads:[~2005-07-13 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4pLpN-1F0-15@gated-at.bofh.it>
[not found] ` <4pLzx-1KX-23@gated-at.bofh.it>
2005-07-13 9:52 ` Christian Boehme [this message]
2005-07-13 9:07 Kernel BUG at objrmap:325 in 2.6.5-7.151-smp (SuSE, x86_64) Christian Boehme
2005-07-13 9:16 ` Arjan van de Ven
2005-07-13 9:59 ` Jan Engelhardt
2005-07-13 10:03 ` Jan Engelhardt
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=42D4E452.9090407@gwdg.de \
--to=christian.boehme@gwdg.de \
--cc=arjan@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.