Discuss June 2005

discuss@lists.centos.org

197 participants
362 discussions

Screaming Interrupt error and hang.
by Lamar Owen 27 Jun '05

27 Jun '05

One system I have is configured thusly: AMD Duron 1200 (I have frequency restrictions in this application, and must stay below 1.3GHz or must be above 2.0GHz, and the 1200 fits nicely in our interference plan; besides, I was given the chip, and it's fast enough for the application). Soyo DRAGON KT400 motherboard, 512MB DDR RAM (DDR266). Silicon Image SATA interface card. Machine boots CentOSPlus 4.1 kernel (2.6.9-11.106.unsupported) perfectly fine UNTIL I plug in a Maxtor SATA drive into the drive slide I have in the machine. Drive and slide work perfectly fine at home with a Gigabyte KT600-based motherboard with VIA SATA interface. After plugging in the SATA drive and rebooting (since libata doesn't yet do hotplug), I get a hang after seeing an 'irq 10: nobody cared! (screaming interrupt?)' error. I have done the kernel command line 'pci=biosirq' and 'acpi=off' suggestions, I have disabled USB, disabled everything that the BIOS will allow. Nothing at this point is sharing IRQ 10 with the Sil 3112 controller. I think it is the latest BIOS version for that motherboard. No matter what I do, it issues the screaming interrupt error until I remove the SATA drive. The DRAGON motherboard has HPT372 software RAID on board (I'm using it as just another two channel ATA host adapter) as well as audio, network, etc). LAN is enabled; both COMs and the LPT are disabled, USB is disabled, audio is disabled. And the motherboard works and has worked perfectly fine for months without the SATA drive in the slide (and with all the peripherals enabled!). Red Hat Bugzilla unresponsive; maybe someone here has seen the problem and knows of some other thing I can tweak. Odd that it works fine with the card in with no drive, but plugging the drive in kills it. With the drive not installed, the card still uses the IRQ, still loads its BIOS, and still shows up in dmesg (this produced with a default boot, non-quiet): [snip] ACPI: (supports S0 S1 S4 S5) ACPI wakeup devices: SLPB PCI0 USB0 USB1 USB2 USB6 USB7 USB8 USB9 LAN0 Freeing unused kernel memory: 148k freed SCSI subsystem initialized libata version 1.10 loaded. sata_sil version 0.8 ACPI: PCI interrupt 0000:00:0b.0[A] -> GSI 10 (level, low) -> IRQ 10 ata1: SATA max UDMA/100 cmd 0xE0832080 ctl 0xE083208A bmdma 0xE0832000 irq 10 ata2: SATA max UDMA/100 cmd 0xE08320C0 ctl 0xE08320CA bmdma 0xE0832008 irq 10 ata1: no device found (phy stat 00000000) scsi0 : sata_sil ata2: no device found (phy stat 00000000) scsi1 : sata_sil device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm(a)uk.sistina.com [snip] It's in the area after the sata_sil driver gets loaded that, when the drive is plugged in, the screaming interrupt occurs, and the system hangs. It DOES detect the drive, though. Oh, and let me head off the obvious thing at the pass: I'm not using any pseudo-RAID features on either the HPT372 or the Sil 3112. Both chips work fine; the Sil 3112 card was in a Windows box previously and has worked with this drive. The HPT372 is working FINE right now as two independent ATA channels. Just looking for some ideas of things to look at (other than 'don't use a FRAID card' 'try another motherboard' and the like; those pseudoanswers will be ignored; please only answer if you have an idea, don't waste bandwidth telling me you don't know, but that SOYO motherboards are junk, etc. Too much of that around here, unfortunately, and it is annoying). -- Lamar Owen Director of Information Technology Pisgah Astronomical Research Institute 1 PARI Drive Rosman, NC 28772 (828)862-5554 www.pari.edu

1 0

SW-RAID on 2 SATA controllers
by Dag Wieers 27 Jun '05

27 Jun '05

Hi, Would it be advisable to use SW-RAID using 2 different SATA controllers. My system happens to have both a VIA VT8237 and SIL3114 SATA controller, and I thought for both performance reason and redundancy using both for a 2 disk RAID1 array would be best. But it's possible that SW-RAID does not like or cannot overcome problems with such a setup or that one of these drivers is known to have issues. Any insight is welcome :) -- dag wieers, dag(a)wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]

5 6

SW-RAID on 2 SATA controllers
by Dag Wieers 27 Jun '05

27 Jun '05

3 2

One Touch Backups for Centos?
by Scott Sharkey 27 Jun '05

27 Jun '05

Hi All, Does anyone have any experience with the external "one touch" backup solutions for CentOS? I'm not expecting the software to work, that would be a miracle. But does anyone know if the hardware is compatible? Recommendations welcome. -Scott

2 2

RE: [CentOS] sendmail and spamassassin
by Marc Powell 27 Jun '05

27 Jun '05

> -----Original Message----- > From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On > Behalf Of James B. Byrne > Sent: Monday, June 27, 2005 11:56 AM > To: centos(a)centos.org > Subject: [CentOS] sendmail and spamassassin > > I have a problem getting spamd and sendmail (both stock CentOS4 rpms) > to work together on a couple of smtp relay machines. This is clearly > a configuration issue and no doubt revolves around my lack of > comprehension of how this is to work. > > Basically, the setup consists of two frontend public smtp transports > that redirect all email through a firewall to an internal imap server > for final delivery. The firewall and sendmail access map prohibit > connections to the imap server except for the local MX gateway. The > external MX gateway is a fallback mx server that routes everything it > queues through the primary gateway. > > So: > > MX 2 routes to MX 1 that routes to IMAP > > MX 2 and MX 1 are running spamd. > > the sendmail.m4 file has the following at its very end: > > dnl # > dnl # MAILERs are always last after all FEATURES are defined > MAILER(smtp)dnl > MAILER(procmail)dnl > > > The contents of /etc/procmailrc are: > > :0fw > | /usr/bin/spamassassin > > > Spamd is running on both. > > There is a local configuration rule set in > /etc/mail/spamassassin/local.cf > > Passing a test message through spamc on MX 1 or MX 2 does not seem to > pick up this rule even for messages constructed to trigger it. > Passing spam messages through spamc -R identifies messages that have > passed through the relays without any spam tags as being high scoring > spam. > > What am I doing wrong? Regardless of your test, your biggest problem is that procmail isn't, and won't, be run on your MX machines because they are not doing local delivery to the mailboxes as I understand your setup. Procmail only comes into play when the messages are being put into the user's mailboxes. You'll want to look at something like MailScanner if you want to do all your spam/virus filtering on your MX servers since that works directly with the queue files and re-injects them back into an outgoing queue for final delivery. There are some drawbacks to that, primarily being that you can't have per-user variation, but we did it quite successfully for several years for ~37,000 users with the same type of architecture you are trying to implement. We have since moved to using MailScanner on our MXs for virus checks, attachment stripping and general mal-ware removal only and our local delivery machines run spamd as a postfix filter so that we can have per-user spam settings. There are quite a few how-tos out there to help you, starting with the spamassassin wiki. -- Marc

1 0

RE: [CentOS] Server Crashing
by Ash Christopher 27 Jun '05

27 Jun '05

You could try the following instead of memtest86, since it has numerous limitations. http://people.redhat.com/dledford/memtest.html Memtest86 didn't report any problems on my server, but this script was able to find them. -----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Greg Knaddison Sent: Monday, June 27, 2005 10:01 AM To: CentOS mailing list Subject: Re: [CentOS] Server Crashing On 6/27/05, Jay <jaybeattie(a)gmail.com> wrote: > On reboot all is fine. > It's running apache and DNS no SSH access. It passes memory test Memtest86. > How long did you run Memtest86? My understanding is that you can run it and have it work for a couple of hours, but then have it fail after two or three days running. Greg _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

2 1

Server Crashing
by Jay 27 Jun '05

27 Jun '05

Greetings. Every couple of day's I have a web server running CentOS 4.1 with all the patches as of Saturday that is crashing every couple of day's. Usualy between 4-6 am. The Console shows: Double Fault gdt at xxxx memory Double Falut tss at xxxx memory On reboot all is fine. It's running apache and DNS no SSH access. It passes memory test Memtest86. I can provide more information if you direct me on what to send. Thanks -Jay

4 3

mythtv on centos4
by Tony 27 Jun '05

27 Jun '05

Has anyone had any success or failures with installing mythtv onto centos4? Even better, has anyone any prebuilt rpms to do this? Looks to me like centos+mythtv is quite an interesting prospect in the always-on single home server environment. -- Cheers, Tony

4 3

Re: CentOS 4.0 -> 4.1 update failing
by Bryan J. Smith <b.j.smith＠ieee.org> 27 Jun '05

27 Jun '05

From: Johnny Hughes <mailing-lists(a)hughesjr.com> > That is by design ... the i686 glibc will not work with the c3 ... the > i686 kernel will. Interesting. Hmmm. > You need to use the i386 glibc. As written, the latest RH glibc SRPM > will not build for --target i486 or --target i586 ... But I've seen several packages where building for --target i386 still results in an --march=i486. In fact, that's probably why they clearly still say ".i386.rpm" despite requiring i486 ISA. > I am close to making it build properly for --target i586, but since > the .i386 glibc works well on i586 and it should build with that > target unmodified in the future, that is the way we will proceed. -- Bryan J. Smith mailto:b.j.smith@ieee.org

2 1

RE: [CentOS] Multiple system updates
by Bryan J. Smith 27 Jun '05

27 Jun '05

From: Peter Arremann > This is a question for you guys out there that have a bunch of similar > configured systems out there... How do you handle your updates? I do not mean > the technical level, but from the logistics. No updates? Just run yum by cron > and grab the latest of the web and trust the developers that it works? > Deploy only certain packages automatically (i.e. omit kernel updates)? > run your own yum/apt/up2date/whatever repos? Unless there are only 2-3 systems, the last option. I _always_ maintain an internal repository that goes through its own "enterprise release." One test system always gets the task of regression testing a new set of updates before it hits production. High security rollouts happen ASAP, other rollouts are far less pressured. For only 2-3 systems, I still have a test system, but it's cheap and its hardware does not match production. So I test on one production as long as I can before upgrading all. If I had a huge client base, I'd just maintain my own repository on the Internet with my releases they feed from. So far, my clients have always had their own resources to maintain the repository and procedures after I setup it up and left.

1 0

← Newer
1
...
5
6
7
8
9
10
11
...
37
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss June 2005