(2013/01/29 10:14), Thomas Renninger wrote: > On Thursday, January 24, 2013 09:23:14 AM Takao Indoh wrote: >> (2013/01/23 9:47), Thomas Renninger wrote: >>> On Monday, January 21, 2013 10:11:04 AM Takao Indoh wrote: >>>> (2013/01/08 4:09), Thomas Renninger wrote: >>> ... >>> >>>>> I tried the provided patches first on 2.6.32, then I verfied with >>>>> 3.8-rc2 >>>>> and in both cases the disk is not detected anymore in >>>>> reset_devices (kexec'ed/kdump) case (but things work fine without these >>>>> patches). >>>> >>>> So the problem that the disk is not detected was caused by exactmap >>>> problem you guys are discussing? Or still not detected even if exactmap >>>> problem is fixed? >>> >>> This problem is related to the 5 PCI resetting patches. >>> Dumping worked with a 2.6.32 and a 3.8-rc2 kernel, adding the PCI >>> resetting >>> patches broke both. I first tried 2.6.32 and verified with 3.8-rc2 to make >>> sure I didn't mess up the backport adjustings of the patches to 2.6.32. >> If you have a chance please try again the patches with the latest >> firmware. > Not sure I can update the firmware as this is a reference platform used exactly > like this in production. Anyway it seems that resetting device makes the disks disappear from your system. I'm wondering if this reset mechanism should be disabled by default and be enabled by boot parameter like reset_devices_on_dmar_fault to prevent a regression like your case. Thanks, Takao Indoh > > I also cannot see how this could help. > > Thomas > >
