On 3/25/07, Gabriel C <[EMAIL PROTECTED]> wrote:
Kevin P. Fleming wrote:
> I just upgraded from 2.6.20.2 to 2.6.20.4 on my Compaq V6000 laptop,
> which has an NVidia core chipset. It has the MCP51 and uses it for PATA
> and SATA.
>
> Booting the 2.6.20.4 kernel causes two messages (and a kernel lockup)
> like this:
>
> 0000:00:0d.0: cannot adjust BAR0 (not I/O)
> 0000:00:0d.0: cannot adjust BAR1 (not I/O)
>
[   18.754623] Enabling SiS 96x SMBus.
[   18.754812] 0000:00:02.5: cannot adjust BAR0 (not I/O)
[   18.754816] 0000:00:02.5: cannot adjust BAR1 (not I/O)
[   18.754819] 0000:00:02.5: cannot adjust BAR2 (not I/O)
[   18.754822] 0000:00:02.5: cannot adjust BAR3 (not I/O)

I am seeing this also, but on a MCP55

Mar 25 18:56:37 treogen [   50.828369] 0000:00:04.0: cannot adjust
BAR0 (not I/O)
Mar 25 18:56:37 treogen [   50.843736] 0000:00:04.0: cannot adjust
BAR1 (not I/O)
Mar 25 18:56:37 treogen [   50.859120] 0000:00:04.0: cannot adjust
BAR2 (not I/O)
Mar 25 18:56:37 treogen [   50.874504] 0000:00:04.0: cannot adjust
BAR3 (not I/O)


00:04.0 IDE interface: nVidia Corporation MCP55 IDE (rev a1) (prog-if
8a [Master SecP PriP])
       Subsystem: ASUSTeK Computer Inc. Unknown device 81f0
       Flags: bus master, 66MHz, fast devsel, latency 0
       [virtual] Memory at 000001f0 (32-bit, non-prefetchable)
[disabled] [size=8]
       [virtual] Memory at 000003f0 (type 3, non-prefetchable)
[disabled] [size=1]
       [virtual] Memory at 00000170 (32-bit, non-prefetchable)
[disabled] [size=8]
       [virtual] Memory at 00000370 (type 3, non-prefetchable)
[disabled] [size=1]
       I/O ports at ffa0 [size=16]
       Capabilities: [44] Power Management version 2
00: de 10 6e 03 05 00 b0 00 a1 8a 01 01 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: a1 ff 00 00 00 00 00 00 00 00 00 00 43 10 f0 81
30: 00 00 00 00 44 00 00 00 00 00 00 00 00 00 03 01

I am not using the IDE interface so I can't tell if it is working or
not, but the boot does not hang.

Torsten
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to