Hi Ben,
Ben Hoffmann wrote:
> Alex,
>
> The error appears in monocolor text full screen right after the Ubuntu
> Splash Screen: At first there are some text lines that pass by too
> fast for me to write down. Then there are three lines that keep
> repeating until I power down the PC. The repeating lines are:
>
> [319.07928] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
> frozen
> [319.07928] ata5.00: cmd ao/00:00 00:00 00:00 00:00 00:00 00:00
> 00:00/ao tag 0
> [319.07928] ata5.00: status: {DRDY}
>
> When these first start, the numbers at the beginning of the line are
> different, then they increase: They start similar to:
> [106.123456] ata1:00 etc......
>
> I also may have missed a colon or two as I hand recorded this.
>
Can you take a picture of it? You may want to try press shift up arrow
key to see (some of) the messages that scrolled by. Do that before the
next step or you lose scroll back option.
I don't have access to EMC system to verify this but you may want to try
reading messages on alternative console 3 or 4, 5?. Use Alt-F3 or Alt-F4
where some drivers drop more information during bootup. I tried that in
virtual EMC but did not work well because base OS interfered somehow.
> Side Note - I get the same thing on two PC's, and this is with the
> latest (as of March 12, 2009) "live CD" of Ubuntu 8.04 and Em2. I even
> downloaded the iso zip a second time to verify it. The two PC's work
It would be better to dump bits from CD you already have into a file and
check it's md5sum against the one you downloaded and I assume verified.
I would check BIOS. Thee might be something in the setup that's
confusing the kernel when it's loading the drivers or one of the drivers
fails to talk to the drive completely.
ata5.00: status: {DRDY}
drive ready? Would need to look into the driver src to see what that
means exactly. There seems to be an issue with ATA drive(r). I wonder
why your system reports ata5 and not ata0 or ata1 for the primary drive?
For comparison my kubuntu has the following in dmesg:
[ 71.298190] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000
irq 14
[ 71.298194] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf008
irq 15
[ 71.616159] ata1.00: ATAPI: LITE-ON LTR-48246S, SS04, max UDMA/33
[ 71.787642] ata1.00: configured for UDMA/33
[ 71.952956] ata2.00: ATA-7: Maxtor 6L200R0, BAH41G10, max UDMA/133
[ 71.952961] ata2.00: 398297088 sectors, multi 0: LBA48
[ 71.968850] ata2.00: configured for UDMA/100
It seems that ata5 is the device that's causing your kernel to hang
during bootup. I'm actually surprised to see my Maxtor (master drive) as
ata2 device and not ata1. In any case, your kernel tries to use ata5
device as a primary drive and hangs there.
> great, one with Vista, the other with XP, and both run the standard
those OS are the last thing to use for troubleshooting. Tektronix 465
would be better...
> Ubuntu Live booted from CD with no problem.
>
> So what am I doing wrong?
>
> Thanks!
> - Ben
>
>
--
Rafael
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
