Crash from ide_pci from generic.ko for jmicron controllers

Bug #84964 reported by Higinio Raventós
228
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Fix Released
Critical
Ben Collins
Nominated for Feisty by Moritz Schneider

Bug Description

Today I did a dist-upgrade and it downloaded many things, included the new Kernel 2.6.20-8 and installed them correctly. I am currently using the previous kernel version (2.6.20-6).

Since today everything had worked fine, but now when grub loads, I select the latest Kernel and the bootslplash appears, the progressbar does not make any progress. If I press Ctrl+Alt+F4 I see the message:

run_progess `/sbin/modprobe` abnormal exit

EDIT: Same bug in the new Kernel (2.6.20-9)
EDIT2: Same bug in the new Kernel (2.6.20-10)
EDIT3: Same bug in the new Kernel (2.6.20-11)
EDIT3: Same bug in the new Kernel (2.6.20-12)

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

Thanks for your bug report. Could you please try booting the new kernel without the 'usplash' and 'quiet' options and report back with what you find? Thanks in advance.

Revision history for this message
Higinio Raventós (higiraven) wrote :

I did that and now I can see the whole error message:

[1.979033] udevd-event [2023]: run_program: '/sbin/modprobe' abnormal exit

Revision history for this message
Higinio Raventós (higiraven) wrote :

more people in ubuntuforums seems to be having a similar problem. Do you need more information?

http://ubuntuforums.org/showthread.php?t=361007

Changed in linux-source-2.6.20:
assignee: brian-murray → nobody
importance: Undecided → Medium
status: Needs Info → Confirmed
Revision history for this message
Laurent GUERBY (laurent-guerby) wrote :

I have an all SATA system (AHCI activated in BIOS of Gigabyte GA-965GM-S2 motherboard, 64 bits core 2 duo) and 2.6.20-8 freezes during boot before mounting disks whereas 2.6.20-6 boot and works just fine.

Revision history for this message
William Chen (revite) wrote :

I am getting the same error except on my computer the error is followed by:

BusyBox v1.1.3(Debian 1:1.1.3-3ubuntu2) Built-in shell (ash)
Enter `help` for a list of built in commands

/bin/sh: can't access tty; job control turned off
(initramfs)

Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

I'm getting the same error message with Feisty Herd 4.

run_program: '/sbin/modprobe' abnormal exit

Revision history for this message
Seif Lotfy (seif) wrote :

I also get the same error using an Asus P5B-VM DO motherboard (G965) and an core 2 duo
HDD is SATA working as a raid and IDE DVD-RAM

but even the 2.6.20-6 amd 5 don't work
thats why i am using the 2.16.17-10 kernel

Revision history for this message
Gaëtan Petit (gaetanp) wrote :

does some of those bug report are similar to this : https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/83313

We are many users to report serial ata not to work in feisty

Please check if your S-ata drives are recognized

Revision history for this message
Higinio Raventós (higiraven) wrote :

I have also got a S-ATA drive...

I think this should be a critical bug as all the people with S-ATA drives cannot even boot.

Revision history for this message
Laurent GUERBY (laurent-guerby) wrote :

Info on my system.

Revision history for this message
FiNeX (finex) wrote :

I've tried both herd3 and herd4: the system doesn't correctly recognise my SATA HD. This is the controller:
00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02)

I've this errors on dmesg (and on the others logfiles)

Feb 19 10:08:59 ubuntu kernel: [ 2403.853220] hdg: DMA interrupt recovery
Feb 19 10:08:59 ubuntu kernel: [ 2403.853226] hdg: lost interrupt
Feb 19 10:09:19 ubuntu kernel: [ 2423.828414] hdg: dma_timer_expiry: dma status == 0x24

From /dev/ i see hdg, hgd1,..., hdg7 (the partition of my SATA HD) but them are not accessible. If I try to mount or fdisk the shell freze and on the log file I've:

Feb 19 10:08:59 ubuntu kernel: [ 2403.853220] hdg: DMA interrupt recovery
Feb 19 10:08:59 ubuntu kernel: [ 2403.853226] hdg: lost interrupt
Feb 19 10:09:19 ubuntu kernel: [ 2423.828414] hdg: dma_timer_expiry: dma status == 0x24

Revision history for this message
Higinio Raventós (higiraven) wrote :

BTW, since Kernel 2.6.17 I get this warning message just after selecting the kernel I'm booting:

"Cannot allocate resource region 2 of device 3.00.0
Cannot allocate resource region 3 of device 3.00.0"

If I "lspci" that device is:

03:00.0 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 02)

I think it is related to this bug.

Revision history for this message
Higinio Raventós (higiraven) wrote :

Today I downloaded Xubuntu 7.04 Herd 4.

While booting, I got exactly the same error followed by:

"/bin/sh/: can't access tty; job control turned off."

Hope it helps.

Revision history for this message
Seif Lotfy (seif) wrote :

I think it has soemthing to do with jmicron
i turned it off in the bios and now it boots
i need it though for my ide dvd-rom

Revision history for this message
Higinio Raventós (higiraven) wrote :

Yes! That's it. I turned off in the BIOS the JMicron SATA/PATA controller and now it works. I cannot use my CD/DVD-ROM now but can boot.

Revision history for this message
Seif Lotfy (seif) wrote : Re: [Bug 84964] Re: Kernel 2.6.20-8 does not boot

try turning off your jmicron controller from the bios
you wil lget ti to work but without the dvd-ram :)

On Sun, 2007-02-18 at 10:43 +0000, Seif Lotfy wrote:
> I also get the same error using an Asus P5B-VM DO motherboard (G965) and an core 2 duo
> HDD is SATA working as a raid and IDE DVD-RAM
>
> but even the 2.6.20-6 amd 5 don't work
> thats why i am using the 2.16.17-10 kernel
>

Revision history for this message
aapgorilla (aapgorilla) wrote : Re: Kernel 2.6.20-8 does not boot

i have the same bug but no options in bios and i agree it is a critical bug

i also think it might be a duplicate of https://launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/78288

Revision history for this message
Ben Collins (ben-collins) wrote :

Can someone send dmesg output for this?

Changed in linux-source-2.6.20:
importance: Medium → High
Revision history for this message
Higinio Raventós (higiraven) wrote :
Download full text (28.2 KiB)

Sure.

higi@HIGILINUX:~$ dmesg
[ 0.000000] Linux version 2.6.20-8-generic (root@vernadsky) (gcc version 4.1.2 20070129 (prerelease) (Ubuntu 4.1.1-31ubuntu2)) #2 SMP Tue Feb 13 05:18:42 UTC 2007 (Ubuntu 2.6.20-8.14-generic)
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] sanitize start
[ 0.000000] sanitize end
[ 0.000000] copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end: 000000000009fc00 type: 1
[ 0.000000] copy_e820_map() type is E820_RAM
[ 0.000000] copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end: 00000000000a0000 type: 2
[ 0.000000] copy_e820_map() start: 00000000000e4000 size: 000000000001c000 end: 0000000000100000 type: 2
[ 0.000000] copy_e820_map() start: 0000000000100000 size: 000000007fea0000 end: 000000007ffa0000 type: 1
[ 0.000000] copy_e820_map() type is E820_RAM
[ 0.000000] copy_e820_map() start: 000000007ffa0000 size: 000000000000e000 end: 000000007ffae000 type: 3
[ 0.000000] copy_e820_map() start: 000000007ffae000 size: 0000000000032000 end: 000000007ffe0000 type: 4
[ 0.000000] copy_e820_map() start: 000000007ffe0000 size: 0000000000020000 end: 0000000080000000 type: 2
[ 0.000000] copy_e820_map() start: 00000000fee00000 size: 0000000000001000 end: 00000000fee01000 type: 2
[ 0.000000] copy_e820_map() start: 00000000ffb00000 size: 0000000000500000 end: 0000000100000000 type: 2
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000007ffa0000 (usable)
[ 0.000000] BIOS-e820: 000000007ffa0000 - 000000007ffae000 (ACPI data)
[ 0.000000] BIOS-e820: 000000007ffae000 - 000000007ffe0000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000007ffe0000 - 0000000080000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
[ 0.000000] 1151MB HIGHMEM available.
[ 0.000000] 896MB LOWMEM available.
[ 0.000000] found SMP MP-table at 000ff780
[ 0.000000] Entering add_active_range(0, 0, 524192) 0 entries of 256 used
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0 -> 4096
[ 0.000000] Normal 4096 -> 229376
[ 0.000000] HighMem 229376 -> 524192
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0 -> 524192
[ 0.000000] On node 0 totalpages: 524192
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 4064 pages, LIFO batch:0
[ 0.000000] Normal zone: 1760 pages used for memmap
[ 0.000000] Normal zone: 223520 pages, LIFO batch:31
[ 0.000000] HighMem zone: 2303 pages used for memmap
[ 0.000000] HighMem zone: 292513 pages, LIFO batch:31
[ 0.000000] DMI 2.4 present.
[ 0.000000] ACPI: RSDP (v000 ACPIAM ) @ 0x000fae40
[ 0.000000] ACPI: RSDT (v001 A M I OEMRSDT 0x08000610 MSFT 0x00000097) @ 0x7ffa0000
[ 0.000000] ACPI: FADT (v002 A M I...

Revision history for this message
Higinio Raventós (higiraven) wrote :

I took last dmesg on Kernel 2.6.20-8 with JMicron Controller disabled. Do you need me to do it in Kernel 2.6.20-6 with JMicron Controller enabled?

Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Please post the output _with_ JMicron Controller enabled.

Changed in linux-source-2.6.20:
status: Confirmed → Needs Info
Revision history for this message
Higinio Raventós (higiraven) wrote :
Download full text (30.0 KiB)

higi@HIGILINUX:~$ dmesg
[ 0.000000] Linux version 2.6.20-6-generic (root@palmer) (gcc version 4.1.2 20070106 (prerelease) (Ubuntu 4.1.1-21ubuntu7)) #2 SMP Wed Jan 31 20:53:39 UTC 2007 (Ubuntu 2.6.20-6.11-generic)
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] sanitize start
[ 0.000000] sanitize end
[ 0.000000] copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end: 000000000009fc00 type: 1
[ 0.000000] copy_e820_map() type is E820_RAM
[ 0.000000] copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end: 00000000000a0000 type: 2
[ 0.000000] copy_e820_map() start: 00000000000e4000 size: 000000000001c000 end: 0000000000100000 type: 2
[ 0.000000] copy_e820_map() start: 0000000000100000 size: 000000007fea0000 end: 000000007ffa0000 type: 1
[ 0.000000] copy_e820_map() type is E820_RAM
[ 0.000000] copy_e820_map() start: 000000007ffa0000 size: 000000000000e000 end: 000000007ffae000 type: 3
[ 0.000000] copy_e820_map() start: 000000007ffae000 size: 0000000000032000 end: 000000007ffe0000 type: 4
[ 0.000000] copy_e820_map() start: 000000007ffe0000 size: 0000000000020000 end: 0000000080000000 type: 2
[ 0.000000] copy_e820_map() start: 00000000fee00000 size: 0000000000001000 end: 00000000fee01000 type: 2
[ 0.000000] copy_e820_map() start: 00000000ffb00000 size: 0000000000500000 end: 0000000100000000 type: 2
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000007ffa0000 (usable)
[ 0.000000] BIOS-e820: 000000007ffa0000 - 000000007ffae000 (ACPI data)
[ 0.000000] BIOS-e820: 000000007ffae000 - 000000007ffe0000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000007ffe0000 - 0000000080000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
[ 0.000000] 1151MB HIGHMEM available.
[ 0.000000] 896MB LOWMEM available.
[ 0.000000] found SMP MP-table at 000ff780
[ 0.000000] Entering add_active_range(0, 0, 524192) 0 entries of 256 used
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0 -> 4096
[ 0.000000] Normal 4096 -> 229376
[ 0.000000] HighMem 229376 -> 524192
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0 -> 524192
[ 0.000000] On node 0 totalpages: 524192
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 4064 pages, LIFO batch:0
[ 0.000000] Normal zone: 1760 pages used for memmap
[ 0.000000] Normal zone: 223520 pages, LIFO batch:31
[ 0.000000] HighMem zone: 2303 pages used for memmap
[ 0.000000] HighMem zone: 292513 pages, LIFO batch:31
[ 0.000000] DMI 2.4 present.
[ 0.000000] ACPI: RSDP (v000 ACPIAM ) @ 0x000fae40
[ 0.000000] ACPI: RSDT (v001 A M I OEMRSDT 0x08000610 MSFT 0x00000097) @ 0x7ffa0000
[ 0.000000] ACPI: FADT (v002 A M I OEMFACP ...

Revision history for this message
Laurent GUERBY (laurent-guerby) wrote :

Ben, dmesg lspci etc are in my attachment above "2007-02-18 16:28:59 UTC"

Revision history for this message
Mark McKenzie (mark-errai) wrote :

Hi

I recently did an upgrade from Edgy to Feisty on AMD64 (core 2 duo on an intel p965 chipset w/jmicron PATA) and found the same issue

I nailed it down to a race condition in the boot process. Basically, when you're booting off your local disk, the "piix" driver (the old driver) always wins, and since it seems broken the system doesn't boot. However, when you're booting off CD the ata_piix driver sometimes wins, and you can access your disk.

Proof that it was the piix driver: I ripped apart the initrd for 2.6.20-8, removed /lib/modules/*/kernel/drivers/ide/pci/*, and rebuilt it. Worked like a treat.

A solution might be to have the libata based drivers attempt to load in the boot process before the old style ones. The older drivers don't seem to cause any issues if they're loaded after libata.

Changed in linux-source-2.6.20:
status: Needs Info → Confirmed
Revision history for this message
Ben Collins (ben-collins) wrote : Re: modprobe abnormal exit - Kernel 2.6.20-8 does not boot

I think this is the correct. The piix driver was not supposed to be used, and I have corrected the code which is supposed to disable it for chipsets where ata_piix is preferred.

Changed in linux-source-2.6.20:
assignee: nobody → ben-collins
status: Confirmed → Fix Committed
Revision history for this message
Higinio Raventós (higiraven) wrote :

Same problem with the new Kernel 2.6.20-9, shall I report a new bug?

description: updated
Revision history for this message
Shane (duairc) wrote : Re: modprobe abnormal exit - Kernel 2.6.20-8/9 does not boot

Yeah, this bug occurs in the new kernel (2.6.20-9). I'm using an iBook G4, and I haven't had this problem with -8 or -6. This is frustrating as -9 was supposed to fix the wireless drivers that -8 broke.

Revision history for this message
Moritz Schneider (neoxan) wrote :

Got the same problem. With herd 4 and the daily build from today. I also got JMicron Controller, but i cannot disable it because i need it for my Drive.

Revision history for this message
Philippe Escarbassière (phil-esc) wrote :

Same issue with -8 and -9 kernel but not with -6 (on a Gigabyte GA-965P-DS4)

Revision history for this message
pidgas (pidgas) wrote :

I'm running feisty on an Asus P5W DH Deluxe. It _has_ a JMicron JMB363 SATA controller in it, but it also has a Intel ICH7R Southbridge which controls 3 SATA connectors on the board.

My drives are connected to the Intel ICH7R connectors, not the JMicron. Nothing is plugged into the JMicron and I get the exact same behavior as that described here. Specifically, the boot drive is not recognized, modprobe complains and I end up in Busybox (if I wait long enough). The behavior has been present since the update to 2.6.20-8 and persists in 2.6.20-9. I have not tried disabling the JMicron controller, but will be glad to.

Pid

Revision history for this message
pidgas (pidgas) wrote :

Disabled JMicron controller, and things booted right up. Didn't miss a beat with 2.6.20-9.

Pid

Revision history for this message
clinteas (terminate111) wrote :

This bug still exists on Herd-5 for me,on an ASUS P5b MoBo,C2D E6600 Processor,JMicron Controller.Disabling the controller makes it bootable,just without CD-Rom,as mentioned before.

clint

Revision history for this message
clinteas (terminate111) wrote :

Interestingly,the above (disabling the JMicron controller makes feisty bootable)only applies to the LiveCD of Herd-5,once installed/upgraded to Herd-5 via apt on disk,the Kernel 2.6.20-9 does not boot,even with the controller disabled !

clint

Revision history for this message
Higinio Raventós (higiraven) wrote :

I have got P5b mobo and E6600 as well. With Herd5, nothing has changed. If I disable JMicron Controller, it boots, if I don't, it doesn't boot. Nothing new.

Revision history for this message
Francesco Fumanti (frafu) wrote :
Revision history for this message
Francesco Fumanti (frafu) wrote :

I succeeded in booting by adding irqpoll to the boot options of the 2.6.20-9 kernel. (as suggested in duplicate #78288 of the bug)

Revision history for this message
Higinio Raventós (higiraven) wrote :

adding irqpoll option did not do anything for me. Still freezing.

Revision history for this message
clinteas (terminate111) wrote :

I have to say,im rather disappointed with how this bug is handled....
I assembled a testing PC tonight,P4 3 GB,gigabyte board,nothing flash,and it booted the Herd-4 CD nicely,installed everything in a flash,no worries at all,works like a charm.
We have known about this bug for what,3 months now,and no fix on the horizon,any Linuxer with a >2.6.17 kernel and /or c2d processor is just fucked??
Mr Shuttleworth,have a look at whos getting your funds !!!

Revision history for this message
Francesco Fumanti (frafu) wrote :

Maybe it is finally not a duplicate of bug #78288, because I am not the only one to report on #78288 to succeed to boot with the irqpoll option...

Sorry if I did a mistake.

Revision history for this message
Higinio Raventós (higiraven) wrote :

I do not know your criteria for setting what the importance of a bug is.

What I know is that a _huge_ amount of people are having this problem and cannot boot. I usually write in the ubuntu forums, and there are _A LOT_ of posts related to this issue.

Shouldn't this bug be assigned as _CRITICAL_? I am just telling what my opinion is, but this issue has meant an exceptionally important regression for Ubuntu.

Kyle McMartin (kyle)
Changed in linux-source-2.6.20:
importance: High → Critical
status: Fix Committed → Confirmed
description: updated
Changed in linux-source-2.6.20:
status: Confirmed → Fix Committed
description: updated
description: updated
Changed in linux-source-2.6.20:
status: Fix Committed → Fix Released
Changed in linux-source-2.6.20:
status: Fix Released → Confirmed
Changed in linux-source-2.6.20:
assignee: ben-collins → ubuntu-kernel-team
Changed in linux-source-2.6.20:
assignee: ubuntu-kernel-team → ben-collins
status: Confirmed → In Progress
Changed in linux-source-2.6.20:
status: In Progress → Fix Committed
Changed in linux-source-2.6.20:
status: Fix Committed → Fix Released
88 comments hidden view all 168 comments
Revision history for this message
aftertaf (david-wooffindin) wrote :

Hi,

Since I switched to Feisty i've had this problem too.

I have IDE Drives & dvd, and an integrated S-ATA controlller that I do not yet use and cannot deactivate in BIOS.

I have not yet tried any of the boot options specified, I will inform you when i test reboot with new kernel.

A Question. How can I identify the S-ATA controller chip? other than dmesg with this line:
00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02)

Thanks,

David

Revision history for this message
Memo (memo-cj-ro) wrote :

The bug is fixed. You still can't boot a daily build if it doesn't have included the 2.6.20-13 kernel. You can check if the fix is included by checking the cd's manifest:

For example:
feisty-desktop-amd64.manifest
or
feisty-desktop-i386.manifest

It's useless to download the latest image for those that this bug had affected unless you see that in the manifest it is included the 2.6.20-13 kernel.

Revision history for this message
UBfusion (ubfusion) wrote :

@Gheorge: Heh, it took me 5 minutes to realize that you mean the feisty-desktop-amd64.manifest on the website and not a file in the iso....

If you mean to look at the "linux-generic" line, 0326 has 2.6.20.12.9

So it seems we have to wait one more day.... (unless there's a 0326.1 under way) Of course the CD does not boot.

Revision history for this message
Higinio Raventós (higiraven) wrote :

i cannot reproduce the bug anymore with linux-image-2.6.20-13-generic. Fixed.

Revision history for this message
Peter.J (peter-johnsson) wrote :

Is there any way i can merge the new kernel (where to download?) into the iso of the daily build i currently have? Instead of waiting for days for it to be included in the next release.

Revision history for this message
Marius Nestor (marius-nestor) wrote :

I've just upgrade to 2.6.20-13.21 a few minutes ago and it works perfect also on my GA-965P-S3 - Intel P965+ ICH8 chipset (JMicron controller) motherboard. Thank you!

Revision history for this message
RobMueller (ubuntu-robm) wrote :

Another positive result. My Gigabyte 965GM-S2 now boots 2.6.20-13 as well.

Revision history for this message
Bane (rudlavibizon) wrote :

So what do i do, now that the bug has been fixed, if i want to do a clean install of feisty beta?

Revision history for this message
Maegashira (rainerda) wrote :

@Bane
you have to download the daily built found here:
http://cdimage.ubuntu.com/daily/current/
although you will often find only the alternate install there and they very often they don't keep track of the image size < 700megs. i also need a clean install because i smashed my system with an early update before this was fixed. still waiting for the next beta.

Revision history for this message
Peter.J (peter-johnsson) wrote :

Confirmed in the 27th daily build, kernel 2.6.20.13 :D

Great work guys.

Revision history for this message
apjaworski (apjaworski) wrote : Re: [Bug 84964] Re: Crash from ide_pci from generic.ko for jmicroncontrollers

Unfortunately the fix still does not work for me :-). Again, I have a new
system with Abit AB9 Pro motherboard. I was looking into the Bios setting
and it actually has 2 SATA controllers: JMicron and Sil3121 (or something
like that). Both controllers are set to PCI mode although only the JMicron
has the ACHI (?) mode.

In any case, I just downloaded the current Feisty (with the March 27 date)
and tried to boot it. I got a bunch of messages that looked different than
befoer but the end result was pretty much the same. At the end I was
getting a series of messages for ata5 stating things like "failed to set
xfermode" then "failed to recover some devices", then "retrying in 5 sec".
After a few seconds a very similar series but saying something about
limiting UDMA speed to 133 then to 100. The same series appeared for ata6
and after that I got the "ATA abnormal exit" thing and this was it.

Is my motherboard that peculiar? Anybody else with Abit out there having
the same or different luck.

Finally (and I am repeating myself), I do not understand WHY CAN I BOOT 6.10
just fine???

Thanks for everybody's efforts although the results are very disappointing
for me - it looks like I will be stuck with running Windows for a while.
Any words of wisdom or suggestions will be greatly appreciated,

Andy

----- Original Message -----
From: "Bane" <email address hidden>
To: <email address hidden>
Sent: Monday, March 26, 2007 5:09 PM
Subject: [Bug 84964] Re: Crash from ide_pci from generic.ko for
jmicroncontrollers

So what do i do, now that the bug has been fixed, if i want to do a
clean install of feisty beta?

--
Crash from ide_pci from generic.ko for jmicron controllers
https://launchpad.net/bugs/84964

Revision history for this message
simdoly (simdoly) wrote : Re: [Bug 84964] Re: Crash from ide_pci from generic.ko for jmicron controllers

Thanks for your considerate assistance.

I get ISO image from "http://cdimage.ubuntu.com/daily-live/current", and
burn it to a CD.
Then boot computer from this CD. And I tried install ubuntu 7.04.

First time, install progress is look like success. But after select
language(Korean), the moniter screen change like "red rain". So, I can't
install ubuntu 7.04.

Then, I tried again.
This time, I select English language. Thereupon, I can install ubuntu 7.04.
After install, I change language to Korean.

Well, because your kindly assistance, I can experience ubuntu 7.04.

Thanks very much!! You are a good men.

2007/3/27, Peter.J <email address hidden>:
>
> Confirmed in the 27th daily build, kernel 2.6.20.13 :D
>
> Great work guys.
>
> --
> Crash from ide_pci from generic.ko for jmicron controllers
> https://launchpad.net/bugs/84964
>

Revision history for this message
simdoly (simdoly) wrote : Re: [Bug 84964] Re: Crash from ide_pci from generic.ko for jmicroncontrollers

Thanks for your considerate assistance.

I get ISO image from "http://cdimage.ubuntu.com/daily-live/current", and
burn it to a CD.
Then boot computer from this CD. And I tried install ubuntu 7.04.

First time, install progress is look like success. But after select
language(Korean), the moniter screen change like "red rain". So, I can't
install ubuntu 7.04.

Then, I tried again.
This time, I select English language. Thereupon, I can install ubuntu 7.04.
After install, I change language to Korean.

Well, because your kindly assistance, I can experience ubuntu 7.04.

Thanks very much!! You are a good men.

2007/3/28, apjaworski <email address hidden>:
>
> Unfortunately the fix still does not work for me :-). Again, I have a new
> system with Abit AB9 Pro motherboard. I was looking into the Bios setting
> and it actually has 2 SATA controllers: JMicron and Sil3121 (or something
> like that). Both controllers are set to PCI mode although only the
> JMicron
> has the ACHI (?) mode.
>
> In any case, I just downloaded the current Feisty (with the March 27 date)
> and tried to boot it. I got a bunch of messages that looked different
> than
> befoer but the end result was pretty much the same. At the end I was
> getting a series of messages for ata5 stating things like "failed to set
> xfermode" then "failed to recover some devices", then "retrying in 5 sec".
> After a few seconds a very similar series but saying something about
> limiting UDMA speed to 133 then to 100. The same series appeared for ata6
> and after that I got the "ATA abnormal exit" thing and this was it.
>
> Is my motherboard that peculiar? Anybody else with Abit out there having
> the same or different luck.
>
> Finally (and I am repeating myself), I do not understand WHY CAN I BOOT
> 6.10
> just fine???
>
> Thanks for everybody's efforts although the results are very disappointing
> for me - it looks like I will be stuck with running Windows for a while.
> Any words of wisdom or suggestions will be greatly appreciated,
>
> Andy
>
>
> ----- Original Message -----
> From: "Bane" <email address hidden>
> To: <email address hidden>
> Sent: Monday, March 26, 2007 5:09 PM
> Subject: [Bug 84964] Re: Crash from ide_pci from generic.ko for
> jmicroncontrollers
>
>
> So what do i do, now that the bug has been fixed, if i want to do a
> clean install of feisty beta?
>
> --
> Crash from ide_pci from generic.ko for jmicron controllers
> https://launchpad.net/bugs/84964
>
> --
> Crash from ide_pci from generic.ko for jmicron controllers
> https://launchpad.net/bugs/84964
>

Revision history for this message
Matti Laakso (matti-laakso) wrote :

I have two systems with a JMicron-controller. First one has an Asus Commando motherboard, and it works perfectly as of 2.6.20-13.

The second one with Abit AB9 still does not work however. I get the same messages as apjaworski, i.e., it complains about a timeout with ata5 and not being able to set xfermode, then it retries two times and disables ata5. HOWEVER, ata5 corresponds to my primary hard disk, which is not connected to JMicron, rather it is connected to ICH8 SATA-port. So this may be a different bug altogether. Edgy works fine though, and so did Feisty with kernel 2.6.19-7 (IIRC).

Revision history for this message
rennen01 (carl-agbayani) wrote : Re: [Bug 84964] Re: Crash from ide_pci from generic.ko for jmicroncontrollers

Problem still not fixed for me either. Attempted to use Fiesty Fawn
20070327.1 from cdimages.ubuntu.com

On Wed, 2007-03-28 at 05:35 +0000, apjaworski wrote:
> Unfortunately the fix still does not work for me :-). Again, I have a new
> system with Abit AB9 Pro motherboard. I was looking into the Bios setting
> and it actually has 2 SATA controllers: JMicron and Sil3121 (or something
> like that). Both controllers are set to PCI mode although only the JMicron
> has the ACHI (?) mode.
>
> In any case, I just downloaded the current Feisty (with the March 27 date)
> and tried to boot it. I got a bunch of messages that looked different than
> befoer but the end result was pretty much the same. At the end I was
> getting a series of messages for ata5 stating things like "failed to set
> xfermode" then "failed to recover some devices", then "retrying in 5 sec".
> After a few seconds a very similar series but saying something about
> limiting UDMA speed to 133 then to 100. The same series appeared for ata6
> and after that I got the "ATA abnormal exit" thing and this was it.
>
> Is my motherboard that peculiar? Anybody else with Abit out there having
> the same or different luck.
>
> Finally (and I am repeating myself), I do not understand WHY CAN I BOOT 6.10
> just fine???
>
> Thanks for everybody's efforts although the results are very disappointing
> for me - it looks like I will be stuck with running Windows for a while.
> Any words of wisdom or suggestions will be greatly appreciated,
>
> Andy
>
>
> ----- Original Message -----
> From: "Bane" <email address hidden>
> To: <email address hidden>
> Sent: Monday, March 26, 2007 5:09 PM
> Subject: [Bug 84964] Re: Crash from ide_pci from generic.ko for
> jmicroncontrollers
>
>
> So what do i do, now that the bug has been fixed, if i want to do a
> clean install of feisty beta?
>
> --
> Crash from ide_pci from generic.ko for jmicron controllers
> https://launchpad.net/bugs/84964
>

Revision history for this message
UBfusion (ubfusion) wrote :

I confirm that Asus P5B-VM (with ICH8 and JMicron) now boots the 0326 amd64 live cd.

I tested with the RAID option for JMicron. Remains to be seen whether the AHCI and BASIC options work too.

Revision history for this message
UBfusion (ubfusion) wrote :

Correction to my previous comment above (#114) - I meant that 0327(.0) build was OK.

Revision history for this message
mkgs (mohan-kgs) wrote :

0327 build amd64 image works fine on ASUS P5B-E mobo (with ICH8 and JMicron), Core2Duo and SATA drives. Note I did not try RAID options in these SATA drives yet, they are used as IDE device for now. Sata drives are connected to ICH8 controller and CD ROM connected to JMicron controller.

Thanks for fixing this issue.

Revision history for this message
JoseStefan (josestefan) wrote :

Fixed for me too, on the current daily.

In regards to my last post, seems like the new kernel was not in the disc by then, which would explain the results.

Revision history for this message
Alex Willmer (alex-moreati) wrote :

Latest kernel has fixed this for me on an Asus P5B VM, original reprt was bug 86156

Revision history for this message
takai (chrisp-plebeians) wrote :

I am having this issue again with the 20070329 nightly build. Main issue comes post-install, with the SATA controller (either JMicron or ICH8) not being able to set xfermode properly.

Hw: Asus P5B-Deluxe, 500gb SATA (connected on either JMicron or ICH8)

Revision history for this message
takai (chrisp-plebeians) wrote :

Ok, regarding my last post i have now fixed it by blacklisting intel_agp and adding irqpoll to the boot line, and fiddling with the JMicron and ICH8 settings in the bios.

Revision history for this message
Bane (rudlavibizon) wrote :

I made a mistake and did a clean install of daily build 29.03. Now i can boot only if i disable jmicron controller in bios but then i can't use dvd-rw. When i boot with jmicron enabled i have "error 17: cannot mount selected partition". Can anyone suggest what should i do to fix this.

[core2duo, asus p5b]

Revision history for this message
godot (godotcg-launchpad) wrote :

takai and others still having problems with sata complaining with xfermode, you may be interested by this bug report : https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/90715

Revision history for this message
simdoly (simdoly) wrote :

Today, I tried install daily build 30.03.2007
The installer screen can't visible.
Problem still not fixed.

Intel Core 2 Duo 6300
GIGABYTE GA-965P-DS3
ATI Radeon X1950GT / 512 MB GDDR2
Samsung DVD-Multi SH-S183L
22" Wide monitor

Sorry, I poor at English.....

Revision history for this message
siucdude (siucdude) wrote :

Just wanted to say, I get the same issue with two sata drives, the daily and any fisty cd wont load. edgy is no problem.

Revision history for this message
Crakie (baloedebruinebeer) wrote :

The fix also does not work perfectly for me (Abit AB9 Pro board with Jmicron and ICH8 controllers).

I did manage to install the daily build of April 1th with the "pci=biosirq" option in the bootloader. Feisty boots now, but only with pci=biosirq noapic nolapic acpi=of options in grub.

Revision history for this message
Ariyau (hawaii5o) wrote :

I installed and booted the 2007-04-07 build without any problem. One SATA HD on ICH8 and one on the Jmicron set as IDE. Asus P5B-E mobo. Grub seems to get confused which mbr to install in, it seems to choose the ide (/dev/sdb) by default. Fixed by specifying the /dev/sda.

Thanks for the effort.

Revision history for this message
Rich Perry (ricperry1) wrote : Re: [Bug 84964] Re: Crash from ide_pci from generic.ko for jmicron controllers

/dev/sdb is the SATA drive. See if you have /dev/hda which would be your
IDE drive.

On 4/9/07, Ariyau <email address hidden> wrote:
>
> I installed and booted the 2007-04-07 build without any problem. One
> SATA HD on ICH8 and one on the Jmicron set as IDE. Asus P5B-E mobo.
> Grub seems to get confused which mbr to install in, it seems to choose
> the ide (/dev/sdb) by default. Fixed by specifying the /dev/sda.
>
> Thanks for the effort.
>
> --
> Crash from ide_pci from generic.ko for jmicron controllers
> https://bugs.launchpad.net/bugs/84964
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Revision history for this message
juice (artur-makowka) wrote :

still got the same problem with http://cdimage.ubuntu.com/daily/current/feisty-alternate-i386.iso from 10 April.

Gigabyte 965P-S3 , trying to install it on IDE HDD connected to JMicron

modprobe is showing some errors and i got dropped to busybox sh

it complains about missing /dev/root/dev or some /root/.static/something...

and if i check ls /dev/sd* or ls /dev/hd* when on busybox sh, i get nothing.
system works fine on windows and debian

Revision history for this message
Aaron (soulblade) wrote :

Hi there

I have a 965P-DS3 with a E6300.

2.6.20-14 - did not boot.
2.6.20-15 - does boot !!!

Revision history for this message
simdoly (simdoly) wrote :

Aaron!
Me too.

I have a 965P-DS3, E6300 and ATI 1950GT.
I update some files yesterday. And reboot system. But did not boot.
Help~~!!

Revision history for this message
Aaron (soulblade) wrote :

@simdoly

Hi

As soon as you turn your PC on. look for the count down at the lower left of the screen.

Press Esc and pick the oldest kernel.

Once you have booted in ubuntu run the update again and i should down load 2.6.20-15 and that might fix the problem.

For now, I have gone back to 6.10 but are looking forwards to the final 7.04.

Revision history for this message
Daniel Matysiak (dmatysiak) wrote :

I have posted about a similar problem on bug #96084. Attached is the error I get when trying to begin the Feisty installation (I have disabled my JMicron controller and the same error occurs). Of course, the installation does not proceed. I too have an Intel Core 2 Duo (E6600), abit AB9 pro motherboard, geforce 7600gt,,, lspci is linked to here: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/96084/comments/49

Revision history for this message
cjv (cjv133) wrote :

I think I may have the same problem, I have a HP Compaq nc8430 laptop (precise hw config at the end). I've been running 6.10 ok, but trying clean 7.04 install crashes with the following message:

------------------------------------------
BusyBox v1.1.3 (Deian 1:1.1.3-3ubuntu3) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs) [ 24.808000] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action ....
0x2 frozen
[ 24.808000] ata5.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 ....
ata 36 in
[ 30.804000] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 30.804000] ata5.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 ....
ata 36 in
------------------------------------------

No matter what resolutions I try or parameters added. ISOs've been md5 checked.

I've tried also the Alternate ISO: it installs (weird) but then it doesn't boot at all.

Carlos

------------------------------------------
Laptop hw config:

- ATI Mobility Radeon X1600 PCI-Express x16
- 2GB RAM DDR2 dual-channel 2 x 1Gb PC2-5300 (333 MHz) 5-5-5-15-20
- Seagate Momentus 7200.1 ST 980825AS harddisk - 80 GB - SATA-150
- Intel Core Duo T2400
- Intel i945PM motherboard

Revision history for this message
David Nichols (dwnichols) wrote :

I had a similar problem installing from the Feisty LiveCD using an Asus P4S333-VM motherboard. This motherboard does not have any SATA functionality, nor do I have any SATA plugin cards. The only cards I have installed are a Soundblaster Live 5.1 and an Asus N6200 AGP card. The installation went fine, but the first boot failed with the modprobe abnormal exit. After several reboots, I got to one of the alternate terminals and find that the machine is getting stuck while working with the attached USB devices. (I have a generic 4-port hub by CyberPower and a USB 2.0 7-1 media reader built into my floppy drive.) I have three hard drives on my system. hda is (will be) / and /boot for ubuntu as well as /boot for fedora 6. hdb is DOS6.22, the swap file for ubuntu and fedora and / for fedora. hdc is WindowsXP and hdd is a DVD writer. I disconnect both USB devices and every drive except for hda and hdd. Boot LiveCD, install, everything boots fine. Installed hdb. Re-install Fiesty, everything boots fine. Install hdc. Everything boots fine. I then plug in my hub under power. I reboot, and the system freezes (no Num Lock toggle). Once. After that, it boots fine. Turn off power, install the media reader on an internal USB header, reboot.... And everything boots fine.

I've spent about three hours on this, but I haven't actually started using the system yet. I'm willing to re-install and see if I can replicate the problem if someone can tell me how to generate useful log files.

Revision history for this message
cjv (cjv133) wrote :

Regarding my post on 2007-04-14, just to inform that the recently downloaded feisty-desktop-i386.iso from the 15-Apr-2007 with kernel 2.6.20-15 (as written in manifest) fails with exactly the same simptoms as written on previous mails.
In my humble opinion, this bug is NOT fixed.

I suppose it's not much help, but just to inform, I've installed and running ok Suse 10.2 and FC6. But by far I prefer Ubuntu. Any help would be appreciated.

Revision history for this message
zeno (zeno-78) wrote :

I have the same problem explained here on a abit ab9 with Intel Core 2 duo (e6320). The exact problem of Daniel Matysiak. Please, if you need more info i will be very pleased to give it. It's a very big problem for me since i only use Ubuntu as O.S. and i have a new PC completely stopped due to this critical bug :(
Hope to hear news very soon.
ZeNo

Revision history for this message
zeno (zeno-78) wrote :

This is my "adventure":
i installed ubuntu feisty 7.04 with noapic and irqpoll options and i had a problem when partitioning... i couldn't do a manual partition, so i installed with the automatic partition. After the installation, when the system boot, i have a lot of errors on the ATA and the system hangs anf gives me the error "/bin/sh: can't access tty; job control turned off". After that i found a guide on the web where there was some tips to install ubuntu 6.10 on my abit ab9 motherboard. The guide says to install using irqpoll options at boot (i need also noapic) and it says to attach the hard disk to the jmicron sata port and disable Os usb legacy support in the bios. With these tips i installed ubuntu 6.10 but i can't use the mouse. Then, when i make a apt-get update/upgrade i can't boot: another time a lot of error messages about a problem on the ata (same errors reported here). So, i tried to disable the jmicron port in the bios and i tried to boot with the hard disk connected to the ICH8 sata ports and the system started but, another time, i couldn't use the mouse. I made an upgrade to feisty but the upgrade hanged and now i can't boot because of a problem on /dev/sda1 that seems to be deleted: i receive this error at boot: "ALERT! /dev/sda1 does not exist. Dropping to a shell!".
Th question is: if i buy an IDE-SATA/PCI adapter do you think that i can boot and install my system in the meanwhile that this bug will be solved?

Revision history for this message
Chuck Smith (smith.chuck) wrote :

Is it possible there has been a regression of this in the 2.6.20-16 update that was just released? I'm experiencing nearly identical problems as reported in this thread.

Displaying first 40 and last 40 comments. View all 168 comments or add a comment.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.