Ticket #3 (closed defect: duplicate)

Opened 14 years ago

Last modified 14 years ago

HIGHMEM causes kernel to crash

Reported by: kazutomo Owned by: [email protected]
Priority: major Milestone:
Component: ZeptoOS Version:
Keywords: Cc:

Description

kernel panic msg below

maybe kmap_atomic() race condition

We don't use HIGHMEM since 2/2GB split was used but we might need HIGHMEM later to provide a bigger address space to user.


NET: Registered protocol family 17 Freeing unused kernel memory: 192k init init started: BusyBox v1.4.2 (2008-05-07 02:58:20 UTC) multi-call binary eth0: Link status [RX+,TX+] Starting RPC portmap daemon..done kmap_pte=c037f200 idx=3 type=3 cpuid=0 kernel BUG in kmap_atomic at include2/asm/highmem.h:94! Oops: Exception in kernel mode, sig: 5 #1 SMP NR_CPUS=4 NIP: C01B6764 LR: C01B6764 CTR: 00000000 REGS: c02bba80 TRAP: 0700 Not tainted (2.6.19.2) MSR: 00029000 <EE,ME> CR: 24028022 XER: 00000000 TASK = c0233a00[0] 'swapper' THREAD: c02ba000 CPU: 0 GPR00: C01B6764 C02BBB30 C0233A00 0000002A 00021000 FFFFFFFF C02F0000 00004000 GPR08: 00000000 C0230000 00000C10 C0235324 24028082 00000000 00000000 00000000 GPR16: 00000000 00000000 00000000 C02C0000 00000000 C02FF3C0 C01B68FC C02BBB78 GPR24: C1C783BC 00000078 C0C8BC68 00001000 C02BA000 00000003 00000000 C037F218 NIP [C01B6764] xdr_partial_copy_from_skb+0x398/0x3b8 LR [C01B6764] xdr_partial_copy_from_skb+0x398/0x3b8 Call Trace: [C02BBB30] [C01B6764] xdr_partial_copy_from_skb+0x398/0x3b8 (unreliable) [C02BBB70] [C01B7DC4] xs_tcp_data_recv+0x2dc/0x490 [C02BBBC0] [C016B5BC] tcp_read_sock+0x150/0x1bc [C02BBC00] [C01B8860] xs_tcp_data_ready+0x98/0xc8 [C02BBC30] [C017465C] tcp_rcv_established+0x770/0x9b8 [C02BBC70] [C017B280] tcp_v4_do_rcv+0xec/0x3fc [C02BBCC0] [C017DD64] tcp_v4_rcv+0x8e4/0xa98 [C02BBD10] [C015DF4C] ip_local_deliver+0x150/0x340 [C02BBD40] [C015DBC4] ip_rcv+0x32c/0x564 [C02BBD80] [C013FF00] netif_receive_skb+0x220/0x2d4 [C02BBDB0] [C0141FC8] process_backlog+0xac/0x188 [C02BBDF0] [C0142148] net_rx_action+0xa4/0x1dc [C02BBE30] [C0025CBC] do_softirq+0x9c/0x12c [C02BBE70] [C0006998] do_softirq+0x60/0x64 [C02BBE90] [C0025A90] irq_exit+0x54/0x64 [C02BBEA0] [C0006A28] do_IRQ+0x8c/0x104 [C02BBEC0] [C0002408] ret_from_except+0x0/0x18 [C02BBF80] [C000A334] cpu_idle+0xc4/0xd4 [C02BBFA0] [C00016AC] rest_init+0x2c/0x3c [C02BBFB0] [C02C07A4] start_kernel+0x290/0x2f8 [C02BBFF0] [C0000204] skpinv+0x1a8/0x1e4 Instruction dump: 38800000 4be97b59 2f830000 907a0000 419e0030 807a0000 4bfffe30 3c60c01e 7fa5eb78 38c00003 38632b1c 4be69bfd <0fe00000> 48000000 7fdbf050 4bffff28 Kernel panic - not syncing: Aiee, killing interrupt handler!

Attachments

tractmp.txt (2.2 KB) - added by kazutomo 14 years ago.
kernel panic message

Change History

Changed 14 years ago by kazutomo

kernel panic message

comment:1 Changed 14 years ago by kazutomo

  • Status changed from new to closed
  • Resolution set to duplicate
Note: See TracTickets for help on using tickets.