From: Foli Ayivoh <it21@arcor.de>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andy Shaw <ashaw@seberg.co.uk>,
Stefan Smietanowski <stesmi@stesmi.com>
Subject: Re: [BUGREPORT 1/3] Kernel Oops with HPT372A IDE controller
Date: Fri, 9 Jun 2006 11:51:29 +0200 [thread overview]
Message-ID: <200606091151.29642.it21@arcor.de> (raw)
In-Reply-To: <446CEB72.30302@ru.mvista.com>
Sergei Shtylyov wrote:
>
> Hello, I wrote:
>
> >>>> Kernel Oops with HighPoint RocketRAID ATA133 aka HPT372A/N since
> >>>> kernel 2.6
> >>>> Now tested with kernel 2.6.17-rc4
>
> >>>> Kernel is on bootable CD-ROM
> >>>> Modules are loaded from initrd
>
> >>>> This is what I copied from screen:
>
> >>>> Loading hpt366
> >>>> [17179578.396000] HPT372A: IDE controller at PCI slot 0000:01:0a.0
> >>>> [17179578.400000] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
> >>>> [17179578.404000] ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [APC1]
> >>>> -> GSI 16 (level, high) -> IRQ 18
> >>>> [17179578.408000] HPT372A: chipset revision 2
> >>>> [17179578.412000] HPT372A: 100% native mode on irq 18
> >>>> [17179578.416000] hpt: HPT372N detected, using 372N timing.
> >>>> [17179578.420000] FREQ: 125 PLL: 45
> >>>> [17179579.536000] No Clock Stabilization!!!
> >>>> [17179579.540000] hpt: no known IDE timings, disabling DMA
> >>>> [17179579.544000] hpt: HPT372N detected, using 372N timing.
> >>>> [17179579.548000] FREQ: 156 PLL: 66
> >>>> [17179579.664000] No Clock Stabilization!!!
>
> >>> Please try my latest patches. This one should fix this (and oops
> >>> should be gone):
>
> >>> http://marc.theaimsgroup.com/?l=linux-ide&m=114677223914159&w=2
>
> >> all patches applied, but I still get Kernel Oops :-(
>
> >> some smal difference here:
>
> >> HPT372A: IDE controller at PCI slot 0000:01:0a.0
> >> ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
> >> ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [APC1] -> GSI 16 (level,
> >> high) -> IRQ 18
> >> HPT372A: chipset revision 2
> >> HPT372A: 100% native mode on irq 18
> >> + HPT37X: no clock data saved by BIOS
> >> + HPT3xxN detected, FREQ: 124, PLL: 45
> >> + HPT37xN unknown bus timing [48 4].
>
> > Hm, the BIOS seems to behave nastier than expected -- looks like it
> > reprograms DPLL but doesn't save the initial f_CNT (needed to determine the
> > PCI clock). Well, I know that it always sets DPLL to 50 MHz, no matter
> > what's the chip, so will try to work around this... :-/
>
> OTOH, there might be another reason to that: the BIOS saves f_CNT but the
> register it uses for this isn't mapped to the PCI config. space, only to the
> I/O space (it's undocumented, after all). Andy Shaw's report seems to confirm
> this -- his RAID BIOS seems to be modern enough to save the f_CNT but the
> driver probably fails to read it (I don't have the full boot log yet).
> So, try the attached patch please. Foli, if this won't help, can you tell
> what version your HighPoint BIOS is?
>
> MBR, Sergei
>
Hello Sergei,
I'm back.
SORRY! for the delay!
-----------------------------------------------------------------------------------------------------------------
this time patches tested with stable kernel 2.6.16.20
lspci -xxx -s 1:a (without hpt366 driver)
01:0a.0 RAID bus controller: Triones Technologies, Inc. HPT372A/372N (rev 02)
00: 03 11 05 00 05 00 30 02 02 00 04 01 08 40 00 00
10: 01 7c 00 00 01 80 00 00 01 84 00 00 01 88 00 00
20: 01 8c 00 00 00 00 00 00 00 00 00 00 03 11 01 00
30: 00 00 00 00 60 00 00 00 00 00 00 00 0b 01 08 08
40: 42 82 84 12 42 82 84 12 8a f4 c1 0a 8a f4 c1 0a
50: 05 00 00 00 05 00 00 00 1b 00 10 23 1e 00 20 00
60: 01 00 22 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 7d 00 f0 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
after applying your patches in following order:
HPT3xxN-clocking-fixes.patch
HPT37x-fix-timing-tables.patch
HPT3xx-fix-hotswap.patch
HPT3xx-fix-case-of-multiple-chips.patch
HPT3xx-use-f_CNT-saved-by-BIOS.patch
HPT3xx-optimize-timing-tables.patch
HPT3xx-rework-rate-filtering.patch
HPT37x-read-f_CNT-from-port.patch
HPT3xx-print-real-chip-name.patch
HPT3xx-use-pci_find_slot.patch
HPT3xx-cache-MCR-address.patch
HPT37x-merge-speedproc.patch
(for info: last two patches get the first two hunks rejeckted, only comments)
I get this:
HPT372N: IDE controller at PCI slot 0000:01:0a.0
ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [APC1] -> GSI 16 (level, high) -> IRQ 185
HPT372N: chipset revision 2
HPT372N: 100% native mode on irq 185
HPT372N: FREQ: 80, PLL: 35
HPT372N: using 50MHz internal PLL
ide2: BM-DMA at 0x8c00-0x8c07, BIOS settings: hde:DMA, hdf:DMA
ide3: BM-DMA at 0x8c08-0x8c0f, BIOS settings: hdg:pio, hdh:pio
Probing IDE interface ide2...
hde: WDC WD800BB-00CAA1, ATA DISK drive
hdf: WDC WD800BB-00BSA0, ATA DISK drive
ide2 at 0x7c00-0x7c07,0x8002 on irq 185
hde: max request size: 128KiB
hde: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
hde: cache flushes not supported
hde: hde1
hdf: max request size: 128KiB
hdf: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
hdf: cache flushes not supported
hdf: hdf1
(for info: on ide3 no disks)
lspci -xxx -s 1:a (with patched hpt366 driver)
01:0a.0 RAID bus controller: Triones Technologies, Inc. HPT372A/372N (rev 02)
00: 03 11 05 00 05 00 30 02 02 00 04 01 00 78 00 00
10: 01 7c 00 00 01 80 00 00 01 84 00 00 01 88 00 00
20: 01 8c 00 00 00 00 00 00 00 00 00 00 03 11 01 00
30: 01 00 0a 50 60 00 00 00 00 00 00 00 0b 01 08 08
40: 42 82 84 12 42 82 84 12 8a f4 c1 0a 8a f4 c1 0a
50: 05 00 00 00 05 00 00 00 1b 00 00 21 23 00 25 00
60: 01 00 22 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 90 00 f0 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-----------------------------------------------------------------------------------------------------------------
thanks for your time and efforts!
can you also help how to access the RAID 1 set?
best regards
Foli
prev parent reply other threads:[~2006-06-09 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 19:10 [BUGREPORT 1/3] Kernel Oops with HPT372A IDE controller Foli Ayivoh
2006-05-15 14:54 ` Sergei Shtylyov
2006-05-16 22:59 ` Foli Ayivoh
2006-05-17 14:36 ` Sergei Shtylyov
2006-05-18 21:47 ` Sergei Shtylyov
2006-05-19 7:36 ` Andy Shaw
2006-05-19 16:58 ` Sergei Shtylyov
2006-06-09 9:51 ` Foli Ayivoh [this message]
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=200606091151.29642.it21@arcor.de \
--to=it21@arcor.de \
--cc=101551.753@compuserve.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ashaw@seberg.co.uk \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@ru.mvista.com \
--cc=stesmi@stesmi.com \
/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;
as well as URLs for NNTP newsgroup(s).