#8878 closed bug (invalid)
KDL on newer Apple trackpad/internal keyboard
Reported by: | DHowett | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | System/Kernel | Version: | R1/Development |
Keywords: | boot-failure | Cc: | |
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
I'm pretty sure that something about the USB devices in newer apple laptops causes the kernel to explode.
Touch the trackpad/internal keyboard just outside the bootloader and it panics normally, it panics so hard that it won't even display the backtrace. I managed to get one though.
Attachments (2)
Change History (12)
by , 12 years ago
Attachment: | Photo Aug 12, 2 39 05 PM.jpg added |
---|
comment:1 by , 12 years ago
This is coming from IRC, I am not the bug reporter so I don't have all the details.
by , 12 years ago
Attachment: | 0001-Check-if-name-is-NULL-before-calling-strcmp.patch added |
---|
Check if name is NULL before calling strcmp() on it. This should prevent the KDL here by returning a NULL command instead
comment:2 by , 12 years ago
patch: | 0 → 1 |
---|
comment:3 by , 12 years ago
Blocking: | 7665 added |
---|
comment:4 by , 8 years ago
This patch doesn't look right, for several reasons.
1) There is no reason for this command to be called with a NULL string. If it happens, it's better to crash so the actual bug can be fixed, instead of hiding the issue. 2) In the attached KDL, nothing points at the passed string being NULL. Parameters are passed on the stack, so you couldn't see them in that picture. But, if the problem was dereferencing a NULL pointer, the message would say "unhandled page fault at 0", and it says some other address. I think you saw the 0 in EAX, but that is probably the index into the strings used by strcmp. 3) If we check the code in the HID keyboard driver (src/add-ons/kernel/drivers/input/usb_hid/KeyboardProtocolHandler.cpp), we can see that the string passed is a constant, and cannot be NULL. But this also means, it cannot be the cause of the page fault if everything is going ok.
So, this issue points at some memory corruption iside the kernel. Maybe the string was overwritten with something, or maybe the list of KDL commands is corrupt.
Is the problem still valid? Can anyone reproduce it in recent versions of Haiku?
comment:5 by , 8 years ago
patch: | 1 → 0 |
---|
comment:6 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:7 by , 6 years ago
Keywords: | boot-failure added |
---|
comment:8 by , 6 years ago
Blocking: | 7665 removed |
---|
comment:10 by , 5 years ago
Milestone: | R1 |
---|
Remove milestone for tickets with status = closed and resolution != fixed
KDL of crash