Processor status in SPAU

Hi,
The objects during SPAU resolution have a red cross (processor status).Please can anyone explain what this is exactly.
Also in our pre-prod and prod systems during SP upgrade in transaction SPAU we only have some objects with this red cross and there are no objects which needs adjustment.
So please can anyone let me know if still SPAU needs to be carried out in the system.
Please reply ASAP.We are having a dilemma if we need to send these systems to the Developers for SPAU resolution.
Awaiting your reply,
Harish.

HI
For getting Red cross for some objects in SPAU means there are some errors are there in Red cross objects. You need to clear that errors with the help of ABAPer only.
Reward if it helps
Chandra

Similar Messages

Alert: Host Processor Status

Hi, Im new in this community. I've this recient error in my server Dell Poweredge R720 :
Object: VCenter - Status: Warning - Name: Health status monitoring
Object: My Host - Status: Alert- Name: Host Processor Status
I need asist for fix this issue. thanks!

HI
For getting Red cross for some objects in SPAU means there are some errors are there in Red cross objects. You need to clear that errors with the help of ABAPer only.
Reward if it helps
Chandra

Can't Insert VI while Processor Status Window is Open

I've found that you can't drop a VI onto your Block Diagram by chosing "Select a VI..." from your Functions Pallet while the Processor Status window is open. Simply close the Processor Status window, or drag the VI icon onto your block diagram works while the Processor Status window is open. Just a small bug, no biggie.

Eric,
Thanks for reporting this issue. I have reported the issue to R&D.
Michael P
National Instruments

How to reset OSS Notes with Question mark status in SPAU

Hi,
We are doing SPAU adjustments. In that under Note we have many OSS notes with status "Question Mark". We ran SAPRUPGM again. But still we have this question mark.
We realized some of the notes are not applicable and want to reset. But when I select the note and reset, it gives a pop up to confirm the reset. I select "reset" there. But instead of reseting it gives me a popup asking to download the OSS note. If I cancel it it goes back to the initial SPAU screen. Nothing done. If I okay it it tries downloading the note.
How to solve this situation?
Can you also tell me if it is okay to leave the notes without resetting.
Regards,
Ravikanth
Edited by: Ravikanth Tunuguntla on Aug 12, 2008 5:37 PM

Appreciate the reply. I of course did try to re-execute SAPRUPGM. In background, it runs for 2 seconds and produces no log or spool. When I run on-line, and un-tick the box for output log file, the resulting list shows these messages for the gree question mark notes.   These notes are no longer visible in SNOTE. Basically I'm stuck - with the green question mark, I don't know how to get rid of these Notes in SPAU.
Corrections in SAP Note
NOTE 0000683004 0003                                                        Inconsistent data
NOTE 0000693190 0002                                                        Inconsistent data
NOTE 0000731027 0001                                                        Inconsistent data
NOTE 0000764040 0003                                                        Inconsistent data
NOTE 0000768618 0001                                                        Inconsistent data
NOTE 0000770227 0001                                                        Inconsistent data
NOTE 0000772460 0001                                                        Data for SAP Note 0000772460 incomplete
NOTE 0000775691 0002                                                        Inconsistent data
NOTE 0000777671 0003                                                        Inconsistent data
NOTE 0000782311 0002                                                        Inconsistent data
NOTE 0000784108 0001                                                        Inconsistent data
NOTE 0000785324 0002                                                        Inconsistent data
NOTE 0000802475 0004                                                        Inconsistent data
NOTE 0000826538 0002                                                        Inconsistent data
NOTE 0000843717 0002                                                        Inconsistent data
NOTE 0000864505 0002                                                        Inconsistent data

P_CATERR_N Processor Error

Hello,
We had a Server Shutdown on UCS C220.
In the IMC Console we see this
[F0174][critical][equipment-inoperable][sys/rack-unit-1/board] P_CATERR_N: A catastrophic fault has occurred on one of the processors: Please check the processors' status.
P_CATERR_N: Processor sensor, Predictive Failure asserted
I searched web for
P_CATERR_N, but could not find anything.
What is wrong ? Any idea ? Thanks a lot
Armin

Hi,
Well, this is not good sign. I have seen this ERROR leads to resolution as either firmware upgrade or RMA. Please open a TAC case for it.
- Ashok
Please rate the post or mark as correct answer as it will help others looking for similar information

No Version Found

we ran SPAU and it came up with few problems,
under the "Without Modification Assistant" tab i have got few objects which have red light on it and when I click on it and try to click on the "versions" tab, it says no version found and when I click on the red light it gives me this window
Background
   The object has been modified without using the Modification Assistant.
   Therefore no support is available from the system for transferring your
   modifications.
Procedure
       Before you adjust your modifications, you can select multiple
   objects or a subtree.
       If you have selected multiple objects, you can skip the processing
   of this object.
   You can use the "Processor/Status" function to add other processors.
   If you have modified an object where multiple versions are possible,
   then the last version that contains changes has been stored in "version
I want to know what exactly the problem is with my objects and how to get that fix.
Thanks,
Rajeev Gupta

Using 2 accounts and cross-posting is counter productive for the forums.
Please stop it and follow up on your old thread first.
Please do that, the other account will be deleted.
If you do not follow up on your threads in the next days, then all your accounts will be merged, and everyone will see who you are...
Please respect the forum rules!
Cheers,
Julius

Hyper-v Live Migration not completing when using VM with large RAM

hi,
i have a two node server 2012 R2 cluster hyper-v which uses 100GB CSV, and 128GB RAM across 2 physical CPU's (approx 7.1GB used when the VM is not booted), and 1 VM running windows 7 which has 64GB RAM assigned, the VHD size is around 21GB and the BIN file
is 64GB (by the way do we have to have that, can we get rid of the BIN file?).
NUMA is enabled on both servers, when I attempt to live migrate i get event 1155 in the cluster events, the LM starts and gets into 60 something % but then fails. the event details are "The pending move for the role 'New Virtual Machine' did not complete."
however, when i lower the amount of RAM assigned to the VM to around 56GB (56+7 = 63GB) the LM seems to work, any amount of RAM below this allows LM to succeed, but it seems if the total used RAM from the physical server (including that used for the
VMs) is 64GB or above, the LM fails.... coincidence since the server has 64GB per CPU.....
why would this be?
many thanks
Steve

Hi,
I turned NUMA spanning off on both servers in the cluster - I assigned 62 GB, 64GB and 88GB and each time the VM started up no problems. with 62GB LM completed, but I cant get LM to complete with 64GB+.
my server is a HP DL380 G8, it has the latest BIOS (I just updated it today as it was a couple of months behind), i cant see any settings in BIOS relating to NUMA so i'm guessing it is enabled and cant be changed.
if i run the cmdlt as admin I get ProcessorsAvailability : {0, 0, 0, 0...}
if i run it as standard user i get ProcessorsAvailability
my memory and CPU config are as follows, hyper-threading is enabled for the CPU but I dont
think that would make a difference?
Processor 1 1 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 1 4 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 1 9 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 1 12 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 2 1 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 2 4 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 2 9 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 2 12 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor Name
Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz
Processor Status
OK
Processor Speed
2400 MHz
Execution Technology
12/12 cores; 24 threads
Memory Technology
64-bit Capable
Internal L1 cache
384 KB
Internal L2 cache
3072 KB
Internal L3 cache
30720 KB
Processor 2
Processor Name
Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz
Processor Status
OK
Processor Speed
2400 MHz
Execution Technology
12/12 cores; 24 threads
Memory Technology
64-bit Capable
Internal L1 cache
384 KB
Internal L2 cache
3072 KB
Internal L3 cache
30720 KB
thanks
Steve

[semi-solved] dell xps 12 touchscreen not working (2013, 12-9Q33)

does anyone know how to get the touch screen working the dell xps 12?
ran windows on it for a few days and there did not appear to be any hardware issues with touchscreen (or anything else).
deleted all windows partitions and installed arch + kde with no issues, boots and runs great. but no response from the touch screen.
have tried to cat every /dev/input/event* but get nothing when tapping touch screen.
beleve it uses an atmel maxtouch digitizer... which i think should be picked up by udev... but dont think udev even sees the device, it just detetcs boring old mouse.
this looks like a simmilar issue with ubuntu https://bugs.launchpad.net/ubuntu/+sour … ug/1218973 but on my system there is no indication that it is an i2c device.
tried atmel kernel but still no action https://git.kernel.org/cgit/linux/kerne … mel-mxt-ts
lsusb
Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:09fa Intel Corp.
Bus 001 Device 003: ID 0bda:5716 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 8087:07dc Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
input
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ Integrated Webcam id=9 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
↳ Dell WMI hotkeys id=12 [slave keyboard (3)]
sudo cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input0
U: Uniq=
H: Handlers=sysrq kbd event0
B: PROP=0
B: EV=120013
B: KEY=1100f02902000 8380307cf910f001 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2
U: Uniq=
H: Handlers=event2
B: PROP=0
B: EV=21
B: SW=1
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
U: Uniq=
H: Handlers=kbd event3
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0001 Vendor=10ec Product=0668 Version=0001
N: Name="HDA Digital PCBeep"
P: Phys=card1/codec#0/beep0
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/input/input4
U: Uniq=
H: Handlers=kbd event4
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card1/input5
U: Uniq=
H: Handlers=event5
B: PROP=0
B: EV=21
B: SW=4
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input6
U: Uniq=
H: Handlers=kbd event6
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Dell WMI hotkeys"
P: Phys=wmi/input0
S: Sysfs=/devices/virtual/input/input7
U: Uniq=
H: Handlers=kbd rfkill event7
B: PROP=0
B: EV=13
B: KEY=1500b00000000 200300000 0 0
B: MSC=10
I: Bus=0003 Vendor=0bda Product=5716 Version=3204
N: Name="Integrated Webcam"
P: Phys=usb-0000:00:14.0-5/button
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input8
U: Uniq=
H: Handlers=kbd event8
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input9
U: Uniq=
H: Handlers=mouse0 event9
B: PROP=5
B: EV=b
B: KEY=e520 610000 0 0 0 0
B: ABS=660800011000003
I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input10
U: Uniq=
H: Handlers=kbd event10
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel MID HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input11
U: Uniq=
H: Handlers=event11
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel MID HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input12
U: Uniq=
H: Handlers=event12
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel MID HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input13
U: Uniq=
H: Handlers=event13
B: PROP=0
B: EV=21
B: SW=140
sudo dmidecode
[sudo] password for gamera:
# dmidecode 2.12
# SMBIOS entry point at 0x000f04c0
SMBIOS 2.7 present.
56 structures occupying 2720 bytes.
Table at 0x000EBA70.
Handle 0xDA00, DMI type 218, 251 bytes
OEM-specific Type
Header and Data:
DA FB 00 DA B2 00 0D 5F 0F 37 40 7D 00 00 00 00
00 7E 00 01 00 00 00 75 01 01 80 01 00 76 01 02
80 01 00 4F 02 05 80 01 00 50 02 06 80 00 00 A5
02 02 00 00 00 A6 02 02 00 01 00 9C 00 03 00 01
00 9B 00 03 00 00 00 8A 01 04 00 01 00 89 01 04
00 00 00 7F 01 05 00 00 00 80 01 05 00 01 00 53
01 06 00 00 00 52 01 06 00 01 00 7B 01 07 00 00
00 7C 01 07 00 01 00 94 01 08 00 00 00 93 01 08
00 01 00 7D 00 09 00 00 00 2D 00 0A 00 01 00 2E
00 0A 00 00 00 6E 00 0B 00 00 00 95 00 0C 00 01
00 96 00 0C 00 00 00 2F 02 0D 00 01 00 30 02 0D
00 00 00 50 02 0E 00 00 00 51 02 0E 00 01 00 52
02 0E 00 02 00 53 02 0E 00 03 00 54 02 0E 00 04
00 56 02 0E 00 05 00 F0 00 5D 80 01 00 ED 00 5E
80 01 00 4B 01 5F 80 01 00 4A 01 60 80 01 00 EA
00 0F 00 01 00 FF FF 00 00 00 00
Handle 0xDA01, DMI type 218, 251 bytes
OEM-specific Type
Header and Data:
DA FB 01 DA B2 00 0D 5F 0F 37 40 EB 00 0F 00 00
00 37 01 61 80 01 00 38 01 62 80 01 00 39 01 63
80 01 00 3D 03 66 80 01 00 3E 03 67 80 01 00 2E
02 07 80 01 00 2D 02 08 80 01 00 4F 03 09 80 01
00 50 03 0A 80 01 00 0E 01 64 80 01 00 0F 01 65
80 01 00 47 01 68 80 01 00 46 01 69 80 01 00 36
02 17 80 01 00 35 02 18 80 01 00 36 03 19 80 01
00 37 03 1A 80 01 00 3A 03 1B 80 01 00 3B 03 1C
80 01 00 41 03 1D 80 01 00 42 03 1E 80 01 00 43
03 1F 80 01 00 44 03 20 80 01 00 45 03 21 80 01
00 46 03 22 80 01 00 47 03 23 80 01 00 4B 03 24
80 01 00 4C 03 25 80 01 00 4A 02 0B 80 01 00 26
03 0C 80 01 00 5B 03 0D 80 01 00 5C 03 0E 80 01
00 5D 03 0F 80 01 00 5E 03 10 80 01 00 5F 03 11
80 01 00 60 03 12 80 01 00 0C 80 13 80 01 00 04
A0 14 80 01 00 FF FF 00 00 00 00
Handle 0xDA02, DMI type 218, 29 bytes
OEM-specific Type
Header and Data:
DA 1D 02 DA B2 00 0D 5F 0F 37 40 44 01 15 80 01
00 45 01 16 80 01 00 FF FF 00 00 00 00
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: A02
Release Date: 07/26/2013
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 2048 kB
Characteristics:
MCA is supported
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 0.2
Firmware Revision: 0.2
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Dell Inc.
Product Name: XPS 12-9Q33
Version: A02
Serial Number: FZS4SY1
UUID: 4C4C4544-005A-5310-8034-C6C04F535931
Wake-up Type: Power Switch
SKU Number: XPS 12-9Q33
Family:
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: Dell Inc.
Product Name: XPS 12-9Q33
Version: A02
Serial Number: .FZS4SY1.CN1296139P0049.
Asset Tag: Not Specified
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: To Be Filled By O.E.M.
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
Manufacturer: Dell Inc.
Type: Portable
Lock: Not Present
Version: Not Specified
Serial Number: FZS4SY1
Asset Tag: Not Specified
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000000
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 0
SKU Number: To be filled by O.E.M.
Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: PS2Mouse
External Connector Type: PS/2
Port Type: Mouse Port
Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: Keyboard
External Connector Type: PS/2
Port Type: Keyboard Port
Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A1
Internal Connector Type: None
External Reference Designator: TV Out
External Connector Type: Mini Centronics Type-14
Port Type: Other
Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A2A
Internal Connector Type: None
External Reference Designator: COM A
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A2B
Internal Connector Type: None
External Reference Designator: Video
External Connector Type: DB-15 female
Port Type: Video Port
Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External Reference Designator: USB1
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External Reference Designator: USB2
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External Reference Designator: USB3
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9A1 - TPM HDR
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9C1 - PCIE DOCKING CONN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2B3 - CPU FAN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6C2 - EXT HDMI
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3C1 - GMCH FAN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0015, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1D1 - ITP
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0016, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9E2 - MDC INTPSR
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0017, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9E4 - MDC INTPSR
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0018, DMI type 9, 17 bytes
System Slot Information
Designation: J6B2
Type: x16 PCI Express
Current Usage: In Use
Length: Long
ID: 0
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:00:01.0
Handle 0x0019, DMI type 9, 17 bytes
System Slot Information
Designation: J6B1
Type: x1 PCI Express
Current Usage: In Use
Length: Short
ID: 1
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:00:1c.3
Handle 0x001A, DMI type 10, 6 bytes
On Board Device Information
Type: Video
Status: Enabled
Description: Mobile Intel HD Graphics
Handle 0x001B, DMI type 11, 5 bytes
OEM Strings
String 1: Dell System
String 2: 1[05E3h]
String 3: 3[1.0]
String 4: 4[0001]
String 5: 5[0000]
String 6: 6[D0, D4, D8, DA, DE]
String 7: 7[]
String 8: 8[]
String 9: 9[]
String 10: 10[A02]
String 11: 11[]
String 12: 12[]
String 13: 13[P20S]
String 14: 14[0]
String 15: 15[0]
Handle 0x001C, DMI type 12, 5 bytes
System Configuration Options
Option 1: To Be Filled By O.E.M.
Handle 0x001D, DMI type 21, 7 bytes
Built-in Pointing Device
Type: Touch Pad
Interface: Bus Mouse
Buttons: 2
Handle 0x001E, DMI type 22, 26 bytes
Portable Battery
Location: System Battery
Manufacturer: SDI
Manufacture Date: Not Specified
Serial Number: Not Specified
Name: DELL 7YM0739
Chemistry: Lithium Ion
Design Capacity: 51060 mWh
Design Voltage: 7400 mV
SBDS Version: 1.0
Maximum Error: 100%
OEM-specific Information: 0x00000001
Handle 0x001F, DMI type 32, 20 bytes
System Boot Information
Status: No errors detected
Handle 0x0021, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x00000000
Handle 0x0022, DMI type 28, 20 bytes
Temperature Probe
Description: CPU Internal Temperature
Location: Processor
Status: OK
Maximum Value: 127.0 deg C
Minimum Value: 0.0 deg C
Resolution: 1.000 deg C
Tolerance: 0.5 deg C
Accuracy: Unknown
OEM-specific Information: 0x00000000
Handle 0xB000, DMI type 176, 10 bytes
OEM-specific Type
Header and Data:
B0 0A 00 B0 00 00 00 00 E3 05
Handle 0xB100, DMI type 177, 12 bytes
OEM-specific Type
Header and Data:
B1 0C 00 B1 1A 06 00 00 00 00 00 00
Handle 0x0025, DMI type 208, 12 bytes
OEM-specific Type
Header and Data:
D0 0C 25 00 02 05 FE 00 E3 05 01 02
Strings:
20130614
20130924
Handle 0x0026, DMI type 212, 57 bytes
OEM-specific Type
Header and Data:
D4 39 26 00 70 00 71 00 01 49 50 48 9C 00 49 FC
01 9B 00 49 FC 00 7F 01 4A FB 04 80 01 4A FB 00
53 01 4A F7 08 52 01 4A F7 08 7B 01 4A EF 10 7C
01 4A EF 10 FF FF 00 00 00
Handle 0x0027, DMI type 216, 9 bytes
OEM-specific Type
Header and Data:
D8 09 27 00 01 02 01 00 00
Strings:
INTEL
0000
Handle 0x0028, DMI type 217, 8 bytes
OEM-specific Type
Header and Data:
D9 08 28 00 01 02 00 00
Strings:
Handle 0x0029, DMI type 219, 11 bytes
OEM-specific Type
Header and Data:
DB 0B 29 00 00 01 02 03 00 04 05
Strings:
Handle 0x002A, DMI type 220, 22 bytes
OEM-specific Type
Header and Data:
DC 16 2A 00 01 F0 00 00 02 F0 00 00 00 00 03 F0
04 F0 00 00 00 00
Handle 0x002B, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 2B 00 00 00 00 00 00 03 00 00 00 00 00 00
00 00 00
Handle 0x002C, DMI type 222, 16 bytes
OEM-specific Type
Header and Data:
DE 10 2C 00 01 08 FF FF 00 00 00 00 00 00 00 00
Handle 0x002D, DMI type 4, 42 bytes
Processor Information
Socket Designation: SOCKET 0
Type: Central Processor
Family: Core i5
Manufacturer: Intel
ID: 51 06 04 00 FF FB EB BF
Signature: Type 0, Family 6, Model 69, Stepping 1
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz
Voltage: 1.2 V
External Clock: 100 MHz
Max Speed: 3800 MHz
Current Speed: 1600 MHz
Status: Populated, Enabled
Upgrade: Socket rPGA988B
L1 Cache Handle: 0x0004
L2 Cache Handle: 0x0005
L3 Cache Handle: 0x0006
Serial Number: Not Specified
Asset Tag: Fill By OEM
Part Number: Fill By OEM
Core Count: 2
Core Enabled: 2
Thread Count: 4
Characteristics:
64-bit capable
Handle 0x0004, DMI type 7, 19 bytes
Cache Information
Socket Designation: CPU Internal L1
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 128 kB
Maximum Size: 128 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Other
Associativity: 8-way Set-associative
Handle 0x0005, DMI type 7, 19 bytes
Cache Information
Socket Designation: CPU Internal L2
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Back
Location: Internal
Installed Size: 512 kB
Maximum Size: 512 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 8-way Set-associative
Handle 0x0006, DMI type 7, 19 bytes
Cache Information
Socket Designation: CPU Internal L3
Configuration: Enabled, Not Socketed, Level 3
Operational Mode: Write Back
Location: Internal
Installed Size: 3072 kB
Maximum Size: 3072 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 12-way Set-associative
Handle 0x0007, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 16 GB
Error Information Handle: Not Provided
Number Of Devices: 2
Handle 0x0020, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x0007
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 2048 MB
Form Factor: SODIMM
Set: None
Locator: ChannelA-DIMM0
Bank Locator: BANK 0
Type: DDR3
Type Detail: Synchronous
Speed: 1600 MHz
Manufacturer: Hynix/Hyundai
Serial Number: 00000001
Asset Tag: 0987654321
Part Number:
Rank: 1
Configured Clock Speed: 1600 MHz
Handle 0x0023, DMI type 20, 35 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x0020
Memory Array Mapped Address Handle: 0x002F
Partition Row Position: 2
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x0024, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x0007
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 2048 MB
Form Factor: SODIMM
Set: None
Locator: ChannelB-DIMM0
Bank Locator: BANK 2
Type: DDR3
Type Detail: Synchronous
Speed: 1600 MHz
Manufacturer: Hynix/Hyundai
Serial Number: 00000002
Asset Tag: 0987654321
Part Number:
Rank: 1
Configured Clock Speed: 1600 MHz
Handle 0x002E, DMI type 20, 35 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FFFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x0024
Memory Array Mapped Address Handle: 0x002F
Partition Row Position: 2
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x002F, DMI type 19, 31 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FFFFFFFF
Range Size: 4 GB
Physical Array Handle: 0x0007
Partition Width: 2
Handle 0x0037, DMI type 131, 64 bytes
OEM-specific Type
Header and Data:
83 40 37 00 31 00 00 00 00 00 00 00 00 00 00 00
F8 00 43 9C 00 00 00 00 01 20 00 00 05 00 09 00
D1 05 02 00 00 00 00 00 C8 00 FF FF 00 00 00 00
00 00 00 00 26 00 00 00 76 50 72 6F 00 00 00 00
Handle 0x0038, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1
Handle 0x0039, DMI type 127, 4 bytes
End Of Table
Last edited by fungi (2013-10-13 10:31:45)

Semi solved the problem by building a kernel with an ubuntu .config from http://kernel.ubuntu.com/~kernel-ppa/ma … y/current/
I think i have multi touch working on the touchscreen, but this has resulted in breakage of the synapic touchpad which is now operating in a very simple mode (no scrolling or multitouch).
Probably best to follow https://bugs.launchpad.net/ubuntu/+sour … ug/1218973 and http://thread.gmane.org/gmane.linux.kernel.input/32207 for a real solution

Error during configuration of EWA report

Dear Experts,
I am configuring EWA for my Production system. I have maintained the system in SMSY and generated RFC destinations. The RFC check is in GREEN. I have activated the SDCCN in the satellite system. The satellite system is put in Solution. Everything looks correct. However, when i am running any task in SDCCN like "Refresh sessions", "Refresh Service definitions", it fails with the following error:
Refresh of service definitions started from destination SM_SOLCLNT001_BACK
error reading system ID on SM_SOLCLNT001_BACK
Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=20 thRc=497#Unable to dete
Error refreshing service definitions from destination SM_SOLCLNT001_BACK
Task rescheduled for 20111216101604 ( attempt 0001 )
The RFC is working properly. I recreated the RFC many times but the same error. The RFC check is successful. I have removed all the RFCs and created them again in SMSY but to no avail.
Please help.
Thanks in Advance

Hi,
Did you get chance to check the Remote Login of the RFC and authorizations of the user?
Go to SDCCN of Satellite System.
1. Check the status of Task Processor.
Menu "Goto->Settings->Task Processor"; Check Task Processor Status, make sure its active.
2. Check the Task-Specific Settings
In t-code SDCCN --> Menu "Goto->Settings->Task-Specific" . Check the following under "Session Data Collection".
"Data request->Settings ". Confirm the checkbox is checked for "Allow Approximate Data Collection".
"Maintenance->Settings".
"RFC Destinations->Settings" --> Make sure SOLMAN SID is maintained here along with SOLMAN Back RFC destination.
Also check this note 727998 - Complete Replacement of Service Definitions for SDCC/SDCCN

Disappearing External Drives

2 days in a row now 2 external fire wire drives have disappeared from view on our Intel X-serve. The fire wire drives are used for back-up. These are identical LaCie drives. One is connected to the Firewire 800 port on the back of the X-serve, and the other is connected to the second Firewire 800 port on the first drive. Since early January, each night both drives are ejected, using Apple Remote Desktop on another computer (the server is headless), then powered off, and one drive unplugged and carried off site. In the morning the second drive is brought back-in, connected to the first one, then both are powered up, without problem. Now, for the second day in a row, sometime during the day both firewire drives "dropped off" . The drives do not show up on the Server Monitor application, don't show up on the X-serve's desktop (when viewed using Apple Remote Desktop), and don't show up when the Disk Utility application is run on the server. However, if you run System Profiler on the X-serve, both external firewire drives are shown, with correct information.
Yesterday, I tried to correct the situation by restarting the sever. The result was nothing came up, the Server Monitor application reported the temperatures, fans, power supplies, etc. as all running normal, but also showed that the X-serve had no hard drive (external or internal), no memory, and no network ports. None of the processor status lights on the front of the X-serve came on, and no network services were available on the LAN. Only after I shut the server down for several hours and then restarted it did everything come back up normal (including the firewire drives). I am therefore hesitant to restart the server now. I tried cycling the power to the external drives after they disappeared and it made no difference.
My questions are: (1) Is there a UNIX Terminal command or some other command that might work in mounting the drives, since, if System profiler can see the drives, some other parts of the OS must be able to communicate with the drives, and (2) does anybody have any clues as to what files, caches or whatever may have become corrupted that I can clear/ reset/restore so that this does not keep happening?
Intel X-Serve Mac OS X (10.4.8)

Solved own problem. Somebody in the office, concerned about how even light contact could cause the handle for the internal hard drive bay to pop out, thought it would be a good idea to use the hardware lock. When the hardware lock is on, the system won't recognize external hard drives. Found out the hard way that when the hardware lock is on, and the X-serve is rebooted, it wouldn't recognize any hard drive, or even the internal DVD/CD drive.

LCD Brightness Toshiba Equium A100-147

I can't seem to set the brightness on my toshiba laptop.
$ xbacklight -set 00
$
Seems to pause for a while then returns a prompt as if it had completed but nothing changes.
$ toshset -lcd 50
required kernel toshiba support not enabled.
Self explanatory.
$ sudo setpci -v -s 00:02.1 F4.B=00
0000:00:02.1 @f4 0
This doesn't do anything either.
My current battery life is appalling. After a full charge and 35mins uptime I'm now on 43%. I have an xterm, google-chrome, X11 and fluxbox open. I've enabled most of the things in the laptop-mode daemon and another odd point if that my fan seems to be turning on at 46deg and off at 45deg. So all I can hear is fannnnnnn, offffffff, fannnnnnnn, offffffffff.
Weird.
Also, I'm using the xf86-video-intel-newest from the AUR.
Any help on any situation would be great. Thanks.
Last edited by BaconPie (2010-12-21 01:52:01)

dziambo wrote:show "dmidecode"
$ sudo dmidecode
# dmidecode 2.10
SMBIOS version fixup (2.31 -> 2.3).
SMBIOS 2.3 present.
36 structures occupying 1161 bytes.
Table at 0x000DC010.
Handle 0x0000, DMI type 0, 20 bytes
BIOS Information
Vendor: Phoenix Technologies LTD
Version: 2.00
Release Date: 08/30/2006
Address: 0xE4180
Runtime Size: 114304 bytes
ROM Size: 1024 kB
Characteristics:
ISA is supported
PCI is supported
PC Card (PCMCIA) is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
ACPI is supported
USB legacy is supported
AGP is supported
BIOS boot specification is supported
Handle 0x0001, DMI type 1, 25 bytes
System Information
Manufacturer: TOSHIBA
Product Name: Satellite A100
Version: PSB10U-SA10ES1
Serial Number: 12345678901234567
UUID: Not Settable
Wake-up Type: Power Switch
Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Intel Corporation
Product Name: MPAD-MSAE Customer Reference Boards
Version: Not Applicable
Serial Number: Not Applicable
Handle 0x0003, DMI type 3, 21 bytes
Chassis Information
Manufacturer: No Enclosure
Type: Other
Lock: Not Present
Version: N/A
Serial Number: None
Asset Tag: No Asset Tag
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000000
Height: 52 U
Number Of Power Cords: 18
Contained Elements: 0
Handle 0x0004, DMI type 4, 35 bytes
Processor Information
Socket Designation: U1
Type: Central Processor
Family: Other
Manufacturer: Intel
ID: E8 06 00 00 FF FB E9 BF
Version: Genuine Intel(R) CPU T2
Voltage: 3.3 V
External Clock: Unknown
Max Speed: 500 MHz
Current Speed: 1600 MHz
Status: Populated, Enabled
Upgrade: Slot 1
L1 Cache Handle: 0x0005
L2 Cache Handle: 0x0006
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Handle 0x0005, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1 Cache
Configuration: Enabled, Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 16 kB
Maximum Size: 16 kB
Supported SRAM Types:
Burst
Pipeline Burst
Asynchronous
Installed SRAM Type: Asynchronous
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x0006, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2 Cache
Configuration: Enabled, Socketed, Level 2
Operational Mode: Write Back
Location: External
Installed Size: 2048 kB
Maximum Size: 512 kB
Supported SRAM Types:
Burst
Pipeline Burst
Asynchronous
Installed SRAM Type: Burst
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x0007, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J19
Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
External Reference Designator: COM 1
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J23
Internal Connector Type: 25 Pin Dual Inline (pin 26 cut)
External Reference Designator: Parallel
External Connector Type: DB-25 female
Port Type: Parallel Port ECP/EPP
Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J11
Internal Connector Type: None
External Reference Designator: Keyboard
External Connector Type: Circular DIN-8 male
Port Type: Keyboard Port
Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J12
Internal Connector Type: None
External Reference Designator: PS/2 Mouse
External Connector Type: Circular DIN-8 male
Port Type: Keyboard Port
Handle 0x000B, DMI type 9, 13 bytes
System Slot Information
Designation: PCI Slot J11
Type: 32-bit PCI
Current Usage: Unknown
Length: Long
ID: 0
Characteristics:
5.0 V is provided
3.3 V is provided
Handle 0x000C, DMI type 9, 13 bytes
System Slot Information
Designation: PCI Slot J12
Type: 32-bit PCI
Current Usage: Unknown
Length: Long
ID: 0
Characteristics:
5.0 V is provided
3.3 V is provided
Handle 0x000D, DMI type 9, 13 bytes
System Slot Information
Designation: PCI Slot J13
Type: 32-bit PCI
Current Usage: Unknown
Length: Long
ID: 0
Characteristics:
5.0 V is provided
3.3 V is provided
Handle 0x000E, DMI type 10, 6 bytes
On Board Device Information
Type: Sound
Status: Disabled
Description: ADI
Handle 0x000F, DMI type 11, 5 bytes
OEM Strings
String 1: This is the Intel Calistoga
String 2: Chipset CRB Platform
Handle 0x0010, DMI type 12, 5 bytes
System Configuration Options
Option 1: Jumper settings can be described here.
Handle 0x0011, DMI type 15, 29 bytes
System Event Log
Area Length: 16 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: General-purpose non-volatile data functions
Access Address: 0x0000
Status: Valid, Not Full
Change Token: 0x00000001
Header Format: Type 1
Supported Log Type Descriptors: 3
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: Single-bit ECC memory error
Data Format 2: Multiple-event
Descriptor 3: Multi-bit ECC memory error
Data Format 3: Multiple-event
Handle 0x0012, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 2 GB
Error Information Handle: Not Provided
Number Of Devices: 2
Handle 0x0013, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x0012
Error Information Handle: No Error
Total Width: 32 bits
Data Width: 32 bits
Size: 1024 MB
Form Factor: SODIMM
Set: 1
Locator: M1
Bank Locator: Bank 0
Type: DDR
Type Detail: Synchronous
Speed: Unknown
Manufacturer: Not Specified
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Handle 0x0014, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x0012
Error Information Handle: No Error
Total Width: 32 bits
Data Width: 32 bits
Size: 1024 MB
Form Factor: SODIMM
Set: 1
Locator: M2
Bank Locator: Bank 1
Type: DDR
Type Detail: Synchronous
Speed: Unknown
Manufacturer: Not Specified
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Handle 0x0015, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Array Handle: 0x0012
Partition Width: 0
Handle 0x0016, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0003FFFFFFF
Range Size: 1 GB
Physical Device Handle: 0x0013
Memory Array Mapped Address Handle: 0x0015
Partition Row Position: Unknown
Interleave Position: Unknown
Interleaved Data Depth: Unknown
Handle 0x0017, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00040000000
Ending Address: 0x0007FFFFFFF
Range Size: 1 GB
Physical Device Handle: 0x0014
Memory Array Mapped Address Handle: 0x0015
Partition Row Position: Unknown
Interleave Position: Unknown
Interleaved Data Depth: Unknown
Handle 0x0018, DMI type 23, 13 bytes
System Reset
Status: Enabled
Watchdog Timer: Present
Boot Option: Do Not Reboot
Boot Option On Limit: Do Not Reboot
Reset Count: Unknown
Reset Limit: Unknown
Timer Interval: Unknown
Timeout: Unknown
Handle 0x0019, DMI type 24, 5 bytes
Hardware Security
Power-On Password Status: Disabled
Keyboard Password Status: Unknown
Administrator Password Status: Disabled
Front Panel Reset Status: Unknown
Handle 0x001A, DMI type 25, 9 bytes
System Power Controls
Next Scheduled Power-on: 12-31 23:59:59
Handle 0x001B, DMI type 26, 20 bytes
Voltage Probe
Description: Voltage Probe
Location: Processor
Status: OK
Maximum Value: Unknown
Minimum Value: Unknown
Resolution: Unknown
Tolerance: Unknown
Accuracy: Unknown
OEM-specific Information: 0x00000000
Handle 0x001C, DMI type 27, 12 bytes
Cooling Device
Temperature Probe Handle: 0x001D
Type: Fan
Status: OK
OEM-specific Information: 0x00000000
Handle 0x001D, DMI type 28, 20 bytes
Temperature Probe
Description: Temperature Probe
Location: Processor
Status: OK
Maximum Value: Unknown
Minimum Value: Unknown
Resolution: Unknown
Tolerance: Unknown
Accuracy: Unknown
OEM-specific Information: 0x00000000
Handle 0x001E, DMI type 29, 20 bytes
Electrical Current Probe
Description: Electrical Current Probe
Location: Processor
Status: OK
Maximum Value: Unknown
Minimum Value: Unknown
Resolution: Unknown
Tolerance: Unknown
Accuracy: Unknown
OEM-specific Information: 0x00000000
Handle 0x001F, DMI type 30, 6 bytes
Out-of-band Remote Access
Manufacturer Name: Intel
Inbound Connection: Enabled
Outbound Connection: Disabled
Handle 0x0020, DMI type 32, 20 bytes
System Boot Information
Status: <OUT OF SPEC>
Handle 0x0021, DMI type 136, 8 bytes
OEM-specific Type
Header and Data:
88 08 21 00 FF FF 00 00
Strings:
Handle 0x0022, DMI type 150, 14 bytes
OEM-specific Type
Header and Data:
96 0E 22 00 01 01 00 00 00 00 00 00 00 00
Strings:
ABSOLUTE(PHOENIX) CLM
Handle 0x0023, DMI type 127, 4 bytes
End Of Table
Last edited by BaconPie (2010-12-24 13:50:34)

Solaris 10 [11/06]: Second CPU not accessible using psradm / psrinfo / ...

Hi all,
Some months ago I've build up a small Server for some home projects with Solaris 10 x86 11/06. All things are running fine but Solaris does not use the second CPU that is installed.
I have a FSC D1306 server board from an old Primergy P200 server.
First, I saw that my system only uses one CPU:
# psrinfo
0       on-line   since 10/04/2007 20:13:27I then checked, if the system recognizes the second processor socket at all:
# prtdiag
System Configuration: FUJITSU SIEMENS D1306
BIOS Configuration: FUJITSU SIEMENS // Phoenix Technologies Ltd. 4.06 Rev. 1.05.1306             12/12/2003
==== Processor Sockets ====================================
Version                          Location Tag
Pentium(R) III                   CPU 0
Pentium(R) III                   CPU 1
[ . . . ]After that I wanted to see, if the second processor has been detected properly by the BIOS:
# smbios -t SMB_TYPE_PROCESSOR
ID    SIZE TYPE
4     61   SMB_TYPE_PROCESSOR (processor)
Manufacturer: Intel
Version: Pentium(R) III
Location Tag: CPU 0
Family: 17 (Pentium III)
CPUID: 0x383fbff000006b1
Type: 3 (central processor)
Socket Upgrade: 4 (ZIF socket)
Socket Status: Populated
Processor Status: 1 (enabled)
Supported Voltages: 1.7V
External Clock Speed: Unknown
Maximum Speed: 1400MHz
Current Speed: 1400MHz
L1 Cache: 6
L2 Cache: 7
L3 Cache: None
ID    SIZE TYPE
5     61   SMB_TYPE_PROCESSOR (processor)
Manufacturer: Intel
Version: Pentium(R) III
Location Tag: CPU 1
Family: 17 (Pentium III)
CPUID: 0x383fbff000006b4
Type: 3 (central processor)
Socket Upgrade: 4 (ZIF socket)
Socket Status: Populated
Processor Status: 1 (enabled)
Supported Voltages: 1.7V
External Clock Speed: Unknown
Maximum Speed: 1400MHz
Current Speed: 1400MHz
L1 Cache: 8
L2 Cache: 9
L3 Cache: None^^ Well, I guess it was detected properly. But after running prtconf and prtpicl I saw that there was only one processor available to Solaris.
Can anyone help me enabling the second CPU? I would like to use it because I have some applications that would run much better on two CPU's rather than one.
Thanks for all tips,
C]-[aoZ
Edited by: CHaoSlayeR on Oct 28, 2007 7:04 AM

If memory serves, to get multi-cpu working, you must enable acpi in the bios. Given that this is a pIII, it is in the era where api was either really buggy or was off by default (so you should also check to make sure the bios was the latest...)
-r

Solaris 10 + PVIO with 2 vcpus on OVM 2.2.1

Solaris 10 was installed with pv drivers on a domU. And two vcpus were given to it like this:
[root@earthscience ~]# xm vcpu-list
Name ID VCPU CPU State Time(s) CPU Affinity
Domain-0 0 0 2 -b- 9938.4 any cpu
Domain-0 0 1 3 -b- 532.9 any cpu
Domain-0 0 2 2 -b- 334.5 any cpu
Domain-0 0 3 1 r-- 670.0 any cpu
s10_hvm1 5 0 0 -r- 18325.5 0
s10_hvm1 5 1 - p 0.0 2 <-- always in 'p' state
However, one CPU was always in 'p' state whatever heavy process was running on Solaris. And
Solaris only saw one cpu with cpuinfo command in mdb.
bash-3.00#mdb -k
Loading modules: [ unix krtld genunix specfs dtrace cpu.generic uppc ufs ip hook neti sctp arp usba fcp fctl nca lofs zfs nfs random md cpc crypto fcip logindmux ptm sppp ]
::cpuinfo
::cpuinfoID ADDR FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD PROC
0 fffffffffbc293a0 1b 1 0 59 no no t-0 ffffffff87115500 mdb
Tough smbios in Solaris saw two cpus:
bash-3.00# smbios
1025 35 SMB_TYPE_PROCESSOR (processor)
Manufacturer: AMD
Location Tag: CPU 1
Family: 1 (other)
CPUID: 0x1789fbff00040f13
Type: 3 (central processor)
Socket Upgrade: 1 (other)
Socket Status: Populated
Processor Status: 1 (enabled)
Supported Voltages:
External Clock Speed: Unknown
Maximum Speed: 2793MHz
Current Speed: 2793MHz
L1 Cache: 0
L2 Cache: 0
L3 Cache: 0
ID SIZE TYPE
1026 35 SMB_TYPE_PROCESSOR (processor)
Manufacturer: AMD
Location Tag: CPU 2
Family: 1 (other)
CPUID: 0x1789fbff00040f13
Type: 3 (central processor)
Socket Upgrade: 1 (other)
Socket Status: Populated
Processor Status: 1 (enabled)
Supported Voltages:
External Clock Speed: Unknown
Maximum Speed: 2793MHz
Current Speed: 2793MHz
L1 Cache: 0
L2 Cache: 0
L3 Cache: 0
Did any one see this before?

I found there were some errors in kernel log messages. It seems that the apix and pcplusmp can not start up.
bash-3.00# dmesg
Jan 13 23:49:24 s10u10b4 unix: [ID 223955 kern.info] x86_feature: clfsh
Jan 13 23:49:24 s10u10b4 unix: [ID 508459 kern.warning] WARNING: Cannot load ps
m apix
Jan 13 23:49:24 s10u10b4 unix: [ID 508459 kern.warning] WARNING: Cannot load ps
m pcplusmp
Jan 13 23:49:24 s10u10b4 unix: [ID 168242 kern.info] mem = 2096764K (0x7ff9f000
Jan 13 23:49:24 s10u10b4 rootnex: [ID 466748 kern.info] root nexus = i86pc
Jan 13 23:49:24 s10u10b4 iommulib: [ID 321598 kern.info] NOTICE: iommulib_nexus
_register: rootnex-1: Succesfully registered NEXUS i86pc nexops=fffffffffbcf2d6
0
Edited by: 819809 on 2011-1-17 上午12:51

Debugging LabVIEW/Blackfin application is VERY SLOW...

Hey guys,
I am working through the evaluation example programs for LabVIEW Embedded for Blackfin, and I'm using various debug channels (instrumented, non-instrumented), but I do not have an emulator....
I have found that the debugging (breakpoints, single-stepping, etc.) is extremely slow and painful....is this a non-issue with an emulator ($4000!)?
I can't see where debugging with the non-emulator channels is practical....I'm hoping that an emulator (ADI-HPUSB-ICE or equivalent) solves the problem and behaves more like a local debugger when single-stepping and such...
Does anyone have any experience with development and debug using an emulator vs. the slower speed intrusive debug methods?
Thanks,
Larry

Hey,
I use the yellow crossover cable that came with my EZ-Kit.
As I stated earlier, I make sure that the only ethernet connection that is "live" is the one connected to the EZ-Kit.
I use the Processor Status window to view the current state of the connection with the board. Sometimes, I find that I have to press the Debug button on the project window, then Cancel the connection to get the board to HALT. I have reached a point where I don't need to hard-reset or unplug the board very often.
I have attached screen shots of the Build Options panels that I am using now.
Hope this helps,
Larry
Attachments:
BuildOptions3.png ‏16 KB
BuildOptions1.png ‏12 KB
BuildOptions2.png ‏11 KB

ARM Embedded serial buffers

Hi All,
Colleagues and I have had some very recent experience with serial buffers when using the ARM Embedded module (1.1) for LabVIEW, using the LPC23xx series controller (we are using the LPC2368/87). I thought it best to share should others find some crazy things going on.
We were losing packet information when large packets came through on the normal 64 byte allocation for the incoming serial buffer. These large packets happened fairly regularly with other small packets in between. At times we found that 2 bytes would be dropped thus losing the CRC check and forcing a drop in the packet information. It took some time to work why (surely it was to do with our firmware!) but we soon realised we had to adjust this serial buffer size from 64 to something much larger - 256 or 512 - even though we have another buffer within our producer loop. This serial buffer change is done in the ARM_serial.c file, easily found using Keil uVision; line #48:
#define SER_IN_BUF_SIZE 64
Even though we initialised the buffer size (using "Serial Port Init.vi") to 512 there was no change to the hardcoded value of 64.
In terms of RAM allocation, a change in the 'serial in buffer' size (power of 2 change) will generate a x4 memory allocation in your heap space (ZI data). This means, if I increase my buffer size by 256 bytes I also reduce my available heap space (run-time RAM) by 1024 bytes. This can be significant if you are very tight on memory (changed using line #100 in your 'target'.s file - LPC2300.s for me).
I hope that helps for somebody.

Resolving this problem did take us some time, first in identifying why we were losing packets after setting the buffer size on the init.vi to 512 and second in realising that it wasn't working. We had packets (largest ones) with a size of 130 bytes coming in every 100 ms. Trying to handle these packets takes time and heap space - if you use more than one queue (for more than one consumer loops). In terms of memory efficiency we have stayed away from using too many queues due to dynamic memory allocation; if too many packets came in and we weren't able to process them quick enough then the heap will become full and the controller will crash ("Memory Abort" error - as indicated in the LabVIEW processor status window).
We previously went over the known issues site and couldn't find a mention of serial buffer size allocation input on the ...init.vi (see: http://digital.ni.com/public.nsf/websearch/270545BCCF971FE9862574F20049095C?opendocument&Submitted&&...).
You mentioned that it is an intended design, which is surprising. Having the option for the user to control their hardware settings using firmware (LabVIEW) would have been a real plus for NI.
I also noticed that the serial buffer size is allocated for each port - well, we think so anyway. We have 4 ports on our controller, which is why we see a quadruple increase in heap allocation with an increase in buffer size. Is there some way for us to isolate the buffer size to each port, thereby giving the (default) 64 bytes to the unused ports and increasing the allocation to those that need it ? This would put more control in the user to maximise their memory usage with more efficiency, especially if all you are using are 2 ports and are tight with memory.

Processor status in SPAU

Similar Messages

Maybe you are looking for