reboot problem using linux 3.x.x

[devtry]

I observed this problem for the first time when I compiled and installed linux 3.2.1 on Ubuntu 11.04.

This is the problem (what happens step by step):

 - I reboot the computer (from Ubuntu)
 - the system shuts down correctly
 - the fan stops
 - the fan restarts
 - some seconds go by (when the manufacturer's name - the bios - should appear)
 - the computer is powered off after a sharp sound (as if I used the power button)
 - some seconds go by
 - the computer is automatically turned on and everything goes right
 - the last step doesn't happen if the supply if from the battery (the computer never turns on by itself)

I then tried Ubuntu 11.10 and now Ubuntu 12.04 (beta 1): the problem is still the same.

I also tried the latest kernel development version from "http://kernel.ubuntu.com/~kernel-ppa/mainline/": linux 3.3. The problem is still the same.

I read "https://wiki.ubuntu.com/BIOSandUbuntu" and I used the "reboot=<letter>" parameter to change reboot method: I tried with "a" and "p" but the problem was still the same; "reboot=b" (BIOS) resolved the problem.

On Ubuntu 11.04 I found out this:

 - last linux version without the problem: 2.6.39
 - first linux version with the problem: 3.0.0

This is description of the system from which I'm reporting the bug (and which is affected by the bug):

Hardware
-------------
Model: Acer Aspire 1810TZ
Motherboard: JM11-MS

BIOS
-------
Vendor: INSYDE
Version: v1.3314 (the latest version)
Release Date: 08/31/2010
ROM Size: 2048 kB

Operative System
----------------
Description: Ubuntu precise (development branch)
Release: 12.04

Kernel
----------
3.2.0-20-generic-pae (the whole 3.x.x series seems to be affected by the bug)

Most of these pieces of information should be avaiable in the attachments.

Please let me know if more details or other commands' outputs are needed.

Thank you for the help!

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-20-generic-pae 3.2.0-20.32
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12
Uname: Linux 3.2.0-20-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.95-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lorenzo 1658 F.... pulseaudio
Date: Sun Mar 25 20:04:56 2012
HibernationDevice: RESUME=UUID=8454997e-892a-4b53-876c-ccfea678074a
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
MachineType: Acer Aspire 1810TZ
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic-pae root=UUID=834c4fb1-e775-4492-ac70-caa36a4c18fd ro quiet splash vt.handoff=7
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/31/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: v1.3314
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JM11-MS
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: Aspire 1810TZ
dmi.product.version: v1.3314
dmi.sys.vendor: Acer

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[devtry (devtry)]

Thank you for your interest, Joseph Salisbury!

The bug affects all the 3.x.x kernel series (also the official Ubuntu one: 3.2.0-20), but you are right: it should also be an upstream bug.

I have never opened a bug upstream, but (since you say that it would be useful) I'll try.

I just need some free time to do it.

I'll be as quicker as I can!

[Leann Ogasawara (leannogasawara)]

Hi devtry,

You mentioned that using reboot=bios resolves your reboot issue. I've created a patch [1] and built a test kernel [2]. Could you please give it a test and confirm you are able to reboot without needing the reboot=bios workaround. Thanks in advance. I would also just like to note that I've tried submitting patches similar to this one upstream in the past but have received push back from the maintainers [3]. I haven't had time to provide an more systematic solution.

[1] http://people.canonical.com/~ogasawara/lp964687/0001-UBUNTU-SAUCE-no-up-x86-reboot-Make-Acer-Aspire-1810T.patch
[2] http://people.canonical.com/~ogasawara/lp964687/i386/generic-pae/
[3] https://lists.ubuntu.com/archives/kernel-team/2011-August/016888.html

[devtry (devtry)]

Hi Leann Ogasawara,

thank you for your answer to this report!

I have installed the modified kernel you provided (thanks for compiling it: you made me save a lot of time).
I confirm I am able to reboot without needing the "reboot=bios" workaround.

Which version is the kernel you have used? If it is 3.2.13 maybe I should try the one without the patch: just to be sure that the problem is not resolved by the latest stable kernel version.

I've read your patch; I had already had a look at "reboot.c" and I had noticed that there were some patches like yours and I thought: maybe something like this would resolve the problem, but I didn't know exactly how to do it. Thanks!

Should I still report the bug upstream? Maybe to work for a systematic solution?
I'm also wondering: the Aspire 1810TZ CPU is 64 bit; if I'm right with a 64 bit system you cannot use "reboot=bios" option.
Then the bug should be resolved in a different way? Or maybe the bug could be only for the 32 bit system?

Thanks again for the help!