HyperT reset needed HyperT reset not needed
In the scan_hypertranport_chain.c missed one "else"
YH.
-----邮件原件----- 发件人: Stefan Reinauer [mailto:stepan@suse.de] 发送时间: 2003年9月8日 8:02 收件人: LinuxBIOS 主题: newer solo motherboards
Testing the newmethod solo image on a newer motherboard I get the following:
with 1 dimm module: LinuxBIOS-1.1.4.0Fallback Mon Sep 8 16:21:32 CEST 2003 starting... setting up resource map.... done. Enabling routing table for node 00000000 done. Enabling UP settings Disabling read/write/fill probes for UP... done. coherent_ht_finalize done SMBus controller enabled Ram1.00 setting up CPU00 northbridge registers done. Ram2.00 disabling dimm01 disabling dimm01 133Mhz disabling dimm01 RAM: 0x00040000 KB Ram3 Initializing memory: done Ram4 TOP_MEM: 0000000010000000 Testing DRAM : 00000000-10000000 DRAM fill: 00000000-10000000 [..] DRAM filled DRAM verify: 00000000-10000000 [..] DRAM verified Done. LinuxBIOS-1.1.4.0Fallback Mon Sep 8 16:21:32 CEST 2003 starting... Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.1.4.0Fallback Mon Sep 8 16:21:32 CEST 2003 booting... Finding PCI configuration type. PCI: Using configuration type 1 Enumerating: AMD K8 Northbridge Enumerating: AMD K8 Enumerating: NSC 87360 Enumerating buses...PCI: pci_scan_bus for bus 0 PCI: 00:18.0 [1022/1100] enabled PCI: 00:18.1 [1022/1101] enabled PCI: 00:18.2 [1022/1102] enabled PCI: 00:18.3 [1022/1103] ops PCI: 00:18.3 [1022/1103] enabled amdk8_scan_chains max: 0 starting... Hyper transport scan link: 0 max: 1 PCI: 01:01.0 [1022/7454] enabled next_unitid: 0004 PCI: 01:04.0 [1022/7460] enabled next_unitid: 0008 HyperT reset needed HyperT reset not needed PCI: pci_scan_bus for bus 1 PCI: 01:01.0 [1022/7454] ops PCI: 01:01.0 [1022/7454] enabled PCI: 01:02.0 [1022/7455] bus ops PCI: 01:02.0 [1022/7455] enabled PCI: 01:04.0 [1022/7460] enabled PCI: 01:05.0 [1022/7468] bus ops PCI: 01:05.0 [1022/7468] enabled PCI: 01:05.1 [1022/7469] ops PCI: 01:05.1 [1022/7469] enabled PCI: 01:05.2 [1022/746a] enabled PCI: 01:05.3 [1022/746b] ops PCI: 01:05.3 [1022/746b] enabled PCI: 01:05.5 [1022/746d] enabled PCI: 01:05.6 [1022/746e] enabled PCI: pci_scan_bus for bus 2 PCI: 02:00.0 [1002/5157] enabled PCI: pci_scan_bus returning with max=02 PCI: pci_scan_bus for bus 3 PCI: 03:00.0 [1022/7464] ops PCI: 03:00.0 [1022/7464] enabled PCI: 03:00.1 [1022/7464] ops PCI: 03:00.1 [1022/7464] enabled PCI: 03:00.2 [1022/7463] ops PCI: 03:00.2 [1022/7463] enabled PCI: 03:01.0 [1022/7462] enabled PCI: 03:05.0 [14e4/1645] enabled PCI: pci_scan_bus returning with max=03 Hyper transport scan link: 0 new max: 3 Hypertransport scan link done amdk8_scan_chains max: 3 done PCI: pci_scan_bus returning with max=03 done Allocating resources... ASSIGN RESOURCES, bus 0 PCI: 00:18.0 c0 <- [0x00001000 - 0x00002fff] node 0 link 0 io PCI: 00:18.0 b8 <- [0xe0000000 - 0xf81fffff] node 0 link 0 mem ASSIGN RESOURCES, bus 1 PCI: 01:01.0 10 <- [0xe0000000 - 0xefffffff] prefmem PCI: 01:02.0 1c <- [0x00001000 - 0x00001fff] bus 2 io PCI: 01:02.0 24 <- [0xf0000000 - 0xf7ffffff] bus 2 prefmem PCI: 01:02.0 20 <- [0xf8000000 - 0xf80fffff] bus 2 mem ASSIGN RESOURCES, bus 2 PCI: 02:00.0 10 <- [0xf0000000 - 0xf7ffffff] prefmem PCI: 02:00.0 14 <- [0x00001000 - 0x000010ff] io PCI: 02:00.0 18 <- [0xf8000000 - 0xf800ffff] mem ASSIGNED RESOURCES, bus 2 PCI: 01:04.0 1c <- [0x00002000 - 0x00001fff] bus 3 io PCI: 01:04.0 24 <- [0xf8200000 - 0xf81fffff] bus 3 prefmem PCI: 01:04.0 20 <- [0xf8100000 - 0xf81fffff] bus 3 mem ASSIGN RESOURCES, bus 3 PCI: 03:00.0 10 <- [0xf8110000 - 0xf8110fff] mem PCI: 03:00.1 10 <- [0xf8111000 - 0xf8111fff] mem PCI: 03:00.2 10 <- [0xf8113000 - 0xf81130ff] mem PCI: 03:00.2 14 <- [0xf8114000 - 0xf811401f] mem PCI: 03:01.0 10 <- [0xf8112000 - 0xf8112fff] mem PCI: 03:05.0 10 <- [0xf8100000 - 0xf810ffff] mem ASSIGNED RESOURCES, bus 3 PCI: 01:05.0 00 <- [0x00000000 - 0xffffffff] io PCI: 01:05.0 00 <- [0x00000000 - 0xffffffff] mem PCI: 01:05.1 20 <- [0x000028e0 - 0x000028ef] io PCI: 01:05.2 10 <- [0x000028c0 - 0x000028df] io PCI: 01:05.5 10 <- [0x00002000 - 0x000020ff] io PCI: 01:05.5 14 <- [0x00002880 - 0x000028bf] io PCI: 01:05.6 10 <- [0x00002400 - 0x000024ff] io PCI: 01:05.6 14 <- [0x00002800 - 0x0000287f] io ASSIGNED RESOURCES, bus 1 ASSIGNED RESOURCES, bus 0 Allocating VGA resource done. Enabling resourcess... PCI: 00:18.0 cmd <- 00 PCI: 01:01.0 cmd <- 06 PCI: 01:02.0 bridge ctrl <- 003e PCI: 01:02.0 cmd <- 07 PCI: 02:00.0 cmd <- 83 PCI: 01:04.0 bridge ctrl <- 0000 PCI: 01:04.0 cmd <- 07 PCI: 03:00.0 cmd <- 02 PCI: 03:00.1 cmd <- 02 PCI: 03:00.2 cmd <- 02 PCI: 03:01.0 cmd <- 02 PCI: 03:05.0 cmd <- 02 PCI: 01:05.0 cmd <- 0f PCI: 01:05.1 cmd <- 01 PCI: 01:05.2 cmd <- 01 PCI: 01:05.3 cmd <- 00 PCI: 01:05.5 cmd <- 01 PCI: 01:05.6 cmd <- 01 PCI: 00:18.1 cmd <- 00 PCI: 00:18.2 cmd <- 00 PCI: 00:18.3 cmd <- 00 done. Initializing devices... PCI: 00:18.3 init NB: Function 3 Misc Control.. done. PCI: 01:02.0 init PCI: 01:05.0 init lpc_init PCI: 01:05.1 init ide_init IDE1 IDE0 PCI: 01:05.3 init PCI: 03:00.0 init USB: Setting up controller.. done. PCI: 03:00.1 init USB: Setting up controller.. done. PCI: 03:00.2 init USB: Setting up controller.. done. Devices initialized mmio_base: 3670016KB totalram: 256M Initializing CPU #0 cpufixup RAM: 0x00040000 KB Enabling cache... Setting fixed MTRRs(0-88) type: UC Setting fixed MTRRs(0-88) type: WB DONE fixed MTRRs Setting variable MTRR 0, base: 0MB, range: 256MB, type WB Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.1.4.0Fallback Mon Sep 8 16:21:32 CEST 2003 rebooting... Finding PCI configuration type. [..] now it repeatedly resets into pci configuration...
With 2 ram modules I found another interesting problem:
LinuxBIOS-1.1.4.0Fallback Mon Sep 8 16:21:32 CEST 2003 starting... setting up resource map.... done. Enabling routing table for node 00000000 done. Enabling UP settings Disabling read/write/fill probes for UP... done. coherent_ht_finalize done SMBus controller enabled Ram1.00 setting up CPU00 northbridge registers done. Ram2.00 133Mhz RAM: 0x00080000 KB Ram3 Initializing memory: done Ram4 TOP_MEM: 0000000020000000 Testing DRAM : 00000000-20000000 DRAM fill: 00000000-20000000 [..] Now the testing of the first 256 MB work fine, but the second 256 MB fail completely: 10000008:0fffffc8 1000000c:0fffffcc 10000010:0fffffd0 10000014:0fffffd4 10000018:0fffffd8 10000020:0fffffe0 10000024:0fffffe4 10000028:0fffffe8 1000002c:0fffffec 10000030:0ffffff0 10000040:10000000 10000044:0fffffc4 10000048:0fffffc8 1000004c:0fffffcc [..] 10000130:0ffffff0 10000134:10000034 10000138:100000b8 10000140:10000000 10000144:0fffffc4 10000148:0fffffc8 1000014c:0fffffcc 10000150:0fffffd0 10000154:0fffffd4 10000160:0fffffe0
So far...
Stefan
* YhLu YhLu@tyan.com [030908 18:55]:
HyperT reset needed HyperT reset not needed
In the scan_hypertranport_chain.c missed one "else"
YH.
./src/devices/hypertransport.c:hypertransport_scan_chain() should do the right thing, i.e. trigger a reset. And it seems the reset should go to PCIDEV(1,4,0), as on all other hammer boards. But obviously the code does not do a reset, or does it continue at the same PC afterwards?
SMBus controller enabled Ram1.00 setting up CPU00 northbridge registers done. Ram2.00
How can i verify that the smbus channels LinuxBIOS uses are correct for my board? The old solos only found RAM in the first socket it seems.
Hyper transport scan link: 0 max: 1 PCI: 01:01.0 [1022/7454] enabled next_unitid: 0004 PCI: 01:04.0 [1022/7460] enabled next_unitid: 0008 HyperT reset needed
[ LinuxBIOS should restart HERE ]
HyperT reset not needed PCI: pci_scan_bus for bus 1 PCI: 01:01.0 [1022/7454] ops
[..]
Stefan
-
Stefan Reinauer -
YhLu