On Wed, Apr 8, 2015 at 8:20 AM, Jan Engelhardt wrote:
> On Wednesday 2015-04-08 15:41, Jan Engelhardt wrote:
>
>>Starting somewhere around v4.0-rc1 and persisting through commit
>>v4.0-rc7, there is a new NULL deference apparently happening in
>>conjunction with xfs. This inhibits this machine's
On Wed, Apr 8, 2015 at 8:20 AM, Jan Engelhardt jeng...@inai.de wrote:
On Wednesday 2015-04-08 15:41, Jan Engelhardt wrote:
Starting somewhere around v4.0-rc1 and persisting through commit
v4.0-rc7, there is a new NULL deference apparently happening in
conjunction with xfs. This inhibits this
On Wednesday 2015-04-08 15:41, Jan Engelhardt wrote:
>Starting somewhere around v4.0-rc1 and persisting through commit
>v4.0-rc7, there is a new NULL deference apparently happening in
>conjunction with xfs. This inhibits this machine's booting,
>as xfs is used for the root filesystem.
>
>First
Starting somewhere around v4.0-rc1 and persisting through commit
v4.0-rc7, there is a new NULL deference apparently happening in
conjunction with xfs. This inhibits this machine's booting,
as xfs is used for the root filesystem.
First bisection points at first-bad commit v4.0-rc1~8, and since
Starting somewhere around v4.0-rc1 and persisting through commit
v4.0-rc7, there is a new NULL deference apparently happening in
conjunction with xfs. This inhibits this machine's booting,
as xfs is used for the root filesystem.
First bisection points at first-bad commit v4.0-rc1~8, and since
On Wednesday 2015-04-08 15:41, Jan Engelhardt wrote:
Starting somewhere around v4.0-rc1 and persisting through commit
v4.0-rc7, there is a new NULL deference apparently happening in
conjunction with xfs. This inhibits this machine's booting,
as xfs is used for the root filesystem.
First
6 matches
Mail list logo
