Opened 12 years ago

Closed 6 years ago

Last modified 5 years ago

#9167 closed bug (fixed)

KDL after plugging in USB-to-serial device

Reported by: dsuden Owned by: axeld
Priority: normal Milestone: R1/beta2
Component: Network & Internet/Stack Version: R1/alpha4
Keywords: Cc: ttcoder
Blocked By: Blocking:
Platform: All

Description (last modified by diver)

Maybe this was caused by plugging in the USB-to-serial adapter while the computer was running instead of with it turned off...I've since done a reboot and we'll see if it happens again or not. But when I plugged one of those USB-2-Serial dongle adapters to a USB port on the back of my Haiku machine, I got the attached KDL.

KDL due to plugging in USB-2-Serial adapter while computer running

Attachments (1)

IMG_0482.JPG (960.2 KB ) - added by dsuden 12 years ago.
KDL due to plugging in USB-2-Serial adapter while computer running

Download all attachments as: .zip

Change History (9)

by dsuden, 12 years ago

Attachment: IMG_0482.JPG added

KDL due to plugging in USB-2-Serial adapter while computer running

comment:1 by anevilyak, 12 years ago

Interestingly, the attached panic actually points towards a memory management issue in the network stack, and doesn't appear to be related to plugging that adapter in at first glance.

comment:2 by dsuden, 12 years ago

Might just have been coincidence in that case. We'll monitor the situation and see if it repeats itself and under what conditions.

comment:3 by diver, 10 years ago

Component: - GeneralNetwork & Internet/Stack
Description: modified (diff)
Owner: changed from nobody to axeld

comment:4 by jackburton, 6 years ago

No update in 6 years. Could be closed, I guess.

comment:5 by diver, 6 years ago

#5527 could be related.

comment:6 by ttcoder, 6 years ago

Cc: ttcoder added

This must have been the very sole time I ever saw "ObjectDepot" appear in a KDL for us in all those years, let alone for our stations. As to the UDP and TCP code, there were 2 bugs, the former was fixed in hrev51603 and we never saw it again.

So that one would be for the archives... I think dsuden will agree to close this too.

comment:7 by waddlesplash, 6 years ago

Resolution: fixed
Status: newclosed

Indeed, it looks like this was a duplicate of #5527, which was fixed.

comment:8 by nielx, 5 years ago

Milestone: R1R1/beta2

Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone

Note: See TracTickets for help on using tickets.