| 2008-04-03 15:41:16 |
dino99 |
bug |
|
|
added bug |
| 2008-04-07 07:17:05 |
dino99 |
bug |
|
|
added attachment 'uname-a.log' (uname-a.log) |
| 2008-04-07 07:17:35 |
dino99 |
bug |
|
|
added attachment 'proc_version_signature.log' (proc_version_signature.log) |
| 2008-04-07 07:17:59 |
dino99 |
bug |
|
|
added attachment 'lsusb.log' (lsusb.log) |
| 2008-04-07 07:18:19 |
dino99 |
bug |
|
|
added attachment 'lspci-vvnn.log' (lspci-vvnn.log) |
| 2008-04-07 07:18:42 |
dino99 |
bug |
|
|
added attachment 'interrupts.log' (interrupts.log) |
| 2008-04-07 07:19:08 |
dino99 |
bug |
|
|
added attachment 'dmidecode.log' (dmidecode.log) |
| 2008-04-07 07:19:34 |
dino99 |
bug |
|
|
added attachment 'dmesg.log' (dmesg.log) |
| 2008-04-07 07:22:29 |
dino99 |
description |
I'm using an Asus mobo P5wdh with c2d, Hardy Heron 2.6.24-14
The trouble is when booting: a wrong device is detected corresponding in fact (found similar subject on google) to one of the Jmicron / Silicon chipset on the mobo.
So, booting is very long and i need to add irqpoll into grub.
Messages are: - (initramfs) 228.001986 ata4 s RST failed error 16
- hdio_get_identity failed for /dev/.tmp-8-16
- idm_validate_table disk read failed
- device is on Dma blacklist, disabling Dma
This mobo (and P5 asus family) is not very recent (2006/06) but frequently used by Linux community, and all bios or kernel updates have not solved the hardware detection. So , i wonder if some words (without disabling multi-cores cpu) could be adding into grub or some script to blacklist this "wrong device"
ps: i don't want to compile kernel |
I'm using an Asus mobo P5wdh with c2d, Hardy Heron 2.6.24-14 (same thing with 24-15 / sysinfo 0.7 identify an other mobo than mine )
The trouble is when booting: a wrong device is detected corresponding in fact (found similar subject on google) to one of the Jmicron / Silicon chipset on the mobo.
So, booting is very long and i need to add irqpoll into grub.
Messages are: - (initramfs) 228.001986 ata4 s RST failed error 16
- hdio_get_identity failed for /dev/.tmp-8-16
- idm_validate_table disk read failed
- device is on Dma blacklist, disabling Dma
This mobo (and P5 asus family) is not very recent (2006/06) but frequently used by Linux community, and all bios or kernel updates have not solved the hardware detection. So , i wonder if some words (without disabling multi-cores cpu) could be adding into grub or some script to blacklist this "wrong device"
|
|
| 2008-04-10 22:33:24 |
Leann Ogasawara |
linux: importance |
Undecided |
Medium |
|
| 2008-04-10 22:33:24 |
Leann Ogasawara |
linux: assignee |
|
ubuntu-kernel-team |
|
| 2008-04-10 22:33:24 |
Leann Ogasawara |
linux: status |
New |
Triaged |
|
| 2008-04-11 16:03:19 |
dino99 |
title |
wrong ata device detected |
wrong ata device detected (Hardy Heron 2.6.24-15) |
|
| 2008-04-12 07:55:42 |
dino99 |
bug |
|
|
added attachment 'lshal.log' (lshal.log) |
| 2008-04-12 07:56:34 |
dino99 |
bug |
|
|
added attachment 'lshw.log' (lshw.log) |
| 2008-04-15 15:36:21 |
dino99 |
bug |
|
|
added attachment 'fdisk-l.log' (fdisk-l.log) |
| 2008-04-15 15:37:40 |
dino99 |
title |
wrong ata device detected (Hardy Heron 2.6.24-15) |
wrong ata device detected (Hardy Heron 2.6.24-15 & 16) |
|
| 2008-05-01 09:27:10 |
dino99 |
bug |
|
|
added attachment 'dmesg.log' (dmesg.log) |
| 2008-11-30 18:00:33 |
Leann Ogasawara |
linux: status |
Triaged |
Fix Released |
|
| 2008-11-30 18:00:33 |
Leann Ogasawara |
linux: statusexplanation |
|
Thanks for the update dino99. Glad to hear this appears to be resolved. I'm setting this to Fix Released per your last comment. Thanks. |
|
