I don't have a *real* answer for you but I believe that message you're seeing is actually not a kernel oops. There is a configuration option available in the newer kernels that allows the kernel to print a backtrace for any processes stuck in a UNINTERRUPTIBLE state for a defined period (default is set at 120 seconds). So, that is what it looks like is happening on your machine.
Again, not really an answer to your question, but hopefully help point you in a better direction for troubleshooting. Your new question is, why is "vgs" stuck in a UNINTERRUPTIBLE state? -- Jon Miller On Fri, Oct 12, 2012 at 10:33 AM, Michael MacIsaac <[email protected]>wrote: > Hello list, > > This is odd - I'm having a RHEL 6.2 system die on shutdown while trying to > shut down the loopback interface: > > Shutting down system logger: Ý OK ¨ > Shutting down interface eth0: Ý OK ¨ > Shutting down loopback interface: Ý OK ¨ > INFO: task vgs:2171 blocked for more than 120 seconds. > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > vgs D 00000000004cd070 0 2171 2170 0x00000200 > 000000007ca74dc8 00000000004d6a00 0000000000132c0a 000000007b6f7850 > 000000007b6f7820 000000000080ee80 00000000008a7e00 000000007ca75228 > 0000000000000001 000000007ca75228 00000000024ed400 000000000080ee80 > 00000000008a7e00 000000007ca75228 0000000000810f68 000000000336de00 > 00000000004d6d18 00000000004cc5b8 000000007b6f7850 000000007b6f7a08 > Call Trace: > (Ý<00000000004cc5b8>¨ schedule+0x5a4/0xfe0) > Ý<00000000004cd070>¨ io_schedule+0x7c/0xd4 > Ý<00000000002939b8>¨ __blockdev_direct_IO_newtrunc+0x7a0/0xdfc > Ý<000000000029408c>¨ __blockdev_direct_IO+0x78/0xf0 > Ý<00000000002916ea>¨ blkdev_direct_IO+0x72/0x80 > Ý<00000000001f34f0>¨ generic_file_aio_read+0x75c/0x7b0 > Ý<0000000000254fc8>¨ do_sync_read+0xf0/0x154 > Ý<0000000000255fa0>¨ vfs_read+0xa0/0x1a0 > Ý<00000000002561a2>¨ SyS_read+0x5a/0xac > Ý<000000000011863c>¨ sysc_tracego+0xe/0x14 > Ý<0000004b5b19c6fc>¨ 0x4b5b19c6fc > > Has anyone seen this? > > Just a bit more info - I did add an eth1 using a 2nd NIC to another > VSWITCH with no OSA (for a "private interconnect"). Not sure if that's > pertinent, but I believe it started after I added that. Also, this is a > clone - the golden image does not die like this. After reIPLing, here's > the output of ifconfig and uname -a: > > [root@lnxsa2 ~]# ifconfig > eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:61 > inet addr:9.12.7.4 Bcast:9.12.15.255 Mask:255.255.240.0 > inet6 addr: fe80::ff:fe00:61/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:164 errors:0 dropped:0 overruns:0 frame:0 > TX packets:73 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:14119 (13.7 KiB) TX bytes:10514 (10.2 KiB) > > eth1 Link encap:Ethernet HWaddr 02:00:00:00:00:62 > inet addr:10.1.1.4 Bcast:10.1.1.255 Mask:255.255.255.0 > inet6 addr: fe80::ff:fe00:62/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:27 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:3993 (3.8 KiB) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > [root@lnxsa2 ~]# uname -a > Linux lnxsa2.itso.ibm.com 2.6.32-220.el6.s390x #1 SMP Wed Nov 9 08:20:08 > EST 2011 s390x s390x s390x GNU/Linux > (Hmm, now I halt a second time and it shuts down normally - strange.) > > It has the undesired effect of the virtual machine not logging off on halt > :(( > > Any help will be appreciated > > "Mike MacIsaac" <mikemac at-sign us.ibm.com> > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
