search for: 1f

A recently created and fully functional CentOS 7.3 VM fails to boot after applying CR updates: ... ;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS...

...100% fault.fs.zfs.device Problem in: zfs://pool=storage/vdev=83de319aad25c131 Affects: zfs://pool=storage/vdev=83de319aad25c131 FRU: - Location: - From my message log: Jul 8 20:11:53 fortress scsi: [ID 107833 kern.warning] WARNING: / sbus at 1f,0/SUNW,fas at 2,8800000/sd at 6,0 (sd19): Jul 8 20:11:53 fortress SCSI transport failed: reason ''incomplete'': retrying command Jul 8 20:12:56 fortress scsi: [ID 365881 kern.info] fas: 6.0: cdb=[ 0xa 0x0 0x1 0xda 0x2 0x0 ] Jul 8 20:12:56 fortress scsi: [ID 36588...

hello, I''m running XEN 2.0 on IBM ThinkPad T23. Now the weird thing is that I get two different outputs from /sbin/lspci depending on whether I run 2.6.8.1-xen0 or 2.6.8.1-bproc. In particular the output from 2.6.8.1-xen0 seems to be missing those 4 lines 0000:00:01.0 PCI bridge: Intel Corp. 82830 830 Chipset AGP Bridge (rev 02) 0000:00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI

I''m using xen-unstable, and I''ve successfully made a passthrough of an intel storage controller to an HVM domU, binding with pciback. 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) I can access the array from within Windows by installing Intel Rapide Storage Drivers, and everything works as it should. I only have a small problem, I would like to boot the guest OS directly f...

...+++++++++++++++------- 1 file changed, 15 insertions(+), 7 deletions(-) diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S index 49167258d587..15bd5530d2ae 100644 --- a/arch/x86/entry/entry_64.S +++ b/arch/x86/entry/entry_64.S @@ -194,12 +194,15 @@ entry_SYSCALL_64_fastpath: ja 1f /* return -ENOSYS (already in pt_regs->ax) */ movq %r10, %rcx + /* Ensures the call is position independent */ + leaq sys_call_table(%rip), %r11 + /* * This call instruction is handled specially in stub_ptregs_64. * It might end up jumping to the slow path. If it jumps, RAX *...

...# nvidia-detect Error getting device_class nvidia-detect also quits with exit-code 255. Could this be a bug in nvidia-detect? Or is it an unsupported configuration? The following hardware is detected, it seems some sort of unknown Intel device is detected by the OS: # lspci | grep VGA 00:1f.5 Non-VGA unclassified device: Intel Corporation Device a2a4 21:00.0 VGA compatible controller: NVIDIA Corporation Device 1cb2 (rev a1) # lspci -n | egrep '00:1f.5|21:00.0' 00:1f.5 0000: 8086:a2a4 21:00.0 0300: 10de:1cb2 (rev a1) Tested with the following version (with equal resul...

..."/pci at 0,0/pci8086,25ae at 1c/pci11ab,11ab at 3/disk at 3,0" 5 "sd" "/pci at 0,0/pci8086,25ae at 1c/pci11ab,11ab at 3/disk at 4,0" 6 "sd" "/pci at 0,0/pci8086,25ae at 1c/pci11ab,11ab at 3/disk at 1,0" 9 "sd" "/pci at 0,0/pci-ide at 1f,1" 0 "pci-ide" "/pci at 0,0/pci-ide at 1f,1/ide at 0" 0 "ata" "/pci at 0,0/pci-ide at 1f,1/ide at 0/sd at 0,0" 1 "sd" "/pci at 0,0/pci-ide at 1f,1/ide at 1" 1 "ata" "/pci at 0,0/pci-ide at 1f,2" 1 "pci-ide&quo...

...> Quite surely bit 0 of that CX is not set. But bit 2 "Enhanced Disk Drive" > could be set. > https://en.wikipedia.org/wiki/INT_13H > > I understand on David's BIOS after > > andw $1,%cx /* Bit 0 = fixed disk subset */ > jz 1f > > jz jumps because CX is 0. This gets pushed to the stack. > (So the code around the int 13 assumes that either int 13 fails and returns > CX == 0, or the reply is good enough to reach "andw 1,%cx". Ewww ...) Well... I'm not quite following you. If it reaches andw 1,%...

...gpu/drm/nouveau/dispnv50/core507d.c | 25 ++++++++++++++++----- > > > 1 file changed, 19 insertions(+), 6 deletions(-) > > > > > > diff --git a/drivers/gpu/drm/nouveau/dispnv50/core507d.c > > > b/drivers/gpu/drm/nouveau/dispnv50/core507d.c > > > index e341f572c2696..5e86feec3b720 100644 > > > --- a/drivers/gpu/drm/nouveau/dispnv50/core507d.c > > > +++ b/drivers/gpu/drm/nouveau/dispnv50/core507d.c > > > @@ -65,13 +65,26 @@ core507d_ntfy_init(struct nouveau_bo *bo, u32 offset) > > > int > > > core507d_caps_...

Hi All, I have a windows 7 as my domU and some windows based drivers are not fully functional (like: touchpad-driver etc ) because they are SMBus based. I was looking at a way to passthrough the SMBus at 00:1f.03 on south bridge ( 00:1f.0), I was debugging at pt-graphics.c and understand that it is detecting the south bridge and passing it through but the other functions for the same dev-id are not getting passed through. Seeking help if someone can help me to get the function ''3'' also...

.../lib/samba/sysvol/LOPRODUCTS.LOCAL/scripts # browseable = no # read only=No [sysvol] path = /var/lib/samba/sysvol browseable = no read only = no [3D-Content] path=/opt/data/shared/3d-content valid users = @LOPRODUCTS\wob-admins @LOPRODUCTS\domänen-admins invalid users = @"LOPRODUCTS\authlite 1f tag" browseable = no read only = no writeable = yes create mode = 0660 force create mode = 0660 force user = administrator directory mode = 0770 force directory mode = 0770 force group = wob-admins [CI] path = /opt/data/shared/ci valid users = @LOPRODUCTS\wob-admins @LOPRODUCTS\domänen-admins...

Hi, I've installed * 1.2.1 with latest bristuff patches (0.3.0-PRE-1f). When I activate music-on-hold on a SIP-to-SIP connection, the music sounds like in a fast-forward play mode. On the *-console I can see much lines like this: -- Silence suppression is disabled (option_silence_suppression=0 chan->timingfd=18) What's going on? With bristuff 0.3.0-PRE-1d e...

...f that CX is not set. But bit 2 "Enhanced Disk Drive" >> could be set. >> https://en.wikipedia.org/wiki/INT_13H >> >> I understand on David's BIOS after >> >> andw $1,%cx /* Bit 0 = fixed disk subset */ >> jz 1f >> >> jz jumps because CX is 0. This gets pushed to the stack. >> (So the code around the int 13 assumes that either int 13 fails and returns >> CX == 0, or the reply is good enough to reach "andw 1,%cx". Ewww ...) > > Well... I'm not quite following you...

Hello, my server has massive problems with my NIC. I got: "Detected Tx Unit Hang". At the moment I use 2.6.31 from Jeremy, does anyone know if it''s fixed in 2.6.32 or newer tree? Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...ost install. Note that I''ve tried this a few times, so you''ll see tank faulted in the post install from previous install attempts. >> Live CD Install AVAILABLE DISK SELECTIONS: 0. c7d0 <WDC WD10- WD-WMAV5012875-0001-931.51GB> /pci at 0,0/pci-ide at 1f,2/ide at 0/cmdk at 0,0 1. c7d1 <WDC WD10- WD-WMAV5011699-0001-931.51GB> /pci at 0,0/pci-ide at 1f,2/ide at 0/cmdk at 1,0 2. c8d0 <WDC WD10- WD-WMAV5011404-0001-931.51GB> /pci at 0,0/pci-ide at 1f,2/ide at 1/cmdk at 0,0 3. c8d1 <DEFAULT cyl 60797...

...-) >> >> diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S >> index 49167258d587..15bd5530d2ae 100644 >> --- a/arch/x86/entry/entry_64.S >> +++ b/arch/x86/entry/entry_64.S >> @@ -194,12 +194,15 @@ entry_SYSCALL_64_fastpath: >> ja 1f /* return -ENOSYS (already in pt_regs->ax) */ >> movq %r10, %rcx >> >> + /* Ensures the call is position independent */ >> + leaq sys_call_table(%rip), %r11 >> + >> /* >> * This call instructi...

...-) >> >> diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S >> index 49167258d587..15bd5530d2ae 100644 >> --- a/arch/x86/entry/entry_64.S >> +++ b/arch/x86/entry/entry_64.S >> @@ -194,12 +194,15 @@ entry_SYSCALL_64_fastpath: >> ja 1f /* return -ENOSYS (already in pt_regs->ax) */ >> movq %r10, %rcx >> >> + /* Ensures the call is position independent */ >> + leaq sys_call_table(%rip), %r11 >> + >> /* >> * This call instructi...

...mation in syslog or the output from dmesg /lib/modules/2.4.20-8/misc/wcfxo.o: insmod /lib/modules/2.4.20-8/misc/wcfxo.o failed /lib/modules/2.4.20-8/misc/wcfxo.o: insmod wcfxo failed [prompt]# dmesg <SNIPPET> Zapata Telephony Interface Registered on major 196 PCI: Found IRQ 9 for device 00:1f.6 PCI: Sharing IRQ 9 with 00:1f.3 PCI: Sharing IRQ 9 with 00:1f.5 x=0000 reg=05 value=00 x=0001 reg=05 value=08 PCI: Setting latency timer of device 00:1f.6 to 64 x=0002 reg=01 value=80 x=0003 reg=07 value=00 x=0004 reg=08 value=01 x=0005 reg=09 value=89 x=0006 reg=0a value=00 x=0007 reg=05 value=0...

...MSI, was released in late 1998. The 430FX chipset only supports PCI 2.0. > >> >> So given that the PCI device itself supports MSI, how do we tell that >> it shouldn't actually get turned on? > > Generally, some message in dmesg like: > [ 17.322311] ahci 0000:00:1f.2: irq 119 for MSI/MSI-X > [ 17.322319] ahci 0000:00:1f.2: irq 120 for MSI/MSI-X > [ 17.322326] ahci 0000:00:1f.2: irq 121 for MSI/MSI-X > [ 17.322333] ahci 0000:00:1f.2: irq 122 for MSI/MSI-X > [ 17.322339] ahci 0000:00:1f.2: irq 123 for MSI/MSI-X > > Also you can check /...

...x CyrixInstead Centaur CentaurHauls Transmeta GenuineTMx86 Transmeta TransmetaCPU UMC UMC UMC UMC BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000001ff77000 (usable) BIOS-e820: 000000001ff77000 - 000000001ff79000 (ACPI NVS) BIOS-e820: 000000001ff79000 - 0000000020000000 (reserved) BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved) BIOS-e820: 00000000ffb00000 - 000000010000...