Bug 199223 - AACRAID crashes immediately on PPC32
Summary: AACRAID crashes immediately on PPC32
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Other (show other bugs)
Hardware: PPC-32 Linux
: P1 blocking
Assignee: drivers_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-27 13:16 UTC by carlojpisani
Modified: 2018-03-28 13:15 UTC (History)
0 users

See Also:
Kernel Version: 4.9.* .. 4.16.0
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description carlojpisani 2018-03-27 13:16:34 UTC
hi
insmod  /lib/modules/4.16.0-Fearless-Coyote-mdd-2xG4-dirty/kernel/drivers/scsi/aacraid/aacraid.ko

[  493.719845] Adaptec aacraid driver 1.2.1[50877]-custom 
[  493.719913] aacraid 0001:10:15.0: enabling device (0004 -> 0006) 
[  613.726766] AAC0: adapter kernel panic'd fffffffd. 
[  673.722761] AAC0: adapter kernel failed to start, init status = 48. 

# uname -r 
4.16.0-Fearless-Coyote-mdd-2xG4-git 
(it's the last kernel I got from the git repository) 

this kind of bug is also present in these kernels 
- kernel-4.9.72-2xG4 
- kernel-4.9.90-2xG4 

pci=nocrs doesn't help, I have already added it to cmdline

cat /proc/cmdline 
root=/dev/hda4 ro root=/dev/hda4 real_root=/dev/hda4 CONSOLE=/dev/tty1 pci=nocrs 

I am using this PCI-X SATA card (Adaptec AAR-2410SA)

0001:10:15.0 RAID bus controller: Adaptec AAC-RAID (rev 01) 
        Subsystem: Adaptec AAR-2410SA PCI SATA 4ch (Jaguar II) 
        Flags: 66MHz, slow devsel, IRQ 58 
        Memory at 84000000 (32-bit, prefetchable) [size=64M] 
        Expansion ROM at 80088000 [disabled] [size=32K] 
        Capabilities: [80] Power Management version 2 

the used target is an Apple PowerMac G4, "[M]irrore[D] [D]oors" (aka MDD) model.

let me know if you need more info, and which info you need
Thanks.
Comment 1 carlojpisani 2018-03-28 08:20:09 UTC
nsmod takes a lot of time, 2-3 minutes, then it crashes 

on dmesg i see 

immediately: 

[  491.162332] Adaptec aacraid driver 1.2.1[50877]-custom 
[  491.162402] aacraid 0001:10:15.0: enabling device (0004 -> 0006) 


2-3 minutes later ... 

[  611.170736] AAC0: adapter kernel panic'd fffffffd. 
[  671.170734] AAC0: adapter kernel failed to start, init status = 48.
Comment 2 carlojpisani 2018-03-28 08:36:46 UTC
giving a name functions, here we can see which functions fail inside the kernel module 

[ 1229.322354] aac_rx_restart_adapter AAC0: adapter kernel panic'd fffffffd.
[ 1289.322350] aac_rx_init AAC0: adapter kernel failed to start, init status = 48.

also, I tried passing pci=noacpi as kernel parameter

cat /proc/cmdline
root=/dev/hda4 ro root=/dev/hda4 real_root=/dev/hda4 CONSOLE=/dev/tty1 pci=noacpi

but it doesn't help
Comment 3 carlojpisani 2018-03-28 13:15:04 UTC
giving a name to called functions and points inside the kernel module:

Adaptec aacraid driver 1.2.1[50877]-custom
aac_rx_init initialize
aac_rx_init Check to see if the board panic'd while booting
aac_rx_init says the board has no panic while booting
aac_rx_init AAC0: adapter self-test OK
aac_rx_init AAC0: adapter monitor p
aac_rx_init Wait for the adapter to be up and running
aac_rx_init  Wait up to 3 minutes
aac_rx_restart_adapter AAC0: adapter kernel panic'd fffffffd.
aac_rx_init AAC0: adapter kernel failed to start, init status = 48.
aac_rx_init -> error_iounmap

(names are based on comments written inside the driver
I have just added a printk)

Note You need to log in before you can comment on or make changes to this bug.