Re: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not

[Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>]

Hi,

On Friday 27 July 2007, dth wrote:
> I have a via mini-itx epia 5000 motherboard as a firewall.
> It has an ide device: PQI 128MB flash DOM [1] which just plugs
> directly into the ide connector on the motherboard.
> 2.6.22-git17 works, although it gives some warning 
> hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
> hda: set_drive_speed_status: error=0x04 { DriveStatusError }

Should be harmless for now but we would like to fix it the long-term,
please send "hdparm --Istdout /dev/hda" output.

> Full dmesg output [2]
> 
> When i compiled any 2.6.23-rc1 kernel out so far it always froze on me.
> Yesterday i tried 2.6.23-rc1-git3 and i booted until:

No IDE changes yet after 2.6.22-git17 so something else must have broke down.

Please retry with the latest -git kernel and if the problem is still
there install git, get kernel tree and run git-bisect.

Since 2.6.22-git17 works fine the initial "good" commit would be
e51f802babc5e368c60fbfd08c6c11269c9253b0 and the initial "bad" one
f695baf2df9e0413d3521661070103711545207a (for 2.6.23-rc1).

If you need some practical examples on using git-bisect, this one

http://www.reactivated.net/weblog/archives/2006/01/using-git-bisect-to-find-buggy-kernel-patches/

is a very good one (IMO).

> VP_IDE: VIA vt8231 (rev 10) IDE UDMA100 controller on pci0000:00:11.1
>     ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
>     ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
> Marking TSC unstable due to: possible TSC halt in C2.
> Time: acpi_pm clocksource has been installed.
> hda: PQI IDE DiskOnModule, ATA DISK drive
> hda: IRQ probe failed (0xfff2)

This message would indicate broken IRQ routing, however it is no
longer present in the log for the kernel 2.6.23-rc1-git4 ([3]).

Interesting that the kernel 2.6.22-git17 (log [2]) doesn't use via82cxxx
IDE host driver while the kernel 2.6.23-rc1-git4 (log [3]) does...?

> Clocksource tsc unstable (delta = 84358771493 ns)
> 
> So i went back to 2.6.22-git17.
> This morning i saw a fresh git4 and compiled/installed that.
> This kernel actually booted! (once)
> I had a netconsole running to catch the lucky event [3]
> 
> After about 2 minutes of working however, the whole machine froze.
> No message at the console, not able to toggle numlock, no magic
> sysrq key features: solid frozen.
> After the power cycle i was not able to boot the same kernel
> ever again. It was just like a timer had run out and it wouldn't 
> work anymore. 
> 
> I know my hardware is "ancient" and the flash thing is probably
> not current. My firewall however is solar powerpowered (10 watt 

Neat. :)

> power consumption) and it would be fun if i could run the latest/
> greatest kernels on it.

With the buggy commit number obtained from git-bisect it should be
fixed quite quickly.

> Config files and hdparm info on the DOM in the same directory as
> dmesg output.
> 
> Any comments appriciated.
> 
> Danny
> 
> [1] http://www.memorydepot.com/ssd_diskonmodule.asp
> [2] http://www.dth.net/kernel/via_output_2.6.22_git17
> [3] http://www.dth.net/kernel/via_output_2.6.23-rc1-git4

Thanks,
Bart
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/