* [bug] Hi, need your help about raid1 causing kernel panic!
@ 2023-01-03 1:28 Liam Zeng
2023-01-06 1:01 ` John Stoffel
0 siblings, 1 reply; 2+ messages in thread
From: Liam Zeng @ 2023-01-03 1:28 UTC (permalink / raw)
To: linux-raid
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
Hope you kindly forgive my troubles. I have worked with a bug for
several days, and I really need your help, even a kind encouragement.
here's some informations
kernel version: 5.10.107
cpu arch: arm64
the system install on /dev/md9, which make up of raid1 of two disks;
the bug: every time I transfer files (50G file, using samba or ftp),
the system will break down.
I have not modified any code of md.
And the attachment is the log.
I would appreciate any reply!
[-- Attachment #2: kernel_panic_log --]
[-- Type: application/octet-stream, Size: 5130 bytes --]
# df -h
Filesystem Size Used Available Use% Mounted on
devtmpfs 472.4M 0 472.4M 0% /dev
/dev/md9 7.4G 1.6G 5.4G 23% /
tmpfs 488.8M 80.9M 407.9M 17% /tmp
tmpfs 488.8M 96.0K 488.7M 0% /run
tmpfs 488.8M 4.4M 484.4M 1% /opt/var
/dev/vg0/lv0 100.0G 51.6G 47.4G 52% /Volume2
/dev/vg0/lv0 100.0G 51.6G 47.4G 52% /home
# [ 1589.409216] Unable to handle kernel paging request at virtual address ffffffc0135e3c38
[ 1589.411188] Mem abort info:
[ 1589.411883] ESR = 0x96000007
[ 1589.412643] EC = 0x25: DABT (current EL), IL = 32 bits
[ 1589.413960] SET = 0, FnV = 0
[ 1589.414719] EA = 0, S1PTW = 0
[ 1589.415499] Data abort info:
[ 1589.416214] ISV = 0, ISS = 0x00000007
[ 1589.417166] CM = 0, WnR = 0
[ 1589.417905] swapper pgtable: 4k pages, 39-bit VAs, pgdp=0000000001f20000
[ 1589.419565] [ffffffc0135e3c38] pgd=000000003dfff003, p4d=000000003dfff003, pud=000000003dfff003, pmd=0000000002d4d003, pte=0000000000000000
[ 1589.422677] Internal error: Oops: 96000007 [#1] PREEMPT SMP
[ 1589.424060] Modules linked in: wimax sctp_diag sctp l2tp_ip6 l2tp_eth l2tp_ip l2tp_ppp l2tp_netlink l2tp_core rpcrdma rpcsec_gss_krb5 br_netfilter ebt_nflog ebt_log ebt_snat ebt_redirectN
[ 1589.424239] ipt_CLUSTERIP ipt_rpfilter ipt_ah iptable_raw iptable_nat iptable_mangle iptable_filter ip_tables nf_flow_table_ipv4 nft_dup_ipv4 nft_fib_ipv4 nft_reject_ipv4 nf_nat_snmp_baY
[ 1589.445813] xt_MASQUERADE xt_REDIRECT xt_RATEEST xt_NFQUEUE xt_NFLOG xt_NETMAP xt_LOG xt_HMARK xt_HL xt_FLOWOFFLOAD xt_DSCP xt_CT xt_CLASSIFY xt_CHECKSUM xt_nat xt_set ip_set xt_connmara
[ 1589.467638] nfnetlink_cthelper nfnetlink_cttimeout nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nfnetlink_osf nfnetlink_log nfnetlink_queue nfnetlink_acct nfnetlink si
[ 1589.489110] scsi_transport_fc raid_class eeprom_93cx6 nbd test_alloc_ion_protected test_protecteds__notifier asn1_decoder ts_fsm ts_bm ts_kmp crc64 crc_ccitt libcurve25519 libcurve25519s
[ 1589.531577] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.10.107 #201
[ 1589.533131] Hardware name: Realtek Bleeding Edge EVB (1GB spi) Pure Nas (DT)
[ 1589.534880] pstate: 80400085 (Nzcv daIf +PAN -UAO -TCO BTYPE=--)
[ 1589.536376] pc : __wake_up_common+0x60/0x178
[ 1589.537436] lr : __wake_up_common_lock+0x88/0xd0
[ 1589.538582] sp : ffffffc010fd3b00
[ 1589.539404] x29: ffffffc010fd3b00 x28: 0000000000004e00
[ 1589.540724] x27: 0000000000000000 x26: ffffff800c0a3800
[ 1589.542045] x25: 0000000000000001 x24: ffffffc010fd3bb0
[ 1589.543366] x23: 0000000000000000 x22: 0000000000000000
[ 1589.544685] x21: 0000000000000003 x20: ffffff800c0a38e0
[ 1589.546005] x19: ffffff800c0a38d8 x18: 0000000000000000
[ 1589.547325] x17: 0000000000000000 x16: 0000000000000000
[ 1589.548645] x15: 0000007f92cef7f8 x14: 0000000000000000
[ 1589.549965] x13: 0000000000000000 x12: 0000000000000000
[ 1589.551285] x11: 0000000000000040 x10: ffffffc010ea1d30
[ 1589.552604] x9 : ffffffc010096eb0 x8 : ffffff8000400268
[ 1589.553925] x7 : ffffffc0135e3c20 x6 : 0000000000000000
[ 1589.555245] x5 : ffffffc010fd3bb0 x4 : 0000000000000000
[ 1589.556565] x3 : 0000000000000000 x2 : 0000000000000001
[ 1589.557885] x1 : 0000000000000003 x0 : ffffffc0135e3c38
[ 1589.559205] Call trace:
[ 1589.559816] __wake_up_common+0x60/0x178
[ 1589.560791] __wake_up_common_lock+0x88/0xd0
[ 1589.561852] __wake_up+0x1c/0x28
[ 1589.562656] mempool_free+0x98/0xb0
[ 1589.563525] raid_end_bio_io+0xe4/0x160
[ 1589.564479] r1_bio_write_done+0x70/0x80
[ 1589.565453] raid1_end_write_request+0x1a4/0x3e8
[ 1589.566601] bio_endio+0x134/0x1d8
[ 1589.567448] blk_update_request+0x258/0x538
[ 1589.568490] scsi_end_request+0x38/0x208
[ 1589.569464] scsi_io_completion+0x70/0x568
[ 1589.570482] scsi_finish_command+0xe8/0xf8
[ 1589.571499] scsi_softirq_done+0x84/0x108
[ 1589.572497] blk_done_softirq+0xc0/0xf0
[ 1589.573452] __do_softirq+0x154/0x40c
[ 1589.574363] irq_exit+0xc0/0xd0
[ 1589.575147] __handle_domain_irq+0x6c/0xc0
[ 1589.576163] gic_handle_irq+0x90/0x154
[ 1589.577094] el1_irq+0xcc/0x180
[ 1589.577878] arch_cpu_idle+0x14/0x20
[ 1589.578768] default_idle_call+0x60/0x1c0
[ 1589.579766] do_idle+0x210/0x280
[ 1589.580569] cpu_startup_entry+0x2c/0x58
[ 1589.581544] secondary_start_kernel+0x138/0x148
[ 1589.582672] Code: aa0503f8 f9002bfb aa0403f7 5280001b (f9400cf3)
[ 1589.584186] ---[ end trace 69da70e34abbc676 ]---
[ 1589.585333] Kernel panic - not syncing: Oops: Fatal exception in interrupt
[ 1589.587041] SMP: stopping secondary CPUs
[ 1590.627082] SMP: failed to stop secondary CPUs 0-3
[ 1590.628271] iso_wa: force gpu sram on
[ 1590.629185] Kernel Offset: disabled
[ 1590.630052] CPU features: 0x0000006,2a00a218
[ 1590.631110] Memory Limit: none
[ 1590.631871] Rebooting in 1 seconds..
[ 1591.632797] SMP: stopping secondary CPUs
[ 1592.674512] SMP: failed to stop secondary CPUs 0-3
NOTICE: smc: std_svc_smc_handler-psci
NOTICE: Send PSCI_SYSTEM_RESET
SYS_RESET
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [bug] Hi, need your help about raid1 causing kernel panic!
2023-01-03 1:28 [bug] Hi, need your help about raid1 causing kernel panic! Liam Zeng
@ 2023-01-06 1:01 ` John Stoffel
0 siblings, 0 replies; 2+ messages in thread
From: John Stoffel @ 2023-01-06 1:01 UTC (permalink / raw)
To: Liam Zeng; +Cc: linux-raid
>>>>> "Liam" == Liam Zeng <zqwliam@gmail.com> writes:
> Hope you kindly forgive my troubles. I have worked with a bug for
> several days, and I really need your help, even a kind
> encouragement.
You need to provide more details. What is your disk setup, what is
your OS base, etc.
> here's some informations
> kernel version: 5.10.107
Is this is a vendor kernel or your own self-compiled one? And if so,
can you move to the latest 6.x kernel instead?
> cpu arch: arm64
> the system install on /dev/md9, which make up of raid1 of two disks;
More details on this setup. Type of disks, their connectivity to the
system, etc.
> the bug: every time I transfer files (50G file, using samba or ftp),
> the system will break down.
Does it break if you copy the file on the system? Do you have enough
disk space to copy a 10g file from one directory to another on the
same RAID1 setup?
Which filesystem are you using?
> I have not modified any code of md.
Good to know.
> And the attachment is the log.
Sorry, I'm not going to bother decoding it. Just attach it as plain
text instead please.
> I would appreciate any reply!
> [DELETED ATTACHMENT kernel_panic_log, Untyped binary data]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-01-06 1:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-01-03 1:28 [bug] Hi, need your help about raid1 causing kernel panic! Liam Zeng
2023-01-06 1:01 ` John Stoffel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox