Re: PCI brokenness

2002-10-03 Thread Mark Murray
This works, thanks! :-) :-) Domo Arrigato! M > I'm not sure, but my thought was something like following patches. > > Thanks > > Index: dev/acpica/acpi.c > === > RCS file: /home/ncvs/src/sys/dev/acpica/acpi.c,v > retrieving revis

Re: PCI brokenness

2002-10-03 Thread Vladimir B.
÷ Wed, 02.10.2002, × 11:31, Mark Murray ÎÁÐÉÓÁÌ: > > I noticed both of yours and the other "me too" reply indicated ACPI was in > > use. Is the behavior different when acpi is disabled? > > Yeah. Booting fails completely. Hard hang after probing the parallel port. Just notice same problem on 4

Re: PCI brokenness

2002-10-03 Thread John Baldwin
On 03-Oct-2002 Mitsuru IWASAKI wrote: >> ># I could be wrong, please correct me :) >> >I think that Libretto 110CT doesn't have PCI-ISA bridge , so no isab, >> >no isa, no isahint (requires isa) w/ acpi enabled. >> >> Hmmm, \_SB.PCI0.EIO has no _ADR, _HID instead. >> But I think ISA or LPC contr

Re: PCI brokenness

2002-10-03 Thread Mitsuru IWASAKI
> ># I could be wrong, please correct me :) > >I think that Libretto 110CT doesn't have PCI-ISA bridge , so no isab, > >no isa, no isahint (requires isa) w/ acpi enabled. > > Hmmm, \_SB.PCI0.EIO has no _ADR, _HID instead. > But I think ISA or LPC controller exists in this system. Adding some dev

Re: PCI brokenness

2002-10-02 Thread Mitsuru IWASAKI
> > Here is my hints file (which has not changed in at least 6 months) > > Ok, so you only have ata0 and no ata1. So that means the ACPI ata > attachment almost worked. Humm, try doing a hack to change ATA_IOADDR_RID > in ata-all.h from 0 to 1 along with the previous patch to add an acpi > atta

Re: PCI brokenness

2002-10-02 Thread Michael McGoldrick
After a cvsup and buildworld/kernel, everything seems to be working again. Thanks! On Wed, Oct 02, 2002 at 08:41:10AM +0900, Mitsuru IWASAKI wrote: > Hi, > > > On 01-Oct-2002 Michael McGoldrick wrote: > > > On Tue, Oct 01, 2002 at 12:48:47PM -0400, John Baldwin wrote: > > >> > > >> On 01-Oct-2

Re: PCI brokenness

2002-10-02 Thread John Baldwin
On 02-Oct-2002 Mark Murray wrote: >> > Ok, so you only have ata0 and no ata1. So that means the ACPI ata >> > attachment almost worked. Humm, try doing a hack to change ATA_IOADDR_RID >> > in ata-all.h from 0 to 1 along with the previous patch to add an acpi >> > attachment for ata and see if t

Re: PCI brokenness

2002-10-02 Thread Mark Murray
> > Ok, so you only have ata0 and no ata1. So that means the ACPI ata > > attachment almost worked. Humm, try doing a hack to change ATA_IOADDR_RID > > in ata-all.h from 0 to 1 along with the previous patch to add an acpi > > attachment for ata and see if that works. I still have no idea why >

Re: PCI brokenness

2002-10-02 Thread Mark Murray
> >> So it doesn't boot at all, that's different from "hard-hang during reboot". > >> :) After ppc your device probe is over. You could be getting an > >> interrupt storm. Can you break into ddb when this happens? > > > > Roger the diference. :-) > > > > No. I cannot break into DDB. The keyb

Re: PCI brokenness

2002-10-02 Thread John Baldwin
On 02-Oct-2002 Mark Murray wrote: >> > "Hard hang" means that the probe messages stop around the parallel >> > device, and nothing else happens. The PCCARD ethernet remains dead. >> > the disk is silent and no amount of keyboard activity does anything >> > at all. Serial console dead. Reset neede

Re: PCI brokenness

2002-10-02 Thread Mark Murray
> > "Hard hang" means that the probe messages stop around the parallel > > device, and nothing else happens. The PCCARD ethernet remains dead. > > the disk is silent and no amount of keyboard activity does anything > > at all. Serial console dead. Reset needed to reboot. > > So it doesn't boot at

Re: PCI brokenness

2002-10-02 Thread John Baldwin
On 02-Oct-2002 Mark Murray wrote: >> > Iwasaki-San's patch made no difference that I could see. Disabling ACPI >> > causes my system to hard-hang during reboot. I might be able to fix that >> > by futzing with device.hints, but that took me a whole weekend and a >> > reinstall last time I tried.

Re: PCI brokenness

2002-10-02 Thread Mark Murray
> > Iwasaki-San's patch made no difference that I could see. Disabling ACPI > > causes my system to hard-hang during reboot. I might be able to fix that > > by futzing with device.hints, but that took me a whole weekend and a > > reinstall last time I tried. Device.hints is a dangerous thing to pl

Re: PCI brokenness

2002-10-02 Thread John Baldwin
On 02-Oct-2002 Mark Murray wrote: >> > I tried this patch, and it made some progress (dmesg included). The >> > ATA system still seems badly broken, there is a spurious mention of >> > some kerneldump. I also have no console. >> >> Hmm, ata0 may be getting the wrong resources. Hmm. Try iwasaki

Re: PCI brokenness

2002-10-02 Thread Mitsuru IWASAKI
> > Hmm, ata0 may be getting the wrong resources. Hmm. Try iwasaki-san's > > patch to acpi_pcib_* instead and see if it that helps. Either that or > > turn off ACPI for the time being. > > Iwasaki-San's patch made no difference that I could see. Disabling ACPI > causes my system to hard-hang d

Re: PCI brokenness

2002-10-02 Thread Mark Murray
> > I tried this patch, and it made some progress (dmesg included). The > > ATA system still seems badly broken, there is a spurious mention of > > some kerneldump. I also have no console. > > Hmm, ata0 may be getting the wrong resources. Hmm. Try iwasaki-san's > patch to acpi_pcib_* instead an

Re: PCI brokenness

2002-10-02 Thread John Baldwin
On 02-Oct-2002 Mark Murray wrote: > Hi > > I tried this patch, and it made some progress (dmesg included). The > ATA system still seems badly broken, there is a spurious mention of > some kerneldump. I also have no console. Hmm, ata0 may be getting the wrong resources. Hmm. Try iwasaki-san's

Re: PCI brokenness

2002-10-02 Thread Mark Murray
Hi I tried this patch, and it made some progress (dmesg included). The ATA system still seems badly broken, there is a spurious mention of some kerneldump. I also have no console. Perhaps the legacy stuff needs to be backed out or disabled pending fixing? M Copyright (c) 1992-2002 The FreeBSD

Re: PCI brokenness

2002-10-02 Thread Michael McGoldrick
On Tue, Oct 01, 2002 at 05:23:34PM -0400, John Baldwin wrote: > > On 01-Oct-2002 Michael McGoldrick wrote: > > On Tue, Oct 01, 2002 at 12:48:47PM -0400, John Baldwin wrote: > >> > >> On 01-Oct-2002 Michael McGoldrick wrote: > >> > 'Me too' > >> > Dmesg from working kernel attached, not sure how

Re: PCI brokenness

2002-10-02 Thread Mark Murray
> On Tue, 1 Oct 2002, Mark Murray wrote: > > I'm running a kernel with your very latest nexus.c 1.49. > > > > The problem of the disappearing HD has not been fixed by this. > > > > Enclosed are verbose mesg's, one from a three-hour-ago > > (1st Oct 2002, 11:00 am, BST) kernel (broken), and anoth

Re: PCI brokenness

2002-10-01 Thread Niels Chr. Bank-Pedersen
On Wed, Oct 02, 2002 at 08:41:10AM +0900, Mitsuru IWASAKI wrote: > Hi, > [...] > > Can you try with the stuff I committed yesterday? It fixed the case (for > > my tests at least) of legacy0 failing to attach or probe when acpi failed > > to attach. > > If still failed, please try this. > I've

Re: PCI brokenness

2002-10-01 Thread John Baldwin
On 01-Oct-2002 Mitsuru IWASAKI wrote: > Hi, > >> On 01-Oct-2002 Michael McGoldrick wrote: >> > On Tue, Oct 01, 2002 at 12:48:47PM -0400, John Baldwin wrote: >> >> >> >> On 01-Oct-2002 Michael McGoldrick wrote: >> >> > 'Me too' >> >> > Dmesg from working kernel attached, not sure how to get a dm

Re: PCI brokenness

2002-10-01 Thread Mitsuru IWASAKI
Hi, > On 01-Oct-2002 Michael McGoldrick wrote: > > On Tue, Oct 01, 2002 at 12:48:47PM -0400, John Baldwin wrote: > >> > >> On 01-Oct-2002 Michael McGoldrick wrote: > >> > 'Me too' > >> > Dmesg from working kernel attached, not sure how to get a dmesg from the > >> > broken one. :( > >> > Send me

Re: PCI brokenness

2002-10-01 Thread John Baldwin
On 01-Oct-2002 Michael McGoldrick wrote: > On Tue, Oct 01, 2002 at 12:48:47PM -0400, John Baldwin wrote: >> >> On 01-Oct-2002 Michael McGoldrick wrote: >> > 'Me too' >> > Dmesg from working kernel attached, not sure how to get a dmesg from the >> > broken one. :( >> > Send me a mail if any furth

Re: PCI brokenness

2002-10-01 Thread Michael McGoldrick
On Tue, Oct 01, 2002 at 12:48:47PM -0400, John Baldwin wrote: > > On 01-Oct-2002 Michael McGoldrick wrote: > > 'Me too' > > Dmesg from working kernel attached, not sure how to get a dmesg from the > > broken one. :( > > Send me a mail if any further info would help. > > (I have built two kernels

Re: PCI brokenness

2002-10-01 Thread Nate Lawson
On Tue, 1 Oct 2002, Mark Murray wrote: > I'm running a kernel with your very latest nexus.c 1.49. > > The problem of the disappearing HD has not been fixed by this. > > Enclosed are verbose mesg's, one from a three-hour-ago > (1st Oct 2002, 11:00 am, BST) kernel (broken), and another > from a wo

Re: PCI brokenness

2002-10-01 Thread John Baldwin
On 01-Oct-2002 Michael McGoldrick wrote: > 'Me too' > Dmesg from working kernel attached, not sure how to get a dmesg from the > broken one. :( > Send me a mail if any further info would help. > (I have built two kernels recently, both have had this problem) What exact problem do you have. No P

Re: PCI brokenness

2002-10-01 Thread Michael McGoldrick
'Me too' Dmesg from working kernel attached, not sure how to get a dmesg from the broken one. :( Send me a mail if any further info would help. (I have built two kernels recently, both have had this problem) On Tue, Oct 01, 2002 at 01:06:59PM +0100, Mark Murray wrote: > Hi > > I'm running a kern

RE: PCI brokenness

2002-10-01 Thread John Baldwin
On 01-Oct-2002 Mark Murray wrote: > Hi > > I'm running a kernel with your very latest nexus.c 1.49. > > The problem of the disappearing HD has not been fixed by this. > > Enclosed are verbose mesg's, one from a three-hour-ago > (1st Oct 2002, 11:00 am, BST) kernel (broken), and another > from

PCI brokenness

2002-10-01 Thread Mark Murray
Hi I'm running a kernel with your very latest nexus.c 1.49. The problem of the disappearing HD has not been fixed by this. Enclosed are verbose mesg's, one from a three-hour-ago (1st Oct 2002, 11:00 am, BST) kernel (broken), and another from a working Sept 22nd kernel. M -- o Mark Murra