Opened 14 years ago
Closed 14 years ago
#5071 closed bug (duplicate)
Getting KDL while scanning wireless networks ...
| Reported by: | herdemir | Owned by: | colin |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Network & Internet/Wireless | Version: | R1/Development |
| Keywords: | iprowifi2200 | Cc: | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
First of all, Thanks Colin for your work with wlan stack. Thanks to you, I'm able to write this ticket under haiku with Intel Pro Wireless 2200BG wireless card, which was the last hardware that wasn't supported by Haiku until NOW! ;) . Thanks.
As for bug report:
ASSERT_FAILED(src/system/kernel/condition_variable.cpp:line 216) sConditionVariableHash.Lookup(object) == __null
After getting to the desktop I am getting to KDL mentioning above. Since I can't provide a screenshot, I will explain it with words. After I looked to backtrace, it gets assertion failure at following function, with values:
ConditionVariable::Publish(<some adress value>, "scan")
It seems to KDL while scanning wireless networks. I typed several times co until I connect to my wireless network ,the KDls stop. I can connect to internet with no problem. I tried it yesterday with a previos build, too, but I wasn't getting such KDLs. It seems some recent changes to condition variables causes such KDL.
I also used your wlanconfig tool and tried to scan wireless networks, but it KDLed immediately at the same function, but the reason for KDL exception this time was a page fault. This time co becomes useless, and need reboot. It just happens at scanning wireless networks.
If I can find my digital camera, I will post screenshots, but it may come a little late.
Tested revision: hrev34449
Change History (2)
comment:1 by , 14 years ago
| Owner: | changed from to |
|---|
comment:2 by , 14 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Replying to herdemir:
Thank you for taking the time of writing this bug report!
I'm pretty sure I know the reason for this crash, so no need for the screenshot (yet ;)
This Bug Report pin points to the same fundamental bug as reported in #5072 which provides a screenshot already. So I'm closing this ticket as a duplicate. This is no critic on your bug report herdemir, ticket #5072 just appeared somewhat earlier on my radar :)