Re: [gentoo-user] Recommend a good replacement for XFCE?
On Sat, 2016-09-24 at 01:52 -0400, waltd...@waltdnes.org wrote: > On Fri, Sep 23, 2016 at 11:45:26PM +, Grant Edwards wrote > > > Would anybody care to make a recommendation? > > How about ditching "Desktop Environment" altogether and using a > "Window Manager" instead? I use ICEWM. It has to be configured with > a > text editor, but you can then set it and forget it. If using a Window Manager fits, awesome is worth a mention. https://awesomewm.org/ * Very stable, fast and small codebase and footprint; * First window manager using asynchronous XCB library instead of the old synchronous Xlib: make awesome less subject to latency than many window managers; * Very well documented source code and API; * No mouse needed: everything can be performed with keyboard; * Real multihead support (XRandR, Xinerama or Zaphod mode) with per screen desktops (tags); * Implement many Freedesktop standards: EWMH, XDG Base Directory, XEmbed, Desktop Notification, System Tray; * Doesn't distinguish between layers: there is no floating or tiled layer; * Use tags instead of workspaces: allow to place clients on several tags, and display several tags at the same time; * A lot of Lua extensions to add features: dynamic tagging, widget feeding, tabs, layouts; * D-Bus support; And more. Regards, Carlos
Re: [gentoo-user] THE SCREAM. (Pulseaudio)
On Tue, 2015-09-29 at 13:57 -0400, Alan Grimes wrote: > I thought it was just a pulseaudio configuration, so I managed to get > that bastard restarted, no luck, then it was complaining that the > audio > device was stuck or something, I warm booted then cold booted... > Still > no sound. =( > > Nothing has changed on the machine except I made the horrible, > unforgivable mistake of trying to update the software on my machine. > =\ > > It has been so long since I have had a problem with my audio config, > I > don't know where to begin solving this. Right now there are no error > messages, it just pretends to play sound normally but doesn't. =( Hi Alan, I have the same hardware and pulseaudio configuration as you. (I guess it's quite stock standard). I've had the odd occasion where I "loose" sound after using the keyboard's shortcut key for mute. A little one liner got it back: amixer -D pulse set Master 1+ unmute This assumes you're using alsa as the backend for pulseaudio. Other possibilities are missing modules, kernel compiled with missing options, missing packages for audio subsystem pulseaudio communicates with. It's hard to be specific without exact errors. Hope that helps. Carlos
Re: [gentoo-user] Output of sensor k10temp-pci-00c3
On Fri, 2013-03-22 at 20:58 +0100, Sascha Cunz wrote: In the recent thread system freezes during compiles, Carlos Henderson showed the output of $(sensors), among them the output of the k10temp-pci-00c3. I stopped trusting that sensor. After some hours of idle, it shows me: k10temp-pci-00c3 Adapter: PCI adapter temp1:+16.8°C (high = +70.0°C) (crit = +70.0°C, hyst = +67.0°C) 16.8°C is roughly 4°C _below_ the room temperature. If I'd boot to Windows right now, the mainboard-manufacturer's system utility shows a CPU temperature of 25°C (which is more or less the usual value it shows for Windows when idle). My CPU is: processor : 5 vendor_id : AuthenticAMD cpu family : 21 model : 1 model name : AMD FX(tm)-6200 Six-Core Processor stepping: 2 microcode : 0x6000626 running on an Asrock mainboard (Kernel is a gentoo-3.8.1-r1). My question to the list is: Could this strange temperature be realistic? Does anyone have similar observations with AMD-Bulldozers? Sascha Hi Sascha, As a comparison, here's my machines processor: vendor_id : AuthenticAMD cpu family : 16 model : 10 model name : AMD Phenom(tm) II X6 1100T Processor stepping: 0 microcode : 0x1bf From the kernel document hwmon/k10temp has a couple points: 1. The driver detects the mainboard socket type and not the processors actual capabilities. If an AM3 processor is on an AM2+ mainboard, driver options may be required. 2. The temperature reported is relative to the point at which the system must supply the maximum cooling for the processors specified maximum case temperature and maximum thermal power dissipation. It would appear that the temperature reported is quite possibly correct, although not intuitive or easily verified as valid. Hope that helps. Regards, Carlos
Re: [gentoo-user] System freezes during compiles [SOLVED]
On Wed, 2013-03-20 at 20:57 +0100, Volker Armin Hemmann wrote: you might just hit a thrashing situation. Linux is very bad when it comes to abusing swap in case of an emergency. But it also sounds like overheating or a power problem. Power problems might be caused by the PSU - but it could also be the power circuitry of your mobo. First of all, thank you to everyone for the superb help and suggestions regarding this problem. Yesterday, I enabled some swap space, but the system froze on the first attempt at compiling glibc. The next cheapest option was to clean the case of dust. The CPU heat sink was clogged with a think layer of dust. After thoroughly cleaning the case, the system compiled glibc, the kernel, qtcore and other packages without freezing. The only downside is since the fins on the heat sink are exposed directly to the fan again, the noise level has gone up. When I checked the RPMs in the BIOS I noticed a setting which states, decrease CPU voltage and frequency in the event of a temperature threshold being exceeded. This would explain the kernel watchdog messages reporting stalls were detected. For anyone that's curious, here's the output of sensors and free during the compile of glibc. Swap wasn't being touched at all, there's still 4GB of memory free. The cpu was getting close to the threshold limit even after the heat sink was cleaned of dust. k10temp-pci-00c3 Adapter: PCI adapter temp1:+58.9°C (high = +70.0°C) (crit = +71.0°C, hyst = +66.0°C) it8720-isa-0228 Adapter: ISA adapter in0: +1.49 V (min = +0.00 V, max = +4.08 V) in1: +1.47 V (min = +0.00 V, max = +4.08 V) in2: +3.38 V (min = +0.00 V, max = +4.08 V) +5V: +2.96 V (min = +0.00 V, max = +4.08 V) in4: +3.07 V (min = +0.00 V, max = +4.08 V) in5: +3.25 V (min = +0.00 V, max = +4.08 V) in6: +4.08 V (min = +0.00 V, max = +4.08 V) ALARM 5VSB: +2.98 V (min = +0.00 V, max = +4.08 V) Vbat: +3.28 V fan1:6750 RPM (min =0 RPM) fan2: 0 RPM (min =0 RPM) fan3: 0 RPM (min =0 RPM) fan4: 0 RPM (min =0 RPM) temp1:+31.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp2:+67.0°C (low = +127.0°C, high = +127.0°C) sensor = thermal diode temp3:+70.0°C (low = +127.0°C, high = +127.0°C) sensor = thermal diode cpu0_vid:+0.525 V intrusion0: ALARM total used free sharedbuffers cached Mem: 816740031953004972100 0 62024 1379256 -/+ buffers/cache:17540206413380 Swap: 511996 0 511996 Once again, a big thanks for everyone's help. Regards, Carlos
Re: [gentoo-user] System freezes during compiles
On Wed, 2013-03-20 at 16:27 -0500, Paul Hartman wrote: I had a virtual server that kept crashing/rebooting during compiles of large packages such as php. It ended up being because it was running out of memory. Added another 1GB of swap space and it has been happy ever since. Thanks Paul. Volker suggested a possible caused was swap. I'll allocate some swap space after the smartctl self-test finishes and try to recompile gcc a few times. Regards, Carlos
Re: [gentoo-user] System freezes during compiles
On Thu, 2013-03-21 at 06:45 +0100, Volker Armin Hemmann wrote: You got your answer. 8gig and no swap is NOT ENOUGHT. It's a strong indicator, which is going to be corrected. I am slightly confused by the resulting behaviour however. I was of the impression oomkiller would start to kill processes when unallocated memory is getting scarce? How would no free memory cause CPU stalls? Regards, Carlos
Re: [gentoo-user] System freezes during compiles
On Wed, 2013-03-20 at 18:43 +0100, Daniel Wagener wrote: Frozen means there is no Hard Drive Activity going on right? And there is no other indication, that you are just running out of memory? I can't categorically state if there was drive activity. I was so fixated on regaining control of the machine that I failed to pay attention to the state of the HDD LED. I'll make a point of checking it the next time the machine appears to freeze. I saw no other indications of memory exhaustion after the system came back from the soft-power reset button being pressed. Regards, Carlos
Re: [gentoo-user] System freezes during compiles
On Wed, 2013-03-20 at 08:17 +, Mick wrote: Stating the obvious, it seems that the kernel is struggling and indeed you may have come across some nasty kernel bug. However, it could well be that it is not related to the kernel you're running, or your kernel config. It could be a problem with the power supply being faulty and causing these lock ups. Unless someone else comes up with a better idea to troubleshoot it further, I would consider replacing the power supply with another of a known good condition. Thanks for the good advice Mick. I don't have spare hardware on-tap so switching psu, memory or processor may prove to be tricky. It's one of those catch 22's where I don't want to spend on components that aren't faulty, however I need to spend on components to test if they're faulty. I've been given a few other test to perform before I start moving to hardware replacement. Regards, Carlos
Re: [gentoo-user] System freezes during compiles
On Wed, 2013-03-20 at 20:57 +0100, Volker Armin Hemmann wrote: you might just hit a thrashing situation. Linux is very bad when it comes to abusing swap in case of an emergency. But it also sounds like overheating or a power problem. Power problems might be caused by the PSU - but it could also be the power circuitry of your mobo. It's not a thrashing issue as I don't have any swap. The 8GB of ram has been sufficient memory for all tasks thus far. I have no objection to allocating some swap space if it could resolve the issue. Actually, Grant and you both suggested possible heat issues which has just made me think that I should check for dust build up in the CPU heat sink. There so much dust where I live that I have to vacuum dust build up from the case. The sensors tool reports 51C, it doesn't appear to be running too hot, but I don't have a baseline to compare it to. I see I need to implement monitoring for this machine once it's stable again. k10temp-pci-00c3 Adapter: PCI adapter temp1:+51.0°C (high = +70.0°C) (crit = +71.0°C, hyst = +66.0°C) I'll give the inside a clean this weekend and see if there's any improvement. Thanks for the suggestions. Regards, Carlos
Re: [gentoo-user] Re: System freezes during compiles
On Wed, 2013-03-20 at 16:14 +, Grant Edwards wrote: On 2013-03-20, Carlos Hendson skyc...@gmx.net wrote: That's by no means conclusive, however, I've also run a complete pass of memcheck for over an hour without any issues reported. FWIW. I've had flakey memory that ran memcheck fine for several hours and multiple passes -- but if I let it run long enough, it would fail. I wouldn't be confident unless memtest ran for at least 12 hours (24 would be even better). I'd also keep an eye on CPU core temperature. A failing hard-drive can also cause some pretty strange behavior. If you're drives are smart (AFAICT, all recent ones are), ask them how they're feeling with 'smartclt' or something like that. I'll run a 24 hour memtest this weekend. I started a long test on the hard drive: smartctl -t long /dev/sda smartctl -a /dev/sda also appears to indicate various errors (the output is attached). I'll trying to track down some documentation as to what they're actually reporting. Looking at the difference between the output of smartctl for before and during the test, there has been an increase in errors detected for ID #195 Before test: 195 Hardware_ECC_Recovered 0x001a 001 001 000Old_age Always - 241822 During test: 195 Hardware_ECC_Recovered 0x001a 001 001 000Old_age Always - 243582 Could this be the cause of the stalls during compiles? If it is the cause, is it possible for the kernel to detect such failures and report them? Thanks to you and everyone else for your ideas and suggestions. Regards, Carlos smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.7.10-gentoo] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: SAMSUNG SpinPoint M5 Device Model: SAMSUNG HM250JI Serial Number:S0TVJQSQ501163 LU WWN Device Id: 5 0f 031501163 Firmware Version: HS100-10 User Capacity:250,059,350,016 bytes [250 GB] Sector Size: 512 bytes logical/physical Device is:In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0 Local Time is:Wed Mar 20 20:55:00 2013 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 32) The self-test routine was interrupted by the host with a hard or soft reset. Total time to complete Offline data collection:( 103) seconds. Offline data collection capabilities:(0x51) SMART execute Offline immediate. No Auto Offline data collection support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 2) minutes. Extended self-test routine recommended polling time:( 103) minutes. SCT capabilities: (0x003f) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 100 051Pre-fail Always - 40 3 Spin_Up_Time0x0007 252 252 025Pre-fail Always - 2000 4 Start_Stop_Count0x0032 099 099 000Old_age Always - 2012 5 Reallocated_Sector_Ct 0x0033 054 054 010Pre-fail Always - 428 7 Seek_Error_Rate 0x000f 252 252 051Pre-fail Always - 0 8 Seek_Time_Performance
[gentoo-user] System freezes during compiles
Hello, For last few weeks or so, I've been getting intermittent hard lock-ups during the emerge of various packages. It appears the more compile intensive the package, the more likely the lock-up. These lock-ups have occurred under kernels 3.4.9 and 3.7.10 with gcc 4.5.4 and 4.6.3. Once the machine is in a frozen state, the only thing that responds is the soft power reset button. Some times the machine lock-ups again after the button is pressed (this is because the compile resumes once the system comes out of it's frozen state). If the system subsequently lock-ups because I wasn't able to cancel the compile fast enough only a only option left is a hard power reset (10sec + hold power button). If I cancel the compile, the system is perfectly responsive and functions normally. There are kernel stack traces in /var/log/messages which I'm unable to decipher and diagnose as to what caused the lock-up. If I had to guess, I'd blame an incorrect setting in the .config, but since I'm stuck in the diagnostic of what part of the kernel might be experiencing the problem, I need a bit of help to pin point the issue. I believe it to be a kernel configuration issue because when I booted the machine using a system rescue Live CD, I was able to chroot into the system and emerge packages like gcc without the lock-up problem occurring. That's by no means conclusive, however, I've also run a complete pass of memcheck for over an hour without any issues reported. I'd like to completely rule out hardware failure, what diagnostic tools tools are recommend to try identify potential hardware issue of this type? The various kernel stack traces are attached in case someone wants to take a look. I can provide more information should it be needed. Any help or advice would be appreciated. Regards, Carlos Mar 12 23:42:03 hydra kernel: [58066.564110] [ cut here ] Mar 12 23:42:03 hydra kernel: [58068.663176] WARNING: at kernel/watchdog.c:241 watchdog_overflow_callback+0x93/0x9e() Mar 12 23:42:03 hydra kernel: [58068.673235] Hardware name: GA-990FXA-D3 Mar 12 23:42:03 hydra kernel: [58068.673303] Watchdog detected hard LOCKUP on cpu 2 Mar 12 23:42:03 hydra kernel: [58068.751056] Modules linked in: usb_storage uas ipv6 it87 hwmon_vid fglrx(PO) uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core joydev radeon i2c_al go_bit ttm drm_kms_helper drm r8169 xhci_hcd ata_generic pata_acpi i2c_piix4 mii i2c_core pata_atiixp wmi serio_raw k10temp powernow_k8 pcspkr mperf freq_table Mar 12 23:42:03 hydra kernel: [58068.945979] Pid: 720, comm: cc1 Tainted: P O 3.4.9-gentoo #2 Mar 12 23:42:03 hydra kernel: [58068.946053] Call Trace: Mar 12 23:42:03 hydra kernel: [58069.054704] NMI [81030050] ? warn_slowpath_common+0x78/0x8c Mar 12 23:42:03 hydra kernel: [58069.231277] [810300fc] ? warn_slowpath_fmt+0x45/0x4a Mar 12 23:42:03 hydra kernel: [58069.271020] [8107bf89] ? watchdog_overflow_callback+0x93/0x9e Mar 12 23:42:03 hydra kernel: [58069.271135] [8107bef6] ? touch_nmi_watchdog+0x62/0x62 Mar 12 23:42:03 hydra kernel: [58069.293566] [8108c002] ? __perf_event_overflow+0x12c/0x1ae Mar 12 23:42:03 hydra kernel: [58069.293689] [8108a0a1] ? perf_event_update_userpage+0x13/0xbf Mar 12 23:42:03 hydra kernel: [58069.293811] [8100db25] ? x86_pmu_handle_irq+0xbe/0xf3 Mar 12 23:42:03 hydra kernel: [58069.293939] [8151ff39] ? nmi_handle.isra.4+0x3e/0x61 Mar 12 23:42:03 hydra kernel: [58069.294038] [8151fffb] ? do_nmi+0x9f/0x287 Mar 12 23:42:03 hydra kernel: [58069.294139] [8151f7e2] ? end_repeat_nmi+0x1a/0x1e Mar 12 23:42:03 hydra kernel: [58069.294253] [8151f084] ? _raw_spin_lock_irq+0x6/0x6 Mar 12 23:42:03 hydra kernel: [58069.294357] [8151f084] ? _raw_spin_lock_irq+0x6/0x6 Mar 12 23:42:03 hydra kernel: [58069.314699] [8151f084] ? _raw_spin_lock_irq+0x6/0x6 Mar 12 23:42:03 hydra kernel: [58069.318869] EOE IRQ [81059da5] ? ntp_tick_length+0x23/0x28 Mar 12 23:42:03 hydra kernel: [58069.319051] [8105972a] ? do_timer+0x89/0x465 Mar 12 23:42:03 hydra kernel: [58069.319185] [8105e881] ? tick_do_update_jiffies64+0x74/0x98 Mar 12 23:42:03 hydra kernel: [58069.319300] [8105e9b1] ? tick_sched_timer+0x3f/0x8d Mar 12 23:42:03 hydra kernel: [58069.319424] [810476b7] ? __run_hrtimer.isra.27+0x4b/0xa3 Mar 12 23:42:03 hydra kernel: [58069.319547] [81047ca9] ? hrtimer_interrupt+0xd9/0x1c9 Mar 12 23:42:03 hydra kernel: [58069.319655] [81017b71] ? smp_apic_timer_interrupt+0x6e/0x80 Mar 12 23:42:03 hydra kernel: [58069.319750] [81524907] ? apic_timer_interrupt+0x67/0x70 Mar 12 23:42:03 hydra kernel: [58069.319810] EOI Mar 12 23:42:03 hydra kernel: [58069.324331] ---[ end trace b1a58589d91a0dec ]--- Mar 12 23:58:02 hydra kernel: [59023.803433] [ cut here ] Mar 12 23:58:02 hydra
Re: [gentoo-user] Looks like a nasty bug in portage .38
On Mon, 2012-12-24 at 22:46 +0530, Nilesh Govindrajan wrote: I'm on ~amd64. Updated portage in the morning. But it seems the .38 version has a nasty bug. It freezes the system every single time I try to compile a cross tool chain. I tried with various options, like reducing make jobs, etc, but didn't help. Back to .31 and things seem to be moving better. Anyone else faced this? I've noticed a few freezes during emerges on my system in the last week or two. The system is currently building x11-libs/qt-webkit-4.8.4 and has had a series of freezes. Portage: sys-apps/portage-2.1.11.31 Kernel: sys-kernel/gentoo-sources-3.4.9 dmesg produced an entry which may be related: [ 8003.626681] hrtimer: interrupt took 4376464 ns I haven't looked any further into the issue as yet, as I don't have the time available. While writing this email the system froze for 47 seconds with no new kernel messages. :/ Regards, Carlos
Re: [gentoo-user] Re: SAR vs collectl
On Fri, 2012-08-31 at 14:50 +, James wrote: my bad.. No, not your bad. I was in the same boat as you when I wanted to install sar. I found the gentoo package name on the web. Sorry if my previous post suggested the executed commands would have found the package name for sar on a system which didn't already have it installed. Got any syntax that would allow me to know that sar was in sysstat? equery belongs /usr/bin/sar returns a blank line for me As you discovered equery belongs file name only returns results for installed packages which own filename. I'm not aware of any tool that will tell you what files a package will create/own before it's built and installed on the system. It would be nice if there was some sort of online database that could be queried for such information. Something like how the equery tool functions but online instead of locally. Regards, Carlos
Re: [gentoo-user] SAR vs collectl
On Thu, 2012-08-30 at 18:25 +, James wrote: Is SAR quickly available for Gentoo (an overlay I missed)? hydra ~ # which sar /usr/bin/sar hydra ~ # equery belongs /usr/bin/sar * Searching for /usr/bin/sar ... app-admin/sysstat-10.0.5 (/usr/bin/sar) hydra ~ # Hope that helps, Carlos
Re: [gentoo-user] (s)mplayer problems
On Fri, 2012-02-10 at 09:31 +0100, Helmut Jarausch wrote: Many thanks, the workaround mentioned in this link fixes the segment fault. Still, audio doesn't work, yet. It seems mplayer doesn't have the codec required for the WMV format. You should check mplayer has the win32codecs use flag enabled. You can do this with equery or eix (or other equivalent tools). equery uses mplayer eix mplayer Use the information from the the wiki to help you pick the right flags and required packages: http://en.gentoo-wiki.com/wiki/MPlayer For example, the mplayer output posted in another message has the text: Xlib: extension NV-GLX missing on display :0. [vdpau] Error when calling vdp_device_create_x11: 1 The use flag description for vdpau says: + + vdpau : Enables experimental VDPAU support (requires nVidia video cards) to offload MPEG2/MPEG4/VC1/WMV CPU processing to video card Since you have an ATI graphics card in this machine, you can safely disable the vdpau use flag. Hope that helps. Regards, Carlos
Re: [gentoo-user] (s)mplayer problems
On Wed, 2012-02-08 at 14:40 +0100, Helmut Jarausch wrote: On 02/08/2012 02:07:55 PM, Nilesh Govindrajan wrote: On Wed 08 Feb 2012 06:31:19 PM IST, Helmut Jarausch wrote: Hi, I need some advice. Since a short time I have tremendous problems with mplayer / smplayer and I don't know why. First, vlc works just fine, i.e. video and audio Second, mplayer produces a segment fault within fglrx (ati- drivers-12.1-r1 with gentoo-sources-3.2.x) Third, smplayer does show the video (without a segment fault) but doesn't play audio. How can I isolate the problem? Many thanks for a hint, Helmut. Run mplayer on the command line and see what error it throws. Paste it here. Unfortunately, that's impossible. mplayer starts, opens a window and then segfaults, i.e. kills Xorg and forces me to reboot the machine. Xorg.0.log.old shows Backtrace: [ 1669.886] 0: /usr/bin/X (xorg_backtrace+0x26) [0x564f86] [ 1669.886] 1: /usr/bin/X (0x40+0x168bc9) [0x568bc9] [ 1669.886] 2: /lib64/libpthread.so.0 (0x7fa7aa5f4000+0x10ff0) [0x7fa7aa604ff0] [ 1669.887] 3: /usr/lib64/xorg/modules/drivers/fglrx_drv.so (xs111LookupPrivate+0x22) [0x7fa7a778c372] [ 1669.887] 4: /usr/lib64/xorg/modules/drivers/fglrx_drv.so (xclLookupPrivate+0xd) [0x7fa7a7167cdd] [ 1669.887] 5: /usr/lib64/xorg/modules/amdxmm.so (X740XvPutImage +0x12e) [0x7fa7a441f81e] [ 1669.887] 6: /usr/bin/X (0x40+0x8a84e) [0x48a84e] [ 1669.888] 7: /usr/lib64/xorg/modules/extensions/libextmod.so (0x7fa7a83f8000+0xf53e) [0x7fa7a840753e] [ 1669.888] 8: /usr/bin/X (0x40+0x36979) [0x436979] [ 1669.888] 9: /usr/bin/X (0x40+0x2613a) [0x42613a] [ 1669.888] 10: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7fa7a952b3cd] [ 1669.888] 11: /usr/bin/X (0x40+0x2645d) [0x42645d] [ 1669.888] Segmentation fault at address 0x20 Thanks, Helmut. Did you read this and follow the advice to work around Xv as mentioned in the elog? This release of ati-drivers has a crashing bug when using Xv video. To avoid this problem, configure your video playback software for OpenGL output. See https://bugs.gentoo.org/show_bug.cgi?id=391193
Re: [gentoo-user] udev + /usr
On Fri, 2011-09-16 at 10:57 -0500, Dale wrote: Give it time. Something will need /home on the root partition next. Like someone else posted, we are headed towards windows land with this. I won't be surprised if /boot will have to be on / next too. Dale :-) :-) Funnily enough, Windows 7 implements a separate boot partition from the default system partition. The partition is not only a boot partition but a has rescue environment also. How the tables are turning ... go figure. Carlos -- Sent using GNU/Linux - Perpetuate Freedom.
Re: [gentoo-user] Strange problem while uploading
On Sun, 2010-10-31 at 11:14 +0100, Jacques Montier wrote: Hi all, I use the online french file storage Securibox (similar to Adrive or others) to backup some data. https://www.securibox.fr/ Everything worked before upgrading gentoo by emerge -auvDN world. Now, i can open my personal space, delete files, but i can't upload files anymore. Have you subsequently run: revdep-rebuild -v -- --ask to ensure any updated package dependencies are also rebuilt? Regards, Carlos
[gentoo-user] [HELP] Intermittent software RAID failures
Hello,
I've got a Dell Inspiron 1720 laptop with dual 2.5 hard drives setup
using software RAID1. I've had this computer for about a year and half
and all's been working well.
I've experienced intermittent software RAID errors like those found in
the softraid-fail.txt attachment.
Initially I suspected a kernel bug because it started around the same
time I'd upgraded the kernel (around the 2.6.30 upgrade) but subsequent
kernel upgrades haven't improved the situation.
I've run smartctl --all and bablocks on both disks, but nothing is
reported as faulty.
I don't understand what is causing RAID to report these faults and would
like some ideas as to how I can further diagnose the problem.
Thanks in advance,
Carlos
Feb 28 15:14:16 pheonix kernel: ata3.00: exception Emask 0x10 SAct 0x0 SErr
0x1 action 0xe frozen
Feb 28 15:14:16 pheonix kernel: ata3.00: irq_stat 0x0040, PHY RDY changed
Feb 28 15:14:16 pheonix kernel: ata3: SError: { PHYRdyChg }
Feb 28 15:14:16 pheonix kernel: ata3.00: cmd
ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Feb 28 15:14:16 pheonix kernel: res 40/00:0c:97:74:25/00:00:0c:00:00/40 Emask
0x10 (ATA bus error)
Feb 28 15:14:16 pheonix kernel: ata3.00: status: { DRDY }
Feb 28 15:14:16 pheonix kernel: ata3: hard resetting link
Feb 28 15:14:19 pheonix kernel: ata3: SATA link up 1.5 Gbps (SStatus 113
SControl 300)
Feb 28 15:14:19 pheonix kernel: ata3.00: configured for UDMA/133
Feb 28 15:14:19 pheonix kernel: ata3: EH complete
Feb 28 15:14:19 pheonix kernel: end_request: I/O error, dev sdb, sector
178062452
Feb 28 15:14:19 pheonix kernel: raid1: Disk failure on sdb1, disabling device.
Feb 28 15:14:19 pheonix kernel: raid1: Operation continuing on 1 devices.
Feb 28 15:14:19 pheonix kernel: md: recovery of RAID array md0
Feb 28 15:14:19 pheonix kernel: md: minimum _guaranteed_ speed: 1000
KB/sec/disk.
Feb 28 15:14:19 pheonix kernel: md: using maximum available idle IO bandwidth
(but not more than 20 KB/sec) for recovery.
Feb 28 15:14:19 pheonix kernel: md: using 128k window, over a total of
178024192 blocks.
Feb 28 15:14:19 pheonix kernel: md: resuming recovery of md0 from checkpoint.
Feb 28 15:14:19 pheonix kernel: md: md0: recovery done.
Feb 28 15:14:19 pheonix kernel: RAID1 conf printout:
Feb 28 15:14:19 pheonix kernel: --- wd:1 rd:2
Feb 28 15:14:19 pheonix kernel: disk 0, wo:0, o:1, dev:sda8
Feb 28 15:14:19 pheonix kernel: disk 1, wo:1, o:0, dev:sdb1
Feb 28 15:14:19 pheonix kernel: md: recovery of RAID array md0
Feb 28 15:14:19 pheonix kernel: md: minimum _guaranteed_ speed: 1000
KB/sec/disk.
Feb 28 15:14:19 pheonix kernel: md: using maximum available idle IO bandwidth
(but not more than 20 KB/sec) for recovery.
Feb 28 15:14:19 pheonix kernel: md: using 128k window, over a total of
178024192 blocks.
Feb 28 15:14:19 pheonix kernel: md: resuming recovery of md0 from checkpoint.
Feb 28 15:14:19 pheonix kernel: md: md0: recovery done.
Feb 28 15:14:20 pheonix kernel: RAID1 conf printout:
Feb 28 15:14:20 pheonix kernel: --- wd:1 rd:2
Feb 28 15:14:20 pheonix kernel: disk 0, wo:0, o:1, dev:sda8
Feb 28 15:14:20 pheonix kernel: disk 1, wo:1, o:0, dev:sdb1
Feb 28 15:14:20 pheonix kernel: RAID1 conf printout:
Feb 28 15:14:20 pheonix kernel: --- wd:1 rd:2
Feb 28 15:14:20 pheonix kernel: disk 0, wo:0, o:1, dev:sda8
Feb 28 15:14:20 pheonix kernel: disk 1, wo:1, o:0, dev:sdb1
Feb 28 15:14:20 pheonix kernel: RAID1 conf printout:
Feb 28 15:14:20 pheonix kernel: --- wd:1 rd:2
Feb 28 15:14:20 pheonix kernel: disk 0, wo:0, o:1, dev:sda8
Mar 12 19:38:06 pheonix kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr
0x1 action 0xe frozen
Mar 12 19:38:06 pheonix kernel: ata1.00: irq_stat 0x0040, PHY RDY changed
Mar 12 19:38:06 pheonix kernel: ata1: SError: { PHYRdyChg }
Mar 12 19:38:06 pheonix kernel: ata1.00: cmd
ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Mar 12 19:38:06 pheonix kernel: res 40/00:24:b6:fa:df/00:00:17:00:00/40 Emask
0x10 (ATA bus error)
Mar 12 19:38:06 pheonix kernel: ata1.00: status: { DRDY }
Mar 12 19:38:06 pheonix kernel: ata1: hard resetting link
Mar 12 19:38:09 pheonix kernel: ata1: SATA link up 1.5 Gbps (SStatus 113
SControl 300)
Mar 12 19:38:09 pheonix kernel: ata1.00: configured for UDMA/133
Mar 12 19:38:09 pheonix kernel: ata1: EH complete
Mar 12 19:38:09 pheonix kernel: end_request: I/O error, dev sda, sector
305244964
Mar 12 19:38:09 pheonix kernel: raid1: Disk failure on sda8, disabling device.
Mar 12 19:38:09 pheonix kernel: raid1: Operation continuing on 1 devices.
Mar 12 19:38:09 pheonix kernel: md: recovery of RAID array md0
Mar 12 19:38:09 pheonix kernel: md: minimum _guaranteed_ speed: 1000
KB/sec/disk.
Mar 12 19:38:09 pheonix kernel: md: using maximum available idle IO bandwidth
(but not more than 20 KB/sec) for recovery.
Mar 12 19:38:09 pheonix kernel: md: using 128k window, over a total of
178024192 blocks.
Mar 12 19:38:09 pheonix kernel: md: resuming recovery of md0 from checkpoint.
Mar 12 19:38:09 pheonix kernel: md: md0:
Re: [gentoo-user] 'if echo hello' in .bashrc
Alan McKinnon wrote: On Friday 08 May 2009 16:01:14 Mike Kazantsev wrote: On Fri, 8 May 2009 14:38:58 +0100 Stroller strol...@stellar.eclipse.co.uk wrote: To find the part to which I refer you'll need to scroll down about halfway through that page to Colorize grep; the author advises adding: if echo hello|grep --color=auto l /dev/null 21; then export GREP_OPTIONS='--color=auto' GREP_COLOR='1;32' fi to ~/.bashrc Why does he echo hello, please? Some greps (like BSD one) might not support '--color' option, so echo hello|grep --color=auto l will return error code, skipping if clause, and won't break grep operation by adding an unsupported option. except that STDERR is combined with STDOUT and sent to /dev/null so the script will never get it, the if is always true and the entire check is redundant. Better would be if echo hello|grep --color=auto l /dev/null ; then The redirection of output doesn't affect the return code of grep in the above case. Grep's return code is determined by matching 'l' against the output of echo hello. The desired effect of the above code is to evaluate if the --color option is supported by grep on the system. The STDERR and STDOUT redirection is an attempt to not pollute the systems screen when performing that test. To illustrate: 1. A system that supports --color $ if echo hello|grep --color=auto l /dev/null 21; then echo Grep returned : $?; else echo Grep returned : $?; fi Grep returned : 0 2. A system that doesn't support --color (simulated by supplying --unspported as an option to grep) $ if echo hello|grep --unsupported l /dev/null 21; then echo Grep returned : $?; else echo Grep returned : $?; fi -bash: echo: write error: Broken pipe [1] Grep returned : 2 3. Just to complete the examples, the result of grep not matching echo's output but still supporting the --color option. (achieved by search hello for the letter 'z') $ if echo hello|grep --color z /dev/null 21; then echo Grep returned : $?; else echo Grep returned : $?; fi Grep returned : 1 Regards, Carlos [1] The reason an error message is shown here is because it's bash that's reporting the broken pipe error. Grep's error message was redirected to /dev/null, which was: grep: unrecognized option '--unsupported' Usage: grep [OPTION]... PATTERN [FILE]... Try `grep --help' for more information. So even when the system doesn't support --color, that original code will pollute the screen with bash's error message.
