With apic enabled on this board, some normal amount of disk access
(including building a kernel) is successful. However, irqs are messed up.
The eepro100 module for the onboard 82559 nic loads, but prints this after
the revision history: PCI: No IRQ known for interrupt pin A of device
00:07.0. Pr
04:11:32AM -0400, Chris Siebenmann wrote:
> Envelope-to: [EMAIL PROTECTED]
> Delivery-date: Thu, 28 Jun 2001 04:11:14 -0400
> To: [EMAIL PROTECTED] ("J. Nick Koston")
> Subject: Re: Asus CUV4X-DLS
> X-Newsgroups: mail.linux.kernel
> In-Reply-To: [EMAIL PROTECTED]>
&g
28 Jun 2001 08:27:17 -0400
> From: John Cavan <[EMAIL PROTECTED]>
> X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.4.5-ac18 i686)
> X-Accept-Language: en
> To: "J. Nick Koston" <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Subject: Re: Asus CUV4X-DLS
>
> John
John Cavan wrote:
> I have an AIC7 based SCSI card in my machine as well, hooked up to a
> Jaz. I haven't actually used it in ages, but I'll test it to see of the
> problem is apparent on CUV4X-D board as well.
First, I copied 640 Mb file to the jaz disk, no problem. Then I ran the
same comma
"J. Nick Koston" wrote:
>
> Thanks for the tips, however it doesn't help :-(
It was worth a shot...
> > Also, try passing "noapic" to the kernel on boot if the problem still
> > persists. The downside is that all interrupts will be handled by a
> > single CPU. There is a definite problem with V
Thanks for the tips, however it doesn't help :-(
Anyways in case anyone is curious the i/o problem still happens
with an aic7xxx card put in and the onboard scsi disabled.
[snip]
> "J. Nick Koston" wrote:
> >
> > There seems to be a major problem with this board and 2.4.x kernels.
> > I consis
There seems to be a major problem with this board and 2.4.x kernels.
I consistantly get SCSI Input/Output errors on multiple drives that I
know are good when running a SMP kernel. These errors do no happen
with a UP kernel. This is happening on multiple systems and with
multiple know good scsi
> When it gets to the point of activating the second processor, kernel
> 2.4.3-ac13 starts spewing:
>
> probable hardware bug: clock timer configuration lost - probably a VIA686a
>motherboard.
> probable hardware bug: restoring chip configuration.
That is useful informtion. The kernel is seeing
All,
I unfortunately don't have the time this evening to produce actual kernel
messages, but I did want to throw out that I have an ASUS CUV4X-DLS board
too, with two PIII/1GHz processors in it, and I cannot get it to boot an
SMP kernel at all. In addition to the built-in devices, the foll
I have some info at "http://web.irridia.com/linux/"; from an LPr having
issues, including the dmidecode output and a mostly complete boot-time
dmesg dump from an LPr and LP1000r. The LPr was running 2.4.2-pre4 and
the LP1000r is running 2.4.5-pre1, both without "noapic". Please let me
know i
> But the distributions use _the_ kernel. Even if -ac is fixed, it's not
> really something I would be willing to put in production. Until I found
Actually by unit count Linus is currently losing to me on 2.4 shipping.
Thats one reason I really want to get the stuff I have back into the main
I'm losing the timer interrupt, but it's not driver-specific -- only the
motherboard is required to reproduce for me; different SCSI, RAID, and
ether drivers have been swapped out. Nothing with "HP" on it seems to
work, and it wouldn't surprise me in the least to find out that HP's
stuff is b
The failure mode I'm seeing is that the timer interrupt disappears.
Hard to schedule processes at that point. I'm not seeing the IRQ issues
personally.
HP's LP1000r machine uses ServerWorks, but still shows the problem. I
only have access to HP SMP hardware currently, but they all have the
> Got good reviews at the time, and I thought it was more general than
> ne2k. I don't remember it going forward to Linus (but I've not looked).
ne2k is the big one it shows up on. Its on my for Linus list in the next few
pushes of stuff.
-
To unsubscribe from this list: send the line "unsubscri
On Thu, 3 May 2001, Alan Cox wrote on APIC problems in 2.4:
> There are five cases I am seeing
> 1.Serverworks total APIC hose ups.
> Fix: remove OSB4 or use -ac tree
> 2.440BX and similar boards losing interrupts on some drivers
> Fix: use -ac
> 3.APIC errors notably check
> I just wanted to throw in my two cents and say that there appear to be
> widespread issues with the APIC code in 2.4.x. I'm tempted to stick my
> neck out and say that it might be best to disable SMP IOAPIC by default
> until APIC can be massaged, at least for a wider variety of hardware.
I
ing a little difficulty
> trying to solve. I have a system with a ASUS CUV4X-DLS system
> board, Bios 1004, 1GB of memory. dual P3 933MHz processors,
> a G450 Matrox card in the AGP slot, and a SBLive! sound
> card in PCI Slot 4.
>
> I have provided the output from dmesg below and the
> trying to solve. I have a system with a ASUS CUV4X-DLS system
>
> The problem is that the system will boot everytime if and only
> if I use "noapic". If I do not use "noapic", the system will
Known problem with the CUV4X boards.
> What is the impact o
I am encountering a problem I am having a little difficulty
trying to solve. I have a system with a ASUS CUV4X-DLS system
board, Bios 1004, 1GB of memory. dual P3 933MHz processors,
a G450 Matrox card in the AGP slot, and a SBLive! sound
card in PCI Slot 4.
I have provided the output from dmesg
19 matches
Mail list logo
