Hi Brad, I found the problem that was causing this error. Specifically, it is this changeset:
changeset: 7909:eee578ed2130 user: Joel Hestness <[email protected]> date: Sun Feb 06 22:14:18 2011 -0800 summary: Ruby: Fix to return cache block size to CPU for split data transfers Link: http://reviews.m5sim.org/r/393/diff/#index_header Previously, I mentioned it was a couple of changesets prior to this one, but the changes between them are related, so it wasn't as obvious what was happening. In fact, this corresponds to the assert() for the block size you had put in to deal with x86 unaligned accesses, but then later removed because of LL/SC in Alpha. It's not clear to me why this is causing a problem, or rather why this doesn't return the default 64 byte block size from the ruby system, but commenting out those lines of code allowed it to work. Maybe Korey could confirm? Malek On Wed, Mar 9, 2011 at 8:24 PM, Beckmann, Brad <[email protected]> wrote: > I still have not been able to reproduce the problem, but I haven't tried in a > few weeks. So does this happen when booting up the system, independent of > what benchmark you are running? If so, could you send me your command line? > I'm sure the disk image and kernel binaries between us are different, so I > don't necessarily think I'll be able to reproduce your problem, but at least > I'll be able to isolate it. > > Brad > > > >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] >> On Behalf Of Malek Musleh >> Sent: Wednesday, March 09, 2011 4:41 PM >> To: M5 Developer List >> Subject: Re: [m5-dev] Ruby FS - DMA Controller problem? >> >> Hi Korey, >> >> I ran into a similar problem with a different benchmark/boot up attempt. >> There is another thread on m5-dev with 'Ruby FS failing with recent >> changesets' as the subject. I was able to track down the changeset which it >> was coming from, but I did not look further into the changeset as to why it >> was causing it. >> >> Brad said he would take a look at it, but I am not sure if he was able to >> reproduce the problem. >> >> Malek >> >> On Wed, Mar 9, 2011 at 7:08 PM, Korey Sewell <[email protected]> wrote: >> > Hi all, >> > I'm trying to run Ruby in FS mode for the FFT benchmark. >> > >> > However, I've been unable to fully boot the kernel and error with a >> > panic in the IDE disk controller: >> > panic: Inconsistent DMA transfer state: dmaState = 2 devState = 1 @ >> > cycle 62640732569001 >> > [doDmaTransfer:build/ALPHA_FS_MOESI_CMP_directory/dev/ide_disk.cc, >> > line 323] >> > >> > Has anybody run into a similar error or does anyone have any >> > suggestions for debugging the problem? I can run the same code using >> > the M5 memory system and FFT finishes properly so it's definitely a >> > ruby-specific thing. It seems to track this down , I could diff >> > instruction traces (M5 v. Ruby) or maybe even diff trace output from >> > the IdeDisk trace flags but those routes seem a bit heavy-handed >> considering the amount of trace output generated. >> > >> > The command line this was run with is: >> > build/ALPHA_FS_MOESI_CMP_directory/m5.opt >> configs/example/ruby_fs.py >> > -b fft_64t_base -n 1 >> > >> > The output in system.terminal is: >> > hda: M5 IDE Disk, ATA DISK drive >> > hdb: M5 IDE Disk, ATA DISK drive >> > hda: UDMA/33 mode selected >> > hdb: UDMA/33 mode selected >> > hdc: M5 IDE Disk, ATA DISK drive >> > hdc: UDMA/33 mode selected >> > ide0 at 0x8410-0x8417,0x8422 on irq 31 >> > ide1 at 0x8418-0x841f,0x8426 on irq 31 >> > ide_generic: please use "probe_mask=0x3f" module parameter for probing >> > all legacy ISA IDE ports >> > ide2 at 0x1f0-0x1f7,0x3f6 on irq 14 >> > ide3 at 0x170-0x177,0x376 on irq 15 >> > hda: max request size: 128KiB >> > hda: 2866752 sectors (1467 MB), CHS=2844/16/63 >> > hda:<4>hda: dma_timer_expiry: dma status == 0x65 >> > hda: DMA interrupt recovery >> > hda: lost interrupt >> > unknown partition table >> > hdb: max request size: 128KiB >> > hdb: 1008000 sectors (516 MB), CHS=1000/16/63 >> > hdb:<4>hdb: dma_timer_expiry: dma status == 0x65 >> > hdb: DMA interrupt recovery >> > hdb: lost interrupt >> > >> > Thanks again, any help or thoughts would be well appreciated. >> > >> > -- >> > - Korey >> > _______________________________________________ >> > m5-dev mailing list >> > [email protected] >> > http://m5sim.org/mailman/listinfo/m5-dev >> > >> _______________________________________________ >> m5-dev mailing list >> [email protected] >> http://m5sim.org/mailman/listinfo/m5-dev > > > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev > _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
