ubuntu 6.10 installer crashed

Bug #97675 reported by Ryan
2
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 166, in ?
    main()
  File "/usr/bin/ubiquity", line 161, in main
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 57, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 305, in run
    self.process_step()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 856, in process_step
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 631, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code 139; see /var/log/syslog

Revision history for this message
Ryan (ryan-nelson01) wrote :
Revision history for this message
Ryan (ryan-nelson01) wrote :
Revision history for this message
Colin Watson (cjwatson) wrote :

Exit code 139 is a segmentation fault; in this particular context, that basically means that there's been a problem reading from the CD, and the squashfs errors in your logs support that theory. This is generally due to a faulty CD/DVD disk or drive, rather than being an installer bug as such. It may help to clean the CD/DVD, to burn the CD/DVD at a lower speed, or to clean the CD/DVD drive lens (cleaning kits are often available from electronics suppliers).

That said, there's a kernel oops in this syslog, which the kernel team should look at.

Changed in ubiquity:
status: Unconfirmed → Confirmed
Revision history for this message
Tim Gardner (timg-tpi) wrote :

This appears to be related to a CD media defect, or a host memory problem. The kernel fault is quite fundamental. I suggest running the memory test first, then the media check to make sure your platform is sane.

Revision history for this message
Ryan (ryan-nelson01) wrote : Re: [Bug 97675] Re: ubuntu 6.10 installer crashed

So i should use the memory test on the install CD? I have re-burned the CD
at the slowest speed and i am now going to test the memory to determine
where the problem might be.

On 3/29/07, Tim Gardner <email address hidden> wrote:
> This appears to be related to a CD media defect, or a host memory
> problem. The kernel fault is quite fundamental. I suggest running the
> memory test first, then the media check to make sure your platform is
> sane.
>
> --
> ubuntu 6.10 installer crashed
> https://launchpad.net/bugs/97675
>

Revision history for this message
Phillip Lougher (phillip-lougher) wrote :

Yes. Use the memory test on the install CD.

On 3/29/07, Ryan <email address hidden> wrote:
> So i should use the memory test on the install CD? I have re-burned the CD
> at the slowest speed and i am now going to test the memory to determine
> where the problem might be.
>
>
> On 3/29/07, Tim Gardner <email address hidden> wrote:
> > This appears to be related to a CD media defect, or a host memory
> > problem. The kernel fault is quite fundamental. I suggest running the
> > memory test first, then the media check to make sure your platform is
> > sane.
> >
> > --
> > ubuntu 6.10 installer crashed
> > https://launchpad.net/bugs/97675
> >
>
> --
> ubuntu 6.10 installer crashed
> https://launchpad.net/bugs/97675
>

Revision history for this message
Ryan (ryan-nelson01) wrote :

test 5 reported 6 errors - i assume this means that I have a bad stick of
memory that could have caused this problem. If you have any suggestions to
correcting the problem please let me know. Thanks for the help.

On 3/29/07, Phillip Lougher <email address hidden> wrote:
>
> Yes. Use the memory test on the install CD.
>
>
> On 3/29/07, Ryan <email address hidden> wrote:
> > So i should use the memory test on the install CD? I have re-burned the
> CD
> > at the slowest speed and i am now going to test the memory to determine
> > where the problem might be.
> >
> >
> > On 3/29/07, Tim Gardner <email address hidden> wrote:
> > > This appears to be related to a CD media defect, or a host memory
> > > problem. The kernel fault is quite fundamental. I suggest running the
> > > memory test first, then the media check to make sure your platform is
> > > sane.
> > >
> > > --
> > > ubuntu 6.10 installer crashed
> > > https://launchpad.net/bugs/97675
> > >
> >
> > --
> > ubuntu 6.10 installer crashed
> > https://launchpad.net/bugs/97675
> >
>
> --
> ubuntu 6.10 installer crashed
> https://launchpad.net/bugs/97675
>

Revision history for this message
Tim Gardner (timg-tpi) wrote :

An application of cash seems appropriate :)

Changed in linux-source-2.6.17:
status: Confirmed → Rejected
Revision history for this message
Phillip Lougher (phillip-lougher) wrote :

If you have more than one DIMM, it is always worth testing them individually to pin-point the bad DIMM.

When removing DIMMs or testing them individually make sure you observe any motherboard restrictions. Normally if you have more than one DIMM on a channel they must be matched, and if you're testing a single DIMM, there is often a recommended slot to put it.

If or once you've identified the offending DIMM, try to reinstall.

Revision history for this message
Phillip Lougher (phillip-lougher) wrote :

Obviously keep in mind you may have a faulty DIMM slot or motherboard. Although this is less likely than a faulty DIMM.

Revision history for this message
Ryan (ryan-nelson01) wrote :

I was actually able to solve this problem by chaging BIOS settings,
specifically I changed

"Configure SDRAM by SPD" from disabled to Enabled
"SDRAM frequency" changed to Auto
"SDRAM Command Rate" changed from 1T to 2T

I think this was just an issue of the ram not being able to keep up with the
commands

On 3/29/07, Phillip Lougher <email address hidden> wrote:
>
> Obviously keep in mind you may have a faulty DIMM slot or motherboard.
> Although this is less likely than a faulty DIMM.
>
> --
> ubuntu 6.10 installer crashed
> https://launchpad.net/bugs/97675
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.