Modul HPT366 w kernelu 2.6.2-2.2

[Rafał Gruszczyński]

Witam
Mimo usilnych staran nie moge zmusic kontrolera HPT372 to pracy. kazda
proba zamontowania konczy sie takim komunikatem:
 
Feb 22 15:37:40 server kernel: HPT372: IDE controller at PCI slot
0000:00:0e.0
Feb 22 15:37:40 server kernel: HPT372: chipset revision 5
Feb 22 15:37:40 server kernel: HPT37X: using 33MHz PCI clock
Feb 22 15:37:40 server kernel: Unable to handle kernel paging request at
virtual address 57e58965
Feb 22 15:37:40 server kernel: printing eip:
Feb 22 15:37:40 server kernel: e183f169
Feb 22 15:37:40 server kernel: *pde = 00000000
Feb 22 15:37:40 server kernel: Oops: 0000 [#1]
Feb 22 15:37:40 server kernel: CPU:    0
Feb 22 15:37:40 server kernel: EIP:    0060:[<e183f169>]    Tainted: P  
Feb 22 15:37:40 server kernel: EFLAGS: 00010206
Feb 22 15:37:40 server kernel: EIP is at
ide_pci_register_host_proc+0x29/0x40 [ide_core]
Feb 22 15:37:40 server kernel: eax: 57e58955   ebx: c15ec400   ecx:
e1ed1eb8   edx: 57e58955
Feb 22 15:37:40 server kernel: esi: d7125ddf   edi: d7125e34   ebp:
d7125dc4   esp: d7125dc4
Feb 22 15:37:40 server kernel: ds: 007b   es: 007b   ss: 0068
Feb 22 15:37:40 server kernel: Process modprobe (pid: 3607,
threadinfo=d7124000 task=d72d92e0)
Feb 22 15:37:40 server kernel: Stack: d7125de8 e1ed1713 e1ed1eb8
00000003 0000003f d7125ddf 08000000 0000000b 
Feb 22 15:37:40 server kernel: 00000001 d7125e1c e183c4c8 c15ec400
e1f81b56 00000001 d7125e0c 00000000 
Feb 22 15:37:40 server kernel: 00000001 0000ffff 00000000 00000000
c15ec400 e1f81b5d d7125e3c e183c54a 
Feb 22 15:37:40 server kernel: Call Trace:
Feb 22 15:37:40 server kernel: [<e1ed1713>]
init_chipset_hpt366+0x193/0x1d0 [hpt366]
Feb 22 15:37:40 server kernel: [<e183c4c8>]
do_ide_setup_pci_device+0x128/0x180 [ide_core]
Feb 22 15:37:40 server kernel: [<e183c54a>]
ide_setup_pci_device+0x2a/0x80 [ide_core]
Feb 22 15:37:40 server kernel: [<e1ed1db2>] init_setup_hpt366+0xa2/0x1a5
[hpt366]
Feb 22 15:37:40 server kernel: [<e1f81713>] hpt366_init_one+0x43/0x90
[hpt366]
Feb 22 15:37:40 server kernel: [<c01ac1cb>]
pci_device_probe_static+0x4b/0x60
Feb 22 15:37:40 server kernel: [<c01ac216>] __pci_device_probe+0x36/0x50
Feb 22 15:37:40 server kernel: [<c01ac25c>] pci_device_probe+0x2c/0x50
Feb 22 15:37:40 server kernel: [<c01ef4cd>] bus_match+0x3d/0x70
Feb 22 15:37:40 server kernel: [<c01ef5fa>] driver_attach+0x5a/0x90
Feb 22 15:37:40 server kernel: [<c01ef8f4>] bus_add_driver+0xa4/0xc0
Feb 22 15:37:40 server kernel: [<c01efd51>] driver_register+0x31/0x40
Feb 22 15:37:40 server kernel: [<c01ac43b>]
pci_register_driver+0x5b/0x80
Feb 22 15:37:40 server kernel: [<e183c6db>]
ide_pci_register_driver+0x3b/0x50 [ide_core]
Feb 22 15:37:40 server kernel: [<e1f81772>] hpt366_ide_init+0x12/0x20
[hpt366]
Feb 22 15:37:40 server kernel: [<c01340bb>] sys_init_module+0x10b/0x200
Feb 22 15:37:40 server kernel: [<c010b1b3>] syscall_call+0x7/0xb
Feb 22 15:37:40 server kernel: 
Feb 22 15:37:40 server kernel: Code: 8b 40 10 85 c0 75 f7 89 4a 10 c9 c3
89 0d 1c 08 85 e1 eb f6
 
Nie ma znaczenia czy, laduje go przez modprobe hpt366 czy przez dodanie
do initrd. 
Czy jest to jakis mój blad czy blad modulu w kernelu??
Jeśli mój blad to co mogę robic zle?
 
[root w server worek]# grep PREMO /etc/sysconfig/geninitrd
#PREMODS="hpt366 via82cxxx"
 
Dodam ze w 2.6.0-1.9 ten kontroler dzialal bez problemow. 
 
Pozdrawiam
Rafał Gruszczyński
mailto:pld w gizmonet.neostrada.pl