Re: PCI-PCI Bridge Problems
> > From: Michael Harnois [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, December 12, 2000 6:31 AM > > > > On Tue, 12 Dec 2000 05:02:59 -0800, Mike Smith > > <[EMAIL PROTECTED]> said: > > > > > I'll keep working on this one; things will go a lot faster if I > > > can get my hands on a system that misbehaves in a corresponding > > > fashion. > > > > You're welcome to come to Iowa and use mine. I'll even put you up. > > Just make sure you bring a shovel... :-) Oh ick, snow. I hate that stuff. 8) On a more relevant tangent; Michael the first - is the most recent cut of the code still not finding things on your PCI bus? I noticed that your ATA controller *was* showing up... If you could, could you try applying http://ziplok.dyndns.org/msmith/pci.diff to a fresh -current source tree and building that? (Make sure you use 'config -g' as well, since the last set of problems reported may have been due to an unclean kernel compile directory). The output from a verbose boot with the above patch might help track some of this down. Thanks! Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: PCI-PCI Bridge Problems
> From: Michael Harnois [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 12, 2000 6:31 AM > > On Tue, 12 Dec 2000 05:02:59 -0800, Mike Smith > <[EMAIL PROTECTED]> said: > > > I'll keep working on this one; things will go a lot faster if I > > can get my hands on a system that misbehaves in a corresponding > > fashion. > > You're welcome to come to Iowa and use mine. I'll even put you up. Just make sure you bring a shovel... :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-PCI Bridge Problems
On Tue, 12 Dec 2000 05:02:59 -0800, Mike Smith <[EMAIL PROTECTED]> said: > I'll keep working on this one; things will go a lot faster if I > can get my hands on a system that misbehaves in a corresponding > fashion. You're welcome to come to Iowa and use mine. I'll even put you up. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA [EMAIL PROTECTED] [EMAIL PROTECTED] EDUCATION, n. That which discloses to the wise and disguises from the foolish their lack of understanding. -- Ambrose Bierce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-PCI Bridge Problems
> I cvsuped current ~2000/12/11 @ ~ 22:00, the previous version was > from around 2000/12/07. Before the update my Dual intel nic was > happy post update the nic isn't even probed. > > attached is a pciconf -v -l from before and after as well as a > a boot -v from after. If you need more info let me know and I'll > go back to the 2000/12/11 kernel. Actually, I take some of what I said back. > pcib1@pci0:13:0: class=0x060400 card=0x00dc chip=0x00241011 rev=0x03 >hdr=0x01 > vendor = 'Digital Equipment Corporation' > device = 'DC21151/2 PCI-PCI Bridge' > class= bridge > subclass = PCI-PCI ... > pcib1: at device 13.0 on pci0 > pcib1: secondary bus 6 > pcib1: subordinate bus 6 > pcib1: I/O decode0x6-0x60fff > pcib1: memory decode 0x0-0xf > pcib1: prefetched decode 0x0-0xf > pci1: physical bus=6 > pci1: on pcib1 There are bugs in the code you're running that I fixed tonight, but even so the decode registers there look *totally* wrong. Please cvsup and try again; I'm just about to commit some patches to the bridge code that should at least get that part right, then we'll see what's still going on. Sorry about this. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-PCI Bridge Problems
> I cvsuped current ~2000/12/11 @ ~ 22:00, the previous version was > from around 2000/12/07. Before the update my Dual intel nic was > happy post update the nic isn't even probed. Hrm. That's odd; I have one of those here (with a Compaq label on it) as part of my test set. In fact, I have twelve different ethernet devices in the test machine right now trying to reproduce this. 8( > attached is a pciconf -v -l from before and after as well as a > a boot -v from after. If you need more info let me know and I'll > go back to the 2000/12/11 kernel. About the only thing different I can see between your setup and mine is that your bridge gets bus 6, but comes up as pci bus 1. There may still be assumptions somewhere in the code that the pci bus device number corresponds to the bus number, although I'm not having any luck finding them. 8( I'll keep working on this one; things will go a lot faster if I can get my hands on a system that misbehaves in a corresponding fashion. Thanks for the report; keep your eyes out for commits to the PCI code that mention this problem. If you do try again, please let me know how you go. If you're motivated to get involved with the code, I'd be more than happy to point you at a few things worth checking out. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
