[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
ok, have kernel, can test.
- Subject: ok, have kernel, can test.
- From: bsdalpha at fadesa.es (José M. Fandiño)
- Date: Wed Sep 1 04:56:56 2004
John Baldwin wrote:
> On Tuesday 31 August 2004 01:35 pm, Wilko Bulte wrote:
> > On Tue, Aug 31, 2004 at 06:32:03PM +0200, Poul-Henning Kamp wrote..
> > > Ok, my 1000 is now able to compile a -current kernel and test-boot it
> > > while running the 5.0-RC1 kernel.good I saved.
> > >
> > > First hurdle is confirmed: hw.eisa_slots must be set to something,
> > > 5 works fine.
> > >
> > > I'm compiling a kernel without fxp now to see if that is the cause of
> > > the PCI problem.
> > It is interesting to note the other thread on -alpha about a Miata
> > doing:
> > isp0: [GIANT-LOCKED]
> > xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x8100-0x817f mem
> > 0x81031000-0x8103107f irq 12 at device 8.0 on pci1
> > miibus1: <MII bus> on xl0
> > xlphy0: <3c905C 10/100 internal PHY> on miibus1
> > xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > xl0: Ethernet address: 00:01:02:1a:20:1c
> > xl0: interrupting at CIA irq 12
> > xl0: [GIANT-LOCKED]
> > <hang>
> > Miata -> completely different core chipset. And this is a different NIC as
> > well.
> Sounds like a possible interrupt storm to me, but that stuff hasn't changed
> recently on Alpha.
As a miata-bug victim I have to say it was working with 5.2.1-RELEASE
even with a different NIC. Whether or not it's caused by an interrupt
storm BETA2 seems trigger the bug. I will remain using 5.2.1-RELEASE
but I was curious about the possible cause.
see my posts for dmesg:
-----BEGIN GEEK CODE BLOCK-----
GCS/IT d- s+:+() a- C+++ UBL+++$ P+ L+++ E--- W++ N+ o++ K- w---
O+ M+ V- PS+ PE+ Y++ PGP+>+++ t+ 5 X+$ R- tv-- b+++ DI D++>+++
G++ e- h+(++) !r !z
------END GEEK CODE BLOCK------