[Dell Dimension 2400] IRQ conflict with pci sata vt6421 with two hard drives

[Oltion Kola]

My computer hangs when booting because of a irq conflict. I have a PCI adapter for SATA drives with sata and usb ports with VT6421 chipset. When I boot up with two HD in the sata ports the system behaves badly. Most of the time it hangs (3 over 4 tries) in the 2 first seconds. I have tried the options in the irq debug guide but it does not help.

WORKAROUND: When I put only one HD then the system is OK.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-21-generic 2.6.32-21.32
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: olti 1268 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 17'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 26
   Simple ctrls : 18
CurrentDmesg:
 [ 18.820236] b44: eth1: Link is up at 100 Mbps, full duplex.
 [ 18.820243] b44: eth1: Flow control is off for TX and off for RX.
 [ 18.820581] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
 [ 29.816170] eth1: no IPv6 routers present
Date: Mon Apr 26 23:14:53 2010
HibernationDevice: RESUME=UUID=78bd97bc-8c7b-48b0-8c87-13780d942f8e
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.
MachineType: Dell Computer Corporation Dimension 2400
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=d700ba56-8a55-4228-9d46-07468a334fe0 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:

SourcePackage: linux
dmi.bios.date: 12/02/2003
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A05
dmi.board.name: 0G1548
dmi.board.vendor: Dell Computer Corp.
dmi.board.version: A00
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComputerCorporation:bvrA05:bd12/02/2003:svnDellComputerCorporation:pnDimension2400:pvr:rvnDellComputerCorp.:rn0G1548:rvrA00:cvnDellComputerCorporation:ct15:cvr:
dmi.product.name: Dimension 2400
dmi.sys.vendor: Dell Computer Corporation

[Jeremy Foshee (jeremyfoshee)]

Hi Oltion,

If you could also please 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.]

[Oltion Kola (oltion-kola-gmail)]

Hi Jeremy,
First, thanks for the reply. I tested today the newest kernel for Lucid as you asked.
the latest version was:

linux-image-2.6.34-999-generic_2.6.34-999.201004291005_i386.deb

The original problem seems to not be present (system hang) but there is something else that might be the cause of the problem anyway. During boot I see the following message:

pci 0000:01:09.0: address space collision: [mem 0xfea00000-0xfea03fff pref] conflicts with 0000:01:05.3 [mem 0xfea00000-0xfea0ffff pref]

It looks like there is a memory conflict between the network controller and the raid controller:

$lspci
......
01:05.3 RAID bus controller: VIA Technologies, Inc. VT6421 IDE RAID Controller (rev 50)
01:09.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)
.....

Now I can not access one of the disks. The system boots even with the two sata disks attached but only one of them gets recognised by the system.

Let me know what can I do next.

[penalvch (penalvch)]

Oltion Kola, 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 (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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.13-rc3

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.

[Oltion Kola (oltion-kola-gmail)]

The situation is much worse now, as the system does not boot at all. It
hangs at the moment when it recognizes the two disks. Before one of the
disks was ignored but the system could boot.
So, I'm afraid I can not add debug data unless you let me know what is
the information you need and how I can find it. Even the new kernel can
not be tested as the sytem does not boot at all.

Thanks.

[Oltion Kola (oltion-kola-gmail)]

Tested with the latest build. The problem was present in all kernels I have tested in these 3 years.

[penalvch (penalvch)]

Oltion Kola, thank you for your comments. Just to confirm, you attempted to boot into the live environment of Trusty, and the mainline kernel v3.13-rc3, and neither allowed you to boot with both disks attached?

[Oltion Kola (oltion-kola-gmail)]

That's correct. They don't boot. The boot hangs when displaying information
for the second disk.
Today tried with bsd kernel (Debian/kfreebsd) and it recognizes the disks
and boots properly. Just for information.

On Fri, Dec 20, 2013 at 7:59 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> Oltion Kola, thank you for your comments. Just to confirm, you attempted
> to boot into the live environment of Trusty, and the mainline kernel
> v3.13-rc3, and neither allowed you to boot with both disks attached?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/570434
>
> Title:
> [Dell Dimension 2400] IRQ conflict with pci sata vt6421 with two hard
> drives
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> My computer hangs when booting because of a irq conflict. I have a PCI
> adapter for SATA drives with sata and usb ports with VT6421 chipset.
> When I boot up with two HD in the sata ports the system behaves badly.
> Most of the time it hangs (3 over 4 tries) in the 2 first seconds. I
> have tried the options in the irq debug guide but it does not help.
>
> WORKAROUND: When I put only one HD then the system is OK.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.04
> Package: linux-image-2.6.32-21-generic 2.6.32-21.32
> Regression: No
> Reproducible: Yes
> ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
> Uname: Linux 2.6.32-21-generic i686
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
> Architecture: i386
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: olti 1268 F.... pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 17'
> Mixer name : 'Analog Devices AD1981B'
> Components : 'AC97a:41445374'
> Controls : 26
> Simple ctrls : 18
> CurrentDmesg:
> [ 18.820236] b44: eth1: Link is up at 100 Mbps, full duplex.
> [ 18.820243] b44: eth1: Flow control is off for TX and off for RX.
> [ 18.820581] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
> [ 29.816170] eth1: no IPv6 routers present
> Date: Mon Apr 26 23:14:53 2010
> HibernationDevice: RESUME=UUID=78bd97bc-8c7b-48b0-8c87-13780d942f8e
> InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386
> (20100419.1)
> IwConfig:
> lo no wireless extensions.
>
> eth1 no wireless extensions.
> MachineType: Dell Computer Corporation Dimension 2400
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic
> root=UUID=d700ba56-8a55-4228-9d46-07468a334fe0 ro quiet splash
> ProcEnviron:
> LANG=en_US.utf8
> SHELL=/bin/bash
> RelatedPackageVersions: linux-firmware 1.34
> RfKill:
>
> SourcePackage: linux
> dmi.bios.date: 12/02/2003
> dmi.bios.vendor: Dell Computer Corporation
> dmi.bios.version: A05
> dmi.board.name: 0G1548
> dmi.board.vendor: Dell Computer Corp.
> dmi.board.version: A00
> dmi.chassis.type: 15
> dmi.chassis.vendor: Dell Computer Corpo...

[penalvch (penalvch)]

Oltion Kola, thank you for performing the requested tests. Despite this working in Debian/kfreebsd, given how it's reproducible in mainline, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream ?

Please provide a direct URL to your post once you have made it so that it may be tracked.

Thank you for your understanding.

[Po-Hsu Lin (cypressyew)]

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!