Skip to contentSkip to conversation

New: megraid_mbox kernel panic during st driver initialization

Bugme-new Andrew Morton 2 participants 2 messages Jul 31, 2008 1 message not in the archive SCSI

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]/

Andrew Morton

author
#1 lore raw

(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface).

This bugzilla report appears to not have been sent out to the scsi list.

Quoted 18 lines · On Thu, 31 Jul 2008 07:15:37 -0700 (PDT) [email protected] wrote:

http://bugzilla.kernel.org/show_bug.cgi?id=11194

           Summary: megraid_mbox kernel panic during st driver
                    initialization
           Product: IO/Storage
           Version: 2.5
     KernelVersion: 2.6.25
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: SCSI
        AssignedTo: [email protected]
        ReportedBy: [email protected]
Quoted 3 lines

Latest working kernel version: 2.6.24

Earliest failing kernel version: 2.6.26

The kernel versions are ambiguous.

Which is the earliest failing kernel version?

Quoted 33 lines

Distribution: Debian Lenny (-testing + -unstable + kernel trunk for debian)

Hardware Environment: ASUS P4B 2.0 GHz P4 Motherboard, Dell PERC3/DC (like AMI MegraRAID Elite 1600) LVD Ultra3 SCSI Adaptor with four 80 GB drives on Channel 0 and a SCSI-U2 Seagate DDS-4 tape drive on Channel 1
Software Environment: Debian Lenny (up-to-date), with some unstable and tested with the testing kernel (.25) and the trunk kernel (.26)

Problem Description: The kernel panics (claiming it's in the megaraid_mbox driver) during boot when the st driver would normally report

st0: Block limits 1 - 16777215 bytes.

This is after the logical disk has been found and all filesystems mounted, so the RAID part of the driver is probably fine.

The point at which

st 0:1:6:0: Attached scsi tape st0
st 0:1:6:0: st0: try direct i/o: yes (alignment 512 B)

appears with .24 is passed before the panic, but I haven't actually seen those messages as they scroll by too quickly.

Steps to reproduce:

1) Install debian lenny with a .24 kernel (I'm not sure how you would do that now that .24 is no longer the testing kernel); maybe beta2 would still let you.
2) Install -testing kernel (.25)
3) Attempt to boot using the new kernel
4) Kernel panics, system is unusable

#2 lore raw
Quoted 7 lines · On Thu, 31 Jul 2008 10:48:10 -0700 Andrew Morton <[email protected]>…
Quoted 3 lines

Latest working kernel version: 2.6.24
Earliest failing kernel version: 2.6.26

The kernel versions are ambiguous.

Which is the earliest failing kernel version?

Sorry about that; I did latest failing (unless .27 is out; I haven't tested it). Earliest failing is 2.6.25.

Quoted 38 lines
Quoted 37 lines

Distribution: Debian Lenny (-testing + -unstable + kernel trunk for debian)

Hardware Environment: ASUS P4B 2.0 GHz P4 Motherboard, Dell PERC3/DC (like AMI MegraRAID Elite 1600) LVD Ultra3 SCSI Adaptor with four 80 GB drives on Channel 0 and a SCSI-U2 Seagate DDS-4 tape drive on Channel 1 Software Environment: Debian Lenny (up-to-date), with some unstable and tested with the testing kernel (.25) and the trunk kernel (.26)

Problem Description: The kernel panics (claiming it's in the megaraid_mbox driver) during boot when the st driver would normally report

st0: Block limits 1 - 16777215 bytes.

This is after the logical disk has been found and all filesystems mounted, so the RAID part of the driver is probably fine.

The point at which

st 0:1:6:0: Attached scsi tape st0
st 0:1:6:0: st0: try direct i/o: yes (alignment 512 B)

appears with .24 is passed before the panic, but I haven't actually seen those messages as they scroll by too quickly.

Steps to reproduce:

1) Install debian lenny with a .24 kernel (I'm not sure how you would do that now that .24 is no longer the testing kernel); maybe beta2 would still let you. 2) Install -testing kernel (.25)
3) Attempt to boot using the new kernel
4) Kernel panics, system is unusable

Signature · 5 lines
And that's my crabbing done for the day.  Got it out of the way early, 
now I have the rest of the afternoon to sniff fragrant tea-roses or 
strangle cute bunnies or something.   -- Michael Devore
GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C      http://gnupg.org
No more sea shells:  Daniel's Weblog    http://cshore.wordpress.com