#16973 closed bug (fixed)
KDL: address must be dword aligned
| Reported by: | miqlas | Owned by: | waddlesplash |
|---|---|---|---|
| Priority: | normal | Milestone: | R1/beta4 |
| Component: | Drivers/Disk/NVMe | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | #16955 | |
| Platform: | All |
Description (last modified by )
Tried to start WebPositive on hrev55107 64 bit.
Attachments (23)
Change History (43)
by , 4 years ago
| Attachment: | EF0EFCE0-4EF3-430F-814D-72BE036D2964.jpeg added |
|---|
by , 4 years ago
| Attachment: | 1E358E5C-1E54-4DED-A318-603A840C178C.jpeg added |
|---|
by , 4 years ago
| Attachment: | E5A6B808-0587-4F3A-8470-54EA26A19DD7.jpeg added |
|---|
comment:1 by , 4 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 4 years ago
| Component: | File Systems/packagefs → Drivers/Disk/NVMe |
|---|---|
| Owner: | changed from to |
comment:3 by , 4 years ago
No idea how this might have happened, and not sure when I'll have time to investigate. The DMAResource should have bounced all unaligned addresses...
by , 3 years ago
| Attachment: | P_20211017_175655.jpg added |
|---|
by , 3 years ago
| Attachment: | P_20211017_175723.jpg added |
|---|
by , 3 years ago
| Attachment: | P_20211017_175642.jpg added |
|---|
by , 3 years ago
| Attachment: | P_20211017_175634.jpg added |
|---|
by , 3 years ago
| Attachment: | P_20211017_175739.jpg added |
|---|
by , 3 years ago
comment:5 by , 3 years ago
| Status: | new → in-progress |
|---|
comment:7 by , 3 years ago
| Milestone: | Unscheduled → R1/beta4 |
|---|---|
| Resolution: | → fixed |
| Status: | in-progress → closed |
Diver reports that the KDL is indeed fixed.
by , 3 years ago
| Attachment: | Telegram-1289-debug-27-10-2021-01-46-33.report added |
|---|
comment:9 by , 3 years ago
Tried to start Telegram_desktop / telegram_desktop-3.1.9-1-x86_64.hpkg / hrev55585 64 bit.
telegram_desktop-3.1.9-2-x86_64.hpkg - work fine
comment:10 by , 3 years ago
The newer telegram_desktop package works? So, what is the problem then?
Either way, a Telegram crash is probably not a Haiku problem.
comment:11 by , 3 years ago
As far as I understand, the kim1963's problem returned after your commit https://github.com/haikuports/haikuports/commit/ed11128d7ee87dbe3115d9a0c155614624070efe.
Immediately after starting Telegram a KDL occurs, after which he types "cont" and gets a corresponding crash of Telegram (which makes sense).
PS: I hope kim1963 will attach a KDL photo here soon ;)
comment:12 by , 3 years ago
Ah, that makes sense. Yes, please attach the KDL photo. (Can you not reproduce it, then, 3dEyes?)
by , 3 years ago
| Attachment: | screenshot1112.png added |
|---|
by , 3 years ago
| Attachment: | screenshot1114.png added |
|---|
by , 3 years ago
| Attachment: | P_20211027_120937.jpg added |
|---|
comment:13 by , 3 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
by , 3 years ago
| Attachment: | P_20211027_120949.jpg added |
|---|
by , 3 years ago
| Attachment: | P_20211027_120959.jpg added |
|---|
by , 3 years ago
| Attachment: | P_20211027_121029.jpg added |
|---|
by , 3 years ago
| Attachment: | P_20211027_121035.jpg added |
|---|
by , 3 years ago
| Attachment: | P_20211027_121045.jpg added |
|---|
by , 3 years ago
| Attachment: | P_20211027_121052.jpg added |
|---|
by , 3 years ago
| Attachment: | P_20211027_121121.jpg added |
|---|
comment:14 by , 3 years ago
Can you not reproduce it, then, 3dEyes?
I cannot reproduce this bug anymore on Haiku hrev55592 revision. Probably because I have a different NVME controller.
comment:15 by , 3 years ago
Please update to hrev55596 and then upload a new syslog, as there is more information that will be printed to it now (no need to trigger the KDL, it will definitely still occur.)
comment:16 by , 3 years ago
At least this problem does not trigger for me under QEMU when launching Telegram, with the default NVMe settings (block size 512).
comment:17 by , 3 years ago
OK, after staring at the code more, I realized there was a missing case. See if hrev55599 fixes the problem. If not, please do upload a syslog.
by , 3 years ago
| Attachment: | syslog55592 added |
|---|
by , 3 years ago
| Attachment: | Telegram-1283-debug-28-10-2021-02-16-54.report added |
|---|
comment:19 by , 3 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Very good, thanks for your patience!
comment:20 by , 3 years ago
| Blocking: | 16955 added |
|---|
Changing component since the top of the backtrace is in the NVMe driver.