2.4.22 / HPT372N
As i used the pen&paper method for oops tracking i dont have full oops.
In hpt366.c function hpt372_tune_chipset line 427:
list_conf = pci_bus_clock_list(speed,
(struct chipset_bus_clock_list_entry *)
pci_get_drvdata(dev));
pci_get_drvdata(dev) returns NULL.
Crash happens only if there are some devices attached to hpt.
lspci -vv:
02:00.0 RAID bus controller: Triones Technologies, Inc. HPT366/368/370/370A/372 (rev 06)
Subsystem: Triones Technologies, Inc. HPT370A
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 120 (2000ns min, 2000ns max)
Interrupt: pin A routed to IRQ 22
Region 0: I/O ports at a000 [size=8]
Region 1: I/O ports at a400 [size=4]
Region 2: I/O ports at a800 [size=8]
Region 3: I/O ports at ac00 [size=4]
Region 4: I/O ports at b000 [size=256]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Full config, dmesg(of a non-crash boot) & lspci:
Quoted 7 lines · Marko Kreen
As i used the pen&paper method for oops tracking i dont have full oops.
In
hpt366.cfunctionhpt372_tune_chipsetline 427:
list_conf= pci_bus_clock_list(speed,
(structchipset_bus_clock_list_entry*)
I thought I'd fixed that crash case but it seems your system is over clocked.
FREQ: 85 PLL: 41
hpt: no known IDE timings,
so your PCI bus is running at somewhere about 35Mhz and outside the drivers safe threshold.
Alan
Quoted 9 lines · Alan Cox
Quoted 7 lines · Marko Kreen
As i used the pen&paper method for oops tracking i dont have full oops.
In
hpt366.cfunctionhpt372_tune_chipsetline 427:
list_conf= pci_bus_clock_list(speed,
(structchipset_bus_clock_list_entry*)
Quoted 8 lines
I thought I'd fixed that crash case but it seems your system is over clocked.
FREQ: 85 PLL: 41
hpt: no known IDE timings,so your PCI bus is running at somewhere about 35Mhz and outside the drivers safe threshold.
Thats surprising, nobody has intentionally overclocked it.
Now we did some experimenting with it and no BIOS settings seem to affect the FREQ numbers. (Lower CPU/mem speed, 50/25 AGP/PCI speed.) The FREQ still stays fixed at 85.
Motherboard is EP-4PDA2+.
Any idea how to remove the overclocking? Otherwise it seems like driver bug to me.
Signature · 1 line
marko
Quoted 10 lines · Marko Kreen
Quoted 2 lines
so your PCI bus is running at somewhere about 35Mhz and outside the drivers safe threshold.
Thats surprising, nobody has intentionally overclocked it.
Now we did some experimenting with it and no BIOS settings seem to affect the FREQ numbers. (Lower CPU/mem speed, 50/25 AGP/PCI speed.) The FREQ still stays fixed at 85.
Any idea how to remove the overclocking? Otherwise it seems like driver bug to me.
The hardware measures the PCI bus clock against its own sources and the 85 (0x55) is its timing measurement. The maximum range for the 33Mhz timings on the card is < 0x55 so it decides your clock is outside the safe range. HPT have never given us 40Mhz clock timings for the 372N or as far as I can tell published them so we don't know how to drive it at 40Mhz just 33 and 66.
You could tweak the driver to accept 0x55 but either the card clock is out or you are overclocking your IDE by doing that.