GUTSY - Won't boot after update - Tries to boot A USB FLASH/PEN Drive and then hangs if none is inserted then it just hangs with or without it inserted with both .13 & .14 kernels - .12 is unaffected.

here it is..

here are the

    *uname -a > uname-a.log
    *cat /proc/version_signature > version.log
    *dmesg > dmesg.log
    *sudo lspci -vvnn > lspci-vvnn.log

logs.

NOTE: These were taken when it was booted up in .12 kernel so I don't know if they will somehow show any errors or anything, but it might be worth a look.

I'm guessing this is a related bug, so I'm adding the comment here.

I, too, can not boot either the 2.6.22-13 or the 2.6.22-14 kernel, but can boot with the 2.6.22-12. I am running Gutsy with the latest dist-upgrade on a Thinkpad T61. The boot hangs at this line:

ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)

and then eventually drops into a busybox terminal.

Just for extra infos, here's the output of an lspci:

00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 0c)
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Contoller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HBM (ICH8M-E) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev a1)
03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
15:00.2 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
15:00.3 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 11)
15:00.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11)
15:00.5 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 11)

Please let me know what further ...

yes i can't also boot after the .14 kernel also, and still .12 works for me also. I'm adding the .14 to the description.

in the zip file you will find a copy of my fstab and menu.lst files, i opened them up and did a copy and paste to new documents/txt file just for some extra info.

strange tho urs is

"ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)"

a sata and i presume SCSI device while mine stops after in recovery mode on "25.067306 sd 0:0:0:0 [sda] Attached SCSI Removable disk."

which I have no SCSI disks or any removable ones at all and u use a thinkpad and I use a desktop, however I do now think that urs and mine Per B. Sederberg somehow are crossing paths or something in the kernels or hals, or something..

I'm attaching to this an histroy log of two updates on the 8t when this happened

it happened after the following update: Commit Log for Mon Oct 8 13:51:10 2007

After the time above I did a reboot and then that's when the .13 kernel quit on me, the second one was in the .12 kernel and so it's just there for more info. on all the updates for that day which is not the cause of the crash and so the second updates have nothing to do with the crash at all.

oh if anyone is wondering I did remove the options from the grubmenu on the affected .14 kernel and such and the same thing happens so I know it's not that at least.

i also can't boot after 22-13 kernel. 20-12 is ok. i've noticed that boot everytime stops in different places. Most often on "searching(?or smthng) for files needed to boot". I have Asus x50m, wifi swithed off, no usb-disks, no mmc/sd/ms - cards.
P.S. A couple of boot attempts stops only when KDE started. One time on "services", another on "peripherals".
P.P.S. Sorry for my bad english, i'm not native speaker))

ahh! sorry, not 20-12 kernel is stable! 20-16 ofcourse!

"ahh! sorry, not 20-12 kernel is stable! 20-16 ofcourse!"

?? are u saying that 2.6.22.12 doesn't work for u and that the feisty kernel 2.20.16 (i think that's the kernel i'm guessin) works for u, because I have no probs on my end with 2.6.22.12 kernel at all and not even with the updates again I myself had .13 working then did an update that day - rebooted and it hung and my last update before it all happened is in one of the above threads. By the way your english is fine...

i didn't try 2.6.22-12 at all. In GRUB i have

2.6.22-14-generic - can't boot
2.6.22-14(recovery mode)
2.6.22-13-generic -can't boot
2.6.22.386(?) -cant' boot
2.6.20.16-generic -actual working
2.6.20-16(recovery mode)
2.6.20-15-generic -didn't try
2.6.20-15(recovery mode)

The most intresting thing, that boot freezes at random point. -

ah! i see now, I hope they get it fixed, i think I might try going back to older updates on the history tab for some tests tonight, u know what - that's what i'll do if it does work that way i may be able to put this in the right section or add one, etc..

.386 tho should strange to me on that one.. :/

well I can't as the only version is the current one, grrr! well i'm stuck..

all i've done, its uninstall all entries in "adept", containing ".22-13" and ".22-14". now i boot without pressing "escape" every time and choosing "2.6.20-16-generic".

i'm just waiting for new releases...

So, what's the common denominator here?

We have three people who can not boot with the new kernels 2.6.22-13 or 2.6.22-14, but can boot with earlier kernels or releases of that kernel. If this problem was happening on all machines they would not of released those kernels.

Are we all on laptops with SATA hard drives? I have colleagues who have no problem booting into the 2.6.22-14 kernel on their desktop machine.

I am on a Thinkpad T61, which has one of the "blacklisted" Hitachi hard drives in it, though I have no idea what it means for a HD to be blacklisted. It was booting just fine in the 2.6.22-12 kernel, which I'm still running so that I can work.

Thanks for trying to solve this problem. There is as yet no indication that anyone who has anything to do with the kernel in Ubuntu has looked at this bug.

Best,
Per

"

So, what's the common denominator here?

We have three people who can not boot with the new kernels 2.6.22-13 or 2.6.22-14, but can boot with earlier kernels or releases of that kernel. If this problem was happening on all machines they would not of released those kernels.

Are we all on laptops with SATA hard drives? I have colleagues who have no problem booting into the 2.6.22-14 kernel on their desktop machine.

I am on a Thinkpad T61, which has one of the "blacklisted" Hitachi hard drives in it, though I have no idea what it means for a HD to be blacklisted. It was booting just fine in the 2.6.22-12 kernel, which I'm still running so that I can work.

Thanks for trying to solve this problem. There is as yet no indication that anyone who has anything to do with the kernel in Ubuntu has looked at this bug.

Best,
Per"

A) I am on a Dell 4600i Desktop Computer
B) I was able to boot up kernel .13 fine on this computer until after the updates in the update log http://launchpadlibrarian.net/9925843/updates%20history in the first updates as I always do an reboot afterwards to make sure. That's when it happened and .13 quit booting on me.
C) SATA is EIDE right?? lolz :D I forget because feisty was the only one that started using SCSI drivers :/

D:)

STORAGE INFORMATION
 SCSI device - scsi0
  Vendor: ATA
  Model: ST380013A
 SCSI device - scsi0
  Vendor: ATA
  Model: Maxtor 6Y080L0
 SCSI device - scsi1
  Vendor: MATSHITA
  Model: DVD-ROM SR-8583
 SCSI device - scsi1
  Vendor: HL-DT-ST
  Model: CD-RW GCE-8486B

So, from the launchpad update history it looks like the error was introduced in:

linux-ubuntu-modules-2.6.22-13-generic (2.6.22-13.33) to 2.6.22-13.34

I'm going to add linux-ubuntu-modules as the other error because the source is obviously not broken, it's some way in which they are compiling the modules.

P

again my just stops at when usb inserted at (both .13 and .14)

Loading
Loading please Wait.
-------------------------------------tries to load usb here assuming drive write cache
-------------------------------------tries to load usb here assuming drive write cache

0:0:0:0 is my usb drive by the way

on the .12 kernel it shows loading please wait and the show the kinit trying to resume from image messages and moves on, I always thought the modules were after that lolz... My hard drives are all 4s. They prob. are not going to fix this - i could be wrong however since it's close it seems like there have been no regular updates per day - maybe later on or else they decided to drop all for now until after Gutsy is released if so i'm going to update the .12 kernel with a patch to speed up the OS that a friend showed me and he said it worked for him and then i'll just remove the .13 kernel and .14 kernel...... errrr! but again I don't know nothing of that sort on where it stopped or not and I gotta look up what Baltix is.. ;)

No need to figure out the Baltix :) I accidentally added it in, but couldn't figure out how to remove it.

P

maybe, the same bug? https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/152820

I updated to Gutsy from my 7.04 with all the patches applied and using the alternate CD. After the update the new kernel 2.6.22-14-generic hangs and I am only able to boot using the old 7.04 kernel 2.6.20-16-generic.

Thanks

EXECTLY WHAT I HAVE! Unbootable notebook.

for last half-an-hour tried to boot on 2.6.22-14 kernel in recovery mode. It stops on different places every time. For one attempt i've even saw a user@mycomp sign. When i typed "startx" - KDE started but have freezed on "initializing services". But i'm sure, that it is not services problem, 'cause it hangs on different places of bootlog everytime.

It is critical problem!!, why nobody from development crew didn't even changed the status of this bug report??

I think my problem is related: After upgrade to 7.10 I cannot boot to kernel 2.6.22-14. Good old 2.6.20-16 works just fine.
New kernel always hangs after the line: "PCI: MSI quirk detected. MSI deactivated."

I've posted my information in https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/152820 but I think this is related, or this information might help. In my case the 2.6.22-14-386 kernel is detecting my hard drives as sdx instead of hdx, so nothing in fstab mounts. Kernel 2.6.20-16-386 works fine.

I got mine to work by removing evms and related packages, then mounting /dev/sdx manually. I believe if I edit fstab now, it will work.

thanks for that info. however odd tho I was messing around with boot paramenters and well this boot paramenter

notsc

to stop timestamps did the same thing for me.

Thanks for the info. again Jacob i might try that. :)

No problem. I'm not so sure these are related, but there was a reference to this bug in the fore-mentioned. Just wanted to post the workaround for my problem in case someone made their way here with the same issue.

Editing fstab to reference /dev/sda2 and /dev/sdb2 instead of /dev/hda2 and /dev/hdb2 worked fine. It seems as though the kernel is detecting my disks as SCSI rather than IDE, as they were detected previously. I will have to post my hardware configuration later.

n/m since u gave an example mine is already sda :)

here is mine:
................................
proc /proc proc defaults 0 0
# Entry for /dev/sda1 :
UUID=bb1bc2dd-9190-4494-a6cf-ec3c82ff1e52 / ext3 defaults,errors=remount-ro,noatime,data=writeback 0 1
# Entry for /dev/sda5 :
UUID=fcf15447-ab39-462c-b5e5-e34d8b62a375 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/scd1 /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/sdb1 /media/Old\040Backup ntfs-3g defaults,locale=en_US.UTF-8 0 0
tmpfs /dev/shm tmpfs defaults,ro 0 0
#usbfs
none /proc/bus/usb usbfs devgid=46,devmode=664 0 0
...............................................

I have the WinFast 748K7AA...

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!