Re: pcib allocation failure

2011-06-10 Thread John Baldwin
On Thursday, June 09, 2011 6:08:08 pm deeptec...@gmail.com wrote: > On Thu, Jun 9, 2011 at 8:56 PM, John Baldwin wrote: > > On Thursday, June 09, 2011 2:07:31 pm deeptec...@gmail.com wrote: > >> pcib1: attempting to grow prefetch window for > >> (0xe000-0xefff,0x1000) > >> back

Re: pcib allocation failure

2011-06-09 Thread deeptec...@gmail.com
On Thu, Jun 9, 2011 at 8:56 PM, John Baldwin wrote: > On Thursday, June 09, 2011 2:07:31 pm deeptec...@gmail.com wrote: >> pcib1: attempting to grow prefetch window for >> (0xe000-0xefff,0x1000) >>       back candidate range: 0xe000-0xefff >> pcib1: failed to grow prefetch win

Re: pcib allocation failure

2011-06-09 Thread Chuck Swiger
On Jun 9, 2011, at 11:07 AM, deeptec...@gmail.com wrote: [ ... ] > PS: u should learn to properly use backward references ("it") in ur sentences. Hmm. Let's just say that there are more effective ways to persuade someone like John who is volunteering their time writing patches to continue to tr

Re: pcib allocation failure

2011-06-09 Thread John Baldwin
On Thursday, June 09, 2011 2:07:31 pm deeptec...@gmail.com wrote: > pcib1: attempting to grow prefetch window for > (0xe000-0xefff,0x1000) > back candidate range: 0xe000-0xefff > pcib1: failed to grow prefetch window to 0xd000-0xefff: 6 Hmm, ENXIO is an odd error

Re: pcib allocation failure

2011-06-09 Thread deeptec...@gmail.com
On Thu, Jun 9, 2011 at 3:22 PM, John Baldwin wrote: > Hmm, I would say 'progress' actually as it's getting better: > > >>       map[10]: type Prefetchable Memory, range 32, base 0xe000, size 28, >> enabled >> pcib1: attempting to grow prefetch window for >> (0xe000-0xefff,0x1000)

Re: pcib allocation failure

2011-06-09 Thread John Baldwin
On Wednesday, June 08, 2011 4:20:00 pm deeptec...@gmail.com wrote: > On Wed, Jun 8, 2011 at 7:56 PM, John Baldwin wrote: > > On Wednesday, June 08, 2011 11:20:17 am deeptec...@gmail.com wrote: > >> On Tue, Jun 7, 2011 at 4:35 PM, John Baldwin wrote: > >> found-> vendor=0x1002, dev=0x4170, r

Re: pcib allocation failure

2011-06-08 Thread deeptec...@gmail.com
On Wed, Jun 8, 2011 at 7:56 PM, John Baldwin wrote: > On Wednesday, June 08, 2011 11:20:17 am deeptec...@gmail.com wrote: >> On Tue, Jun 7, 2011 at 4:35 PM, John Baldwin wrote: >> found->       vendor=0x1002, dev=0x4170, revid=0x00 >>       domain=0, bus=1, slot=0, func=1 >>       class=03-80-00,

Re: pcib allocation failure

2011-06-08 Thread John Baldwin
On Wednesday, June 08, 2011 2:05:42 pm deeptec...@gmail.com wrote: > On Wed, Jun 8, 2011 at 7:56 PM, John Baldwin wrote: > > Hmmm, can you revert all your changes to pci_pci.c > > let me note that so far i had at most 1 of the (4) patches applied at > a time (always the last one). if u'd like me

Re: pcib allocation failure

2011-06-08 Thread deeptec...@gmail.com
On Wed, Jun 8, 2011 at 7:56 PM, John Baldwin wrote: > Hmmm, can you revert all your changes to pci_pci.c let me note that so far i had at most 1 of the (4) patches applied at a time (always the last one). if u'd like me to apply "multiple" patches, please send 1 combined patch. __

Re: pcib allocation failure

2011-06-08 Thread John Baldwin
On Wednesday, June 08, 2011 11:20:17 am deeptec...@gmail.com wrote: > On Tue, Jun 7, 2011 at 4:35 PM, John Baldwin wrote: > found-> vendor=0x1002, dev=0x4170, revid=0x00 > domain=0, bus=1, slot=0, func=1 > class=03-80-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0007, statreg=0x02b

Re: pcib allocation failure

2011-06-08 Thread deeptec...@gmail.com
On Tue, Jun 7, 2011 at 4:35 PM, John Baldwin wrote: > On Monday, June 06, 2011 11:02:59 pm deeptec...@gmail.com wrote: >> On Mon, Jun 6, 2011 at 4:52 PM, John Baldwin wrote: >> > Can you try out this change.  It is a possible "real" solution (or at > least a >> > stopgap until we start using mult

Re: pcib allocation failure

2011-06-07 Thread John Baldwin
On Monday, June 06, 2011 11:02:59 pm deeptec...@gmail.com wrote: > On Mon, Jun 6, 2011 at 4:52 PM, John Baldwin wrote: > > Can you try out this change. It is a possible "real" solution (or at least a > > stopgap until we start using multipass to untangle the resource mess a bit > > further): > [

Re: pcib allocation failure

2011-06-06 Thread deeptec...@gmail.com
On Mon, Jun 6, 2011 at 4:52 PM, John Baldwin wrote: > Can you try out this change.  It is a possible "real" solution (or at least a > stopgap until we start using multipass to untangle the resource mess a bit > further): [snip] that doesn't work. i get an allocation failure. _

Re: pcib allocation failure

2011-06-06 Thread John Baldwin
On Saturday, May 28, 2011 9:45:48 pm deeptec...@gmail.com wrote: > On Thu, May 26, 2011 at 3:40 PM, John Baldwin wrote: > > Ohh, you have two devices behind this bridge that have prefetch ranges. > > > > As a hack, can you try this: > > > > Index: pci_pci.c > >

Re: pcib allocation failure

2011-05-31 Thread John Baldwin
On Saturday, May 28, 2011 9:45:48 pm deeptec...@gmail.com wrote: > On Thu, May 26, 2011 at 3:40 PM, John Baldwin wrote: > > Ohh, you have two devices behind this bridge that have prefetch ranges. > > > > As a hack, can you try this: > > > > Index: pci_pci.c > >

Re: pcib allocation failure

2011-05-28 Thread deeptec...@gmail.com
On Thu, May 26, 2011 at 3:40 PM, John Baldwin wrote: > Ohh, you have two devices behind this bridge that have prefetch ranges. > > As a hack, can you try this: > > Index: pci_pci.c > === > --- pci_pci.c   (revision 85) > +++ pci_p

Re: pcib allocation failure

2011-05-26 Thread John Baldwin
On Sunday, May 22, 2011 1:20:39 pm deeptec...@gmail.com wrote: > On Sat, May 21, 2011 at 3:59 PM, deeptec...@gmail.com > wrote: > > On Thu, May 19, 2011 at 11:35 PM, John Baldwin wrote: > >> Index: pci_pci.c > >> === > >> --- pci_pci

Re: pcib allocation failure

2011-05-22 Thread deeptec...@gmail.com
On Sat, May 21, 2011 at 3:59 PM, deeptec...@gmail.com wrote: > On Thu, May 19, 2011 at 11:35 PM, John Baldwin wrote: >> Index: pci_pci.c >> === >> --- pci_pci.c   (revision 222093) >> +++ pci_pci.c   (working copy) >> @@ -162,8 +162,

Re: pcib allocation failure

2011-05-21 Thread deeptec...@gmail.com
On Thu, May 19, 2011 at 11:35 PM, John Baldwin wrote: > On Thursday, May 19, 2011 12:28:46 pm deeptec...@gmail.com wrote: >> On Thu, May 19, 2011 at 2:13 PM, John Baldwin wrote: >> > Yeah, your BIOS continues to behave very poorly.  Please try this hack to > see >> > if it allows your video to st

Re: pcib allocation failure

2011-05-19 Thread John Baldwin
On Thursday, May 19, 2011 12:28:46 pm deeptec...@gmail.com wrote: > On Thu, May 19, 2011 at 2:13 PM, John Baldwin wrote: > > Yeah, your BIOS continues to behave very poorly. Please try this hack to see > > if it allows your video to still work with any AGP aperture size: > > > > Index: pci_pci.c

Re: pcib allocation failure

2011-05-19 Thread deeptec...@gmail.com
On Thu, May 19, 2011 at 2:13 PM, John Baldwin wrote: > Yeah, your BIOS continues to behave very poorly.  Please try this hack to see > if it allows your video to still work with any AGP aperture size: > > Index: pci_pci.c > === > ---

Re: pcib allocation failure

2011-05-19 Thread John Baldwin
On Thursday, May 19, 2011 5:23:42 am deeptec...@gmail.com wrote: > On Tue, May 17, 2011 at 10:40 PM, John Baldwin wrote: > > On Tuesday, May 17, 2011 2:03:42 pm deeptec...@gmail.com wrote: > >> On Tue, May 17, 2011 at 3:44 PM, John Baldwin wrote: > >> > On Saturday, May 14, 2011 12:27:59 pm deept

Re: pcib allocation failure

2011-05-19 Thread deeptec...@gmail.com
On Tue, May 17, 2011 at 10:40 PM, John Baldwin wrote: > On Tuesday, May 17, 2011 2:03:42 pm deeptec...@gmail.com wrote: >> On Tue, May 17, 2011 at 3:44 PM, John Baldwin wrote: >> > On Saturday, May 14, 2011 12:27:59 pm deeptec...@gmail.com wrote: >> >> pcib1: at device 1.0 on pci0 >> >> pcib1: f

Re: pcib allocation failure

2011-05-17 Thread deeptec...@gmail.com
On Tue, May 17, 2011 at 3:44 PM, John Baldwin wrote: > On Saturday, May 14, 2011 12:27:59 pm deeptec...@gmail.com wrote: >> pcib1: at device 1.0 on pci0 >> pcib1: failed to allocate initial prefetch window: 0xd000-0xfaff >> >> the console output is cut shortly after those 2 lines (but the

Re: pcib allocation failure

2011-05-17 Thread John Baldwin
On Saturday, May 14, 2011 12:27:59 pm deeptec...@gmail.com wrote: > pcib1: at device 1.0 on pci0 > pcib1: failed to allocate initial prefetch window: 0xd000-0xfaff > > the console output is cut shortly after those 2 lines (but the machine > seems to continue booting, as i have reset'd the

Re: pcib allocation failure

2011-05-16 Thread Julian Elischer
On 5/15/11 8:50 PM, deeptec...@gmail.com wrote: On Sat, May 14, 2011 at 6:27 PM, deeptec...@gmail.com wrote: pcib1: at device 1.0 on pci0 pcib1: failed to allocate initial prefetch window: 0xd000-0xfaff this happens with a the r221862 kernel, but not with the r221309 kernel. a quick

Re: pcib allocation failure

2011-05-16 Thread John Baldwin
On Sunday, May 15, 2011 8:50:04 pm deeptec...@gmail.com wrote: > On Sat, May 14, 2011 at 6:27 PM, deeptec...@gmail.com > wrote: > > pcib1: at device 1.0 on pci0 > > pcib1: failed to allocate initial prefetch window: 0xd000-0xfaff > > > > this happens with a the r221862 kernel, but not wit

Re: pcib allocation failure

2011-05-15 Thread Garrett Cooper
On Sun, May 15, 2011 at 5:50 PM, deeptec...@gmail.com wrote: > On Sat, May 14, 2011 at 6:27 PM, deeptec...@gmail.com > wrote: >> pcib1: at device 1.0 on pci0 >> pcib1: failed to allocate initial prefetch window: 0xd000-0xfaff >> >> this happens with a the r221862 kernel, but not with the

Re: pcib allocation failure

2011-05-15 Thread deeptec...@gmail.com
On Sat, May 14, 2011 at 6:27 PM, deeptec...@gmail.com wrote: > pcib1: at device 1.0 on pci0 > pcib1: failed to allocate initial prefetch window: 0xd000-0xfaff > > this happens with a the r221862 kernel, but not with the r221309 kernel. > a quick search reveals something: > http://www.free

pcib allocation failure

2011-05-14 Thread deeptec...@gmail.com
pcib1: at device 1.0 on pci0 pcib1: failed to allocate initial prefetch window: 0xd000-0xfaff the console output is cut shortly after those 2 lines (but the machine seems to continue booting, as i have reset'd the machine, after which "/" was found to be improperly dismounted). this happ