On Mon, 9 Apr 2001, Jim Studt wrote:
> G*rard Roudier insightfully opined..
> > Looks like an IRQ problem to me.
> > I mean the kernel wants to change IRQ routing and just do the wrong job.
>
> Give the man a prize!
>
> After failing to work with 2.4.0, 2.4.1, 2.4.3, and 2.4.3-ac3 I
>
For me 2.4.3 + aic7xxx-6.1.10 work fine. I just changed the default
bus settle delay from 15000ms to 5000m, and enabled APIC:
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y
The machine boots, devices are properly detected (unlike 6.1.8),
CDRW reads and burns fine, CDROM
For me 2.4.3 + aic7xxx-6.1.10 work fine. I just changed the default
bus settle delay from 15000ms to 5000m, and enabled APIC:
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y
The machine boots, devices are properly detected (unlike 6.1.8),
CDRW reads and burns fine, CDROM
On Mon, 9 Apr 2001, Jim Studt wrote:
G*rard Roudier insightfully opined..
Looks like an IRQ problem to me.
I mean the kernel wants to change IRQ routing and just do the wrong job.
Give the man a prize!
After failing to work with 2.4.0, 2.4.1, 2.4.3, and 2.4.3-ac3 I
enabled
On 04.10 Vivek Dasmohapatra wrote:
> On Mon, 9 Apr 2001, Alan Cox wrote:
>
> > > A typical startup with 6.1.9 proceeds like this... (6.1.10 hangs silently
> > > after emitting the scsi0 and scsi1 adapter summaries, maybe it is
> > > going through the same gyrations silently.)
> >
> > Try
On Mon, 9 Apr 2001, Alan Cox wrote:
> > A typical startup with 6.1.9 proceeds like this... (6.1.10 hangs silently
> > after emitting the scsi0 and scsi1 adapter summaries, maybe it is
> > going through the same gyrations silently.)
>
> Try saying N to the AIC7xxx driver and Y to AIC7XXX_OLD
G*rard Roudier insightfully opined..
> Looks like an IRQ problem to me.
> I mean the kernel wants to change IRQ routing and just do the wrong job.
Give the man a prize!
After failing to work with 2.4.0, 2.4.1, 2.4.3, and 2.4.3-ac3 I
enabled X86_UP_IOAPIC to stir up the interrupt code and it
Looks like an IRQ problem to me.
I mean the kernel wants to change IRQ routing and just do the wrong job.
Ingo reported me a similar problem a couple of week ago that made failed
the sym53c8xx driver. Looks very similar to this one with the kernel PCI
code wanting to assign IRQ 11 to almost
I can add a "me too" to this thread.
I began playing with 2.4 releases (again) at 2.4.2-ac23 and i can't
manage to boot it properly, even the 2.4.3-ac2. I have an adaptec 2940U
(aic7860 as driver tells me) and both drivers, old and new, dont work
properly. Either i get
I confirm similar problems (see my message from yesterday).
AIC7XXX_OLD also failed for me. I have tried aic 6.1.8 as well
as 6.1.10.
Both 2.4.0 under redhat 7.0 and 2.4.1 as shipped by redhat
wolverine work. As have all earlier versions going back to 2.3.xx
and 2.2.x
On Mon, Apr 09, 2001
> > A typical startup with 6.1.9 proceeds like this... (6.1.10 hangs silently
> > after emitting the scsi0 and scsi1 adapter summaries, maybe it is
> > going through the same gyrations silently.)
> >
>
Alan Cox directs...
> Try saying N to the AIC7xxx driver and Y to AIC7XXX_OLD and see if
> A typical startup with 6.1.9 proceeds like this... (6.1.10 hangs silently
> after emitting the scsi0 and scsi1 adapter summaries, maybe it is
> going through the same gyrations silently.)
>
Try saying N to the AIC7xxx driver and Y to AIC7XXX_OLD and see if that works.
This is important both
I've got a trio of identical PIII machines all failing with aic7xxx under
2.4.3. I've tried both aic7xxx 6.1.9 and 6.1.10 in addition to the one
in 2.4.3 (6.1.5?). These machines work fine under 2.2.18pre21.
I'm looking for any ideas or suggestions on how to fix this.
(Ok, honestly I'm hoping
I've got a trio of identical PIII machines all failing with aic7xxx under
2.4.3. I've tried both aic7xxx 6.1.9 and 6.1.10 in addition to the one
in 2.4.3 (6.1.5?). These machines work fine under 2.2.18pre21.
I'm looking for any ideas or suggestions on how to fix this.
(Ok, honestly I'm hoping
A typical startup with 6.1.9 proceeds like this... (6.1.10 hangs silently
after emitting the scsi0 and scsi1 adapter summaries, maybe it is
going through the same gyrations silently.)
Try saying N to the AIC7xxx driver and Y to AIC7XXX_OLD and see if that works.
This is important both
A typical startup with 6.1.9 proceeds like this... (6.1.10 hangs silently
after emitting the scsi0 and scsi1 adapter summaries, maybe it is
going through the same gyrations silently.)
Alan Cox directs...
Try saying N to the AIC7xxx driver and Y to AIC7XXX_OLD and see if that works.
I confirm similar problems (see my message from yesterday).
AIC7XXX_OLD also failed for me. I have tried aic 6.1.8 as well
as 6.1.10.
Both 2.4.0 under redhat 7.0 and 2.4.1 as shipped by redhat
wolverine work. As have all earlier versions going back to 2.3.xx
and 2.2.x
On Mon, Apr 09, 2001
I can add a "me too" to this thread.
I began playing with 2.4 releases (again) at 2.4.2-ac23 and i can't
manage to boot it properly, even the 2.4.3-ac2. I have an adaptec 2940U
(aic7860 as driver tells me) and both drivers, old and new, dont work
properly. Either i get
Looks like an IRQ problem to me.
I mean the kernel wants to change IRQ routing and just do the wrong job.
Ingo reported me a similar problem a couple of week ago that made failed
the sym53c8xx driver. Looks very similar to this one with the kernel PCI
code wanting to assign IRQ 11 to almost
G*rard Roudier insightfully opined..
Looks like an IRQ problem to me.
I mean the kernel wants to change IRQ routing and just do the wrong job.
Give the man a prize!
After failing to work with 2.4.0, 2.4.1, 2.4.3, and 2.4.3-ac3 I
enabled X86_UP_IOAPIC to stir up the interrupt code and it
On Mon, 9 Apr 2001, Alan Cox wrote:
A typical startup with 6.1.9 proceeds like this... (6.1.10 hangs silently
after emitting the scsi0 and scsi1 adapter summaries, maybe it is
going through the same gyrations silently.)
Try saying N to the AIC7xxx driver and Y to AIC7XXX_OLD and see
On 04.10 Vivek Dasmohapatra wrote:
On Mon, 9 Apr 2001, Alan Cox wrote:
A typical startup with 6.1.9 proceeds like this... (6.1.10 hangs silently
after emitting the scsi0 and scsi1 adapter summaries, maybe it is
going through the same gyrations silently.)
Try saying N to the
22 matches
Mail list logo
