Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #57867 > unrolled thread
| Started by | Rajesh N <mail2rajeshnatarajan@gmail.com> |
|---|---|
| First post | 2017-06-01 07:50 +0200 |
| Last post | 2017-06-08 07:10 +0200 |
| Articles | 4 — 2 participants |
Back to article view | Back to linux.debian.kernel
[LINUX-KERNEL] Kernel hung for more than 120 seconds due to tee process Rajesh N <mail2rajeshnatarajan@gmail.com> - 2017-06-01 07:50 +0200
Re: [LINUX-KERNEL] Kernel hung for more than 120 seconds due to tee process Ben Hutchings <ben@decadent.org.uk> - 2017-06-03 23:30 +0200
Re: [LINUX-KERNEL] Kernel hung for more than 120 seconds due to tee process Ben Hutchings <ben@decadent.org.uk> - 2017-06-03 23:30 +0200
Re: [LINUX-KERNEL] Kernel hung for more than 120 seconds due to tee process Rajesh N <mail2rajeshnatarajan@gmail.com> - 2017-06-08 07:10 +0200
| From | Rajesh N <mail2rajeshnatarajan@gmail.com> |
|---|---|
| Date | 2017-06-01 07:50 +0200 |
| Subject | [LINUX-KERNEL] Kernel hung for more than 120 seconds due to tee process |
| Message-ID | <tNr9E-6Ua-25@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hi,
In debian wheezy system while writing logs to SSD using tee command , we
are experiencing kernel hung problem.
Can anyone help in avoiding this problem ?
I haven't subscribed to kernel mailing list,so re-ponders please CC me in
the reply.
*Kernel trace : *
kernel: [ 960.964830] INFO: task tee:11324 blocked for more than 120
seconds.
kernel: [ 960.966422] Tainted: G O 3.16.0-4-586 #1
kernel: [ 960.967996] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
kernel: [ 960.969607] tee D ffff8803e29a5788 0 11324
1 0x00000000
kernel: [ 960.969614] ffffffff818184a0 0000000000000086 0000000000012ec0
ffff8803e29a5330
kernel: [ 960.969628] 0000000000012ec0 ffff8803e2cdbfd8 0000000000012ec0
ffff8803e29a5330
kernel: [ 960.969632] ffff88040aef2800 ffff88040b317828 fffffffe00000002
ffff8803e29a5330
kernel: [ 960.969640] Call Trace:
kernel: [ 960.969654] [<ffffffff8158259a>] ? schedule_timeout+0x20a/0x270
kernel: [ 960.969659] [<ffffffff811c28ce>] ? pipe_read+0x23e/0x2f0
kernel: [ 960.969665] [<ffffffff81585f09>] ? ldsem_down_read+0x119/0x210
kernel: [ 960.969671] [<ffffffff813cc02c>] ? tty_ldisc_ref_wait+0x1c/0x40
kernel: [ 960.969674] [<ffffffff813c3ccc>] ? tty_write+0x7c/0x2b0
kernel: [ 960.969678] [<ffffffff81286d9f>] ?
security_file_permission+0x2f/0xd0
kernel: [ 960.969681] [<ffffffff813c3f3a>] ?
redirected_tty_write+0x3a/0xd0
kernel: [ 960.969685] [<ffffffff811ba6af>] ? vfs_write+0xbf/0x200
kernel: [ 960.969688] [<ffffffff811bac00>] ? SyS_write+0x50/0xb0
kernel: [ 960.969693] [<ffffffff81586b0d>] ?
system_call_fastpath+0x1a/0x1f
*SystemInfo*
$> uname -a
Linux ACPU2 3.16.0-4-586 #1 SMP Tue Oct 13 13:56:57 CDT 2015 x86_64
GNU/Linux
$> free -m
total used free shared buffers cached
Mem: 15866 7233 8633 0 73 3103
-/+ buffers/cache: 4056 11809
Swap: 32772 0 32772
$> lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 58
Stepping: 9
CPU MHz: 1203.644
BogoMIPS: 4200.03
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 6144K
NUMA node0 CPU(s): 0-7
Thanks,
Rajesh Natarajan.
[toc] | [next] | [standalone]
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Date | 2017-06-03 23:30 +0200 |
| Subject | Re: [LINUX-KERNEL] Kernel hung for more than 120 seconds due to tee process |
| Message-ID | <tOoMq-3LP-15@gated-at.bofh.it> |
| In reply to | #57867 |
[Multipart message — attachments visible in raw view] — view raw
Please use 'reportbug' to open a bug report. This will automatically gather some other useful diagnostic information. Ben. -- Ben Hutchings Experience is directly proportional to the value of equipment destroyed. - Carolyn Scheppner
[toc] | [prev] | [next] | [standalone]
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Date | 2017-06-03 23:30 +0200 |
| Subject | Re: [LINUX-KERNEL] Kernel hung for more than 120 seconds due to tee process |
| Message-ID | <tOoMq-3LP-21@gated-at.bofh.it> |
| In reply to | #57892 |
[Multipart message — attachments visible in raw view] — view raw
On Sat, 2017-06-03 at 22:24 +0100, Ben Hutchings wrote: > Please use 'reportbug' to open a bug report. This will automatically > gather some other useful diagnostic information. More specifically, 'reportbug kernel' should do the right thing. Ben. -- Ben Hutchings Experience is directly proportional to the value of equipment destroyed. - Carolyn Scheppner
[toc] | [prev] | [next] | [standalone]
| From | Rajesh N <mail2rajeshnatarajan@gmail.com> |
|---|---|
| Date | 2017-06-08 07:10 +0200 |
| Message-ID | <tPXRL-8na-3@gated-at.bofh.it> |
| In reply to | #57893 |
[Multipart message — attachments visible in raw view] — view raw
Thanks for the response, but when we dont have physical access to the system as it is running in the field. we do have only kernel logs from the field. any help using the mentioned trace will be helpful. Thanks in advance -Rajesh On Sun, Jun 4, 2017 at 2:55 AM, Ben Hutchings <ben@decadent.org.uk> wrote: > On Sat, 2017-06-03 at 22:24 +0100, Ben Hutchings wrote: > > Please use 'reportbug' to open a bug report. This will automatically > > gather some other useful diagnostic information. > > More specifically, 'reportbug kernel' should do the right thing. > > Ben. > > -- > Ben Hutchings > Experience is directly proportional to the value of equipment > destroyed. > - Carolyn Scheppner > >
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web