Bug#1093371: megaraid_sas didn't work anymore with Xen
Hi,
On Fri, Jan 17, 2025 at 11:22:50PM +0100, Salvatore Bonaccorso wrote:
> Control: tags -1 + moreinfo
> Hi,
>
> On Fri, Jan 17, 2025 at 08:07:31PM +0100, Nicolas DEFFAYET wrote:
> > Package: linux-image
> > Version: 6.1.124-1
> > Severity: critical
> >
> > Hardware:
> > Dell PowerEdge R520 (last BIOS version)
> > Dell PERC H710P (last firmware version)
> >
> > On physical machine:
> > Kernel 6.1.0-25 booted from xen works fine
> > Kernel 6.1.0-30 standalone works fine
> > Kernel 6.1.0-30 booted from xen is looping on megaraid_sas errors bellow.
> >
> > -> Not sure why and what changes between 6.1.0-25 and 6.1.0-30 generate this issue.
> >
> > [ OK ] Started snmpd.service …anagement Protocol (SNMP) Daemon..
> > [ OK ] Finished e2scrub_reap.serv…ine ext4 Metadata Check Snapshots.
> > [ OK ] Started xen.service - LSB: Xen daemons.
> > [ 47.849820] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 47.850296] megaraid_sas 0000:01:00.0: Error building command
> > [ 47.891183] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 47.891709] megaraid_sas 0000:01:00.0: Error building command
> > [ 47.910362] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 47.910780] megaraid_sas 0000:01:00.0: Error building command
> > [ 47.929331] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 47.929840] megaraid_sas 0000:01:00.0: Error building command
> > [ 47.970385] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 47.970810] megaraid_sas 0000:01:00.0: Error building command
> > [ 47.989357] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 47.989769] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.023179] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.023643] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.063207] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.063756] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.095228] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.095999] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.100825] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.101275] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.139157] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.139208] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.139621] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.139635] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.183179] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.183188] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.183201] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.183217] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.219178] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.219629] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.251184] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.251647] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.283142] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.283669] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.315138] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.315684] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.347147] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.347684] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.375203] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.375816] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.407171] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.407721] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.439138] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.439764] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.475163] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.475163] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.475181] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.475196] megaraid_sas 0000:01:00.0: Error building command
> > [ 48.507178] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.507178] megaraid_sas 0000:01:00.0: megasas_build_io_fusion 3259 sge_count (-12) is out of range. Range is: 0-64
> > [ 48.507183] megaraid_sas 0000:01:00.0: Error building command
>
> Can you pinpoint more specifically where the issue has been introduced
> in the Debian released versions? The one with ABI 25 was 6.1.106-3,
> followed by 6.1.112-1, 6.1.115-1, 6.1.119-1, 6.1.123-1 and 6.1.124-1.
>
> Can you pin-point more which of the Debian released versions introduce
> the problem for you? (going a further step once you have that, could
> you bisect the upstream changes to pinpoint the commit upstream in the
> stable series which introduces the problem?)
In particular I would be interested to know if the issue start to
happen between 6.1.112-1 and 6.115-1.
But in any case knowing which Debian revision exactly introduces the
problem would be helpful, then go down more to the upstream versions
and a bisect of them.
Regards,
Salvatore
Reply to: