From: dth <dth@dth.net>
To: linux-kernel@vger.kernel.org
Subject: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not
Date: Fri, 27 Jul 2007 21:38:32 +0200 [thread overview]
Message-ID: <20070727193832.GA20289@dth.net> (raw)
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 }
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:
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)
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
power consumption) and it would be fun if i could run the latest/
greatest kernels on it.
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
--
next reply other threads:[~2007-07-27 20:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 19:38 dth [this message]
2007-07-28 23:42 ` ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not Bartlomiej Zolnierkiewicz
2007-07-29 0:30 ` Danny ter Haar
2007-07-29 1:23 ` Danny ter Haar
2007-07-29 2:48 ` Gabriel C
2007-07-29 3:30 ` Danny ter Haar
2007-07-29 3:54 ` Gabriel C
2007-07-30 2:54 ` Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not: Danny ter Haar
2007-07-30 17:30 ` Len Brown
2007-07-31 1:10 ` Danny ter Haar
2007-07-31 4:00 ` Danny ter Haar
2007-07-31 14:30 ` Danny ter Haar
2007-08-01 0:44 ` Danny ter Haar
2007-08-01 20:03 ` Update: ACPI problems: 2.6.22-git17 working, 2.6.23-rc1* is not: (was ide not working) Danny ter Haar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070727193832.GA20289@dth.net \
--to=dth@dth.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox