search for: 0xa1

...lt;c06217ff>] ? warn_invalid_dmar+0x7f/0xa0 :[<c0abdeb8>] ? check_zero_address+0xfb/0x132 :[<c06608b7>] ? acpi_tb_verify_table+0x1d/0x46 :[<c0abdefd>] ? detect_intel_iommu+0xe/0x57 :[<c0aae15b>] ? mem_init+0x10/0x2ab :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87...

I believe I have now fixed the 0x64 0xa1 0x00 0x00 0x00 0x00 bug in r199364. On Wed, Jan 15, 2014 at 10:53 AM, Craig Topper <craig.topper at gmail.com>wrote: > To fix it we need to change offset8/offset16/etc to have two suboperands > and update the printer to understand that. Also update the disassembler to > add the se...

...137 [ 2.183682] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 2.183825] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 7.183893] ata3.00: qc timeout (cmd 0xec) [ 7.183908] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 7.183960] ata4.00: qc timeout (cmd 0xa1) [ 7.183974] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 7.488894] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 7.488931] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 17.488919] ata3.00: qc timeout (cmd 0xec) [ 17.488934] ata3.00: failed to IDENTIFY...

...s follows: > > 0.157417 Report Descriptor: (656 bytes) => 05 84 09 04 a1 01 09 > 0.157431 24 a1 00 85 01 09 fe 75 08 95 01 15 00 Here is the output from that command. Thank you for your help. usbconfig -u 4 -a 2 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = <0x05 0x84 0x09 0x04 0xa1 0x01 0x09 0x24 0xa1 0x00 0x85 0x01 0x09 0xfe 0x75 0x08 0x95 0x01 0x15 0x00 0x26 0xff 0x00 0xb1 0x22 0x85 0x02 0x09 0xff 0xb1 0x22 0x85 0x03 0x05 0x85 0x09 0x8f 0xb1 0x22 0x85 0x04 0x09 0x89 0xb1 0x22 0x85 0x05 0x09 0x8b 0xb1 0x22 0x85 0x06 0x09 0x2c 0xb1 0x22 0x85 0x07 0x75 0x08 0x95 0x05 0x25 0x64...

Hello, I was wondering if we can get some help in resolving this bug. It was reported earlier and logged in bugme.osdl.org http://bugme.osdl.org/show_bug.cgi?id=4683 The problem is kernel oops at log_do_checkpoint() due to NULL buffer_head. This could be because of some race in journalling code for which I don't have much clue. There is kdump available for analysis as mentioned in the

Hi Konrad, Sometime ago i reported this one at boot up: [ 3009.778974] mcelog:16842 map pfn expected mapping type write-back for [mem 0x0009f000-0x000a0fff], got uncached-minus [ 3009.788570] ------------[ cut here ]------------ [ 3009.798175] WARNING: at arch/x86/mm/pat.c:774 untrack_pfn+0xa1/0xb0() [ 3009.807966] Hardware name: MS-7640 [ 3009.817677] Modules linked in: [ 3009.827524] Pid: 16842, comm: mcelog Tainted: G W 3.7.0-rc5-20121116-reverted-persistent-warn-patwarn #1 [ 3009.837415] Call Trace: [ 3009.847110] [<ffffffff810674fa>] warn_slowpath_common+0x7a/0xb0 [...

Hi, With objdump, i have this (Intel syntax) 64 a1 00 00 00 00 mov eax,fs:0x0 However, if I pass above string to llvm-mc, I would have: $ echo "0x64 0xa1 0x00 0x00 0x00 0x00"|./Release+Asserts/bin/llvm-mc -disassemble -arch=x86 --output-asm-variant=1 .text mov eax, dword ptr [0] You can see a big difference. This is on the latest code. Any idea how to fix this bug? Thank you, Jun -------------- next part -------------- An HTML att...

...t; which leads me to believe Asterisk thinks it should not be displaying it. Can anyone interpret this for me and maybe shed some light on why I am not getting the caller ID name displayed? I have asreceived in my Zapata.conf file. < Facility (len=23, codeset=0) [ 0x9f, 0x8b, 0x01, 0x00, 0xa1, 0x0f, 0x02, 0x01, 0x01, 0x06, 0x07, 0x2a, 0x86, 'H', 0xce, 0x15, 0x00, 0x04, 0x0a, 0x01, 0x00 ] < [6c 0c 21 83 35 30 32 38 38 39 35 35 36 37] < Calling Number (len=14) [ Ext: 0 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) <...

Hi Jun, I'm not sure how to fix this yet, but this looks incorrectly defined in lib/Target/X86/X86InstrInfo.td: def MOV32o32a : Ii32 <0xA1, RawFrm, (outs), (ins offset32:$src), "mov{l}\t{$src, %eax|eax, $src}", [], IIC_MOV_MEM>, Requires<[In32BitMode]>; This instruction can be REX-prefixed for a 64-bit move, and that also doesn't appear to be defined anywhere. I would...

On Thu, Nov 28, 2013 at 1:03 AM, Kay Tiong Khoo <kkhoo at perfwizard.com>wrote: > Hi Jun, > > I'm not sure how to fix this yet, but this looks incorrectly defined in > lib/Target/X86/X86InstrInfo.td: > > def MOV32o32a : Ii32 <0xA1, RawFrm, (outs), (ins offset32:$src), > "mov{l}\t{$src, %eax|eax, $src}", [], IIC_MOV_MEM>, > Requires<[In32BitMode]>; > > This instruction can be REX-prefixed for a 64-bit move, and that also > doesn't appear to be de...

...03? <INTERRUPT> ??????? wMaxPacketSize = 0x0008 ??????? bInterval = 0x000c ??????? bRefresh = 0x0000 ??????? bSynchAddress = 0x0000 usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100 ?datanas: ~# usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = <0x05 0x84 0x09 0x04 0xa1 0x01 0x09 0x24 0xa1 0x00 0x85 0x28 0x09 0xfe 0x79 0x01 0x75 0x08 0x95 0x01 0x15 0x00 0x26 0xff 0x00 0xb1 0x03 0x85 0x29 0x09 0xff 0x79 0x05 0xb1 0x03 0x85 0x2b 0x09 0xfd 0x79 0x03 0xb1 0x03 0x09 0x1a 0xa1 0x02 0x85 0x30 0x09 0x40 0x67 0x21 0xd1 0xf0 0x00 0x55 0x07 0xb1 0x83 0x85 0x31 0x09 0x30 0x75...

...7417 Report Descriptor: (656 bytes) => 05 84 09 04 a1 01 09 >> 0.157431 24 a1 00 85 01 09 fe 75 08 95 01 15 00 > > Here is the output from that command. Thank you for your help. > > usbconfig -u 4 -a 2 do_request 0x81 0x06 0x2200 0 0x100 > REQUEST = <0x05 0x84 0x09 0x04 0xa1 0x01 0x09 0x24 0xa1 0x00 0x85 0x01 0x09 0xfe > 0x75 0x08 0x95 0x01 0x15 0x00 0x26 0xff 0x00 0xb1 0x22 0x85 0x02 0x09 0xff 0xb1 > 0x22 0x85 0x03 0x05 0x85 0x09 0x8f 0xb1 0x22 0x85 0x04 0x09 0x89 0xb1 0x22 0x85 > 0x05 0x09 0x8b 0xb1 0x22 0x85 0x06 0x09 0x2c 0xb1 0x22 0x85 0x07 0x75 0x08 0x95...

...ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > [ 2.183825] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > [ 7.183893] ata3.00: qc timeout (cmd 0xec) > [ 7.183908] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) > [ 7.183960] ata4.00: qc timeout (cmd 0xa1) > [ 7.183974] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4) > [ 7.488894] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > [ 7.488931] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > [ 17.488919] ata3.00: qc timeout (cmd 0xec) > [ 17.488934] ata...

...=87 < Call Ref: len= 2 (reference 86/0x56) (Terminator) < Message type: CONNECT (7) < [1c 1d 9f aa 06 80 01 00 82 01 00 8b 01 00 a1 0f 02 02 4b 36 02 01 55 30 06 82 04 06 1c 08 40] < Facility (len=31, codeset=0) [ 0x9f, 0xaa, 0x06, 0x80, 0x01, 0x00, 0x82, 0x01, 0x00, 0x8b, 0x01, 0x00, 0xa1, 0x0f, 0x02, 0x02, 'K6', 0x02, 0x01, 'U0', 0x06, 0x82, 0x04, 0x06, 0x1c, 0x08, 0x40 ] < [1c 29 9f aa 06 80 01 00 82 01 00 8b 01 00 a1 1b 02 02 4b 45 02 01 02 a1 12 04 0d 4e 4f 52 44 4d 41 4e 4e 2c 45 52 49 43 02 01 01] < Facility (len=43, codeset=0) [ 0x9f, 0xaa, 0x06, 0x80,...

...at smp_tlb_shootdown+0x82 pmap_invalidate_range() at pmap_invalidate_range+0xae vfs_vmio_release() at vfs_vmio_release+0x120 getnewbuf() at getnewbuf+0x7be getblk() at getblk+0x308 cluster_read() at cluster_read+0xc5 ffs_read() at ffs_read+0x37d vn_read() at vn_read+0x17b dofileread() at dofileread+0xa1 kern_preadv() at kern_preadv+0x66 pread() at pread+0x58 syscall() at syscall+0x1ce Xfast_syscall() at Xfast_syscall+0xab --- syscall (475, FreeBSD ELF64, pread), rip = 0x800cf7b5c, rsp = 0x7ffffeff8e78, rbp = 0x7ffffeff8f60 --- db> bt 100132 Tracing pid 810 tid 100132 td 0xffffff00036426e0 cpust...

...94, 0x95, 0x97 }, { 0x94, 0x95, 0x96, 0x98 }, { 0x95, 0x96, 0x97, 0x99 }, { 0x96, 0x97, 0x98, 0x9a }, { 0x97, 0x98, 0x99, 0x9b }, { 0x98, 0x99, 0x9a, 0x9c }, { 0x99, 0x9a, 0x9b, 0x9d }, { 0x9a, 0x9b, 0x9c, 0x9e }, { 0x9b, 0x9c, 0x9d, 0x9f }, { 0x9c, 0x9d, 0x9e, 0xa0 }, { 0x9d, 0x9e, 0x9f, 0xa1 }, { 0x9e, 0x9f, 0xa0, 0xa2 }, { 0x9f, 0xa0, 0xa1, 0xa3 }, { 0xa0, 0xa1, 0xa2, 0xa4 }, { 0xa1, 0xa2, 0xa3, 0xa5 }, { 0xa2, 0xa3, 0xa4, 0xa6 }, { 0xa3, 0xa4, 0xa5, 0xa7 }, { 0xa4, 0xa5, 0xa6, 0xa8 }, { 0xa5, 0xa6, 0xa7, 0xa9 }, { 0xa6, 0xa7, 0xa8, 0xaa }, { 0xa7, 0xa8, 0xa9, 0xab }, { 0xa...

>> >> The output was also not as big as you made it out to be. > > Well, I didn't expect the driver to fail *that* badly :-) > > Assuming the UPS is still at /dev/ugen4.2, can you try the following command? (Probably needs to be run as root, with the driver stopped.) > > usbconfig -u 4 -a 2 dump_curr_config_desc Here is output of the command. Thank you for

Hi Everyone, I'm having trouble getting TrippLite SMX1500LCDT to work on FreeBSD 11.2, nut 2.7.4 installed from FreeBSD port. The debug output is rather big when I'm starting usbhid-ups initially, Please find that attached (gzipped to comply with message size limit). Subsequently, until I unplug and replug the USB cable, I'm geting a shorter debug output, like this: Network UPS

...c_kernel+0x61/0xc0 [ 0.010000] [<ffffffff802cbdf4>] map_vm_area+0x2d4/0x350 [ 0.010000] [<ffffffff802cc5f0>] __vmalloc_area_node+0x140/0x1a0 [ 0.010000] [<ffffffff80740856>] ? alloc_large_system_hash+0x24c/0x2b0 [ 0.010000] [<ffffffff802cc6f1>] __vmalloc_node+0xa1/0xb0 [ 0.010000] [<ffffffff80740856>] ? alloc_large_system_hash+0x24c/0x2b0 [ 0.010000] [<ffffffff80740856>] ? alloc_large_system_hash+0x24c/0x2b0 [ 0.010000] [<ffffffff802cc511>] __vmalloc_area_node+0x61/0x1a0 [ 0.010000] [<ffffffff802cb8db>] ? __get_vm_area...

...ating it lately.. It has happened using CentOS 5.0, 5.1 and now also with 5.2. I'm not sure if it was the same bug earlier, but at least the last two times (with CentOS 5.2) it has been the same, see screenshots. Last lines of the console output: EIP: [<f8af2c5c>] __ip_ct_refresh_acct+0xa1/0x129 [ip_conntrack] SS:ESP 0068:c0724e4c <0>Kernel panic - not syncing: Fatal exception in interrupt At the moment firewall is running CentOS 5.2, Linux kernel 2.6.18-92.1.10.el5.centos.plus. Any tips how to resolve this? -- Pasi