Hi Chris, Thanks!
What kind of an issue was it? You just had to increase the VM_PHYSSEG_MAX definition, or was that a misdirection? Austin BTW, way, how long does it take for such patches to show up in either the 4.1 or patch branch corrections lists on the web site? Austin On Sat, 30 Jun 2007, Chris Kuethe wrote: > On 6/29/07, Austin Hook <[EMAIL PROTECTED]> wrote: > > Trying to set up a fairly heavy duty web server I encountered boot > > problems with this fairly new machine using the release CD ROM. Using the > > -c command at the boot prompt I already see error messages, before it > > gives me the UKC> ... > > > > UVM_PAGE_PHYSLOAD: unable to load physical memory segment > > 5 segments allocated, ignoring 0x7fa9a -> 0x7fad0 > > Increase VM_PHYSSEG_MAX > > > > and repeats this two more times for ranges like: > > 0x7fb1a -> 0x7fb2c > > I just committed a patch to 4.0-stable and 4.1-stable which may help. > > CK > > -- > GDB has a 'break' feature; why doesn't it have 'fix' too?
