Restart function defective with Phoenix 1.26 BIOS

Bug #122159 reported by DaniFilth
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

What should happen: Computer should restart
What actually happens: Computer only partially powers down.

Hello Ubuntu team.

I have just started to use Ubuntu lately, and I found Ubuntu an awesome OS.
However, I have a problem with the 'restart' function in Ubuntu.

In details, the problem is :
-After I successfully got the CD by ordering from Ubuntu website, I installed it on my laptop. Nothing went wrong at this time.
-However, when I chose the 'restart' button to restart my laptop, the problem occurred. At first, everything closed, the screen flashed quickly several times, the Ubuntu logo appeared, the orange bar moved to its end. But when it was at the last step to power off the laptop, the screen remained black even after I waited for a while. Then I had no choice but to manually press the power button to turn my laptop off then turn it on again.
-This problem had never happened to me before when I used Windows. And the 'Turn Off' function worked well without errors, just only the 'Restart' function didn't work as it should.
-I have been looking for helps from my friends, some Ubuntu forums but none of them could give me an exact solution for this problem, either they said they never experienced this before, or they said they didn't know what kind problem it is. (I'm not sure if this may help you, but one friend of mine who is working in IT said that is because I use Ubuntu on a laptop with wireless device, but he said there is no patch to deal with it at the moment)

For more information, I'm using Ubuntu 7.04 with a laptop which has wireless devices, AMD Athlon XP-M Mobile, 768MB RAM, 40GB HD, the rest of the devices is all regular stuffs.

I am really impressed and interested in using and figuring out how Ubuntu works, but this is the problem that has been troubling me all the time.

Please help me to identify what that problem is, and give me your suggestions to solve it.
If you have time please send your guidances to my email, I will be grateful for your helps.

Yours sincerely,
An Ubuntu user.

Revision history for this message
Roberto Sarrionandia (rbs-tito) wrote :

Is the installation fully updated?

Revision history for this message
Roberto Sarrionandia (rbs-tito) wrote :

I believe this may be a duplicate of bug 122154.

Revision history for this message
DaniFilth (ddduong) wrote : Re: [Bug 122159] Re: Problem with the restart function

You mean the first time after Ubuntu was installed ? (Sorry, I'm newbie to
Ubuntu so I need to ask)
Yes, I did update when the pop-up message asked me to let Ubuntu update
(roughly about 61 new updates)

Thanks for your answer

On 26/06/07, Roberto Sarrionandia <email address hidden> wrote:
>
> Is the installation fully updated?
>
> ** Changed in: Ubuntu
> Status: New => Incomplete
>
> --
> Problem with the restart function
> https://bugs.launchpad.net/bugs/122159
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Yours sincerely
Duy Dat Duong a.k.a Dave

Revision history for this message
DaniFilth (ddduong) wrote : Re: Problem with the restart function

Oh, my bug is not a duplicate of the bug 122154 mentioned above, it's similar.
My problem happened with the 'Restart' option, while the 'Turn Off' option worked without errors.

Revision history for this message
Roberto Sarrionandia (rbs-tito) wrote :

We may also need some extra information

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at

Please also provide the output of

sudo dmidecode

Revision history for this message
DaniFilth (ddduong) wrote :

Ok, here are the outputs :

1. Linux danifilth-laptop 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux
2. The output is in the attachment file

Revision history for this message
DaniFilth (ddduong) wrote :
Download full text (15.5 KiB)

(cont - because I don't know how to attach 2 files at a time)

3. In the attachment

The output of "sudo dmidecode" is :

# dmidecode 2.8
SMBIOS 2.3 present.
49 structures occupying 1280 bytes.
Table at 0x000E7480.

Handle 0x0000, DMI type 0, 20 bytes
BIOS Information
        Vendor: Phoenix/FUJITSU
        Version: Version 1.26
        Release Date: 10/22/2004
        Address: 0xE0000
        Runtime Size: 128 kB
        ROM Size: 512 kB
        Characteristics:
                PCI is supported
                PC Card (PCMCIA) is supported
                PNP is supported
                BIOS is upgradeable
                BIOS shadowing is allowed
                Boot from CD is supported
                Selectable boot is supported
                EDD is supported
                3.5"/720 KB floppy services are supported (int 13h)
                Print screen service is supported (int 5h)
                8042 keyboard services are supported (int 9h)
                Serial services are supported (int 14h)
                Printer services are supported (int 17h)
                CGA/mono video services are supported (int 10h)
                ACPI is supported
                USB legacy is supported
                AGP is supported
                BIOS boot specification is supported
                Function key-initiated network boot is supported

Handle 0x0001, DMI type 1, 25 bytes
System Information
        Manufacturer: FUJITSU
        Product Name: 0000000000
        Version:
        Serial Number: 0000000000
        UUID: 69A21CC3-757F-11D9-8B14-000B5D77CCA0
        Wake-up Type: Power Switch

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
        Manufacturer: FUJITSU
        Product Name: FJNB167
        Version:
        Serial Number:

Handle 0x0003, DMI type 3, 13 bytes
Chassis Information
        Manufacturer: FUJITSU
        Type: Notebook
        Lock: Not Present
        Version:
        Serial Number:
        Asset Tag: <BAD INDEX>
        Boot-up State: Unknown
        Power Supply State: Unknown
        Thermal State: Unknown
        Security Status: Unknown

Handle 0x0004, DMI type 4, 32 bytes
Processor Information
        Socket Designation: Onboard
        Type: Central Processor
        Family: Athlon
        Manufacturer: Advanced Micro Devices, Inc.
        ID: A0 06 00 00 FF F9 83 03
        Signature: Family 6, Model A, Stepping 0
        Flags:
                FPU (Floating-point unit on-chip)
                VME (Virtual mode extension)
                DE (Debugging extension)
                PSE (Page size extension)
                TSC (Time stamp counter)
                MSR (Model specific registers)
                PAE (Physical address extension)
                MCE (Machine check exception)
                CX8 (CMPXCHG8 instruction supported)
                SEP (Fast system call)
                MTRR (Memory type range registers)
                PGE (Page global enable)
                MCA (Machine check architecture)
                CMOV (Conditional move instruction supported)
                PAT (Page attribute table)
                PSE-36 (36-bit page size extension)
              ...

description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Changed in linux-source-2.6.20:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Steve Conklin (sconklin) wrote :

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04. Many similar problems were fixed in the Jaunty release. To reopen the bug, click on the current status, under the Status column, and change the status back to "New". Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
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.