This would explain the lack of correlation between card read-write speed and the crashes, and clip length and complexity and the crashes. These bad sections will in theory survive a standard reformat/erase procedure, and then when the camera tries to re-record data over the bad sections, it fails and this causes a deep crash of the entire system. This may have resulted in corruption of a small section of the flash memory in either or both the SD memory cards and/or the FMU128 flash unit. With the first camera I turned the main power switch off while recording to test the cam, and with the second camera the battery went completely flat in the middle of a clip. Neither of my NXCAMs crashed until after I'd recorded clips that had been non-standardly interrupted. Prior to me experiencing the deep crashes on both my NXCAMs I did in fact have clips that were interrupted, in other words while recording the camera was shut down before I hit a REC button to end the clip 'normally'. My thought is, one or both of your units got corrupted and the camera, with limited error reporting, limited on-board diagnostics, and no error correction feature was giving you a ‘catch-all’ error message with little to no meaningful explanation of the real trouble.' I have been able to try another camera and correct the corrupted data flash unit with a good format. Some bit errors can still remain after a format and the unit may not work, or work until the bad spot is addressed again during usage, and in some cases may not reformat at all. One corrupted, the unit must be reformatted. In short, the crashes are not triggered by actual buffer overflows - it's an incorrect error message - but rather by corrupted/bad sectors in flash memory that the camera can't deal with.Ĭurtis writes 'Based on my personal experiences, data to flash memory units can become corrupt during a read/write cycle if power is interrupted. WARNING: line length of 98 exceeds 80 columnsĭiff -git a/drivers/net/ethernet/emulex/benet/be_cmds.c b/drivers/net/ethernet/emulex/benet/be_cmds.c index 528eb0f223b1.b4f5e57d0285 100644 - a/drivers/net/ethernet/emulex/benet/be_cmds.c +++ b/drivers/net/ethernet/emulex/benet/be_cmds.I've just been alerted to a post by Curtis Anderson dated 20 March 2010 in a thread I started which, to me, gives a good lead on what might be causing these buffer overflows and crashes. WARNING: line length of 86 exceeds 80 columns WARNING: line length of 81 exceeds 80 columns Signed-off-by tag matches author and committer No static functions without inline keyword in header filesĮrrors and warnings before: 107 this patch: 107Įrrors and warnings before: 0 this patch: 0 Target tree name not specified in the subject X-Mailing-List: Fix buffer overflow in be_get_module_eeprom Subject: be2net: Fix buffer overflow in be_get_module_eeprom RrZ8ynq3fd5/M7ZjxsBlzMddOuqQevbE59圓BZeUO3Ts+aU92MTZVVDvx+2f5omtURATe7KpRkf+6ĥHE+aQ/oxSe1r8g2lexZ9yoYdnLWRw2As+MNa1jSUQ5VSYy0tKd3yNkF64cvZtTl436cxno= SFZLdd2圎iD1Llxbki1ZDsd9baJsQtbd5uge圆VuJ0RO/qklIAWsAJaCZ/nDfHrIO7Sn/KACVrSYLĠDBOyeUPygbUtro4HiVhXNShm1AQbQ1vrhc6zfKCW0MEmCugruYn3uOTMR8Ijo1AYiC8UUV8Jy1hqĭklP8sV6vlEzkr3元+DdhW0MQqNO9DbMFT4edV5jeQ4INWsxFUHxFdnE2sbqpwdsv03iqyrSz144i +Nt8Rv6eCcAkgOeeM1VovHb7y7/AvbMbaxI17reKnujiMzzykVZKIc1eoxI3Gqa7uXmhpnZ0jvzdL N5n9FzAnjqT/EvMSBhcIKuCNMDbLokI6f9LzdGdFGtyRc0xGUh+VI0M4eB9XEi9hcH8qh4UZuFjl9įhhv8YgBJLssXAFOE2KWd9qeJP+UqTXYpFNaqIqD7NGHgT2ZyYPyJmZyKGxGuz3WPFmT6GBSkkTug H=Content-Transfer-Encoding:Message-Id:Date:Subject:To:From:īh=fPmDHOyG2Rqp5CIpnIIQbmLxoYS8Nalj3lW5lVyk8Ps=ī=iLqyE3/Ft7mvjmD9vgScixnQsyaDSgyE/ttsEIWIj3cX5stt6ncxfxQtutaqjWEWNbZwo5vyu Received: from ( )īy (Postfix) with ESMTPS id 57A5426D4 ĭKIM-Signature: v=1 a=rsa-sha256 q=dns/txt c=relaxed/relaxed d=venev.name

X-Greylist: delayed 4292 seconds by postgrey-1.37 at Received: from ( )īy (Postfix) with ESMTP id 441F4C433EF X-Spam-Checker-Version: SpamAssassin 3.4.0 () onĪ

Buffer overflow in net message