Ubuntu

Gigabyte 965G-DS3 fails with PCI MMCONFIG access method

Reported by Ampinder on 2007-01-18
2
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Medium
Kyle McMartin

Bug Description

During the installation of feisty-desktop-i386 install, I got a error that pop-up on the screen that was saying :
The ext3 file system creation in partition #1 of IDE4 master (hdg) failed

I clicked OK and the installation stopped right there.

Ampinder (ajaysingh99) wrote :
Ampinder (ajaysingh99) wrote :
Ampinder (ajaysingh99) wrote :
Ampinder (ajaysingh99) wrote :
Ampinder (ajaysingh99) wrote :
Ampinder (ajaysingh99) wrote :
Ampinder (ajaysingh99) wrote :

According to syslog, hdg is broken. Please make sure this is (or not) the case testing the hd on another machine or swap it with another disk on the same system.

Fabio

Kyle McMartin (kyle) wrote :

This looks like a dead disk, please swap that disk with another and attempt to reproduce, please.

Ben Collins (ben-collins) wrote :

Marking as such. It's definitely hardware. Check drive and cables.

Thanks

Changed in linux-source-2.6.20:
importance: High → Undecided
status: Needs Info → Rejected
Ampinder (ajaysingh99) wrote :

I have changed the hard drive and I'm still getting the same error message:
The ext3 file system creation in partition #1 of IDE4 master (hdg) failed

This happens when I have entered all the necessary information and I just have to press the "Install" button.

what about cables

Changed in linux-source-2.6.20:
status: Rejected → Needs Info
Ampinder (ajaysingh99) wrote :

Hi,
       I have changed the cables also and I'm still getting the same error message.

Thanks

Kyle McMartin (kyle) wrote :

Could you please try with the following appended to the kernel command line (attach a dmesg please):

pci=nommconf

Ampinder (ajaysingh99) wrote :

Hi,
    I have used "pci=nommconf" and the installation was done completely.

Kyle McMartin (kyle) wrote :

What does that mean? You no longer had issues writing to the disk?

Ampinder (ajaysingh99) wrote :

Yes, I have entered your command and the installation work until the end. I was able to write on the disk, without having any error message getting displayed on the screen.

Kyle McMartin (kyle) wrote :

Ok. Thanks for testing! I'll try to come up with a more permanent solution.

Changed in linux-source-2.6.20:
assignee: nobody → kyle
status: Needs Info → Confirmed
Kyle McMartin (kyle) wrote :

Could you please post the "sudo dmidecode" output as an attachment? I will probably need it to fix this permanently on this board.

Thanks!
  Kyle

Kyle McMartin (kyle) wrote :

I know you guys are busy, so this is a total "wishlist" thing to ask you to do.

If on some of these boxes with strange failures you could test
http://www.linuxfirmwarekit.org/

That would be great and give us a much better understanding if it is the kernel which is broken, or the BIOS/ACPI/etc. of the board in question.

Ampinder (ajaysingh99) wrote :

Hi,
    As you requested Kyle, I'm adding the "dmidecode" output for you. I will shortly try the test kit that you have mentioned (http://www.linuxfirmwarekit.org/).

Kyle McMartin (kyle) wrote :

Thanks very much, Ampinder!

Kyle McMartin (kyle) wrote :

Working on it.

Changed in linux-source-2.6.20:
status: Confirmed → In Progress
Kyle McMartin (kyle) wrote :

Can you confirm that the "Subject" has the right board name?

Tollef Fog Heen (tfheen) wrote :

Bringing milestone forward.

Changed in linux-source-2.6.20:
importance: Undecided → Medium
Tollef Fog Heen (tfheen) wrote :

Moving milestone forward

Marc Tardif (cr3) wrote :

Kyle, the subject has the right board board name which is specifically GA-965G-DS3.

Kyle McMartin (kyle) on 2007-03-09
Changed in linux-source-2.6.20:
status: In Progress → Fix Committed
Kyle McMartin (kyle) wrote :

Ok. Decided just to disable it by default. We can also DMI blacklist (or whitelist) MMCONFIG on different boards based on HW Certification testing.

Changed in linux-source-2.6.20:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers