Re: Asus CUV4X-D, 2.4.3 crashes at boot
From: "Allen Campbell" <[EMAIL PROTECTED]> > Patience is likely to be effective. The chipset isn't exactly rare > being on SMP boards from Gigabyte, MSI, Tyan and Asus, and likely > others. I'm betting it will be fixed soon enough. UP and 2.2.x > kernels worked fine here if you're really desperate. OTOH, the > board is stable once you get past the boot problems... What sort > of production system needs frequent unattended boots? > I was planning to install the box as a colocated production webserver in 1-2 weeks' time. I don't want to colocate a box that I cannot reboot, so I'll just have to sit on it until it's fixed I guess. Regards Simon Garner - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Asus CUR-DLS SMP motherboard
Hello, I'm wondering if anyone has used this motherboard and can confirm if it works under 2.4.3 or not. Having been burned by the Via-based CUV4X-D not working under Linux, I'm keen to find out if this ServerWorks-based board works or not, before throwing away my money. Asus CUR-DLS, ATX, ServerWorks ServerSet III LE, FC-PGA,LAN/SCSI/VGA Specifications: CPU: FCPGA PIII 500-866+MHz/SMP (Symmetical Multi-Processor) dual processors, Socket 370, Chipset: ServerWorks (RCC) ServerSet III LE, Slots: 2 x PCI-64bit/66MHz, 5 x PCI-32bit/33MHz , 1 x ASMS socket (reserved for IPMI/EMP), 4x DIMM. Formfactor: ATX, 66/100/133MHz FSB, DMA-33, PC133 memory support (supports Registered DIMM only, ECC based 64MB to 1GB memory capacity). Built in Intel 82559 LAN, LSI dual channel Ultra160 SCSI controller, ATI Rage-XL graphics with 4MB PC100 SDRAM Any anecdotes? Alternatively, is anyone working on a patch for the Via 694XDP problems? Thanks in advance, Simon Garner - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec 2940 and Linux 2.2.19
From: "Subba Rao" <[EMAIL PROTECTED]> > > Hi, > > The kernel configuration menu items have been changing quite a bit. So, I > apologize for asking a trivial question in this forum. > > I am trying to configure and install linux kernel 2.2.19. This system has > a Adaptec 2940 SCSI adapter. I have enabled SCSI support kernel configuration > menu and also have selected all the Adaptec low-level drivers. They include > (actually what is offered), AHA152X/2825, AHA1542 and AHA1740. When the kernel > is booting up it still does not find the AHA2940 adapter. > > What (other) options should I configure to make Linux 2.2.19 find the adapter? > > Thank you in advance for any help. > -- > > Subba Rao > [EMAIL PROTECTED] > http://members.home.net/subba9/ > You want the Adaptec AIC7xxx driver. Should be listed right under those other three. Cheers Simon Garner - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Asus CUV4X-D, 2.4.3 crashes at boot
Hi, I've compiled kernel 2.4.3 on the following RH7 system, and I'm now getting random crashes at boot, during IO-APIC initialisation. Random meaning that sometimes it boots fine, other times it doesn't, and it hangs in different places (but always around IO-APIC stuff). It almost always hangs after a cold boot - if I do a Ctrl+Alt+Del then it will usually boot up OK. System: Asus CUV4X-D motherboard, Dual P3 800EB. The last thing I see on the screen when it hangs is, for example: CPU1: Intel Pentium III (Coppermine) stepping 06 CPU has booted. Before bogomips. Total of 2 processors activated (3207.98 BogoMIPS). Before bogocount - setting activated=1. Boot done. ENABLING IO-APIC IRQs ...changing IO-APIC physical APIC ID to 2 ... ok. Synchronizing Arb IDs. ...TIMER: vector=49 pin1=2 pin2=0 Sometimes it gets a little further, but it's always somewhere near the IO-APIC stuff. When it does boot, I get: CPU1: Intel Pentium III (Coppermine) stepping 06 CPU has booted. Before bogomips. Total of 2 processors activated (3207.98 BogoMIPS). Before bogocount - setting activated=1. Boot done. ENABLING IO-APIC IRQs ...changing IO-APIC physical APIC ID to 2 ... ok. Synchronizing Arb IDs. init IO_APIC IRQs IO-APIC (apicid-pin) 2-5, 2-10, 2-11, 2-13, 2-19, 2-20, 2-21, 2-22, 2-23 not connected. ..TIMER: vector=49 pin1=2 pin2=0 number of MP IRQ sources: 17. number of IO-APIC #2 registers: 24. testing the IO APIC... IO APIC #2.. register #00: 0200 ...: physical APIC id: 02 register #01: 00178011 ... : max redirection entries: 0017 ... : IO APIC version: 0011 WARNING: unexpected IO-APIC, please mail to [EMAIL PROTECTED] register #02: ... : arbitration: 00 Full dmesg output: http://www.expio.co.nz/~sgarner/orion/smp/dmesg.txt My kernel .config: http://www.expio.co.nz/~sgarner/orion/smp/config.txt Output from lspci -xx: http://www.expio.co.nz/~sgarner/orion/smp/lspcixx.txt Any ideas? Thanks in advance, Simon Garner - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Asus CUV4X-D, 2.4.3 crashes at boot
From: "Allen Campbell" <[EMAIL PROTECTED]> > I've seen the exact same behavior with my CUV4X-D (2x1GHz) under > 2.4.2 (debian woody). In addition, the kernel would sometimes hang > around NMI watchdog enable. At least, I think it's trying to > `enable'. The hang would occur around 50% of boot attempts. Once > booted, everything was stable. A non-SMP 2.4.2 kernel (no IO-APIC > either, sorry, didn't test that) always booted without hangs. Yep, sounds like the same problem. > > Strangely, (happily for me,) the boot hangs stopped with 2.4.3. > I've booted maybe 10 times (hot and cold) since I built 2.4.3 and > I've had no hangs. When I get back to the box, I'll try booting > a few dozen more times and see if I can confirm your observation. > Please do test it. I think you'll find the problem is still very much present. Cheers Simon Garner - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Asus CUV4X-D, 2.4.3 crashes at boot
From: "Mikael Pettersson" <[EMAIL PROTECTED]> > Boot with "nmi_watchdog=0" as a boot parameter. Does it work now? > > Some people have reported before here that the IO-APIC driven NMI > watchdog itself can cause boot-time hangs. > > /Mikael Thanks, but I do not have watchdog support compiled into the kernel. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Asus CUV4X-D, 2.4.3 crashes at boot
From: "Keith Owens" <[EMAIL PROTECTED]> > >Doesn't matter. The NMI-watchdog tries to detect SMP-lockups, and is > >always present. Unless you specifically disable it on boot. > > Not any more. In 2.4.3-ac* the default is no watchdog and it must be > specifically enabled at boot. > nmi_watchdog 0 didn't help - the above would explain why. Any more ideas? My expensive server is basically useless because of this. :( - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Asus CUV4X-D, 2.4.3 crashes at boot
From: "Jeff Garzik" <[EMAIL PROTECTED]> > (private reply, because I have lost discussion context) > > Have you tried booting with 'noapic'? > > Thanks Jeff, this seems to fix the problem, and also fixes my problem with the aic7xxx scsi driver ABORTing multiple times at startup (which I presumed was unrelated). However, the machine now crashes at "Configuring Kernel Parameters" during rc initialisation: Welcome to Red Hat Linux Press 'I' for interactive startup Mounting /proc filesystem...[ OK ] Configuring Kernel Parameters... This is if I type "linux noapic" at the Lilo boot prompt. Also, what do I lose by running with noapic? Thanks Simon Garner - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Asus CUV4X-D, 2.4.3 crashes at boot
Hi all, > > However, the machine now crashes at "Configuring Kernel Parameters" during > rc initialisation: > > > Welcome to Red Hat Linux > Press 'I' for interactive startup > > Mounting /proc filesystem...[ OK ] > Configuring Kernel Parameters... > > > This is if I type "linux noapic" at the Lilo boot prompt. > > Also, what do I lose by running with noapic? > > Just discovered the above is not quite correct - it actually says [ OK ] after Configuring Kernel Parameters, and crashes on the next line. Reading through /etc/rc.d/rc.sysinit, the next line is where it sets the system clock. If I comment out the line: /sbin/hwclock $CLOCKFLAGS Then the system will boot OK with 'noapic'. So presumably the system RTC is not accessed in a SMP-compatible way without APIC. Anyway, I'm not too happy about having to run without APIC - seems more of a workaround than a fix. I'm happy to test patches etc if anyone has any ideas - this problem I presume affects all motherboards using the VIA 694XDP chipset. Thanks in advance, Simon Garner - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Asus CUV4X-D, 2.4.3 crashes at boot
From: "Alan Cox" <[EMAIL PROTECTED]> > > I've seen the exact same behavior with my CUV4X-D (2x1GHz) under > > 2.4.2 (debian woody). In addition, the kernel would sometimes hang > > around NMI watchdog enable. At least, I think it's trying to > > Known problem. Thats one reason why -ac trees had nmi watchdog turned off. It still crashes with nmi_watchdog turned off. Running with noapic fixes it but then the system crashes if you access the RTC with hwclock (and probably creates a hundred other problems...). How can I get this chipset/motherboard supported properly under Linux? I'm happy to test patches etc. on the box. *pleading* Cheers Simon Garner - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
