Upon further investigation, I added some debug printk() statements.
Assuming buffering is not confusing the issue, it looks like the machine
is calling this subroutine, but the subroutine never returns;
ide_config_drive_speed(drive, speed);
The parms are set to these values when the call is made:
drive->name = hde
speed = 0x44
The subroutine ide_config_drive_speed() is part of ide.c
Best Regards,
Robert Laughlin
-- Forwarded message --
Date: Thu, 2 Dec 1999 09:04:10 -0500 (EST)
From: Robert <[EMAIL PROTECTED]>
To: Tim Moore <[EMAIL PROTECTED]>
Cc: raid <[EMAIL PROTECTED]>, Andre Hedrick <[EMAIL PROTECTED]>
Subject: HPT366 prevents boot on Abit BE-6 (probably not raid related)
I am still trying to get my HPT366 channels to work on my ABIT BE6
motherboard. I really appreciate the emails I have gotten to date, but
there is still no joy. Following in the footsteps of Tim Moore, I
upgraded to 2.2.13 with patches raid0145-19990824-2.2.11, and
ide.2.2.13.1999.patch applied. This has made no difference. I
noticed there is a debug option in hpt366.c, namely
HPT366_DEBUG_DRIVE_INFO
So I turned this on to see if it would help me see where the problem is.
So at this point I am getting a few more messages, which may help pin down
where the trouble is. The last message I now get at boot time is coming
from line# 150 in hpt366.c
pci_bus_clock_list: found match: 0x90c9a731
where the hex number is the value of: chipset_table->chipset_settings
which is about to be returned from the subroutine: pci_bus_clock_list()
This subroutine is only called from 3 places, all of which are inside the
same switch statement. They all head for line 192 where there are only
three statements before the next printk(), which of course never comes
out. So, assuming that there in nothing sitting in a buffer someplace,
(and I admit that I do not know enough about the console i/o at this stage
of things to know the affects of buffering), then the system is locking up
on one of those 3 statements, which are:
reg2 &= ~0x8000;
pci_write_config_dword(HWIF(drive)->pci_dev, regtime, reg2);
err = ide_config_drive_speed(drive, speed);
It looks safe to rule out the 1st one. Anyone have any suggestions as to
what is going wrong, or how to fix it?
Best Regards,
Robert Laughlin
