1106:0415 Boot problem with VIA VT6415 PATA IDE Host Controller

[lvm]

kubuntu-32 11.10, Linux server 3.0.0-14-generic-pae #23-Ubuntu SMP Mon Nov 21 22:07:10 UTC 2011 i686 athlon i386 GNU/Linux.

After the motherboard and CPU uograde I started to experience intermittent system frezes during the system boot process with

 udevd[101]: timeout: killing '/sbin/modprobe -bv pci:v00001B4Bd000091A0sv00001849sd000091A0bc01sc01i8f' [145]

message dispayed on screen (white on black, 'thick' system textmode font, not 'thin' ubuntu console font).

If system boots successfully (3 out of 8 attempts so far) it functions without futher problems.

WORKAROUND: I disabled IDE controller system booted normally.

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: ALC892 Analog [ALC892 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: lvm 2342 F.... pulseaudio
 /dev/snd/controlC0: lvm 2342 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe600000 irq 16'
   Mixer name : 'Realtek ALC892'
   Components : 'HDA:10ec0892,18497892,00100302'
   Controls : 35
   Simple ctrls : 20
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfe080000 irq 25'
   Mixer name : 'Nvidia GPU 0d HDMI/DP'
   Components : 'HDA:10de000d,10de0101,00100100'
   Controls : 17
   Simple ctrls : 5
DistroRelease: Ubuntu 11.10
HibernationDevice: RESUME=UUID=d22ce633-8298-47af-bd3b-b2f2c011e08f
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
IwConfig:
 lo no wireless extensions.

 eth2 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-14-generic-pae root=UUID=e5d4b20c-2274-4625-bff0-06fcc27e7755 ro recovery nomodeset
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic-pae 3.0.9
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-14-generic-pae N/A
 linux-backports-modules-3.0.0-14-generic-pae N/A
 linux-firmware 1.60
RfKill:

Tags: oneiric
Uname: Linux 3.0.0-14-generic-pae i686
UpgradeStatus: Upgraded to oneiric on 2011-10-15 (95 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 09/13/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: 990FX Extreme4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd09/13/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn990FXExtreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/916677/+editstatus and add the package name in the text box next to the word Package.

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

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 916677

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[lvm (lvm-royal)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/

[lvm (lvm-royal)]

http://kernel.ubuntu.com/~kernel-ppa/mainline/ has kernels tagged precise and oneric. Am I correct in understanding that you want me to test -precise kernels? 3.2 or 3.2.2 or all of them?

Meanwhile I've upgraded to 3.0.0-15 through regular channels and it changed behavior somewhat: now my system refuses to boot completely (6 times in a row): after the grub screen goes black with cursor blinking in the top left corner and that's it. BUT booting into a recovery mode with the same kernel works fine - I just select continue booting when I get to a prompt and boot wiht no further mishaps (2 out of 2).

And it looks like I was incorrect in suspecting Marvell SATA controller - disabling it in the BIOS doesn't change a thing. BTW system is not overclocked yet - runs with all default settings.

[lvm (lvm-royal)]

Guys, I'd appreciate if you give me a pointer and answer my previos question - I cannot afford to perform lengthy experiments on this system.

Meanwhile I've upgraded to 3.0.0-16 and it changed things a bit once more: booting in safe mode doesn't guarantee success any longer (on maybe I was just lucky previous times), but it allowed some insight into what's going on: when my system lockes up the last line on the screen is always a DVD drive detection (3 out of 3).

[ 3.116027] sdc: sdc1
[ 3.116230] sd 2:0:0:0: [sdc] Attached SCSI disk
[ 3.117191] sdd: sdd1
[ 3.117422] sd 3:0:0:0: [sdd] Attached SCSI disk
[ 3.120788] sdb: sdb1
[ 3.121017] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 3.130707] sda: sda1 sda2 sda3
[ 3.130990] sd 0:0:0:0: [sda] Attached SCSI disk
[ 3.192021] usb 3-3: new high speed USB device number 2 using ehci_hcd
[ 3.278654] scsi 5:0:0:0: Direct-Access ATA Hitachi HDS72202 JKAO PQ: 0 ANSI: 5
[ 3.278803] sd 5:0:0:0: [sde] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 3.278810] sd 5:0:0:0: Attached scsi generic sg4 type 0
[ 3.278878] scsi 5:0:1:0: Direct-Access ATA Hitachi HDS72202 JKAO PQ: 0 ANSI: 5
[ 3.278949] sd 5:0:1:0: Attached scsi generic sg5 type 0
[ 3.278966] sd 5:0:1:0: [sdf] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 3.278997] sd 5:0:1:0: [sdf] Write Protect is off
[ 3.278999] sd 5:0:1:0: [sdf] Mode Sense: 00 3a 00 00
[ 3.279010] sd 5:0:1:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.279583] scsi 8:0:1:0: CD-ROM TSSTcorp CDDVDW SH-S202H SB00 PQ: 0 ANSI: 5

>when it locks up it is always here

[ 3.281276] sdf: sdf1
[ 3.281336] sd 5:0:0:0: [sde] Write Protect is off
[ 3.281389] sd 5:0:0:0: [sde] Mode Sense: 00 3a 00 00
[ 3.281416] sd 5:0:0:0: [sde] Write cache: enable...

[lvm (lvm-royal)]

Yes, looks like it is caused by IDE CD - I tried to access it after a successful boot and the system immediately froze - not even a mouse was stirring. After I disabled IDE controller system booted normally.

[stodjkat (stodjkat)]

This issue affects my ASRock 990FX Extreme4 motherboard too, with current latest release bios v2.00.

Windows is fine, using the Win7 SP1 64bit install CD.

But Linux is problematic to say the least.

I have tried:
Kubuntu 12.04.1 amd64 DVD and Alternate
Xubuntu 12.10 amd64 Desktop
LinuxMint 14.1 Cinnamon DVD 64bit

and even:
System Rescue CD x86 3.3.0 <- gentoo based - does this mean it's an issue in common with other distros?

...all with very limited success. For me I get about 1 successful boot out of every 10 attempts.

I just managed to get kubuntu installed, and it does seem to work OK if it boots up, but I haven't tested it for a long.

I suggest the name of this thread is misleading, since I seem to have the same boot problems whether I disable the Marvell chip in the UEFI BIOS or not.

However I can confirm that turning off the Onboard IDE & 1394 controller has changed the boot up freezes for the better - since I made the change it has booted straight up into kubuntu 4 times in a row now...

Unfortunately that is not an adequate workaround for me since I have a PATA DVD drive, and a PATA HDD for backups, and all the SATA ports are filled with SATA HDDs. For me, to not use the Onboard IDE would remove the whole reason for buying this mobo!

It would be nice to know if/when the Linux drivers for the IDE chipset on this mobo are fixed - it would seem odd for this to be the only mobo that used the hardware with the offending drivers...

Anyway, thanks for posting your workaround - at least I know it's not just me going mad now....

[Paladin24 (happyworm24)]

I have the same problem on ASRock 890FX Deluxe5 mobo.

[Paladin24 (happyworm24)]

Btw, adding noapic and nolapic in /etc/default/grub in parameter GRUB_CMDLINE_LINUX="". And making update-grub in console helps to solve problem.
BUT
Your system will use and see only 1 core of youк processor. Booting is much longer now.
So need new solution!

[Paladin24 (happyworm24)]

I have both IDE hdd and DVD-ROM, so when I unplug DVD-ROM the problem disappears. Have tried both 40 and 80wire cables. This problem does not depend on cable, but IDE CD or DVD is.

[Paladin24 (happyworm24)]

My DVD-ROM - Plextor PX-712A

[Paladin24 (happyworm24)]

Kernel 3.7.6 - same problem.

[Paladin24 (happyworm24)]

Ok, I think I have found temporary solution. I have put my Plextor PX-712A slave and my IDE HDD - master. There is a DMA jumper option on the back of my Plextor-PX712A, so I have put jumper on it too. So
IDE HDD jumper position - Master
Plextor PX-712A jumper positions - Slave and DMA.
This solution works for me on Kernel 3.7.6. I have tried it on kernel 3.5.0 - 17 and it doesn't work. So kernel 3.7.6 needed.
Btw, the behavior of the Plextor PX-712A have changed. Not it opens the tray in two steps sometimes, so 1/2 open then 1 sec break and then fully opened.
Hope this information will help somebody. But it will be good if somebody will find permanent solution or fix the kernel.

[Paladin24 (happyworm24)]

I think the problem is in kernel support VT6415 PATA IDE Host Controller. I cannot check this, but found some information on forums about the same problem.

[Paladin24 (happyworm24)]

May somebody check this solution?
http://alexandrulazar.com/vt6415-kernel-panic-when-enumerating-ide-devices/

[Paladin24 (happyworm24)]

Ok, the solution above works for me 5 out of 5 on kernel 3.7.6 and kernel 3.5.0-23. I belive that it will work on all kernels.
Here is it:
Jumper position on DVD-ROM - Slave. (you don't need second jumper, so Slave position is ok).
Jumper position on HDD - Master.
Then do in console (I have used leafpad because I run Xubuntu):
sudo leafpad /etc/default/grub
Find the line:
GRUB_CMDLINE_LINUX=""
and replace it on:
GRUB_CMDLINE_LINUX="libata.dma=1"
save changes and close text editor.
Then type in console:
sudo update-grub
Reboot.

I belive that this will turn your CD/DVD-ROM in PIO mode instead of DMA.

I think this is a problem with VIA VT6415, because I have found post with the same problem on motherboards of other developers with VIA VT6415.

Hope this help you and hope that this problem will be resolved in new kernel and we could use UDMA on our CD/DVD-ROMs.

[Paladin24 (happyworm24)]

Maybe we should make a new bug report called "Boot problem with VIA VT6415 PATA IDE Host Controller and PATA CD/DVD-ROM"?

[Paladin24 (happyworm24)]

Have found some more usefull information here:
https://bugzilla.kernel.org/show_bug.cgi?id=44111

[stodjkat (stodjkat)]

Thanks for this update.

I can confirm that with the libata.dma=1 setting, the boot is stable for my ASRock 990FX Extreme4, and has no more problems.

At first glance, libata.dma=1 would appear to be forcing DMA to ON, rather than OFF as suggested above, but that's not so important to me in comparison with having a stable boot up. However, just for comparison purposes I tried libata.dma=0 as well, and that seemed to be equally stable during boot up.

Therefore I propose that perhaps the problem is not so much in which value libata.dma ends up being set to, but more in the algorithm that tries to automatically determine which is the appropriate value for my system. Does that make sense or help tie down the precise location of the bug in the code?

[Paladin24 (happyworm24)]

Thank you. I am not pro in this questions, but now we know that this solution helps to solve the problem! Thank you for your answer.
Btw, I have found some information about libata.dma here http://www.kernel.org/doc/Documentation/kernel-parameters.txt:
libata.dma= [LIBATA] DMA control
   libata.dma=0 Disable all PATA and SATA DMA
   libata.dma=1 PATA and SATA Disk DMA only
   libata.dma=2 ATAPI (CDROM) DMA only
   libata.dma=4 Compact Flash DMA only
   Combinations also work, so libata.dma=3 enables DMA
   for disks and CDROMs, but not CFs.

Thus this parameter enables DMA on only on disks, not CD/DVD rom.
I have writen to VIA support team about this problem, hope they will answer on e-mail or in https://bugzilla.kernel.org/show_bug.cgi?id=44111

[Paladin24 (happyworm24)]

VIA Support Team do nothing to help... No answer on mail and forum thread.

[penalvch (penalvch)]

lvm, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[biohazara (biohazara)]

I can confirm this bug still persists on Ubuntu 20.04 64-bit, using an ASRock 990fx Extreme4 motherboard.

The solution pointed out here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/916677/comments/39 seems to still fix the problem.

[penalvch (penalvch)]

biohazara, it would be most helpful if you provided necessary debugging information via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.