On 01/28/2012 01:41, Andriy Gapon wrote:
> on 28/01/2012 11:37 Doug Barton said the following:
>> On 01/28/2012 01:21, Andriy Gapon wrote:
>>> on 28/01/2012 11:13 Doug Barton said the following:
On 01/27/2012 10:21, John Baldwin wrote:
> Does it operate fully with NEW_PCIB disabled entirel
on 28/01/2012 11:37 Doug Barton said the following:
> On 01/28/2012 01:21, Andriy Gapon wrote:
>> on 28/01/2012 11:13 Doug Barton said the following:
>>> On 01/27/2012 10:21, John Baldwin wrote:
Does it operate fully with NEW_PCIB disabled entirely, or do you get this
same message in that
On 01/28/2012 01:21, Andriy Gapon wrote:
> on 28/01/2012 11:13 Doug Barton said the following:
>> On 01/27/2012 10:21, John Baldwin wrote:
>>> Does it operate fully with NEW_PCIB disabled entirely, or do you get this
>>> same message in that case?
>>
>> I put nooptions NEW_PCIB in my kernel config,
on 28/01/2012 11:13 Doug Barton said the following:
> On 01/27/2012 10:21, John Baldwin wrote:
>> Does it operate fully with NEW_PCIB disabled entirely, or do you get this
>> same message in that case?
>
> I put nooptions NEW_PCIB in my kernel config, and got basically the same:
>
> isab0: found
On 01/27/2012 10:21, John Baldwin wrote:
> On Wednesday, January 04, 2012 2:37:55 am Doug Barton wrote:
>> On 01/03/2012 14:14, John Baldwin wrote:
>>> On Wednesday, August 03, 2011 3:55:17 am Doug Barton wrote:
On 08/02/2011 15:06, John Baldwin wrote:
> On Saturday, July 30, 2011 2:49:52
On Wednesday, January 04, 2012 2:37:55 am Doug Barton wrote:
> On 01/03/2012 14:14, John Baldwin wrote:
> > On Wednesday, August 03, 2011 3:55:17 am Doug Barton wrote:
> >> On 08/02/2011 15:06, John Baldwin wrote:
> >>> On Saturday, July 30, 2011 2:49:52 am Andriy Gapon wrote:
> on 19/07/2011
On 01/03/2012 14:14, John Baldwin wrote:
> On Wednesday, August 03, 2011 3:55:17 am Doug Barton wrote:
>> On 08/02/2011 15:06, John Baldwin wrote:
>>> On Saturday, July 30, 2011 2:49:52 am Andriy Gapon wrote:
on 19/07/2011 18:16 John Baldwin said the following:
> Hmm, can you get devinfo -
On Wednesday, August 03, 2011 3:55:17 am Doug Barton wrote:
> On 08/02/2011 15:06, John Baldwin wrote:
> > On Saturday, July 30, 2011 2:49:52 am Andriy Gapon wrote:
> >> on 19/07/2011 18:16 John Baldwin said the following:
> >>> Hmm, can you get devinfo -r output from a working kernel with ichwd
>
on 03/08/2011 01:06 John Baldwin said the following:
> On Saturday, July 30, 2011 2:49:52 am Andriy Gapon wrote:
>> on 19/07/2011 18:16 John Baldwin said the following:
>>> Hmm, can you get devinfo -r output from a working kernel with ichwd loaded?
>>>
>>> You might be able to just build the ker
On Thursday, August 04, 2011 12:20:47 am Test Rat wrote:
> John Baldwin writes:
>
> > Hmmm, so your BIOS just outright lies then? :(
> >
> > Can you check devinfo -u with 'debug.acpi.disabled=hostres' to see where
> > those memory addresses show up?
Ugh, so ACPI just outright lies it would seem.
John Baldwin writes:
> Hmmm, so your BIOS just outright lies then? :(
>
> Can you check devinfo -u with 'debug.acpi.disabled=hostres' to see where
> those memory addresses show up?
I/O memory addresses:
0x0-0x9e7ff (ram0)
0x9e800-0x9 (root0)
0xa-0xb (vga0)
es() is not called when isab0 or
> >> isa0 are attached.
> >>
> >> isab0: found ICH9 or equivalent chipset: Intel ICH9 watchdog timer
> >> ichwd0: on isa0
> >> isab0: found ICH9 or equivalent chipset: Intel ICH9 watchdog timer
> >> acpi
:acpi_alloc_sysres(child->nameunit=ichwd0,
> type=SYS_RES_IOPORT, *rid=0, start=1072, end=1079, count=8, flags=6)
> res=0xfe0007fed380 RF_ACTIVE activated
>> pcib0: allocated type 4 (0x430-0x437) for rid 0 of ichwd0
>> acpi_alloc_resource::acpi_alloc_sysres(child
r equivalent chipset: Intel ICH9 watchdog timer
> acpi_alloc_resource::acpi_alloc_sysres(child->nameunit=ichwd0,
type=SYS_RES_IOPORT, *rid=0, start=1072, end=1079, count=8, flags=6)
res=0xfe0007fed380 RF_ACTIVE activated
> pcib0: allocated type 4 (0x430-0x437) for rid 0 of ichwd0
res=0xfe0007fed380 RF_ACTIVE activated
pcib0: allocated type 4 (0x430-0x437) for rid 0 of ichwd0
acpi_alloc_resource::acpi_alloc_sysres(child->nameunit=ichwd0,
type=SYS_RES_IOPORT, *rid=1, start=1120, end=1151, count=32, flags=6)
res=0xfe0007fed400 RF_ACTIVE activated
pcib0: allocat
On Wednesday, August 03, 2011 4:49:24 am Test Rat wrote:
> Doug Barton writes:
>
> > On 08/02/2011 15:06, John Baldwin wrote:
> >> On Saturday, July 30, 2011 2:49:52 am Andriy Gapon wrote:
> >>> on 19/07/2011 18:16 John Baldwin said the following:
> Hmm, can you get devinfo -r output from a
Doug Barton writes:
> On 08/02/2011 15:06, John Baldwin wrote:
>> On Saturday, July 30, 2011 2:49:52 am Andriy Gapon wrote:
>>> on 19/07/2011 18:16 John Baldwin said the following:
Hmm, can you get devinfo -r output from a working kernel with ichwd
loaded?
You might be able to j
On 08/02/2011 15:06, John Baldwin wrote:
> On Saturday, July 30, 2011 2:49:52 am Andriy Gapon wrote:
>> on 19/07/2011 18:16 John Baldwin said the following:
>>> Hmm, can you get devinfo -r output from a working kernel with ichwd loaded?
>>>
>>> You might be able to just build the kernel with 'no
On Saturday, July 30, 2011 2:49:52 am Andriy Gapon wrote:
> on 19/07/2011 18:16 John Baldwin said the following:
> > Hmm, can you get devinfo -r output from a working kernel with ichwd loaded?
> >
> > You might be able to just build the kernel with 'nooptions NEW_PCIB'.
>
> I believe that I've
On 07/30/2011 19:35, John Baldwin wrote:
> On 7/30/11 7:55 PM, Doug Barton wrote:
>> On 07/30/2011 05:34, John Baldwin wrote:
>>> On Saturday, July 30, 2011 02:49:52 AM Andriy Gapon wrote:
on 19/07/2011 18:16 John Baldwin said the following:
> Hmm, can you get devinfo -r output from a work
On 7/30/11 7:55 PM, Doug Barton wrote:
On 07/30/2011 05:34, John Baldwin wrote:
On Saturday, July 30, 2011 02:49:52 AM Andriy Gapon wrote:
on 19/07/2011 18:16 John Baldwin said the following:
Hmm, can you get devinfo -r output from a working kernel with ichwd
loaded? You might be able to just
On 07/30/2011 05:34, John Baldwin wrote:
> On Saturday, July 30, 2011 02:49:52 AM Andriy Gapon wrote:
>> on 19/07/2011 18:16 John Baldwin said the following:
>>> Hmm, can you get devinfo -r output from a working kernel with ichwd
>>> loaded? You might be able to just build the kernel with 'nooption
On Saturday, July 30, 2011 02:49:52 AM Andriy Gapon wrote:
> on 19/07/2011 18:16 John Baldwin said the following:
> > Hmm, can you get devinfo -r output from a working kernel with ichwd
> > loaded? You might be able to just build the kernel with 'nooptions
> > NEW_PCIB'.
>
> I believe that I've go
on 19/07/2011 18:16 John Baldwin said the following:
> Hmm, can you get devinfo -r output from a working kernel with ichwd loaded?
> You might be able to just build the kernel with 'nooptions NEW_PCIB'.
I believe that I've got a similar problem with amdsbwd(4).
It needs some resources (I/O ports
CH7M watchdog timer
> >> ichwd0: at port 0x1030-0x1037,0x1060-0x107f
> >> on isa0
> >> isab0: found ICH7 or equivalent chipset: Intel ICH7M watchdog timer
> >> pcib0: allocated type 4 (0x1030-0x1037) for rid 0 of ichwd0
> >> pcib0: allocated t
t;> on isa0
>> isab0: found ICH7 or equivalent chipset: Intel ICH7M watchdog timer
>> pcib0: allocated type 4 (0x1030-0x1037) for rid 0 of ichwd0
>> pcib0: allocated type 4 (0x1060-0x107f) for rid 1 of ichwd0
>> ichwd0: unable to reserve GCS registers
>> device_attach: i
el ICH7M watchdog timer
> pcib0: allocated type 4 (0x1030-0x1037) for rid 0 of ichwd0
> pcib0: allocated type 4 (0x1060-0x107f) for rid 1 of ichwd0
> ichwd0: unable to reserve GCS registers
> device_attach: ichwd0 attach returned 6
> pcib0: allocated type 4 (0x2f8-0x2ff) for rid 0 of uart
pcib0: allocated type 4 (0x1060-0x107f) for rid 1 of ichwd0
ichwd0: unable to reserve GCS registers
device_attach: ichwd0 attach returned 6
pcib0: allocated type 4 (0x2f8-0x2ff) for rid 0 of uart1
--
Nothin' ever doesn't change, but nothin' changes much.
28 matches
Mail list logo
