I'm getting a lot of this at boottime:
udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11707)
udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11709)
udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11711)
udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan
It takes a few minutes to boot.
The machine is a Dell PRECISION T5600 with a PERC H310 RAID controller.
Gé Weijers wrote:
I'm getting a lot of this at boottime:
udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11707)
udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11709)
udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11711)
udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan
It takes a few minutes to boot.
The machine is a Dell PRECISION T5600 with a PERC H310 RAID controller.
Hmmm, a) what's *in* this workstation? b) was this a fresh install?
mark
Thanks for answering.
a) The workstation has: - CPU E5-2687W - 32 GB RAM (ECC) - AMD FirePro V7900, original graphics card. (This happens with both the AMD driver installed and not installed.) - MegaRAID SAS 2008 controller configured for RAID1
I had a quad PCIe serial card in it as well, but I have removed it. No change.
b) It's was not a fresh install, but it's been doing this only recently. It started out with CentOS 6.3 or so in november 2012.
I saw some kernel oopses as well, I'm wondering whether the RAID controller is going bad.
Gé
May 16 20:01:25 localhost kernel: ------------[ cut here ]------------ May 16 20:01:25 localhost kernel: WARNING: at kernel/rcutree.c:332 rcu_irq_enter+0x55/0x70() (Tainted: P W --------------- ) May 16 20:01:25 localhost kernel: Hardware name: Precision T5600 May 16 20:01:25 localhost kernel: Modules linked in: fuse ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat xt_CHECKSUM iptable_mangle bridge tpm_infineon nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs autofs4 8021q garp stp llc cpufreq_ondemand acpi_cpufreq freq_table mperf ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables nf_conntrack_ftp nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_REJECT ip6t_ipv6header nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables ipv6 vhost_net macvtap macvlan tun kvm_intel kvm uinput iTCO_wdt iTCO_vendor_support microcode dcdbas fglrx(P)(U) sg ftdi_sio usbserial i2c_i801 i2c_core lpc_ich mfd_core snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd soundcore snd_page_alloc shpchp e1000e ptp pps_core ext4 jbd2 mbcache sr_mod cdrom sd_mod crc_t10dif xhci_hcd ahci megaraid_sas dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan] May 16 20:01:25 localhost kernel: Pid: 0, comm: swapper Tainted: P W --------------- 2.6.32-431.11.2.el6.x86_64 #1 May 16 20:01:25 localhost kernel: Call Trace: May 16 20:01:25 localhost kernel: <IRQ> [<ffffffff81071e27>] ? warn_slowpath_common+0x87/0xc0 May 16 20:01:25 localhost kernel: [<ffffffff81068ff5>] ? enqueue_entity+0x125/0x450 May 16 20:01:25 localhost kernel: [<ffffffff81071e7a>] ? warn_slowpath_null+0x1a/0x20 May 16 20:01:25 localhost kernel: [<ffffffff810ebbb5>] ? rcu_irq_enter+0x55/0x70 May 16 20:01:25 localhost kernel: [<ffffffff8107a7bb>] ? irq_enter+0x1b/0x80 May 16 20:01:25 localhost kernel: [<ffffffff815315d3>] ? do_IRQ+0x43/0xf0 May 16 20:01:25 localhost kernel: [<ffffffff8100b9d3>] ? ret_from_intr+0x0/0x11 May 16 20:01:25 localhost kernel: [<ffffffff811704cf>] ? kmem_cache_free+0xbf/0x2b0 May 16 20:01:25 localhost kernel: [<ffffffff813892b0>] ? scsi_sg_free+0x0/0x60 May 16 20:01:25 localhost kernel: [<ffffffff811220b7>] ? mempool_free_slab+0x17/0x20 May 16 20:01:25 localhost kernel: [<ffffffff81122205>] ? mempool_free+0x95/0xa0 May 16 20:01:25 localhost kernel: [<ffffffff813892fc>] ? scsi_sg_free+0x4c/0x60 May 16 20:01:25 localhost kernel: [<ffffffff81291880>] ? __sg_free_table+0x60/0x80 May 16 20:01:25 localhost kernel: [<ffffffff81389474>] ? __scsi_release_buffers+0x104/0x110 May 16 20:01:25 localhost kernel: [<ffffffff81389f36>] ? scsi_io_completion+0x2a6/0x6c0 May 16 20:01:25 localhost kernel: [<ffffffff813801c2>] ? scsi_finish_command+0xc2/0x130 May 16 20:01:25 localhost kernel: [<ffffffff8138a4b5>] ? scsi_softirq_done+0x145/0x170 May 16 20:01:25 localhost kernel: [<ffffffff8126ea95>] ? blk_done_softirq+0x85/0xa0 May 16 20:01:25 localhost kernel: [<ffffffff8107a8e1>] ? __do_softirq+0xc1/0x1e0 May 16 20:01:25 localhost kernel: [<ffffffff8100c30c>] ? call_softirq+0x1c/0x30 May 16 20:01:25 localhost kernel: [<ffffffff8100c30c>] ? call_softirq+0x1c/0x30 May 16 20:01:25 localhost kernel: <EOI> [<ffffffff8100fa75>] ? do_softirq+0x65/0xa0 May 16 20:01:25 localhost kernel: [<ffffffff8107a795>] ? irq_exit+0x85/0x90 May 16 20:01:25 localhost kernel: [<ffffffff81531605>] ? do_IRQ+0x75/0xf0 May 16 20:01:25 localhost kernel: [<ffffffff8100b9d3>] ? ret_from_intr+0x0/0x11 May 16 20:01:25 localhost kernel: [<ffffffff812e0bee>] ? intel_idle+0xde/0x170 May 16 20:01:25 localhost kernel: [<ffffffff812e0bd1>] ? intel_idle+0xc1/0x170 May 16 20:01:25 localhost kernel: [<ffffffff81426b67>] ? cpuidle_idle_call+0xa7/0x140 May 16 20:01:25 localhost kernel: [<ffffffff81009fc6>] ? cpu_idle+0xb6/0x110 May 16 20:01:25 localhost kernel: [<ffffffff8150d22a>] ? rest_init+0x7a/0x80 May 16 20:01:25 localhost kernel: [<ffffffff81c26f8f>] ? start_kernel+0x424/0x430 May 16 20:01:25 localhost kernel: [<ffffffff81c2633a>] ? x86_64_start_reservations+0x125/0x129 May 16 20:01:25 localhost kernel: [<ffffffff81c26453>] ? x86_64_start_kernel+0x115/0x124 May 16 20:01:25 localhost kernel: ---[ end trace a0e1ee14d68f0684 ]---
On Mon, May 19, 2014 at 1:02 PM, m.roth@5-cent.us wrote:
Gé Weijers wrote:
I'm getting a lot of this at boottime:
udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11707)
udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11709)
udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11711)
udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan
It takes a few minutes to boot.
The machine is a Dell PRECISION T5600 with a PERC H310 RAID controller.
Hmmm, a) what's *in* this workstation? b) was this a fresh install?
mark
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
BTW: I just saw those 'oopses', or I would have mentioned them right away. I'm seriously suspecting the RAID controller.
Gé
On Mon, May 19, 2014 at 2:31 PM, Gé Weijers ge@weijers.org wrote:
Thanks for answering.
a) The workstation has:
- CPU E5-2687W
- 32 GB RAM (ECC)
- AMD FirePro V7900, original graphics card. (This happens with both the
AMD driver installed and not installed.)
- MegaRAID SAS 2008 controller configured for RAID1
I had a quad PCIe serial card in it as well, but I have removed it. No change.
b) It's was not a fresh install, but it's been doing this only recently. It started out with CentOS 6.3 or so in november 2012.
I saw some kernel oopses as well, I'm wondering whether the RAID controller is going bad.
Gé
May 16 20:01:25 localhost kernel: ------------[ cut here ]------------ May 16 20:01:25 localhost kernel: WARNING: at kernel/rcutree.c:332 rcu_irq_enter+0x55/0x70() (Tainted: P W --------------- ) May 16 20:01:25 localhost kernel: Hardware name: Precision T5600 May 16 20:01:25 localhost kernel: Modules linked in: fuse ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat xt_CHECKSUM iptable_mangle bridge tpm_infineon nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs autofs4 8021q garp stp llc cpufreq_ondemand acpi_cpufreq freq_table mperf ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables nf_conntrack_ftp nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_REJECT ip6t_ipv6header nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables ipv6 vhost_net macvtap macvlan tun kvm_intel kvm uinput iTCO_wdt iTCO_vendor_support microcode dcdbas fglrx(P)(U) sg ftdi_sio usbserial i2c_i801 i2c_core lpc_ich mfd_core snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd soundcore snd_page_alloc shpchp e1000e ptp pps_core ext4 jbd2 mbcache sr_mod cdrom sd_mod crc_t10dif xhci_hcd ahci megaraid_sas dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan] May 16 20:01:25 localhost kernel: Pid: 0, comm: swapper Tainted: P W --------------- 2.6.32-431.11.2.el6.x86_64 #1 May 16 20:01:25 localhost kernel: Call Trace: May 16 20:01:25 localhost kernel: <IRQ> [<ffffffff81071e27>] ? warn_slowpath_common+0x87/0xc0 May 16 20:01:25 localhost kernel: [<ffffffff81068ff5>] ? enqueue_entity+0x125/0x450 May 16 20:01:25 localhost kernel: [<ffffffff81071e7a>] ? warn_slowpath_null+0x1a/0x20 May 16 20:01:25 localhost kernel: [<ffffffff810ebbb5>] ? rcu_irq_enter+0x55/0x70 May 16 20:01:25 localhost kernel: [<ffffffff8107a7bb>] ? irq_enter+0x1b/0x80 May 16 20:01:25 localhost kernel: [<ffffffff815315d3>] ? do_IRQ+0x43/0xf0 May 16 20:01:25 localhost kernel: [<ffffffff8100b9d3>] ? ret_from_intr+0x0/0x11 May 16 20:01:25 localhost kernel: [<ffffffff811704cf>] ? kmem_cache_free+0xbf/0x2b0 May 16 20:01:25 localhost kernel: [<ffffffff813892b0>] ? scsi_sg_free+0x0/0x60 May 16 20:01:25 localhost kernel: [<ffffffff811220b7>] ? mempool_free_slab+0x17/0x20 May 16 20:01:25 localhost kernel: [<ffffffff81122205>] ? mempool_free+0x95/0xa0 May 16 20:01:25 localhost kernel: [<ffffffff813892fc>] ? scsi_sg_free+0x4c/0x60 May 16 20:01:25 localhost kernel: [<ffffffff81291880>] ? __sg_free_table+0x60/0x80 May 16 20:01:25 localhost kernel: [<ffffffff81389474>] ? __scsi_release_buffers+0x104/0x110 May 16 20:01:25 localhost kernel: [<ffffffff81389f36>] ? scsi_io_completion+0x2a6/0x6c0 May 16 20:01:25 localhost kernel: [<ffffffff813801c2>] ? scsi_finish_command+0xc2/0x130 May 16 20:01:25 localhost kernel: [<ffffffff8138a4b5>] ? scsi_softirq_done+0x145/0x170 May 16 20:01:25 localhost kernel: [<ffffffff8126ea95>] ? blk_done_softirq+0x85/0xa0 May 16 20:01:25 localhost kernel: [<ffffffff8107a8e1>] ? __do_softirq+0xc1/0x1e0 May 16 20:01:25 localhost kernel: [<ffffffff8100c30c>] ? call_softirq+0x1c/0x30 May 16 20:01:25 localhost kernel: [<ffffffff8100c30c>] ? call_softirq+0x1c/0x30 May 16 20:01:25 localhost kernel: <EOI> [<ffffffff8100fa75>] ? do_softirq+0x65/0xa0 May 16 20:01:25 localhost kernel: [<ffffffff8107a795>] ? irq_exit+0x85/0x90 May 16 20:01:25 localhost kernel: [<ffffffff81531605>] ? do_IRQ+0x75/0xf0 May 16 20:01:25 localhost kernel: [<ffffffff8100b9d3>] ? ret_from_intr+0x0/0x11 May 16 20:01:25 localhost kernel: [<ffffffff812e0bee>] ? intel_idle+0xde/0x170 May 16 20:01:25 localhost kernel: [<ffffffff812e0bd1>] ? intel_idle+0xc1/0x170 May 16 20:01:25 localhost kernel: [<ffffffff81426b67>] ? cpuidle_idle_call+0xa7/0x140 May 16 20:01:25 localhost kernel: [<ffffffff81009fc6>] ? cpu_idle+0xb6/0x110 May 16 20:01:25 localhost kernel: [<ffffffff8150d22a>] ? rest_init+0x7a/0x80 May 16 20:01:25 localhost kernel: [<ffffffff81c26f8f>] ? start_kernel+0x424/0x430 May 16 20:01:25 localhost kernel: [<ffffffff81c2633a>] ? x86_64_start_reservations+0x125/0x129 May 16 20:01:25 localhost kernel: [<ffffffff81c26453>] ? x86_64_start_kernel+0x115/0x124 May 16 20:01:25 localhost kernel: ---[ end trace a0e1ee14d68f0684 ]---
On Mon, May 19, 2014 at 1:02 PM, m.roth@5-cent.us wrote:
Gé Weijers wrote:
I'm getting a lot of this at boottime:
udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11707)
udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11709)
udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11711)
udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan
It takes a few minutes to boot.
The machine is a Dell PRECISION T5600 with a PERC H310 RAID controller.
Hmmm, a) what's *in* this workstation? b) was this a fresh install?
mark
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Gé
Gé Weijers wrote:
Thanks for answering.
a) The workstation has:
- CPU E5-2687W
- 32 GB RAM (ECC)
- AMD FirePro V7900, original graphics card. (This happens with both the
AMD driver installed and not installed.)
- MegaRAID SAS 2008 controller configured for RAID1
I had a quad PCIe serial card in it as well, but I have removed it. No change.
b) It's was not a fresh install, but it's been doing this only recently. It started out with CentOS 6.3 or so in november 2012.
I saw some kernel oopses as well, I'm wondering whether the RAID controller is going bad.
Hard to tell from this. Anything significant in dmesg | tail? I've seen that damn swapper/tainted, but there's some tuning that can be done, that might be hugepage issues. <snip> mark
I'm running a memory check right now, just to rule things out.
Gé
On Mon, May 19, 2014 at 2:36 PM, m.roth@5-cent.us wrote:
Gé Weijers wrote:
Thanks for answering.
a) The workstation has:
- CPU E5-2687W
- 32 GB RAM (ECC)
- AMD FirePro V7900, original graphics card. (This happens with both the
AMD driver installed and not installed.)
- MegaRAID SAS 2008 controller configured for RAID1
I had a quad PCIe serial card in it as well, but I have removed it. No change.
b) It's was not a fresh install, but it's been doing this only recently. It started out with CentOS 6.3 or so in november 2012.
I saw some kernel oopses as well, I'm wondering whether the RAID controller is going bad.
Hard to tell from this. Anything significant in dmesg | tail? I've seen that damn swapper/tainted, but there's some tuning that can be done, that might be hugepage issues.
<snip> mark
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Gé Weijers -
m.roth＠5-cent.us