Toshiba M1 Tecra does not reboot

Bug #190723 reported by Matt Burkhardt
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.20

Reboot goes to blank screen and sits. The only way to get it to reboot is to power off then power on again. This has happened with version 7.04 and 7.10

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
Leann Ogasawara (leannogasawara) wrote :

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

Changed in linux:
status: Incomplete → Won't Fix
Revision history for this message
Matt Burkhardt (matthewboh) wrote :

Still having this problem with Linux kernel 2.6.27-11-generic. I'll try and add the appropriate information

Changed in linux-source-2.6.20 (Ubuntu):
status: Won't Fix → New
tags: added: linux-2.6.27
Revision history for this message
Matt Burkhardt (matthewboh) wrote :
Download full text (5.6 KiB)

Okay - here's what I'm finding in the logs

auth.log

Apr 7 10:00:01 mlb-laptop CRON[14642]: pam_lwidentity(cron:account): PAM config: global:krb5_ccache_type 'FILE'
Apr 7 10:00:01 mlb-laptop CRON[14642]: pam_lwidentity(cron:account): failed to get GP info
Apr 7 10:00:01 mlb-laptop CRON[14642]: pam_lwidentity(cron:account): request failed
Apr 7 10:00:01 mlb-laptop CRON[14642]: pam_lwidentity(cron:account): User 'root' is not known.
Apr 7 10:00:01 mlb-laptop CRON[14642]: pam_lwidentity(cron:account): Returning 7 for user "root"
Apr 7 10:00:01 mlb-laptop CRON[14642]: pam_lwidentity(cron:session): PAM config: global:krb5_ccache_type 'FILE'
Apr 7 10:00:01 mlb-laptop CRON[14642]: pam_lwidentity(cron:session): request failed
Apr 7 10:00:01 mlb-laptop CRON[14642]: pam_lwidentity(cron:session): User 'root' is not known.

daemon.log

Apr 8 11:34:52 mlb-laptop init: tty4 main process (4176) killed by TERM signal
Apr 8 11:34:52 mlb-laptop init: tty5 main process (4177) killed by TERM signal
Apr 8 11:34:52 mlb-laptop init: tty2 main process (4184) killed by TERM signal
Apr 8 11:34:52 mlb-laptop init: tty3 main process (4185) killed by TERM signal
Apr 8 11:34:52 mlb-laptop init: tty6 main process (4186) killed by TERM signal
Apr 8 11:34:52 mlb-laptop init: tty1 main process (5778) killed by TERM signal
Apr 8 11:34:56 mlb-laptop jsvc.exec[5689]: Apr 8, 2009 11:34:56 AM org.apache.coyote.http11.Http11BaseProtocol pause INFO: Pausing Coyote HTTP/1.1 on http-8180
Apr 8 11:34:57 mlb-laptop jsvc.exec[5689]: Apr 8, 2009 11:34:57 AM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina
Apr 8 11:34:57 mlb-laptop jsvc.exec[5689]: Apr 8, 2009 11:34:57 AM org.apache.coyote.http11.Http11BaseProtocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8180
Apr 8 11:34:57 mlb-laptop jsvc.exec[5689]: Apr 8, 2009 11:34:57 AM org.apache.catalina.core.AprLifecycleListener lifecycleEvent INFO: Failed shutdown of Apache Portable Runtime
Apr 8 11:35:05 mlb-laptop acpid: client has disconnected
Apr 8 11:35:05 mlb-laptop chipcardd[5136]: chipcardd.c: 492: Watcher got a termination signal, will terminate child.
Apr 8 11:35:05 mlb-laptop chipcardd[5136]: chipcardd.c: 830: Terminating daemon.
Apr 8 11:35:05 mlb-laptop chipcardd[5137]: chipcardd.c: 488: Daemon got a termination signal
Apr 8 11:35:05 mlb-laptop chipcardd[5136]: chipcardd.c: 857: Daemon terminated, exiting.
Apr 8 11:35:05 mlb-laptop xinetd[5284]: Exiting...
Apr 8 11:35:10 mlb-laptop avahi-daemon[4581]: Got SIGTERM, quitting.
Apr 8 11:35:10 mlb-laptop avahi-daemon[4581]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.1.101.

messages

Apr 8 11:34:52 mlb-laptop bonobo-activation-server (mlb-9497): could not associate with desktop session: Failed to connect to socket /tmp/dbus-ujlQUXOsha: Connection refused
Apr 8 11:34:57 mlb-laptop bonobo-activation-server (mlb-9605): could not associate with desktop session: Failed to connect to socket /tmp/dbus-ujlQUXOsha: Connection refused
Apr 8 11:35:11 mlb-laptop exiting on signal 15

syslog

Apr 8 11:34:52 mlb-laptop init: tty4 main process (4176) killed by TERM signal
Apr 8 11:34:52 mlb-laptop i...

Read more...

Revision history for this message
Matt Burkhardt (matthewboh) wrote :

Sorry - found a bug in the Gnome System Log Viewer too - so here's the correct entries from auth.log

Apr 8 11:34:52 mlb-laptop gdm[5504]: pam_lwidentity(gdm:session): PAM config: global:krb5_ccache_type 'FILE'
Apr 8 11:34:52 mlb-laptop gdm[5504]: pam_unix(gdm:session): session closed for user mlb
Apr 8 11:34:52 mlb-laptop gdm[5504]: pam_lwidentity(gdm:setcred): PAM config: global:krb5_ccache_type 'FILE'
Apr 8 11:34:52 mlb-laptop gdm[5504]: pam_lwidentity(gdm:setcred): PAM config: global:krb5_ccache_type 'FILE'
Apr 8 11:34:52 mlb-laptop gdm[5504]: pam_lwidentity(gdm:setcred): request failed
Apr 8 11:34:52 mlb-laptop gdm[5504]: pam_lwidentity(gdm:setcred): User 'mlb' is not known.
Apr 8 11:34:52 mlb-laptop gdm[5504]: pam_lwidentity(gdm:setcred): request failed
Apr 8 11:34:52 mlb-laptop gdm[5504]: pam_lwidentity(gdm:setcred): User 'mlb' is not known.

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Feisty Fawn 7.04 has reached its end of life some months ago.
As a result, we are closing the linux-source-2.6.20 task.It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains -
http://www.ubuntu.com/getubuntu/releasenotes/904overview. If the issue still exists with the Jaunty
release, please update this report by changing the Status of the "linux (Ubuntu)"
task from "Incomplete" to "New". Also please be sure to run the command below
which will automatically gather and attach updated debug information to this
report. Thanks in advance.

apport-collect -p linux-image-2.6.28-11-generic 190723

Changed in linux-source-2.6.20 (Ubuntu):
status: New → Won't Fix
Changed in linux (Ubuntu):
status: Won't Fix → Incomplete
Revision history for this message
Matt Burkhardt (matthewboh) wrote :

I've upgraded to 9.04 and I'm still having the problem

I also tried to run apport-collect, but I selected read anything and then afterwards was told that I needed to select change anything - but there's no way to change the access rights.

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

Hi Matt,

Just want to try to keep this report up to date. Care to test and confirm this issue remains with the latest development release of Ubuntu (ie Karmic). ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, I'd be curious if you try booting with the 'reboot=b' boot option if that helps. To try booting with this option, press 'Escape' key at the 3 second pause by Grub bootloader. Then press 'e' (edit) on the buggy kernel entry, followed by 'e' again on the kernel line. Then add "reboot=b" without the quotes and press 'b' to boot. Thanks.

Revision history for this message
Matt Burkhardt (matthewboh) wrote :

Sorry Leann for taking so long.

I'm running 9.10 and I'm still having the problem. I tried booting with the reboot=b option and that didn't help out either. I'm now running Linux kernel 2.6.31-16

Changed in linux-source-2.6.20 (Ubuntu):
status: Won't Fix → New
Revision history for this message
Duane Hinnen (duanedesign) wrote :

changed "Status" from incomplete to "New" as the OP has supplied the last bit of requested information.

Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Matt,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 190723

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Feisty Fawn 7.04 has reached it's end of life more than one year ago.
Please don't reopen closed bugs.

Changed in linux-source-2.6.20 (Ubuntu):
status: New → Won't Fix
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
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.