Changes between Initial Version and Version 1 of Ticket #18454, comment 38


Ignore:
Timestamp:
Dec 10, 2023, 12:48:24 AM (12 months ago)
Author:
Mas4hmad

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #18454, comment 38

    initial v1  
    55
    66yes, it could be... from syslog.7 (with lenovo thinkpad x1 carbon) we can see from line 456 that i have {{{_Y17}}} parameter cause have length 0, in line 457 i got {{{_Y18}}} have same length until line 467 i got {{{_Y22}}} parameter.
    7 
    8 in line 468 i got {{{_Y23}}} parameter, but it
    97
    108{{{
    … …  
    2826}}}
    2927
    30 but it can be weird for line 456 which i got {{{_Y24}}} parameter
     28in line 468 i got {{{_Y23}}} parameter, but it jumped to correct maximum address (with wrong range minimum and length)
     29
     30but it can be weird for line 456 which i got right pci range and address eventough have {{{_Y24}}} parameter.
     31
     32is that pci range with that parameter could/might be treat separately? (as we can see from linux dmesgpci,  the pci range with that parameter not seems there like pci range without that parameter. i mean, linux don't generally treat pci range with that parameter unlike other ones).
    3133
    3234from thinkpad x1 carbon it's not hit ASSERT like should be like i got from ideapad flex 10