Your message dated Sat, 24 Apr 2021 10:19:23 -0700 (PDT)
with message-id <[email protected]>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #717678,
regarding BUG: soft lockup - CPU#0 stuck for 23s when running rsync
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
717678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717678
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rsync
Version: 3.0.9-4
Severity: normal
Dear Maintainer,
when using rsync to make a backup, the complete machine (qnap ts-119pii nas
box) becomes
unresponsive. The SSS session dies, I can no longer login to the box. The only
thing left
is to power down the box by long pressing the power button.
Sometimes rsync run for a few minutes before hanging the nas, today (I just
retried it with
the current kernel), it hang after 2 seconds. But that has been varying the
whole time.
The serial console repeatedly shows:
[ 584.399202] BUG: soft lockup - CPU#0 stuck for 23s! [rsync:3603]
[ 584.405233] Modules linked in: sg usb_storage nfsd nfs nfs_acl auth_rpcgss
fscache lockd sunrpc ipv6 ext2 loop hmac xhci_hcd ehci_hcd evdev sha1_generic
usbcore mv_cesa usb_common aes_generic mv643xx_eth inet_lro libphy gpio_keys
ext3 mbcache jbd sd_mod crc_t10dif sata_mv libata scsi_mod
[ 584.431087]
[ 584.432580] Pid: 3603, comm: rsync
[ 584.437298] CPU: 0 Not tainted (3.2.0-4-kirkwood #1 Debian
3.2.41-2.1qnap)
[ 584.444547] PC is at send_to_group.isra.2+0x24/0x154
[ 584.449533] LR is at fsnotify+0x15c/0x1e8
[ 584.453553] pc : [<c00f193c>] lr : [<c00f1bc8>] psr: a0000013
[ 584.453556] sp : cb50dec8 ip : 60000093 fp : 00000001
[ 584.465088] r10: df8b7720 r9 : df8ccbc8 r8 : cb50df34
[ 584.470328] r7 : 00000002 r6 : 00000000 r5 : df8b7720 r4 : 00000002
[ 584.476878] r3 : 00000002 r2 : 00000000 r1 : cb5a8720 r0 : df8b7720
[ 584.483426] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
[ 584.490586] Control: 0005397f Table: 0b510000 DAC: 00000015
[ 584.496357] [<c001369c>] (unwind_backtrace+0x0/0xe0) from [<c00645ac>]
(watchdog_timer_fn+0xe0/0x134)
[ 584.505615] [<c00645ac>] (watchdog_timer_fn+0xe0/0x134) from [<c004365c>]
(__run_hrtimer+0x118/0x1ec)
[ 584.514875] [<c004365c>] (__run_hrtimer+0x118/0x1ec) from [<c0043e80>]
(hrtimer_interrupt+0xe8/0x230)
[ 584.524138] [<c0043e80>] (hrtimer_interrupt+0xe8/0x230) from [<c001a1dc>]
(orion_timer_interrupt+0x20/0x30)
[ 584.533921] [<c001a1dc>] (orion_timer_interrupt+0x20/0x30) from [<c0064e9c>]
(handle_irq_event_percpu+0x7c/0x23c)
[ 584.544226] [<c0064e9c>] (handle_irq_event_percpu+0x7c/0x23c) from
[<c0065084>] (handle_irq_event+0x28/0x38)
[ 584.554098] [<c0065084>] (handle_irq_event+0x28/0x38) from [<c0067240>]
(handle_level_irq+0xac/0xc0)
[ 584.563271] [<c0067240>] (handle_level_irq+0xac/0xc0) from [<c006486c>]
(generic_handle_irq+0x28/0x44)
[ 584.572621] [<c006486c>] (generic_handle_irq+0x28/0x44) from [<c000ed94>]
(handle_IRQ+0x60/0x84)
[ 584.581443] [<c000ed94>] (handle_IRQ+0x60/0x84) from [<c000dab4>]
(__irq_svc+0x34/0x78)
[ 584.589483] [<c000dab4>] (__irq_svc+0x34/0x78) from [<c00f193c>]
(send_to_group.isra.2+0x24/0x154)
[ 584.598482] [<c00f193c>] (send_to_group.isra.2+0x24/0x154) from [<c00f1bc8>]
(fsnotify+0x15c/0x1e8)
[ 584.607568] [<c00f1bc8>] (fsnotify+0x15c/0x1e8) from [<c00c0fa0>]
(vfs_write+0x118/0x178)
[ 584.615782] [<c00c0fa0>] (vfs_write+0x118/0x178) from [<c00c1218>]
(sys_write+0x3c/0x68)
[ 584.623910] [<c00c1218>] (sys_write+0x3c/0x68) from [<c000dea0>]
(ret_fast_syscall+0x0/0x2c)
The command issued was
rsync -av --delete /home/multimedia/bilder /mnt/hdd/backups/daily.0/
I could use rsync with the exact same options on QNAP OS, so this does not seem
to be a HW problem.
I even found another user with the exact same problem (he has the same NAS box).
-- System Information:
Debian Release: 7.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armel (armv5tel)
Kernel: Linux 3.2.0-4-kirkwood
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages rsync depends on:
ii base-files 7.1wheezy1
ii libacl1 2.2.51-8
ii libc6 2.13-38
ii libgcc1 1:4.7.2-5
ii libpopt0 1.16-7
ii lsb-base 4.1+Debian8+deb7u1
rsync recommends no packages.
Versions of packages rsync suggests:
ii openssh-client 1:6.0p1-4
ii openssh-server 1:6.0p1-4
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a very old kernel or the bug is old itself
without resolution.
If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from backports
please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Regards,
Salvatore
--- End Message ---
