Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 271897 Details for
Bug 365291
dev-libs/libusb-1.0.8: lsusb: double free or corruption (!prev)
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
kernel error
dmesg (text/plain), 4.51 KB, created by
Andreis Vinogradovs ( slepnoga )
on 2011-05-02 18:26:24 UTC
(
hide
)
Description:
kernel error
Filename:
MIME Type:
Creator:
Andreis Vinogradovs ( slepnoga )
Created:
2011-05-02 18:26:24 UTC
Size:
4.51 KB
patch
obsolete
> >Apr 27 12:01:22 ashgabad kernel: sd 4:0:0:0: Device offlined - not ready after error recovery >Apr 27 12:01:22 ashgabad kernel: sd 4:0:0:0: [sdc] Unhandled error code >Apr 27 12:01:22 ashgabad kernel: sd 4:0:0:0: [sdc] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK >Apr 27 12:01:22 ashgabad kernel: sd 4:0:0:0: [sdc] CDB: Read(10) >Apr 27 12:01:22 ashgabad kernel: usb 7-1: USB disconnect, address 2 >Apr 27 12:01:22 ashgabad kernel: : 28 00 1a 38 01 30 00 00 08 00 >Apr 27 12:01:22 ashgabad kernel: end_request: I/O error, dev sdc, sector 439877936 >Apr 27 12:01:22 ashgabad kernel: sd 4:0:0:0: rejecting I/O to offline device >Apr 27 12:01:22 ashgabad kernel: sd 4:0:0:0: rejecting I/O to offline device >Apr 27 12:01:22 ashgabad kernel: sd 4:0:0:0: rejecting I/O to offline device >Apr 27 12:01:22 ashgabad kernel: ------------[ cut here ]------------ >Apr 27 12:01:22 ashgabad kernel: WARNING: at fs/buffer.c:1163 mark_buffer_dirty+0x72/0x8a() >Apr 27 12:01:22 ashgabad kernel: Hardware name: H55M-S2 >Apr 27 12:01:22 ashgabad kernel: Modules linked in: configs simfs ipt_MASQUERADE iptable_nat nf_nat iptable_mangle ipt_REJECT xt_state iptable_filter ipt_addrtype ip6table_filter ebtable_broute ebtable_nat xt_NFQUEUE xt_iprange xt_mark xt_owner xt_hashlimit xt_conntrack xt_DSCP xt_connmark xt_CONNMARK xt_MARK ebtable_filter xt_multiport xt_dscp ip6_tables xt_string it87 hwmon_vid hwmon vzdquota vzrst vzcpt ipv6 vznetdev usbhid usb_storage ehci_hcd uhci_hcd usbcore iTCO_wdt i2c_i801 i2c_core >Apr 27 12:01:22 ashgabad kernel: Pid: 21831, comm: flush-8:32 Not tainted 2.6.32-openvz-feoktistov.1-ovz-prod-kvm-ups #1 >Apr 27 12:01:22 ashgabad kernel: Call Trace: >Apr 27 12:01:22 ashgabad kernel: [<ffffffff8103df49>] ? warn_slowpath_common+0x65/0x91 >Apr 27 12:01:22 ashgabad kernel: [<ffffffff810e961e>] ? mark_buffer_dirty+0x72/0x8a >Apr 27 12:01:22 ashgabad kernel: [<ffffffff8116601e>] ? ext2_sync_super+0x37/0x52 >Apr 27 12:01:22 ashgabad kernel: [<ffffffff81166b90>] ? ext2_error+0xb2/0xda >Apr 27 12:01:23 ashgabad kernel: [<ffffffff81163073>] ? ext2_get_inode+0x139/0x13e >Apr 27 12:01:23 ashgabad kernel: [<ffffffff81164263>] ? ext2_write_inode+0x3c/0x31b >Apr 27 12:01:23 ashgabad kernel: [<ffffffff810e3790>] ? writeback_single_inode+0x246/0x2df >Apr 27 12:01:23 ashgabad kernel: [<ffffffff810e4082>] ? writeback_inodes_wb+0x247/0x46a >Apr 27 12:01:23 ashgabad kernel: [<ffffffff810e43a7>] ? wb_writeback+0x102/0x1b9 >Apr 27 12:01:23 ashgabad kernel: [<ffffffff81048a6b>] ? try_to_del_timer_sync+0x66/0x88 >Apr 27 12:01:23 ashgabad kernel: [<ffffffff810e4785>] ? wb_do_writeback+0x199/0x19e >Apr 27 12:01:23 ashgabad kernel: [<ffffffff810e47c5>] ? bdi_writeback_task+0x3b/0xc3 >Apr 27 12:01:23 ashgabad kernel: [<ffffffff810a5dac>] ? bdi_start_fn+0x63/0xc2 >Apr 27 12:01:23 ashgabad kernel: [<ffffffff810a5d49>] ? bdi_start_fn+0x0/0xc2 >Apr 27 12:01:23 ashgabad kernel: [<ffffffff8105328a>] ? kthread+0xb6/0xd0 >Apr 27 12:01:23 ashgabad kernel: [<ffffffff8100cc9a>] ? child_rip+0xa/0x20 >Apr 27 12:01:23 ashgabad kernel: [<ffffffff810531d4>] ? kthread+0x0/0xd0 >Apr 27 12:01:23 ashgabad kernel: [<ffffffff8100cc90>] ? child_rip+0x0/0x20 >Apr 27 12:01:23 ashgabad kernel: ---[ end trace 700b57b2cf4364c3 ]--- >Apr 27 12:01:23 ashgabad kernel: EXT2-fs error (device sdc1): ext2_get_inode: unable to read inode block - inode=12846670, block=51380326 lines 20-63 >Apr 27 12:01:23 ashgabad kernel: EXT2-fs error (device sdc1): ext2_get_inode: unable to read inode block - inode=12847698, block=51380391 >Apr 27 12:01:23 ashgabad kernel: EXT2-fs error (device sdc1): ext2_get_inode: unable to read inode block - inode=13746627, block=54984734 >Apr 27 12:01:23 ashgabad kernel: EXT2-fs error (device sdc1): ext2_get_inode: unable to read inode block - inode=12847699, block=51380391 >Apr 27 12:01:23 ashgabad kernel: EXT2-fs error (device sdc1): ext2_get_inode: unable to read inode block - inode=13746627, block=54984734 >Apr 27 12:01:23 ashgabad kernel: EXT2-fs error (device sdc1): ext2_get_inode: unable to read inode block - inode=12847697, block=51380391 >Apr 27 12:01:23 ashgabad kernel: EXT2-fs error (device sdc1): ext2_get_inode: >Apr 27 12:01:23 ashgabad kernel: EXT2-fs error (device sdc1): ext2_get_inode: unable to read inode block - inode=13746628, block=54984734 >Apr 27 12:01:23 ashgabad kernel: unable to read inode block - inode=12847700, block=51380391 >Apr 27 12:01:23 ashgabad kernel: EXT2-fs error (device sdc1): ext2_get_inode: unable to read inode block - inode=12847701, block=51380391 >Apr 27 12:01:23 ashgabad kernel: EXT2-fs error (device sdc1): ext2_get_inode: unable to read inode block - inode=13746628, block=54984734
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 365291
:
271545
|
271547
| 271897