From: "Tomáš Vrána" <tom@voda.cz>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-mips@linux-mips.org
Subject: Re: Kernel crash in ip_nat on ADM5120
Date: Sat, 28 May 2005 13:42:11 +0200 [thread overview]
Message-ID: <42985913.2040606@voda.cz> (raw)
In-Reply-To: <42984BFC.3000800@voda.cz>
Please reply to tom@voda.cz, I posted from wrong profile first.
Sorry and thanks, Tom
VODA IT wrote:
> Hello,
>
> I get following problem using the 2.6.11 kernel on ADM5120 platform:
> Under heavy network load (ie. flood ping) the kernel crashes in NAT
> (no nat is done actually), removing IP filtering from kernel leaves
> everything perfectly stable.... I am attaching dumps, including
> parsed ksyms. Anyone able to help ?
>
> Thanks, Tom
>
> Kernel panic - not syncing: Caught Machine Check exception - caused by
>
> multiple matching entries in the TLB
>
> ksymoops 2.4.9 on i686 2.6.5-7.151-default. Options used
> -v ../linux-2.6.11-mipscvs-20050326/vmlinux (specified)
> -K (specified)
> -L (specified)
> -O (specified)
> -m ../linux-2.6.11-mipscvs-20050326/System.map (specified)
> -t mipsel -a mipsel
>
> Cpu 0
> $ 0 : 00000000 801f0000 c00042a8 000002a8
> $ 4 : 801cc6f0 8faf4800 00000080 00000001
> $ 8 : 0302a8c0 0102a8c0 8025baf0 8025baf8
> $12 : 00ff0000 00000278 0000003e 72756f73
> $16 : 00000055 80fd4cac 8025baf0 80fd4d28
> $20 : 00000001 00000001 00000000 80f36c00
> $24 : 00000008 00426bc0
> $28 : 8025a000 8025bac8 8025bc78 801a0d78
> Hi : 00000055
> Lo : 0140d97a
> epc : 801a0f18 ip_nat_setup_info+0x27c/0x59c Not tainted
> Status: 10208403 KERNEL EXL IE
> Cause : 00800060
> Kernel panic - not syncing: Caught Machine Check exception - caused by
> Warning (Oops_read): Code line not seen, dumping what data is available
>
>
>>> $12; 00ff0000 <__crc_nf_ct_attach+d834e/e919f>
>>> $15; 72756f73 <__crc_generic_make_request+1144ec/6a77e7>
>>> $17; 80fd4cac <__crc_tcf_exts_destroy+7086d4/72f879>
>>> $18; 8025baf0 <__crc_simple_transaction_release+1bada/c6e8a>
>>> $19; 80fd4d28 <__crc_tcf_exts_destroy+708750/72f879>
>>> $23; 80f36c00 <__crc_tcf_exts_destroy+66a628/72f879>
>>> $25; 00426bc0 <__crc_notify_change+2f24b/1fc50f>
>>> $28; 8025a000 <__crc_simple_transaction_release+19fea/c6e8a>
>>> $29; 8025bac8 <__crc_simple_transaction_release+1bab2/c6e8a>
>>> $30; 8025bc78 <__crc_simple_transaction_release+1bc62/c6e8a>
>>> $31; 801a0d78 <ip_nat_setup_info+dc/59c>
>>
>
>>> PC; 801a0f18 <ip_nat_setup_info+27c/59c> <=====
>>
>
> --------------------
> Got mcheck at 801a0f18
> Cpu 0
> $ 0 : 00000000 801f0000 c00042a8 000002a8
> $ 4 : 801cc6f0 8faf4800 00000080 00000001
> $ 8 : 0302a8c0 0102a8c0 8026fbc8 8026fbd0
> $12 : 00ff0000 00000000 00000000 00000000
> $16 : 00000055 80270cac 8026fbc8 80270d28
> $20 : 00000001 00000001 00000000 80f36c00
> $24 : 00000000 0044ffb4
> $28 : 8026e000 8026fba0 8026fd50 801a0d78
> Hi : 00000055
> Lo : 0140d97a
> epc : 801a0f18 ip_nat_setup_info+0x27c/0x59c Not tainted
> ra : 801a0d78 ip_nat_setup_info+0xdc/0x59c
> Status: 10208403 KERNEL EXL IE
> Cause : 00800060
> PrId : 0001800b
>
> Index: 2 pgmask=4kb va=7fff6000 asid=09
> [pa=00236000 c=3 d=0 v=0 g=0]
> [pa=00fdb000 c=3 d=1 v=1 g=0]
>
> Index: 12 pgmask=4kb va=10004000 asid=09
> [pa=0023d000 c=3 d=1 v=0 g=0]
> [pa=00fcc000 c=3 d=0 v=0 g=0]
>
> Index: 13 pgmask=4kb va=2ab96000 asid=09
> [pa=00d86000 c=3 d=0 v=1 g=0]
> [pa=00000000 c=0 d=0 v=0 g=0]
>
> Index: 14 pgmask=4kb va=00442000 asid=09
> [pa=00c6f000 c=3 d=0 v=0 g=0]
> [pa=00c70000 c=3 d=0 v=1 g=0]
>
> Index: 15 pgmask=4kb va=00450000 asid=09
> [pa=00c7d000 c=3 d=0 v=1 g=0]
> [pa=00000000 c=0 d=0 v=0 g=0]
>
> Kernel panic - not syncing: Caught Machine Check exception - caused by
> multiple matching entries in the TLB.
>
>
>>> $12; 00ff0000 <__crc_nf_ct_attach+d834e/e919f>
>>> $17; 80270cac <__crc_simple_transaction_release+30c96/c6e8a>
>>> $18; 8026fbc8 <__crc_simple_transaction_release+2fbb2/c6e8a>
>>> $19; 80270d28 <__crc_simple_transaction_release+30d12/c6e8a>
>>> $23; 80f36c00 <__crc_tcf_exts_destroy+66a628/72f879>
>>> $25; 0044ffb4 <__crc_notify_change+5863f/1fc50f>
>>> $28; 8026e000 <__crc_simple_transaction_release+2dfea/c6e8a>
>>> $29; 8026fba0 <__crc_simple_transaction_release+2fb8a/c6e8a>
>>> $30; 8026fd50 <__crc_simple_transaction_release+2fd3a/c6e8a>
>>> $31; 801a0d78 <ip_nat_setup_info+dc/59c>
>>
>
>>> PC; 801a0f18 <ip_nat_setup_info+27c/59c> <=====
>>
>
> Kernel panic - not syncing: Caught Machine Check exception - caused by
>
>
>
--
Tomas Vrana <tom@voda.cz>
--------------------------
VODA IT consulting, Borkovany 48, 691 75
http://www.voda.cz/
phone: +420 519 419 416 mobile: +420 603 469 305 UIN: 105142752
WARNING: multiple messages have this Message-ID (diff)
From: "Tomáš Vrána" <tom@voda.cz>
Cc: linux-mips@linux-mips.org
Subject: Re: Kernel crash in ip_nat on ADM5120
Date: Sat, 28 May 2005 13:42:11 +0200 [thread overview]
Message-ID: <42985913.2040606@voda.cz> (raw)
Message-ID: <20050528114211.JwcAS2j0uuytZZ4TCEIJ0f8n7KmB65MhT_LuAS8LOE4@z> (raw)
In-Reply-To: <42984BFC.3000800@voda.cz>
Please reply to tom@voda.cz, I posted from wrong profile first.
Sorry and thanks, Tom
VODA IT wrote:
> Hello,
>
> I get following problem using the 2.6.11 kernel on ADM5120 platform:
> Under heavy network load (ie. flood ping) the kernel crashes in NAT
> (no nat is done actually), removing IP filtering from kernel leaves
> everything perfectly stable.... I am attaching dumps, including
> parsed ksyms. Anyone able to help ?
>
> Thanks, Tom
>
> Kernel panic - not syncing: Caught Machine Check exception - caused by
>
> multiple matching entries in the TLB
>
> ksymoops 2.4.9 on i686 2.6.5-7.151-default. Options used
> -v ../linux-2.6.11-mipscvs-20050326/vmlinux (specified)
> -K (specified)
> -L (specified)
> -O (specified)
> -m ../linux-2.6.11-mipscvs-20050326/System.map (specified)
> -t mipsel -a mipsel
>
> Cpu 0
> $ 0 : 00000000 801f0000 c00042a8 000002a8
> $ 4 : 801cc6f0 8faf4800 00000080 00000001
> $ 8 : 0302a8c0 0102a8c0 8025baf0 8025baf8
> $12 : 00ff0000 00000278 0000003e 72756f73
> $16 : 00000055 80fd4cac 8025baf0 80fd4d28
> $20 : 00000001 00000001 00000000 80f36c00
> $24 : 00000008 00426bc0
> $28 : 8025a000 8025bac8 8025bc78 801a0d78
> Hi : 00000055
> Lo : 0140d97a
> epc : 801a0f18 ip_nat_setup_info+0x27c/0x59c Not tainted
> Status: 10208403 KERNEL EXL IE
> Cause : 00800060
> Kernel panic - not syncing: Caught Machine Check exception - caused by
> Warning (Oops_read): Code line not seen, dumping what data is available
>
>
>>> $12; 00ff0000 <__crc_nf_ct_attach+d834e/e919f>
>>> $15; 72756f73 <__crc_generic_make_request+1144ec/6a77e7>
>>> $17; 80fd4cac <__crc_tcf_exts_destroy+7086d4/72f879>
>>> $18; 8025baf0 <__crc_simple_transaction_release+1bada/c6e8a>
>>> $19; 80fd4d28 <__crc_tcf_exts_destroy+708750/72f879>
>>> $23; 80f36c00 <__crc_tcf_exts_destroy+66a628/72f879>
>>> $25; 00426bc0 <__crc_notify_change+2f24b/1fc50f>
>>> $28; 8025a000 <__crc_simple_transaction_release+19fea/c6e8a>
>>> $29; 8025bac8 <__crc_simple_transaction_release+1bab2/c6e8a>
>>> $30; 8025bc78 <__crc_simple_transaction_release+1bc62/c6e8a>
>>> $31; 801a0d78 <ip_nat_setup_info+dc/59c>
>>
>
>>> PC; 801a0f18 <ip_nat_setup_info+27c/59c> <=====
>>
>
> --------------------
> Got mcheck at 801a0f18
> Cpu 0
> $ 0 : 00000000 801f0000 c00042a8 000002a8
> $ 4 : 801cc6f0 8faf4800 00000080 00000001
> $ 8 : 0302a8c0 0102a8c0 8026fbc8 8026fbd0
> $12 : 00ff0000 00000000 00000000 00000000
> $16 : 00000055 80270cac 8026fbc8 80270d28
> $20 : 00000001 00000001 00000000 80f36c00
> $24 : 00000000 0044ffb4
> $28 : 8026e000 8026fba0 8026fd50 801a0d78
> Hi : 00000055
> Lo : 0140d97a
> epc : 801a0f18 ip_nat_setup_info+0x27c/0x59c Not tainted
> ra : 801a0d78 ip_nat_setup_info+0xdc/0x59c
> Status: 10208403 KERNEL EXL IE
> Cause : 00800060
> PrId : 0001800b
>
> Index: 2 pgmask=4kb va=7fff6000 asid=09
> [pa=00236000 c=3 d=0 v=0 g=0]
> [pa=00fdb000 c=3 d=1 v=1 g=0]
>
> Index: 12 pgmask=4kb va=10004000 asid=09
> [pa=0023d000 c=3 d=1 v=0 g=0]
> [pa=00fcc000 c=3 d=0 v=0 g=0]
>
> Index: 13 pgmask=4kb va=2ab96000 asid=09
> [pa=00d86000 c=3 d=0 v=1 g=0]
> [pa=00000000 c=0 d=0 v=0 g=0]
>
> Index: 14 pgmask=4kb va=00442000 asid=09
> [pa=00c6f000 c=3 d=0 v=0 g=0]
> [pa=00c70000 c=3 d=0 v=1 g=0]
>
> Index: 15 pgmask=4kb va=00450000 asid=09
> [pa=00c7d000 c=3 d=0 v=1 g=0]
> [pa=00000000 c=0 d=0 v=0 g=0]
>
> Kernel panic - not syncing: Caught Machine Check exception - caused by
> multiple matching entries in the TLB.
>
>
>>> $12; 00ff0000 <__crc_nf_ct_attach+d834e/e919f>
>>> $17; 80270cac <__crc_simple_transaction_release+30c96/c6e8a>
>>> $18; 8026fbc8 <__crc_simple_transaction_release+2fbb2/c6e8a>
>>> $19; 80270d28 <__crc_simple_transaction_release+30d12/c6e8a>
>>> $23; 80f36c00 <__crc_tcf_exts_destroy+66a628/72f879>
>>> $25; 0044ffb4 <__crc_notify_change+5863f/1fc50f>
>>> $28; 8026e000 <__crc_simple_transaction_release+2dfea/c6e8a>
>>> $29; 8026fba0 <__crc_simple_transaction_release+2fb8a/c6e8a>
>>> $30; 8026fd50 <__crc_simple_transaction_release+2fd3a/c6e8a>
>>> $31; 801a0d78 <ip_nat_setup_info+dc/59c>
>>
>
>>> PC; 801a0f18 <ip_nat_setup_info+27c/59c> <=====
>>
>
> Kernel panic - not syncing: Caught Machine Check exception - caused by
>
>
>
--
Tomas Vrana <tom@voda.cz>
--------------------------
VODA IT consulting, Borkovany 48, 691 75
http://www.voda.cz/
phone: +420 519 419 416 mobile: +420 603 469 305 UIN: 105142752
next prev parent reply other threads:[~2005-05-28 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 10:46 Kernel crash in ip_nat on ADM5120 VODA IT
2005-05-28 11:42 ` Tomáš Vrána [this message]
2005-05-28 11:42 ` Tomáš Vrána
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=42985913.2040606@voda.cz \
--to=tom@voda.cz \
--cc=linux-mips@linux-mips.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