#14795 closed bug (fixed)
System unbootable (stops on rocket) in hrev52709
| Reported by: | KapiX | Owned by: | mmu_man |
|---|---|---|---|
| Priority: | normal | Milestone: | R1/beta2 |
| Component: | Drivers/Network/ipro1000 | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
As in title. I can't check what is failing (I suspect ipro1000 driver since it came up in the syslog) because I can't get the bootloader menu (#14794).
Change History (8)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
| Component: | - General → Drivers/Network/ipro1000 |
|---|---|
| Owner: | changed from to |
| Status: | new → in-progress |
comment:3 by , 6 years ago
I've just pushed hrev52712 which will possibly help with or even outright fix this. It seems the boot was probably not broken, but it might have taken up to multiple minutes, depending on the hardware you have.
comment:4 by , 6 years ago
I finally managed to get into KDL after invoking the hang, and ... LOL, that wasn't the problem. It's trying to map_physical_memory on a range of NULL to the maximum of a 64-bit pointer, which then deadlocks in the physical memory mapper waiting for more resources.
It seems there are multiple bugs to fix here...
comment:5 by , 6 years ago
| Owner: | changed from to |
|---|---|
| Status: | in-progress → assigned |
"Fixed" in hrev52713 by partially reverting an earlier change by mmu_man. Reassigning to him so he can fix it properly.
comment:6 by , 6 years ago
would you mind checking the BAR size in the PCI dump from syslog? I think it should be in. In any case, the code should be correct, at least I followed the osdev wiki.
comment:7 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Proper fix merged in hrev52715.
comment:8 by , 5 years ago
| Milestone: | Unscheduled → R1/beta2 |
|---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
Confirmed it's ipro1000, I just managed to reproduce it here. That's what I get for not testing on all devices...
If I backlist the driver and then activate it after finishing the boot, the system deadlocks but I can still move windows around. I can't do anything else though.