Discuss November 2013

discuss@lists.centos.org

160 participants
171 discussions

5.10, crashes
by m.roth＠5-cent.us 01 Nov '13

01 Nov '13

We've just started getting this. We're running 5.10, kernel 2.6.32-358.18.1.el6.x86_64. Anyone else seen anything like this, or have any ideas? mark Nov 1 14:34:21 <server> kernel: WARNING: at block/ll_rw_blk.c:543 blk_do_ordered() Nov 1 14:34:21 <server> kernel: Nov 1 14:34:21 <server> kernel: Call Trace: Nov 1 14:34:22 <server> kernel: [<ffffffff8014defa>] blk_do_ordered+0x27a/0x2b3 Nov 1 14:34:22 <server> kernel: [<ffffffff8014ac82>] elv_next_request+0x13e/0x178 Nov 1 14:34:22 <server> kernel: [<ffffffff8807b335>] :scsi_mod:scsi_request_fn+0x6a/0x392 Nov 1 14:34:22 <server> kernel: [<ffffffff8005abd2>] generic_unplug_device+0x22/0x32 Nov 1 14:34:22 <server> kernel: [<ffffffff8004d957>] run_workqueue+0x9e/0xfb Nov 1 14:34:22 <server> kernel: [<ffffffff8004a1aa>] worker_thread+0x0/0x122 Nov 1 14:34:22 <server> kernel: [<ffffffff800a3d4a>] keventd_create_kthread+0x0/0xc4 Nov 1 14:34:22 <server> kernel: [<ffffffff8004a29a>] worker_thread+0xf0/0x122 Nov 1 14:34:22 <server> kernel: [<ffffffff8008f4a9>] default_wake_function+0x0/0xe Nov 1 14:34:22 <server> kernel: [<ffffffff800a3d4a>] keventd_create_kthread+0x0/0xc4 Nov 1 14:34:22 <server> kernel: [<ffffffff800a3d4a>] keventd_create_kthread+0x0/0xc4 Nov 1 14:34:22 <server> kernel: [<ffffffff80032c68>] kthread+0xfe/0x132 Nov 1 14:34:22 <server> kernel: [<ffffffff8005dfc1>] child_rip+0xa/0x11 Nov 1 14:34:22 <server> kernel: [<ffffffff800a3d4a>] keventd_create_kthread+0x0/0xc4 Nov 1 14:34:23 <server> kernel: [<ffffffff80032b6a>] kthread+0x0/0x132 Nov 1 14:34:23 <server> kernel: [<ffffffff8005dfb7>] child_rip+0x0/0x11

3 2

CentOS 5.10 - turn off sosreport?
by m.roth＠5-cent.us 01 Nov '13

01 Nov '13

Anyone know how to make this thing shut up? I can't find anything that does, and it's spamming our central log server.... mark

1 2

Re: [CentOS] new laptop: compiling source for i7 CPUs???
by ken 01 Nov '13

01 Nov '13

On 10/27/2013 05:57 PM ken wrote: > One laptop I'm looking at buying offers these CPU options: > > * 4 Generation Intel® Core™ i7-4700MQ Processor ( 2.4 GHz 6MB L3 Cache - > 4 Cores plus Hyperthreading ) > > * 4th Generation Intel® Core™ i7-4800MQ Processor ( 2.7 GHz 6MB L3 Cache > - 4 Cores plus Hyperthreading ) > > * 4th Generation Intel® Core™ i7-4900MQ Processor ( 2.8 GHz 8MB L3 Cache > - 4 Cores plus Hyperthreading ) > <http://ark.intel.com/compare/75131,75128,75117> shows a side-by-side comparison of the CPUs above. There are differences between the first two. Some of these (as described by Intel) are: * Intel® vPro™ Technology: a set of security and manageability capabilities built into the processor aimed at addressing four critical areas of IT security: 1) Threat management, including protection from rootkits, viruses, and malware 2) Identity and web site access point protection 3) Confidential personal and business data protection 4) Remote and local monitoring, remediation, and repair of PCs and workstations. * Intel® Virtualization Technology for Directed I/O (VT-d): continues from the existing support for IA-32 (VT-x) and Itanium® processor (VT-i) virtualization adding new support for I/O-device virtualization. Intel VT-d can help end users improve security and reliability of the systems and also improve performance of I/O devices in virtualized environments. * Intel® Transactional Synchronization Extensions New Instructions (Intel® TSX-NI): a set of instructions focused on multi-threaded performance scaling. This technology helps make parallel operations more efficient via improved control of locks in software. * Intel® Trusted Execution Technology for safer computing: a versatile set of hardware extensions to Intel® processors and chipsets that enhance the digital office platform with security capabilities such as measured launch and protected execution. It enables an environment where applications can run within their own space, protected from all other software on the system. These aren't the only additional instruction sets on these chips, but, as said, just those which are offered on the two higher models and not on the first-listed. There are quite a few other feature sets listed. > There are considerable price increases with each quite small increase in > speed-- hundreds of dollars--, but over two or three years I think the > extra dollars would be worth the performance increase... *IF* there is a > noticeable performance increase. > > This would depend to a large degree upon the code... specifically, if > the code (OS and apps) makes use of the expanded instruction sets of the > more expensive CPUs. Generally the code doesn't, unless gcc/make is > configured for the particular CPU and then that source is compiled. I've > done this in the (distant) past and noticed a significant increase in > performance over the stock executables provided by the distro. > > > http://gcc.gnu.org/onlinedocs/gcc-4.6.4/gcc/i386-and-x86_002d64-Options.htm… > says "mtune" can be set to one of these: > > corei7 > Intel Core i7 CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, > SSSE3, SSE4.1 and SSE4.2 instruction set support. > corei7-avx > Intel Core i7 CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, > SSSE3, SSE4.1, SSE4.2, AVX, AES and PCLMUL instruction set support. > core-avx-i > Intel Core CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, > SSE4.1, SSE4.2, AVX, AES, PCLMUL, FSGSBASE, RDRND and F16C instruction > set support. > > Does 'cpuinfo' tell us about all of these when they're present, or are > we supposed to find out some other way? > > These three options wouldn't seem to come close to specifying all the > various core i7 CPUs there are and optimizing for all the features of > each. Getting *some* of the additional instructions offered by i7s > would certainly help performance over what the standard distro offers, > but probably still not enough to warrant the extra expense of the > higher-end CPUs. > > http://gcc.gnu.org/onlinedocs/gcc-4.6.4/gcc/i386-and-x86_002d64-Options.htm… > also offers: > > native > This selects the CPU to tune for at compilation time by determining > the processor type of the compiling machine. Using -mtune=native will > produce code optimized for the local machine under the constraints of > the selected instruction set. Using -march=native will enable all > instruction subsets supported by the local machine (hence the result > might not run on different machines). > > but, again, does it make a distinction between the three CPUs cited at > top (and yet others)? If the code produced for all three CPUs is the > identical, then there isn't much point in spending for the costlier CPUs. > > And does using "native" give better or worse results than specifying one > of the core* options? > > Also, when compiling a kernel to run on a VM, should some other gcc > option(s) be used? > > > At this point I'd just be making wild guesses about how all this > actually works out. So does anyone have experience with, or maybe some > inside knowledge about, any of this? > > If so, thanks for any light you can shed. > >

1 0

Re: [CentOS] zimbra test
by Wes James 01 Nov '13

01 Nov '13

On Fri, Nov 1, 2013 at 10:58 AM, Reindl Harald <h.reindl(a)thelounge.net>wrote: > > > Am 01.11.2013 17:46, schrieb Wes James: > > On Fri, Nov 1, 2013 at 10:40 AM, Bart Schaefer < > barton.schaefer(a)gmail.com>wrote: > > > >> On Fri, Nov 1, 2013 at 9:21 AM, Wes James <comptekki(a)gmail.com> wrote: > >>> Why does > >>> removing postfix remove these others. cron and the others are > dependent > >> on > >>> having postfix? Seems odd if they are. > >> > >> They are dependent on having a local SMTP server, for example cron > >> requires one to send email containing the stderr output of (presumably > >> failed) jobs. If the zimbra packages declare the appropriate > >> provides, you should be able to re-install cron et al. after > >> installing zimbra. > > > > I see that from the previous email. I have been reinstalling them and > then > > checking to see how to keep postfix from starting. After installing > > cronie, etc. back, postfix was installed. I did postfix stop, but it > said > > it was not running. I'll have to look in the start up and see if it is > set > > to start on reboot > > why trial and error? > chkconfig postfix off > > are you really have services uncontrolled running > instead explicit dsiable or enable them? > > chkconfig --list and disable anything you are not using > if it comes to servers connected to a network > > chkconfig --help > chkconfig version 1.3.49.3 - Copyright (C) 1997-2000 Red Hat, Inc. > This may be freely redistributed under the terms of the GNU Public License. > Thanks - that info is useful. -wes

2 1

starting/stopping services
by Wes James 01 Nov '13

01 Nov '13

In an earlier thread it was mentioned I could use postfix stop to stop postfix. I'm trying to get sshd started and starting on boot. I did chkconfig sshd on and that worked fine, but then tried sshd start, but that didn't work. It looks like I need to do service sshd start (I did just that and it is now started). Why the difference? Thanks, -wes

2 3

Clutter-gtk 1.4.4
by Jerry Geis 01 Nov '13

01 Nov '13

I have need to compile (from source) clutter-1.16.0 (seems to be fine) and then clutter-gtk 1.4.4 on centos 6.4 (x86-64) I am getting this error: ake[2]: Entering directory `/home/silentm/MessageNet/totem/clutter-gtk-1.4.4/clutter-gtk' CC gtk-clutter-actor.lo CC gtk-clutter-embed.lo In file included from /usr/include/clutter-1.0/clutter/clutter-deform-effect.h:33, from /usr/include/clutter-1.0/clutter/clutter.h:57, from ./gtk-clutter-actor.h:32, from ./gtk-clutter-actor.c:42: /usr/include/clutter-1.0/clutter/clutter-offscreen-effect.h:97: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token In file included from /usr/include/clutter-1.0/clutter/clutter-deform-effect.h:33, from /usr/include/clutter-1.0/clutter/clutter.h:57, from ./gtk-clutter-embed.h:31, from ./gtk-clutter-embed.c:49: /usr/include/clutter-1.0/clutter/clutter-offscreen-effect.h:97: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token In file included from /usr/include/clutter-1.0/clutter/clutter.h:84, Anyone might know why??? Thanks, Jerry

1 0

Re: [CentOS] zimbra test
by Wes James 01 Nov '13

01 Nov '13

On Fri, Nov 1, 2013 at 10:58 AM, Reindl Harald <h.reindl(a)thelounge.net>wrote: <snip> > > why trial and error? > chkconfig postfix off > > are you really have services uncontrolled running > instead explicit dsiable or enable them? > > chkconfig --list and disable anything you are not using > if it comes to servers connected to a network > > chkconfig --help > chkconfig version 1.3.49.3 - Copyright (C) 1997-2000 Red Hat, Inc. > This may be freely redistributed under the terms of the GNU Public License. > I did chkconfig --list|grep postfix and it has postfix 0:off 1:on ......... 6:off The numbers are the run levels the service will run on? After chkconfig postfix off, they all changed to off. 1-5 had been on. -wes

1 0

zimbra test
by Wes James 01 Nov '13

01 Nov '13

I wanted to test zimbra on centos 6 (I'm new to centos). While installing zimbra it said there was a conflict on port 25. So I found out that postfix is the default mta on centos. I then did sudo yum remove postfix and followed the prompts for removing it, but in doing so it removed chrome that I had installed and several other packages that seem to be important. Some of these were cron, some lsb packages, and some others. Why does removing postfix remove these others. cron and the others are dependent on having postfix? Seems odd if they are. Thanks, -wes

2 2

Re: [CentOS] removed items from removing postfix
by Wes James 01 Nov '13

01 Nov '13

On Fri, Nov 1, 2013 at 10:37 AM, Reindl Harald <h.reindl(a)thelounge.net>wrote: > > Am 01.11.2013 17:33, schrieb Wes James: > > Here are the items removed when removing postfix: > > <snip> > > > > > Seems odd to me that those items would need to be removed just because > > postfix is removed. > > what is there odd? > > LSB contains /usr/sbin/sendmail and if you remove all MTA's the > dependencies for LSB packages are no no longer satisfied and > any package which reuqires LSB packages is removed as circullar > dependency > > > http://refspecs.linuxbase.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/b… > > OK. Thanks for the info. -wes

1 0

removed items from removing postfix
by Wes James 01 Nov '13

01 Nov '13

Here are the items removed when removing postfix: Nov 1 09:56:59 localhost yum[22042]: Erased: google-chrome-stable Nov 1 09:57:00 localhost yum[22042]: Erased: redhat-lsb-compat Nov 1 09:57:00 localhost yum[22042]: Erased: redhat-lsb Nov 1 09:57:01 localhost yum[22042]: Erased: redhat-lsb-graphics Nov 1 09:57:01 localhost yum[22042]: Erased: redhat-lsb-printing Nov 1 09:57:02 localhost yum[22042]: Erased: redhat-lsb-core Nov 1 09:57:03 localhost yum[22042]: Erased: sysstat Nov 1 09:57:04 localhost yum[22042]: Erased: crontabs Nov 1 09:57:05 localhost yum[22042]: Erased: cronie-anacron Nov 1 09:57:06 localhost yum[22042]: Erased: cronie Nov 1 09:57:07 localhost yum[22042]: Erased: postfix Seems odd to me that those items would need to be removed just because postfix is removed. Thanks, -wes

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss November 2013