It looks like your device is actually conflicting with itself and not
one of the other devices. You should double check how you (and/or base
classes) are specifying its address ranges and see if there's any
redundancy. It might help to make the bus print out what the conflicting
ranges actually are when it hits that panic to give you a better idea
where to look.

Gabe

Ong Wen Jian wrote:
> Hi Gabe,,
>
> I give you a more details about the error when I try to run the
> simulation ,
>
> My configs/common/FSConfig.py code is here....
>
> class BaseTsunami(Tsunami):
>            ethernet = NSGigE(pci_bus=0, pci_dev=1, pci_func=0)
>     +GraphicDevice = TDFXGPU(pci_bus=0,pci_dev=2,pci_func=0)
>         ide = IdeController(disks=[Parent.disk0, Parent.disk2],
>                             pci_func=0, pci_dev=0, pci_bus=0)
>
> ........other code.......
>
> self.tsunami = BaseTsunami()
>     self.tsunami.attachIO(self.iobus)
>     self.tsunami.ide.pio = self.iobus.port
>     self.tsunami.ethernet.pio = self.iobus.port
>     +self.tsunami.GraphicDevice.pio = self.iobus.port
>
> and the terminal when running in the full system simulation ..
>
> ==== m5 slave terminal: Terminal 0 ====
> M5 console: m5AlphaAccess @ 0xFFFFFD0200000000
> Got Configuration 623
> memsize 8000000 pages 4000
> First free page after ROM 0xFFFFFC0000018000
> HWRPB 0xFFFFFC0000018000 l1pt 0xFFFFFC0000040000 l2pt
> 0xFFFFFC0000042000 l3pt_rpb 0xFFFFFC0000044000 l3pt_kernel
> 0xFFFFFC0000048000 l2reserv 0xFFFFFC0000046000
> kstart = 0xFFFFFC0000310000, kend = 0xFFFFFC0000855898, kentry =
> 0xFFFFFC0000310000, numCPUs = 0x1
> CPU Clock at 2000 MHz IntrClockFrequency=1024
> Booting with 1 processor(s)
> KSP: 0x20043FE8 PTBR 0x20
> Console Callback at 0x0, fixup at 0x0, crb offset: 0x510
> Memory cluster 0 [0 - 392]
> Memory cluster 1 [392 - 15992]
> Initalizing mdt_bitmap addr 0xFFFFFC0000038000 mem_pages 4000
> ConsoleDispatch at virt 10000658 phys 18658 val FFFFFC00000100A8
> unix_boot_mem ends at FFFFFC0000076000
> k_argc = 0
> jumping to kernel at 0xFFFFFC0000310000, (PCBB 0xFFFFFC0000018180 pfn
> 1067)
> CallbackFixup 0 18000, t7=FFFFFC000070C000
> Linux version 2.6.13 ([email protected]
> <mailto:[email protected]>) (gcc version 3.4.3) #1 SMP Sun Oct 8
> 19:52:07 EDT 2006
> Booting GENERIC on Tsunami variation DP264 using machine vector DP264
> from SRM
> Major Options: SMP LEGACY_START VERBOSE_MCHECK
> Command line: root=/dev/hda1 console=ttyS0
> memcluster 0, usage 1, start        0, end      392
> memcluster 1, usage 0, start      392, end    16384
> freeing pages 1069:16384
> reserving pages 1069:1070
> SMP: 1 CPUs probed -- cpu_present_mask = 1
> Built 1 zonelists
> Kernel command line: root=/dev/hda1 console=ttyS0
> PID hash table entries: 1024 (order: 10, 32768 bytes)
> Using epoch = 1900
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 32768 (order: 5, 262144 bytes)
> Inode-cache hash table entries: 16384 (order: 4, 131072 bytes)
> Memory: 118784k/131072k available (3314k kernel code, 8952k reserved,
> 983k data, 224k init)
> Mount-cache hash table entries: 512
> SMP mode deactivated.
> Brought up 1 CPUs
> SMP: Total of 1 processors activated (4002.20 BogoMIPS).
> NET: Registered protocol family 16
> EISA bus registered
>
> and on the host terminal
>
> **** REAL SIMULATION ****
> info: Entering event queue @ 0.  Starting simulation...
> 4012053000: system.terminal: attach terminal 0
> fatal: system.iobus has two ports with same range:
>     system.tsunami.GraphicDevice-pioport
>     system.tsunami.GraphicDevice-pioport
>  @ cycle 10039875000
> [recvStatusChange:build/ALPHA_FS/mem/bus.cc, line 529]
>
> Any guide to solve this problem ?? As I think I just left a step to
> achieve the graphic device plugin into M5 simulator to enabling GPU
> research related activity on M5.
>
> regards
>
>  
> ONG WEN JIAN
> Student
> Department of Computer and Communication Systems Engineering,
> Faculty of Engineering, Universiti Putra Malaysia
> 43400 UPM Serdang, Selangor Darul Ehsan
> Tel : 014 - 930 2150 / 017 - 613 6231
> ------------------------------------------------------------------------
>
> _______________________________________________
> m5-users mailing list
> [email protected]
> http://m5sim.org/cgi-bin/mailman/listinfo/m5-users

_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users

Reply via email to