On 04/03/14 14:25, Nikolai Lifanov wrote:
> On 04/03/14 14:05, Ryan Stone wrote:
>> Can somebody please confirm whether setting hw.pci.enable_ari=0 in the
>> loader fixes the issue or not. That will help me to figure out if the
>> issue is with ARI or if I have somehow broken PCI enumeration in
>>
On 04/03/14 14:05, Ryan Stone wrote:
> Can somebody please confirm whether setting hw.pci.enable_ari=0 in the
> loader fixes the issue or not. That will help me to figure out if the
> issue is with ARI or if I have somehow broken PCI enumeration in
> general (I suspect the later).
> __
Can somebody please confirm whether setting hw.pci.enable_ari=0 in the
loader fixes the issue or not. That will help me to figure out if the
issue is with ARI or if I have somehow broken PCI enumeration in
general (I suspect the later).
___
freebsd-curre
On Thu, 3 Apr 2014, David Wolfskill wrote:
-em0: port 0x2000-0x203f
mem 0xd820-0xd821 irq 54 at device 2.0 on pci3
-em0: Ethernet address: 00:30:48:2d:32:6a
-em1: port 0x2040-0x207f
mem 0xd822-0xd823 irq 55 at device 2.1 on pci3
-em1: Ethernet address: 00:30:48:2d:32:6b
+em0:
On Thu, Apr 03, 2014 at 12:06:51PM -0400, Benjamin Kaduk wrote:
> ...
> I'm also having some trouble booting (into single user mode, so as to run
> the installworld), at r264039
Sympathy
> That would seem to indicate some hardware problem or
> timing issues more than a problem with the
On 04/03/14 12:06, Benjamin Kaduk wrote:
> On Thu, 3 Apr 2014, David Wolfskill wrote:
>
>> And on my laptop, I had no problems (using AHCI). The build machine,
>> though, starts OK, then comes to an inglorious end:
>>
>> Trying to mount root from ufs:/dev/aacd0s4a [rw]...
>> mountroot: waiting fo
On Thu, 3 Apr 2014, David Wolfskill wrote:
And on my laptop, I had no problems (using AHCI). The build machine,
though, starts OK, then comes to an inglorious end:
Trying to mount root from ufs:/dev/aacd0s4a [rw]...
mountroot: waiting for device /dev/aacd0s4a ...
Mounting from ufs:/dev/aacd0s4
