Impossible restart after updating Ubuntu 7.04 to 7.10

[D.Larcher]

I made updating from Ubuntu 7.04. Everithing OK untill restart of computer.
Then it could not restart : display stayed black with following message :

[ 20.314954] PCI : Cannot allocate resource region 1 of device 0000:00:14.0

Updating made on 27/12/07. No failure in transmitted data since I made
previous attempt on 23/10/07 with exactly same problem.

I had to reload version 7.04 to run again, which could be perfectly loaded.
Impossible to run with updated Ubuntu 7.10

ProblemType: Bug
Architecture: i386
Date: Thu Dec 27 17:08:14 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 1:2.18.1-0ubuntu3
PackageArchitecture: i386
ProcCmdline: gnome-panel --sm-client-id default1
ProcCwd: /home/dominique
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-panel
Uname: Linux Ordi-Dom 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

[D.Larcher (do-larcher)]

*I tried to load Ubuntu 7.10 from DVD on my desktop computer (ACER
Aspire T671).
The DVD is ok, since it could load Version 7.10 on another desktop computer.
But same result with my ACER computer : message "PCI : cannot allocate
resource region 1 of device 0000:00:14.0"*

D.Larcher a écrit :
> Public bug reported:
>
> I made updating from Ubuntu 7.04. Everithing OK untill restart of computer.
> Then it could not restart : display stayed black with following message :
>
> [ 20.314954] PCI : Cannot allocate resource region 1 of device
> 0000:00:14.0
>
> Updating made on 27/12/07. No failure in transmitted data since I made
> previous attempt on 23/10/07 with exactly same problem.
>
> I had to reload version 7.04 to run again, which could be perfectly loaded.
> Impossible to run with updated Ubuntu 7.10
>
> ProblemType: Bug
> Architecture: i386
> Date: Thu Dec 27 17:08:14 2007
> DistroRelease: Ubuntu 7.04
> ExecutablePath: /usr/bin/gnome-panel
> Package: gnome-panel 1:2.18.1-0ubuntu3
> PackageArchitecture: i386
> ProcCmdline: gnome-panel --sm-client-id default1
> ProcCwd: /home/dominique
> ProcEnviron:
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=fr_FR.UTF-8
> SHELL=/bin/bash
> SourcePackage: gnome-panel
> Uname: Linux Ordi-Dom 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
>
> ** Affects: ubuntu
> Importance: Undecided
> Status: New
>
>

[Michael Nagel (nailor)]

is this still an issue with intrepid?

[D.Larcher (do-larcher)]

Yes, I still have black screen with Intrepid when I try to load it on my
disc having still Ubuntu 7.04, either with live CD or with Alternate.
I tried to reload and I made twice F6 on first panel.
Then I selected acpi=off
Then I could load Intrepid, but when restarting it stopped after writing
some lines and I could do nothing.

I regret to say that having eliminated Vista, I could easiley load
Ubuntu 7.04.
But after, impossible to load :
- 7.10
- 8.04.1
- 8.10

I would be glad to have some help for moving to Intrepid (but I am not
competent for programming !)

Thanks : D. Larcher

Michael Nagel a écrit :
> is this still an issue with intrepid?
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
>

[D.Larcher (do-larcher)]

I give you following information :

I tried again to install this day Hardy Heron from version 8.01.1 active CD

1) Normal installation : it does not load the kernel, the screen is
black with blinking dash
2) New installation with option : check the CD : nothing, screen black
3) New attempt making selection of language, then twice F6 and selecting
acpi=off

This time it loads the kernel and start apparently, with partition of disk.
But when restarting in normal mode : screen black with just blinking
dash. Nothing possible, even ctrl+alt+F1.

4) New attempt again with acpi=off and restart in recovery mode.
Then it starts but stop after following line :

*[ 22.637.118] io scheduler cfq registered (default)*

and further action impossible.

I made the same experience *with same result*s with version 8.1 Intrepid
Ibex : same message about cfq default.
I am condemned to stay with Feisty Fawn which could be installed without
problem.

I have following material :
Desk computer ACER type T671
Processor Intel dual core 2x1,8 Ghz
memory 895 Mo
Disk SATA 160 Go
Bios RO1-A3
Graphic card ATI Radeon Xpress 1250

Please help : D. Larcher

*I tried to load Ubuntu 7.10 from DVD on my desktop computer (ACER
Aspire T671).
The DVD is ok, since it could load Version 7.10 on another desktop computer.
But same result with my ACER computer : message "PCI : cannot allocate
resource region 1 of device 0000:00:14.0"*

D.Larcher a écrit :
> Public bug reported:
>
> I made updating from Ubuntu 7.04. Everithing OK untill restart of computer.
> Then it could not restart : display stayed black with following message :
>
> [ 20.314954] PCI : Cannot allocate resource region 1 of device
> 0000:00:14.0
>
> Updating made on 27/12/07. No failure in transmitted data since I made
> previous attempt on 23/10/07 with exactly same problem.
>
> I had to reload version 7.04 to run again, which could be perfectly loaded.
> Impossible to run with updated Ubuntu 7.10
>
> ProblemType: Bug
> Architecture: i386
> Date: Thu Dec 27 17:08:14 2007
> DistroRelease: Ubuntu 7.04
> ExecutablePath: /usr/bin/gnome-panel
> Package: gnome-panel 1:2.18.1-0ubuntu3
> PackageArchitecture: i386
> ProcCmdline: gnome-panel --sm-client-id default1
> ProcCwd: /home/dominique
> ProcEnviron:
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=fr_FR.UTF-8
> SHELL=/bin/bash
> SourcePackage: gnome-panel
> Uname: Linux Ordi-Dom 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
>
> ** Affects: ubuntu
> Importance: Undecided
> Status: New
>
>

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

What happens if you use clocksource=jiffies instead of acpi=off?

[D.Larcher (do-larcher)]

Fabio wrote:
> What happens if you use clocksource=jiffies instead of acpi=off?
>
>
Thanks but I am not very competent with programming.
How should I insert "jiffies" ? Write it on the line down the screen
after making F6 ?

I have put in french my problem (not solved) on the french Ubuntu forum
(FAQ) saying :

I have installed without any problem Ubuntu 7.04 on my desk computer ACER.

With 7.10 or 8.04 or 8.10 : impossible. Even the choice "check the CD"
makes a black screen.
With 8.04 or 8.1, making twice F6 and acpi=off, I can run on the live
CD, and when I decide "Install it", it runs, and makes so far partition
of the disk. Then the programm asks : make restart and then I have on
the screen : "starting up..." and black screen with blinking dash, and
keyboard or mouse are out of work.

When I do it again making "escape" and safe starting, then it runs
writing many lines and stop after the line :

[ 22.637118] io scheduler cfq registered (default)

Thanks if you can further help me

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

That's right: after pushing F6, replace acpi=off with clocksource=jiffies manually, then tell me if it works.

[D.Larcher (do-larcher)]

Thanks, I will try it, but later since I have only one desk computer
with only one OS. If installation collapse, I have to re-install Ubuntu
7.04...
I will do it after Christmas and report my conclusion.

(I cannot understand why 7.04 is OK and all other new devlopments cannot
be installed).

Thanks for your help.

Fabio wrote:
> That's right: after pushing F6, replace acpi=off with
> clocksource=jiffies manually, then tell me if it works.
>
>

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

One thing I forgot to mention: if you are able to install with acpi=off, you should also be able to boot with acpi=off. Try to:

1) Install from LiveCD with acpi=off
2) When the GRUB bootloader appears, use the arrow keys to select the desired boot option (typically the first) and press e
3) Go to the boot options row (it should be the second row) and press e again
4) Write acpi=off at the end of the line
5) Press ENTER (or ESC, i can't remember right now) to go back to the previous screen
6) Use the arrow keys to highlight the first row and press b to boot

[D.Larcher (do-larcher)]

Many thanks since I applied the below procedure and I could install
Hardy Heron 8.04. Hurrah !!!!!

It collapsed first time (black screen again), but I did it again after
switching off and it was succesfully.

Now, I have another problem : when I stop the computer and start again,
I have to apply your procedure again otherwise, I have black screen again !
It looks like whether the order acpi=off was not recorded in the programm.

Could you tell me how to arrange this problem ?

Fabio wrote:
> One thing I forgot to mention: if you are able to install with acpi=off,
> you should also be able to boot with acpi=off. Try to:
>
> 1) Install from LiveCD with acpi=off
> 2) When the GRUB bootloader appears, use the arrow keys to select the desired boot option (typically the first) and press e
> 3) Go to the boot options row (it should be the second row) and press e again
> 4) Write acpi=off at the end of the line
> 5) Press ENTER (or ESC, i can't remember right now) to go back to the previous screen
> 6) Use the arrow keys to highlight the first row and press b to boot
>
>

[D.Larcher (do-larcher)]

I discover another trouble when closing the computer : it does not want
to close and displays several lines of message about default on closing
process ! I have to switch off the line...
Please help !

Thanks for your help

Fabio a écrit :
> One thing I forgot to mention: if you are able to install with acpi=off,
> you should also be able to boot with acpi=off. Try to:
>
> 1) Install from LiveCD with acpi=off
> 2) When the GRUB bootloader appears, use the arrow keys to select the desired boot option (typically the first) and press e
> 3) Go to the boot options row (it should be the second row) and press e again
> 4) Write acpi=off at the end of the line
> 5) Press ENTER (or ESC, i can't remember right now) to go back to the previous screen
> 6) Use the arrow keys to highlight the first row and press b to boot
>
>

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

Try using clocksource=jiffies instead of acpi=off: it may get the shutdown to work properly.
If you don't want to type your boot options manually every time you have to edit the file /etc/grub/menu.lst.
If you have other questions that are not strictly related to this bug, please ask them on Ubuntu forums instead of Launchpad.

[D.Larcher (do-larcher)]

Thanks Fabio !
With clocksource=jiffies, the computer starts and close correctly.

Last problem : I cannot find the file /etc/grub/menu.lst.
I have only /etc/grub.d/20_memtest86+

Fabio a écrit :
> Try using clocksource=jiffies instead of acpi=off: it may get the shutdown to work properly.
> If you don't want to type your boot options manually every time you have to edit the file /etc/grub/menu.lst.
> If you have other questions that are not strictly related to this bug, please ask them on Ubuntu forums instead of Launchpad.
>
>

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

Whoops. I meant /boot/grub/menu.lst.

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

This is probably the same issue I'm experiencing: same error message, same workaround.
Booting without quiet also results in a clocksource unstable message.
I encountered it with a Sapphire PURE CrossfireX 770 equipped with an nvidia 8600.

the root cause could be this (taken from dmesg output):
[ 21.816031] ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SOR2 [0xb00-0xb0f]

device 0000:00:14.0 for me identifies the ATI SMBus.

I'm suspecting a BIOS bug.

[D.Larcher (do-larcher)]

Yes, I could also find it in the meantime.
But I am not competent in writing in Linux, and I had some difficulties
in writing the additional "clocksource=jiffies".
I entered as Root, made "vi...(file )", obtained the file .lst open and
entered "i" for insertion, but it has not been accepted and I canceled.
If you have a procedure to end definitely the matter, I thank you in
advance.

Fabio a écrit :
> Whoops. I meant /boot/grub/menu.lst.
>
>

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

Try using vim instead of vi

[D.Larcher (do-larcher)]

Thanks a lot Fabio for your help.
I could modify the starting of Grub
Now starting and closing are OK
I have made notification on the french Forum

Fabio a écrit :
> Try using vim instead of vi
>
>

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

I have nominated this for Jaunty, as it is a showstopper for some users: I think that the system should at least be clever enough to apply the workaround automatically.

[D.Larcher (do-larcher)]

As a shows topper perhaps. It's more obvious if you know that I am
pretty seventy years old this month of may and not at all skilled in
programming !

I do hope that the future system (version 9.04) will be clever enough to
start without help of a grandfather !

Best regards

Fabio a écrit :
> I have nominated this for Jaunty, as it is a showstopper for some users:
> I think that the system should at least be clever enough to apply the
> workaround automatically.
>
>

[Daniel Letzeisen (dtl131)]

Fabio, I have the same problem with an AMD 770 chipset (Biostar TA770SE motherboard). I experience random freezes, which I thought was due to my videocard having a bad V_BIOS checksum. My videocard is an ATI X300SE using the open-source radeon driver. I actually have a replacement (ATI 4550) being shipped to me this week.

I am getting this in my system messages on Ubuntu64 8.10, Ubuntu64 9.04, and Arch Linux64 using 2.6.28 kernel:
 ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SOR1 [0xb00-0xb0f]

I wonder if this is an inherent problem with this chipset (poor HPET support)?

Fabio, you said - "Booting without quiet also results in a clocksource unstable message."
If it's clocksource_tsc (the processor's clock), this is expected behavior because of power-saving schemes (PowerNow, Cool'n'Quiet,Speedstep)

I will keep testing, playing with using the jiffies clock sources and such and get back to you on this bug.

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

I had a look at Windows' control panel: it points out a conflict between ATI SMBus and a certain "high precision timer", which I suppose to be clocksource related. This is probably a consequence of a BIOS bug, but the average user will think "Windows boots and Linux doesn't, which means Linux sucks". This is precisely what Ubuntu is trying to avoid...

[D.Larcher (do-larcher)]

Yes absolutely. I was at first very happy with Ubuntu. But when I could
not update with new versions, I started to think : it's not yet reliable.

Fabio a écrit :
> I had a look at Windows' control panel: it points out a conflict between
> ATI SMBus and a certain "high precision timer", which I suppose to be
> clocksource related. This is probably a consequence of a BIOS bug, but
> the average user will think "Windows boots and Linux doesn't, which
> means Linux sucks". This is precisely what Ubuntu is trying to avoid...
>
>

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

This SEEMS to have been fixed in Jaunty. Unfortunately I'm experiencing two nasty new bugs and I'm trying to realize if they are related to this one before marking as fixed.

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

I'm marking this as fixed, as bug 366262 is probably not related to this. If you have the same problem after upgrading please reopen this bug.

[D.Larcher (do-larcher)]

Please cancel the second Item of this message : I could load easily
Ubuntu 9.10.
I had no additional order to print as e.g. clocksource=jiffies.
It's the first time I could do it so easily...Ubuntu makes improvements.
Thanks

Please note that due to an updating of yesterday 7/11/09, my desk
computer again could not restart as some months ago (I still have Ubuntu
8.04 LTS).

I had to reload 8.04 and modify again the starting by adding
''clocksource=jiffries''.
Now it can start, stop, and restart.

Note also that I tried to load Ubuntu 9.10 from a DVD.
I have seen the small disc Ubuntu blinking and apparently a lot of files
have been loaded from the DVD. But at the end, I got a black screen and
any attempt to do something was impossible excepted switching off the
power line.

LARCHER a écrit :
> Yes absolutely. I was at first very happy with Ubuntu. But when I
> could not update with new versions, I started to think : it's not yet
> reliable.
>
> Fabio a écrit :
>> I had a look at Windows' control panel: it points out a conflict between
>> ATI SMBus and a certain "high precision timer", which I suppose to be
>> clocksource related. This is probably a consequence of a BIOS bug, but
>> the average user will think "Windows boots and Linux doesn't, which
>> means Linux sucks". This is precisely what Ubuntu is trying to avoid...
>>
>>
>