dapper on toshiba sat. m70: gnome immediately freezes with new kernels (incl. 2.6.15-23-386/686)

[florian]

new kernel - same problem with dapper
kernel 2.6.15-19-386, and maybe also -20, works fine for me. with all the new kernels, including the newest 2.6.15-23-386/686, i have always the same problems.
in the boot-process everything seems to work, but when gnome starts, it immediately freezes. with the 686 kernel i can't do anything(only hardboot),
with the 386-kernel it just freezes and then i can switch to another console [ctrl+alt+F2/3..etc]. but when i try to login again i get these error messages and can only hardboot:
(this is only the last part, which i was able to see and to write down...)

[4294758.630000] [<c013e7b3>] __do_IRQ+0x73/0xe0
 " [<c010597a>] do_IRQ+0x1a/0x30
 " [<c01040ea>] common_interrupt+0x1a/0x20
 " [<e08e5ffc>] scsi_request_fn+0x26c/0x3e0
                                                                                         [scsi_mod]
 " [<c01cc8d4>] blk_run_queue+0x44/0x50
 " [<e08e4fe5>] scsi_next_command+0x25/0x40
                                                                                         [scsi_mod]
 " [<e08e50f7>] scsi_end_request+0xb7/0x110
                                                                                         [scsi_mod]
 " [<e08e548c>] scsi_io_completion+0x16c/0x4e0
                                                                                         [scsi_mod]
 " [<e08bae72>] sd_rw_intr+0xa2/0x3c0 [sd_mod]
 " [<c011c6f3>] printk+0x13/0x20
 " [<e08e4d7b>] scsi_device_unbusy+0x6b/0x70
                                                                                         [scsi_mod]
 " [<e08dfcf3>] scsi_finish_command+0x13/0xd0
                                                                                         [scsi_mod]
 " [<e0909e9a>] ata_scsi_qc_complete+0x7a/0xa0
                                                                                              [libdata]
 " [<e087bbb9>] ahci_eng_timeout+0x69/0xb0 [ahci]
 " [<e08e4310>] scsi_error_handler+0x0/0x120
                                                                                         [scsi_mod]
 " [<e0909602>] ata_scsi_error+0x12/0x30 [libdata]
 " [<e08e43ba>] scsi_error_handler+0xaa/0x120
                                                                                         [scsi_mod]
 " [<c0130d53>] kthread+0x93/0xa0
 " [<c0130cc0>] kthread+0x0/0xa0
 " [<c0101385>] kernel_thread_helper+0x5/0x10
 " Code: 34 85 ff 74 0e 8b 45 10 57 8b 30 56 e8 61 9e 86 df 59 5b 8b 04 24 05 90 01 00 00 89 44 24 1c 83 c4 08 5b 5e 5f 5d e9 37 3b 96 df <0f> 0b 27 01 6f be 8e e0 eb 9a e8 98 d3 a0 df eb c5 89 58 04 89
[4294758.630000] <0>Kernel panic - not syncing: Fatal exception in interrupt
[4294758.630000]

after a hardboot most of the log-files are overwritten by the recovery-program...i will attach the only ones available concernig the boot-process with the 2.6.15-23-386 kernel.

Toshiba Satellite M70-194
Intel Pentium M 740, 1,73 GHz
ATI Mobility Radeon X600 SE, 128 MByte Videospeicher
S-ATA, 60 GByte

[florian (sputnik10)]

here is the "messages"-log

[florian (sputnik10)]

the syslog

[florian (sputnik10)]

and a "xorg-log"

see also Bug #42909

[florian (sputnik10)]

kern.log for 2.6.15-23-386 and 2.6.15-23-686

[florian (sputnik10)]

still does not work with the kernel-version

[Daniel T Chen (crimsun)]

Is the system usable if X.Org doesn't start? e.g., change the contents of /etc/X11/default-display-manager to be /bin/true

If it is (doesn't freeze), then please attach /etc/X11/xorg.conf.

[florian (sputnik10)]

i changed the contents of /etc/X11/default-display-manager to be /bin/true: normal login is possible, but when i start a programm (i.e. "sudo nano"), ubuntu crashes with the same/similar error message.
take a look at this thread...
http://www.ubuntuforums.org/showthread.php?t=185879&highlight=toshiba+m70

[aledin (al-dinicola)]

Same problem here, same laptop.
The kernel linux-image-2.6.15-25-386 hangs too.
Kernel linux-image-2.6.15-15-386 works (no crash, no problem); it's the kernel from Flight 4 cd.

[aledin (al-dinicola)]

Same problem with 2.6.15-26-386. Other than 2.6.15-15, the laptop works well with 2.6.16-ck12.

[Mathieu Bérard (mathieu-berard)]

I do possess this very same laptop model.
The ahci (for SATA hard drive access) module hang with dapper kernel.
The solution is to boot a working kernel, add this line in the
/etc/modprobe.d/blacklist file: "blacklist ahci"
You must regenerate your initramfs after doing that:
update-initramfs -u -k 2.6.15-25-386 (or whatever ubuntu kernel you intend to use)
Then try to reboot: the ata_piix driver will be used instead of ahci, and it works.

It is crucial to boot a working kernel to do the modification as any attempt to write on the hard drive on a faulty kernel is likely to just fail, crashing the computer.

By the way: I maintain a kernel module that implement some missing features
of this laptop (temperature reading, lcd backlight probe and control, multimedia
keys, Fn keys,....) it's at http://sourceforge.net/projects/omnibook/

As it is supported by HAL, it is used by gnome-power-manager and thus integrate well with the Gnome desktop.

[Ben Collins (ben-collins)]

This bug may be fixed in the current edgy developement system. In an effort to track this bug to our latest distribution, it is being targeted for edgy.

Please confirm whether this bug exists in edgy. If not, then please re-attach all related output (e.g. dmesg, oops output) while under edgy.

Latest Edgy CD's can be downloaded from:

http://cdimage.ubuntu.com/releases/edgy/knot-1/

If this image does not boot fom you, you can also download a current daily build from:

http://cdimage.ubuntu.com/daily-live/current/

Note that it may only be necessary to boot the LiveCD to see if your bug is fixed. In this case, you do not need to upgrade your installed system at all to confirm it. Certain bugs may require that you do an actual installation.

[Mathieu Bérard (mathieu-berard)]

I do confirm that I am unable to trigger that bug with edgy (2.6.17-6-686) kernel. That is, the provided ahci module is able to correctly drive the ICH6M SATA device.
This bug only concerns dapper kernel.

[Glebushka (venom2001)]

I am still unable to run kubuntu edgy knot 2 livecd with any of options on my TOSHIBA Satellite M70-192-RU. In usual mode i get a blank screen with a text cursor blinking, on safe video same but with white stripes all over the screen.
Also Dapper 6.06.1 alternate cd wont insall - halts in different places, usually at 89% installing additional software, but never after formatting.
Once it installed competely, but i got a kernel panic during boot.
Looks like it affects most linux distribs with kernel newer than 2.6.15.
I also tried openSuse 10.1 with 2.6.16.13 kernel - install hangs at the very beginning of copying files.
The only thing I was able to run on this laptop was mepis 3.4.3 using kernel 2.6.15, but mepis 6.0 based on ubuntu with same kernel wont install.

[Glebushka (venom2001)]

I do confirm that i am unable to boot current (120906) ubuntu edgy livecd with this laptop.
Maybe this page can help solve this
http://eavr.u-strasbg.fr/~loic/toshiba_install.html
it includes config for compiling kernel 2.6.15.2 to use on this laptop, and it seems to work fine, the only problem it's for Slackware.

[Glebushka (venom2001)]

Sorry for repeating, but i have to write that current alternate edgy install downloaded yesterday worked just fine and allowed to load x-window after installing current fglrx driver as described here
http://ubuntuforums.org/showthread.php?t=230565&highlight=toshiba+m70

[Thomas Hotz (thotz-deactivatedaccount)]

Is this now fixed for you in Edgy Eft / Feisty Fawn? Thanks in advance!

[florian (sputnik10)]

edgy works perfect on my Toshiba Satellite M70-194.
i have not yet tested feisty.
florian

[Thomas Hotz (thotz-deactivatedaccount)]

Thanks for your response. I'll close this bug now. If you have any problems with Feisty please feel free to open a new bug report.