From: "Paweł Sikora" <pawel.sikora@agmk.net>
To: Michael Wang <wangyun@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
torvalds@linux-foundation.org, arekm@pld-linux.org,
baggins@pld-linux.org
Subject: Re: [3.6.6] panic on reboot / khungtaskd blocked? (WARNING: at arch/x86/kernel/smp.c:123 native_smp_send_reschedule)
Date: Mon, 12 Nov 2012 13:33:39 +0100 [thread overview]
Message-ID: <3023364.Bjpo0brdul@pawels> (raw)
In-Reply-To: <1539324.MIArxLN8tE@pawels>
On Monday 12 of November 2012 11:22:47 Paweł Sikora wrote:
> On Monday 12 of November 2012 15:40:31 Michael Wang wrote:
> > On 11/12/2012 03:16 PM, Paweł Sikora wrote:
> > > On Monday 12 of November 2012 11:04:12 Michael Wang wrote:
> > >> On 11/09/2012 09:48 PM, Paweł Sikora wrote:
> > >>> Hi,
> > >>>
> > >>> during playing with new ups i've caught an nice oops on reboot:
> > >>>
> > >>> http://imgbin.org/index.php?page=image&id=10253
> > >>>
> > >>> probably the upstream is also affected.
> > >>
> > >> Hi, Paweł
> > >>
> > >> Are you using a clean 3.6.6 without any modify?
> > >
> > > yes, pure 3.6.6 form git tree with modular config.
> > >
> > >> Looks like some threads has set itself to be UNINTERRUPTIBLE with out
> > >> any design on switch itself back later(or the time is too long), are you
> > >> accidentally using some bad designed module?
> > >
> > > hmm, hard to say. mostly all modules are loaded automatically by kernel.
> >
> > Could you please provide the whole dmesg in text? your picture lost the
> > print info of the hung task.
>
> i've grabbed the console via rs232 but there's no more info (see attached txt).
hmm, i have one observation.
during rc.shutdown there're messages on console like this: Cannot stat file /proc/$pid/fd/1: Connection timed out
afaics this file descriptor points to vnc log file on a remote machine, e.g.:
# ps aux|grep xfwm4
eda 1748 0.0 0.0 320220 11224 ? S 13:08 0:00 xfwm4
# readlink -m /proc/1748/fd/1
/remote/dragon/ahome/eda/.vnc/odra:11.log
# mount|grep ahome
dragon:/home/users/ on /remote/dragon/ahome type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.0.2.121,mountvers=3,mountport=45251,mountproto=udp,local_lock=none,addr=10.0.2.121)
so, probably during `killall5 -TERM/-KILL` on shutdown stage something sometimes go wrong
and these processes (xfce4/vncserver) survive the signal and hang on the nfs i/o.
BR,
Paweł.
next prev parent reply other threads:[~2012-11-12 12:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 13:48 [3.6.6] panic on reboot / khungtaskd blocked? (WARNING: at arch/x86/kernel/smp.c:123 native_smp_send_reschedule) Paweł Sikora
2012-11-12 3:04 ` Michael Wang
2012-11-12 7:16 ` Paweł Sikora
2012-11-12 7:40 ` Michael Wang
2012-11-12 10:22 ` Paweł Sikora
2012-11-12 12:33 ` Paweł Sikora [this message]
2012-11-13 2:51 ` Michael Wang
2012-11-13 9:40 ` Paweł Sikora
2012-11-14 2:32 ` Michael Wang
2012-11-14 2:49 ` Robert Hancock
2012-11-14 3:08 ` Michael Wang
2012-11-14 21:10 ` Paweł Sikora
2012-11-15 1:41 ` Michael Wang
2012-11-15 9:40 ` Jan Kara
2012-11-16 2:50 ` Michael Wang
2012-11-16 3:11 ` Jan Kara
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=3023364.Bjpo0brdul@pawels \
--to=pawel.sikora@agmk.net \
--cc=arekm@pld-linux.org \
--cc=baggins@pld-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wangyun@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).