Red Hat Bugzilla – Bug 144302
ata_piix: uable to handle kernel paging request
Last modified: 2013-07-02 22:23:31 EDT
Description of problem:
When installing Fedora Core 3 on a Dell Precision 470, the ata_pixx
driver is called to be loaded and the kernel can not handle a paging
lspci of the IDE and SATA controller (onboard):
00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) IDE
Controller (rev 02)
00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) SATA Controller (rev 02)
Version-Release number of selected component (if applicable):
Install FC3 on a similar device.
Once the module fails, I can test the cdrom, and it starts to load the
aic79xx driver for the SCSI hard drives. It can't finish loading the
driver. When I run ps, I see three loader proceses running. lsmod
shows that both the ata_piix driver and aic97xx are currently loading.
I can not remove the modules.
Created attachment 109389 [details]
dmesg output including kernel errors.
Created attachment 109390 [details]
output of lspci for device information
Created attachment 109392 [details]
Same here on a Precision 670 and a Precision 270. Any way to get
around it and install??
I have try to switch the BIOS SATA setting to Raid Autodetect/ATA (on
a Precision 370) ... and it's the same pb ..
Has anyone been able to reproduce this error on CentOS 4, or RHEL 4? Those seem
to be pretty close to Fedora Core 3, and we might be able to reproduce the bug
I will check if I still have the 470 at my disposal.
This problem doesn't seem to happen on RHEL 4. Is it possible for you to see if
there was a patch between 2.6.9-1 used in FC3 and the 2.6.9-5 kernel used in RHEL 4?
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.
There are a large number of inactive bugs in the database, and this is the only
way to purge them.