[SOLVED] System hung loading domU
Very strange issue. I built a base Arch system and things seem to be functional. I was able to get thing loaded up with xen, I created a domu configuration for xen and managed to get things loaded and Arch installed into a domu without a ton of issues. I then edited the configuration file to use pygrub and loaded up my domu vm.
I execute xl create -c /etc/xen/archdomu.cfg and the system loads, I see grub, timer expired and then the system just sits. The system appears hung, but it is not. If I hit Ctrl+] the system will continue booting to the vm and then everything appears OK with the vm.
Now, if I launch the vm (domU) using xl create /etc/xen/archdomu.cfg to load wihtout the console, the system boots without issue. I can connect with xl console ArchU and the system is fully loaded and ready to go.
So the question is what could be going on. I thought Ctrl+] exits the console, so why is it needed to boot my domu?
Let me know if you need any configuration files or logs and I will be sure to post them if they can help us resolve things. I tried several things including a very minimal grub, but the same thing still happens. Thanks
Last edited by smakovits (2014-01-12 02:00:51)
Solved this by removing the timer from GRUB.
GRUB_TIMEOUT=0
Similar Messages
-
[SOLVED] System hung while mdadm is stabalizing
I've got an external 8 bay SATA RAID chassis (connected to my PC with 2 x eSATA) that I'm trying to expand. It had 5 x 2TB drives (WD20EARS) configured as RAID5. I added 3 more 2TB drives.
I did an mdadm --grow /dev/md3 --number-devices=7
I'd like to get to 7 device with a spare. It gave me an error about not being able to backup some table and then it just went to work stabilizing with the 7 disk configuration. That was about 6 hours ago. The last I saw, it was something like 13% complete. lol!
Meanwhile, I was adding 2 more drives to another drive array. Basically, taking a 4 x 750GB drive RAID5 to a 6 x 750GB array. They are on two different controllers and I was doing it simultaneously. The smaller array gave me a similar error message.
As is always the case, I was moving a bunch of stuff around, clearing room so I could free loose drives I was using for backup and add them into the array. The point being, I've got a mountain of data at stake including several databases and system images of systems that are no longer around but I'd really like to have on hand.
There is a backup of the backups (a 10 x 1.5TB RAID5 chassis). I rsync to it every so often but it hasn't happened for a couple of months. Anyway, I'm sure the backups are fine.
... so here's the situation... the computer is locked. The mouse pointer doesn't move. I'm loathe to reboot the system because I looked up the error message mdadm spit out when I added the disks and it said basically the system couldn't backup a critical table that would allow the operation to be failsafe. The point being, hope nothing happens during the process or all is lost. Of course, something did happen.
I will add the system has been rock stable since I got it. I've never seen it hang before. I'm running 32 bit Arch and did a full system upgrade on Friday.
I've noticed a few bugs regarding particularly large arrays being expanded leading to lockup but those bugs go back to 2006. I would imagine those issues are long fixed.
The system responds to PINGs but will not accept SSH connections.
Any opinions on whether to power cycle the system, or not? Maybe I should unplug the eSATA connections, hoping just one of the arrays will fail allowing the other to recover?
Switch to Windows? lol!
I'm wide open to advice here.
Last edited by TomB17 (2011-03-14 01:00:37)Update:
Since these problems a couple of weeks ago, I ran 'badblocks -wvs' against every disk in the array. After several days with no errors, I re-striped the array as RAID 6 and let it completely build before formatting or using the partition in any way. This time, it completed without hanging.
md125 : active raid6 sdp1[7] sdo1[6] sdn1[5] sdm1[4] sdl1[3] sdk1[2] sdj1[1] sdi1[0]
11721071616 blocks super 1.2 level 6, 512k chunk, algorithm 2 [8/8] [UUUUUUUU]
I formatted with EXT4 and put some data on the drive. It will not store data without corrupting it.
If I download the most recent MiniMyth distrobution and MD5 checksum to that partition, it will not check with md5sum. Downloading the distribution and checksum to another partition, however, works perfectly every time.
md5sum -c ram-minimyth-0.23.1-76.tar.bz2.md5
ram-minimyth-0.23.1-76.tar.bz2: FAILED
md5sum: WARNING: 1 computed checksum did NOT match
I'm at a bit of a roadblock. I thought the partition size might be too big for 32 bit Linux but it looks like it should be good to 16TB with 4KB. dumpe2fs shows the filesystem has 4K block size.
For what it's worth, I didn't specify any of the tuning parameters when I created the stripe set or the file system.
mdadm --create /dev/md125 --level=6 --raid-devices=8 /dev/sd{i,j,k,l,m,n,o,p}1
mkfs.ext4 /dev/md125
I'm going to stew on this a bit but would appreciate ideas. Has anyone else successfully created a large RAID 5 or 6 array? Am I missing something? -
[SOLVED]3.18.5-1-ARCH + system-modules-load.service on Macbook Pro 9,2
After upgrading from 3.18.4-1-ARCH to 3.18.5-1-ARCH this weekend, my systemd service system-modules-load fails during bootup. I checked out
# systemctl status system-modules-load
and found nothing but a warning that my journal has been rotated and the log output is incomplete. I have not hunted down the log or rooted through dmesg as of yet - I need my system functional while working during the week, so I downgraded my kernel back to 3.18.4 for now (under which system-modules-load loads fine). I will reinstall 3.18.5 next weekend and see if I can locate the problem - this post is just a feeler to see if anyone else is encountering this problem with the latest kernel.
Last edited by Olorin (2015-02-06 03:08:31)Yep. It was my own fault. I had been using the b43 driver for my BCM4331 wifi card, and recently switched to broadcom-wl. However, I still was trying to load b43 in /etc/modules-load even though I had removed the driver and module from my system. Not sure why my system only started complaining in 3.18.5, but in any case removing the offending .conf file solved the problem. Thanks, graysky.
-
How to load a class dynamically in the current/system class loader
I need to dynamically load a new jdbc driver jar to the current/system class loader... Please note that creating a new classloader will not help since the DriverManager refers to the systemclassloader itself.
Restarting the application by appending the jar to its classpath will solve the problem but I want to avoid doing this.Did you then create a ClassLoader to load the JDBC
driver and then install it into the system as
directed by the JDBC specification (ie
Class.forName(someClassName))?
And then try to use it from a class loaded fromsome
other ClassLoader (i.e. the system class loader)?
If you did not try this please explain why not.O.K. I just looked at the source to
java.sql.DriverManager. I did not know what I was
talking about, as what I suggested above will not
work.
This is my new Idea:
Create a URLClassLoader to load the JDBC driver also
in this ClassLoader you need to place a helper class
that does the following:
public class Helper {
public Driver getJDBCDriver(String driverClassName,
String url) {
try {
Class.forName(driverClassName);
Driver d = DriverManager.getDriver(url);
return d;
catch(Exception ex) {
ex.printStackTrace();
return null;
}Now create an instance of the Helper class in the new
ClassLoader, and call its getJDBCDriver method to get
an instance of the driver (you will probably have to
create an interface in the root class loader that the
Helper implements so that you can easily call it).
Now from the root classloader you can make calls
directly to the returned Driver and bypass the
DriverManager and its restrictions on cross
ClassLoader access.
The only catch here is that you would have to call to
the returned Driver directly and not use the Driver
Manager.This sounds like will work but I did not want to load DriverManager in a new classloader.. I did a hack
I unzip the jar dynamically in a previously known location (which I included in my classpath when launching the app). The classLoader finds the class now though it did not exist when the app was launched !
A hack of-course but works eh .. -
System hung on candidate selection activities
Hello,
We have recently upgraded our eRecruiting system from EHP3 to EHP6 in the development environment. In the course of testing, I tried to perform request for more information under candidate selection. However, after I changed the letter and tried to display it, but the system hung. I refreshed my screen and tried to get back into the same candidate, but the system said that the candidate is being edited by the test user id that I am currently using.
This is happening to other correspondences with change letter section, such as "Invite for interview" etc. If this problem is solved, it should resolve all similar correspondence issues.Hello Alex,
when upgrading from EhP 3 or lower to EhP 4 or higher several adjustments to the correspondences and the correspondence customizing have to be applied as the solution for changing letters has be changed completely. Could you check the following:
confirm that table T77RCF_DOC_CAT contains and entry with key 0004 and an entry with key 0005
confirm that in table T77RCF_ACT_CAT the value for the document category of the activity category 02 (simple correspondence) is set to 0004
confirm that in table T77RCF_ACT_CAT the value for the document category of the activity category 04 (invitation) is set to 0005
check that the interface of a simple correspondence SMARTFORM is exactly the same as HRRCF_CS_IT_APPLICANT (check for the importing parameter THEAD as this a new parameter which was not existing in the EhP 3 referecnce SMARTFORM HRRCF_CS_APPLICANT)
check that the interface of an invitation SMARTFORM is exactly the same as HRRCF_CS_IT_APPL_INVITATION (check for the importing parameter THEAD as this a new parameter which was not existing in the EhP 3 referecnce SMARTFORM HRRCF_CS_APPL_INVITATION)
just to be sure check that the mapping of correspondence form to include text module is correct in table T77RCF_INCL2FORM
If all this is correct and the issue persists check if the SMARTFORM for the correspondence is testable in the backend. Simply test it in the backend till you display the print preview. You do not need to fill all parameters. Sometimes the system has issues to generate the function module for a SMARTFORM if the initial call is done via web. The backend test ensures that all runtime elements are generated. Then check if the error persists.
If this is still not solving the issue I recomment to customize one of the example SMARTFORMs with name HRRCF_CS_IT_EXA_* for one of your activities (pay attention to use one which matches the activity category of you activity type. If the interface includes an parameter EVENT the form can be used with activity category 04 (invitation) otherwise with activity category 02 (simple correspondence)). Do not forget to maintain the matching letter section text module in table T77RCF_INCL2FORM. You will find the name of the correct text module if you open the SMARTFORM and look for the text with id "MAIN" in the window "Hauptfenster".
If your scenario is working with the example SMARTFORM there is highly likely a problem with your SMARTFORM implementation. If it is not working you have probably a setup issue. If we can narrow the issue we might be able to have additional ideas.
Next to all of the things above. Please check if you get any information in the application log (SLG1) or if there is a dump (ST22).
Kind regards
Roman -
System hungs up after an upgrade (because of the virtualbox ?)
I just update my system's virtualbox to the newest version.
After the upgrade I found my system hungs up after an random period of running...
anybody knows what happened ?
Last edited by Hacksign (2013-10-23 02:31:17)jasonwryan wrote:
Your system in Virtualbox, ie., a virtual machine? Or your actual (host) system?
Logs are accessed via journalctl or, for the packages you upgraded, /var/log/pacman.
It's my actual system.
The actual system hung up ... no any response.
and I guess, it is because the virtualbox, because it is ok when there is no virtual machine running ...
here is the log of last time, which is generated by this command "journalctl --since=today | tac | sed -n '/-- Reboot --/{n;:r;/-- Reboot --/q;p;n;b r}' | tac"
(I didn't find any thing valueable )
-- Logs begin at 三 2013-02-06 10:14:14 CST, end at 三 2013-10-23 10:49:52 CST. --
10月 23 09:19:05 XSign systemd-journal[105]: Runtime journal is using 636.0K (max 176.5M, leaving 264.8M of free 1.7G, current limit 176.5M).
10月 23 09:19:05 XSign systemd-journal[105]: Runtime journal is using 640.0K (max 176.5M, leaving 264.8M of free 1.7G, current limit 176.5M).
10月 23 09:19:05 XSign kernel: Initializing cgroup subsys cpuset
10月 23 09:19:05 XSign kernel: Initializing cgroup subsys cpu
10月 23 09:19:05 XSign kernel: Initializing cgroup subsys cpuacct
10月 23 09:19:05 XSign kernel: Linux version 3.11.6-1-ARCH (nobody@var-lib-archbuild-extra-i686-thomas) (gcc version 4.8.1 20130725 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Oct 19 00:29:46 CEST 2013
10月 23 09:19:05 XSign kernel: e820: BIOS-provided physical RAM map:
10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x00000000000e4000-0x00000000000fffff] reserved
10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000df68ffff] usable
10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x00000000df690000-0x00000000df69dfff] ACPI data
10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x00000000df69e000-0x00000000df6cffff] ACPI NVS
10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x00000000df6d0000-0x00000000df6ddfff] reserved
10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x00000000df6e0000-0x00000000df6fffff] reserved
10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x00000000fff00000-0x00000000ffffffff] reserved
10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x0000000100000000-0x000000011fffffff] usable
10月 23 09:19:05 XSign kernel: Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
10月 23 09:19:05 XSign kernel: SMBIOS 2.5 present.
10月 23 09:19:05 XSign kernel: DMI: System manufacturer System Product Name/P5KPL-AM SE, BIOS 0311 10/30/2008
10月 23 09:19:05 XSign kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
10月 23 09:19:05 XSign kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
10月 23 09:19:05 XSign kernel: e820: last_pfn = 0xdf690 max_arch_pfn = 0x100000
10月 23 09:19:05 XSign kernel: MTRR default type: uncachable
10月 23 09:19:05 XSign kernel: MTRR fixed ranges enabled:
10月 23 09:19:05 XSign kernel: 00000-9FFFF write-back
10月 23 09:19:05 XSign kernel: A0000-BFFFF uncachable
10月 23 09:19:05 XSign kernel: C0000-DFFFF write-protect
10月 23 09:19:05 XSign kernel: E0000-EFFFF write-through
10月 23 09:19:05 XSign kernel: F0000-FFFFF write-protect
10月 23 09:19:05 XSign kernel: MTRR variable ranges enabled:
10月 23 09:19:05 XSign kernel: 0 base 0E0000000 mask FE0000000 uncachable
10月 23 09:19:05 XSign kernel: 1 base 000000000 mask F00000000 write-back
10月 23 09:19:05 XSign kernel: 2 base 100000000 mask FE0000000 write-back
10月 23 09:19:05 XSign kernel: 3 base 0DF700000 mask FFFF00000 uncachable
10月 23 09:19:05 XSign kernel: 4 base 0DF800000 mask FFF800000 uncachable
10月 23 09:19:05 XSign kernel: 5 disabled
10月 23 09:19:05 XSign kernel: 6 disabled
10月 23 09:19:05 XSign kernel: 7 disabled
10月 23 09:19:05 XSign kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
10月 23 09:19:05 XSign kernel: e820: update [mem 0xdf700000-0xffffffff] usable ==> reserved
10月 23 09:19:05 XSign kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [c00ff780]
10月 23 09:19:05 XSign kernel: Scanning 1 areas for low memory corruption
10月 23 09:19:05 XSign kernel: initial memory mapped: [mem 0x00000000-0x00bfffff]
10月 23 09:19:05 XSign kernel: Base memory trampoline at [c009b000] 9b000 size 16384
10月 23 09:19:05 XSign kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
10月 23 09:19:05 XSign kernel: [mem 0x00000000-0x000fffff] page 4k
10月 23 09:19:05 XSign kernel: init_memory_mapping: [mem 0x37000000-0x373fffff]
10月 23 09:19:05 XSign kernel: [mem 0x37000000-0x373fffff] page 2M
10月 23 09:19:05 XSign kernel: init_memory_mapping: [mem 0x30000000-0x36ffffff]
10月 23 09:19:05 XSign kernel: [mem 0x30000000-0x36ffffff] page 2M
10月 23 09:19:05 XSign kernel: init_memory_mapping: [mem 0x00100000-0x2fffffff]
10月 23 09:19:05 XSign kernel: [mem 0x00100000-0x003fffff] page 4k
10月 23 09:19:05 XSign kernel: [mem 0x00400000-0x2fffffff] page 2M
10月 23 09:19:05 XSign kernel: init_memory_mapping: [mem 0x37400000-0x377fdfff]
10月 23 09:19:05 XSign kernel: [mem 0x37400000-0x377fdfff] page 4k
10月 23 09:19:05 XSign kernel: BRK [0x00877000, 0x00877fff] PGTABLE
10月 23 09:19:05 XSign kernel: RAMDISK: [mem 0x7fd60000-0x7ffeffff]
10月 23 09:19:05 XSign kernel: Allocated new RAMDISK: [mem 0x3756e000-0x377fdf01]
10月 23 09:19:05 XSign kernel: Move RAMDISK from [mem 0x7fd60000-0x7ffeff01] to [mem 0x3756e000-0x377fdf01]
10月 23 09:19:05 XSign kernel: ACPI: RSDP 000fbf00 00014 (v00 ACPIAM)
10月 23 09:19:05 XSign kernel: ACPI: RSDT df690000 0003C (v01 A_M_I_ OEMRSDT 10000830 MSFT 00000097)
10月 23 09:19:05 XSign kernel: ACPI: FACP df690200 00084 (v02 A_M_I_ OEMFACP 10000830 MSFT 00000097)
10月 23 09:19:05 XSign kernel: ACPI: DSDT df6905c0 077A2 (v01 A1126 A1126000 00000000 INTL 20051117)
10月 23 09:19:05 XSign kernel: ACPI: FACS df69e000 00040
10月 23 09:19:05 XSign kernel: ACPI: APIC df690390 0006C (v01 A_M_I_ OEMAPIC 10000830 MSFT 00000097)
10月 23 09:19:05 XSign kernel: ACPI: MCFG df690400 0003C (v01 A_M_I_ OEMMCFG 10000830 MSFT 00000097)
10月 23 09:19:05 XSign kernel: ACPI: OEMB df69e040 00080 (v01 A_M_I_ AMI_OEM 10000830 MSFT 00000097)
10月 23 09:19:05 XSign kernel: ACPI: HPET df697d70 00038 (v01 A_M_I_ OEMHPET 10000830 MSFT 00000097)
10月 23 09:19:05 XSign kernel: ACPI: GSCI df69e0c0 02024 (v01 A_M_I_ GMCHSCI 10000830 MSFT 00000097)
10月 23 09:19:05 XSign kernel: ACPI: Local APIC address 0xfee00000
10月 23 09:19:05 XSign kernel: 2686MB HIGHMEM available.
10月 23 09:19:05 XSign kernel: 887MB LOWMEM available.
10月 23 09:19:05 XSign kernel: mapped low ram: 0 - 377fe000
10月 23 09:19:05 XSign kernel: low ram: 0 - 377fe000
10月 23 09:19:05 XSign kernel: BRK [0x00878000, 0x00878fff] PGTABLE
10月 23 09:19:05 XSign kernel: Zone ranges:
10月 23 09:19:05 XSign kernel: DMA [mem 0x00001000-0x00ffffff]
10月 23 09:19:05 XSign kernel: Normal [mem 0x01000000-0x377fdfff]
10月 23 09:19:05 XSign kernel: HighMem [mem 0x377fe000-0xdf68ffff]
10月 23 09:19:05 XSign kernel: Movable zone start for each node
10月 23 09:19:05 XSign kernel: Early memory node ranges
10月 23 09:19:05 XSign kernel: node 0: [mem 0x00001000-0x0009efff]
10月 23 09:19:05 XSign kernel: node 0: [mem 0x00100000-0xdf68ffff]
10月 23 09:19:05 XSign kernel: On node 0 totalpages: 914990
10月 23 09:19:05 XSign kernel: free_area_init_node: node 0, pgdat c06d7740, node_mem_map f597e020
10月 23 09:19:05 XSign kernel: DMA zone: 32 pages used for memmap
10月 23 09:19:05 XSign kernel: DMA zone: 0 pages reserved
10月 23 09:19:05 XSign kernel: DMA zone: 3998 pages, LIFO batch:0
10月 23 09:19:05 XSign kernel: Normal zone: 1744 pages used for memmap
10月 23 09:19:05 XSign kernel: Normal zone: 223230 pages, LIFO batch:31
10月 23 09:19:05 XSign kernel: HighMem zone: 5374 pages used for memmap
10月 23 09:19:05 XSign kernel: HighMem zone: 687762 pages, LIFO batch:31
10月 23 09:19:05 XSign kernel: Using APIC driver default
10月 23 09:19:05 XSign kernel: ACPI: PM-Timer IO Port: 0x808
10月 23 09:19:05 XSign kernel: ACPI: Local APIC address 0xfee00000
10月 23 09:19:05 XSign kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
10月 23 09:19:05 XSign kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
10月 23 09:19:05 XSign kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
10月 23 09:19:05 XSign kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
10月 23 09:19:05 XSign kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
10月 23 09:19:05 XSign kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
10月 23 09:19:05 XSign kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
10月 23 09:19:05 XSign kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
10月 23 09:19:05 XSign kernel: ACPI: IRQ0 used by override.
10月 23 09:19:05 XSign kernel: ACPI: IRQ2 used by override.
10月 23 09:19:05 XSign kernel: ACPI: IRQ9 used by override.
10月 23 09:19:05 XSign kernel: Using ACPI (MADT) for SMP configuration information
10月 23 09:19:05 XSign kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
10月 23 09:19:05 XSign kernel: smpboot: Allowing 4 CPUs, 2 hotplug CPUs
10月 23 09:19:05 XSign kernel: nr_irqs_gsi: 40
10月 23 09:19:05 XSign kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
10月 23 09:19:05 XSign kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000e3fff]
10月 23 09:19:05 XSign kernel: PM: Registered nosave memory: [mem 0x000e4000-0x000fffff]
10月 23 09:19:05 XSign kernel: e820: [mem 0xdf700000-0xfedfffff] available for PCI devices
10月 23 09:19:05 XSign kernel: Booting paravirtualized kernel on bare hardware
10月 23 09:19:05 XSign kernel: setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1
10月 23 09:19:05 XSign kernel: PERCPU: Embedded 14 pages/cpu @f5934000 s33536 r0 d23808 u57344
10月 23 09:19:05 XSign kernel: pcpu-alloc: s33536 r0 d23808 u57344 alloc=14*4096
10月 23 09:19:05 XSign kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
10月 23 09:19:05 XSign kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 913214
10月 23 09:19:05 XSign kernel: Kernel command line: root=/dev/sda2 ro init=/usr/lib/systemd/systemd
10月 23 09:19:05 XSign kernel: PID hash table entries: 4096 (order: 2, 16384 bytes)
10月 23 09:19:05 XSign kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
10月 23 09:19:05 XSign kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
10月 23 09:19:05 XSign kernel: Initializing CPU#0
10月 23 09:19:05 XSign kernel: allocated 7320696 bytes of page_cgroup
10月 23 09:19:05 XSign kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
10月 23 09:19:05 XSign kernel: Initializing HighMem for node 0 (000377fe:000df690)
10月 23 09:19:05 XSign kernel: Memory: 3612756K/3659960K available (4262K kernel code, 426K rwdata, 1356K rodata, 608K init, 948K bss, 47204K reserved, 2751048K highmem)
10月 23 09:19:05 XSign kernel: virtual kernel memory layout:
fixmap : 0xfff15000 - 0xfffff000 ( 936 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
.init : 0xc06e9000 - 0xc0781000 ( 608 kB)
.data : 0xc0529d5e - 0xc06e8a00 (1787 kB)
.text : 0xc0100000 - 0xc0529d5e (4263 kB)
10月 23 09:19:05 XSign kernel: Checking if this processor honours the WP bit even in supervisor mode...Ok.
10月 23 09:19:05 XSign kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
10月 23 09:19:05 XSign kernel: Preemptible hierarchical RCU implementation.
10月 23 09:19:05 XSign kernel: RCU dyntick-idle grace-period acceleration is enabled.
10月 23 09:19:05 XSign kernel: Dump stacks of tasks blocking RCU-preempt GP.
10月 23 09:19:05 XSign kernel: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
10月 23 09:19:05 XSign kernel: NR_IRQS:2304 nr_irqs:712 16
10月 23 09:19:05 XSign kernel: CPU 0 irqstacks, hard=f4c08000 soft=f4c0a000
10月 23 09:19:05 XSign kernel: Console: colour VGA+ 80x25
10月 23 09:19:05 XSign kernel: console [tty0] enabled
10月 23 09:19:05 XSign kernel: hpet clockevent registered
10月 23 09:19:05 XSign kernel: tsc: Fast TSC calibration using PIT
10月 23 09:19:05 XSign kernel: tsc: Detected 3010.099 MHz processor
10月 23 09:19:05 XSign kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6022.03 BogoMIPS (lpj=10033663)
10月 23 09:19:05 XSign kernel: pid_max: default: 32768 minimum: 301
10月 23 09:19:05 XSign kernel: Security Framework initialized
10月 23 09:19:05 XSign kernel: AppArmor: AppArmor disabled by boot time parameter
10月 23 09:19:05 XSign kernel: Yama: becoming mindful.
10月 23 09:19:05 XSign kernel: Mount-cache hash table entries: 512
10月 23 09:19:05 XSign kernel: Initializing cgroup subsys memory
10月 23 09:19:05 XSign kernel: Initializing cgroup subsys devices
10月 23 09:19:05 XSign kernel: Initializing cgroup subsys freezer
10月 23 09:19:05 XSign kernel: Initializing cgroup subsys net_cls
10月 23 09:19:05 XSign kernel: Initializing cgroup subsys blkio
10月 23 09:19:05 XSign kernel: CPU: Physical Processor ID: 0
10月 23 09:19:05 XSign kernel: CPU: Processor Core ID: 0
10月 23 09:19:05 XSign kernel: mce: CPU supports 6 MCE banks
10月 23 09:19:05 XSign kernel: CPU0: Thermal monitoring enabled (TM2)
10月 23 09:19:05 XSign kernel: Last level iTLB entries: 4KB 128, 2MB 4, 4MB 4
Last level dTLB entries: 4KB 256, 2MB 0, 4MB 32
tlb_flushall_shift: -1
10月 23 09:19:05 XSign kernel: Freeing SMP alternatives memory: 20K (c0781000 - c0786000)
10月 23 09:19:05 XSign kernel: ACPI: Core revision 20130517
10月 23 09:19:05 XSign kernel: ACPI: All ACPI Tables successfully acquired
10月 23 09:19:05 XSign kernel: ftrace: allocating 19099 entries in 38 pages
10月 23 09:19:05 XSign kernel: Enabling APIC mode: Flat. Using 1 I/O APICs
10月 23 09:19:05 XSign kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
10月 23 09:19:05 XSign kernel: smpboot: CPU0: Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz (fam: 06, model: 0f, stepping: 0b)
10月 23 09:19:05 XSign kernel: APIC calibration not consistent with PM-Timer: 139ms instead of 100ms
10月 23 09:19:05 XSign kernel: APIC delta adjusted to PM-Timer: 2090297 (2926401)
10月 23 09:19:05 XSign kernel: Performance Events: PEBS fmt0+, 4-deep LBR, Core2 events, Intel PMU driver.
10月 23 09:19:05 XSign kernel: perf_event_intel: PEBS disabled due to CPU errata
10月 23 09:19:05 XSign kernel: ... version: 2
10月 23 09:19:05 XSign kernel: ... bit width: 40
10月 23 09:19:05 XSign kernel: ... generic registers: 2
10月 23 09:19:05 XSign kernel: ... value mask: 000000ffffffffff
10月 23 09:19:05 XSign kernel: ... max period: 000000007fffffff
10月 23 09:19:05 XSign kernel: ... fixed-purpose events: 3
10月 23 09:19:05 XSign kernel: ... event mask: 0000000700000003
10月 23 09:19:05 XSign kernel: CPU 1 irqstacks, hard=f4cce000 soft=f4cd8000
10月 23 09:19:05 XSign kernel: Initializing CPU#1
10月 23 09:19:05 XSign kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
10月 23 09:19:05 XSign kernel: smpboot: Booting Node 0, Processors #1
10月 23 09:19:05 XSign kernel: Brought up 2 CPUs
10月 23 09:19:05 XSign kernel: smpboot: Total of 2 processors activated (12045.07 BogoMIPS)
10月 23 09:19:05 XSign kernel: devtmpfs: initialized
10月 23 09:19:05 XSign kernel: PM: Registering ACPI NVS region [mem 0xdf69e000-0xdf6cffff] (204800 bytes)
10月 23 09:19:05 XSign kernel: RTC time: 9:19:01, date: 10/23/13
10月 23 09:19:05 XSign kernel: NET: Registered protocol family 16
10月 23 09:19:05 XSign kernel: ACPI: bus type PCI registered
10月 23 09:19:05 XSign kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
10月 23 09:19:05 XSign kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
10月 23 09:19:05 XSign kernel: PCI: not using MMCONFIG
10月 23 09:19:05 XSign kernel: PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=3
10月 23 09:19:05 XSign kernel: PCI: Using configuration type 1 for base access
10月 23 09:19:05 XSign kernel: bio: create slab <bio-0> at 0
10月 23 09:19:05 XSign kernel: ACPI: Added _OSI(Module Device)
10月 23 09:19:05 XSign kernel: ACPI: Added _OSI(Processor Device)
10月 23 09:19:05 XSign kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
10月 23 09:19:05 XSign kernel: ACPI: Added _OSI(Processor Aggregator Device)
10月 23 09:19:05 XSign kernel: ACPI: EC: Look up EC in DSDT
10月 23 09:19:05 XSign kernel: ACPI: Executed 1 blocks of module-level executable AML code
10月 23 09:19:05 XSign kernel: ACPI: SSDT df6a00f0 001D2 (v01 AMI CPU1PM 00000001 INTL 20060113)
10月 23 09:19:05 XSign kernel: ACPI: Dynamic OEM Table Load:
10月 23 09:19:05 XSign kernel: ACPI: SSDT (null) 001D2 (v01 AMI CPU1PM 00000001 INTL 20060113)
10月 23 09:19:05 XSign kernel: ACPI: SSDT df6a02d0 00143 (v01 AMI CPU2PM 00000001 INTL 20060113)
10月 23 09:19:05 XSign kernel: ACPI: Dynamic OEM Table Load:
10月 23 09:19:05 XSign kernel: ACPI: SSDT (null) 00143 (v01 AMI CPU2PM 00000001 INTL 20060113)
10月 23 09:19:05 XSign kernel: ACPI: Interpreter enabled
10月 23 09:19:05 XSign kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130517/hwxface-571)
10月 23 09:19:05 XSign kernel: ACPI: (supports S0 S1 S3 S4 S5)
10月 23 09:19:05 XSign kernel: ACPI: Using IOAPIC for interrupt routing
10月 23 09:19:05 XSign kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
10月 23 09:19:05 XSign kernel: PCI: MMCONFIG at [mem 0xf0000000-0xf3ffffff] reserved in ACPI motherboard resources
10月 23 09:19:05 XSign kernel: PCI: Using MMCONFIG for extended config space
10月 23 09:19:05 XSign kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
10月 23 09:19:05 XSign kernel: ACPI: No dock devices found.
10月 23 09:19:05 XSign kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
10月 23 09:19:05 XSign kernel: acpi PNP0A08:00: ACPI _OSC support notification failed, disabling PCIe ASPM
10月 23 09:19:05 XSign kernel: acpi PNP0A08:00: Unable to request _OSC control (_OSC support mask: 0x08)
10月 23 09:19:05 XSign kernel: acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
10月 23 09:19:05 XSign kernel: PCI host bridge to bus 0000:00
10月 23 09:19:05 XSign kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
10月 23 09:19:05 XSign kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
10月 23 09:19:05 XSign kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
10月 23 09:19:05 XSign kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
10月 23 09:19:05 XSign kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000dffff]
10月 23 09:19:05 XSign kernel: pci_bus 0000:00: root bus resource [mem 0xdf700000-0xffffffff]
10月 23 09:19:05 XSign kernel: pci 0000:00:00.0: [8086:29c0] type 00 class 0x060000
10月 23 09:19:05 XSign kernel: pci 0000:00:02.0: [8086:29c2] type 00 class 0x030000
10月 23 09:19:05 XSign kernel: pci 0000:00:02.0: reg 0x10: [mem 0xfea80000-0xfeafffff]
10月 23 09:19:05 XSign kernel: pci 0000:00:02.0: reg 0x14: [io 0xdc00-0xdc07]
10月 23 09:19:05 XSign kernel: pci 0000:00:02.0: reg 0x18: [mem 0xe0000000-0xefffffff pref]
10月 23 09:19:05 XSign kernel: pci 0000:00:02.0: reg 0x1c: [mem 0xfe900000-0xfe9fffff]
10月 23 09:19:05 XSign kernel: pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
10月 23 09:19:05 XSign kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xfea78000-0xfea7bfff 64bit]
10月 23 09:19:05 XSign kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: System wakeup disabled by ACPI
10月 23 09:19:05 XSign kernel: pci 0000:00:1d.0: [8086:27c8] type 00 class 0x0c0300
10月 23 09:19:05 XSign kernel: pci 0000:00:1d.0: reg 0x20: [io 0xd400-0xd41f]
10月 23 09:19:05 XSign kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
10月 23 09:19:05 XSign kernel: pci 0000:00:1d.1: [8086:27c9] type 00 class 0x0c0300
10月 23 09:19:05 XSign kernel: pci 0000:00:1d.1: reg 0x20: [io 0xd480-0xd49f]
10月 23 09:19:05 XSign kernel: pci 0000:00:1d.1: System wakeup disabled by ACPI
10月 23 09:19:05 XSign kernel: pci 0000:00:1d.2: [8086:27ca] type 00 class 0x0c0300
10月 23 09:19:05 XSign kernel: pci 0000:00:1d.2: reg 0x20: [io 0xd800-0xd81f]
10月 23 09:19:05 XSign kernel: pci 0000:00:1d.2: System wakeup disabled by ACPI
10月 23 09:19:05 XSign kernel: pci 0000:00:1d.3: [8086:27cb] type 00 class 0x0c0300
10月 23 09:19:05 XSign kernel: pci 0000:00:1d.3: reg 0x20: [io 0xd880-0xd89f]
10月 23 09:19:05 XSign kernel: pci 0000:00:1d.3: System wakeup disabled by ACPI
10月 23 09:19:05 XSign kernel: pci 0000:00:1d.7: [8086:27cc] type 00 class 0x0c0320
10月 23 09:19:05 XSign kernel: pci 0000:00:1d.7: reg 0x10: [mem 0xfea77c00-0xfea77fff]
10月 23 09:19:05 XSign kernel: pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
10月 23 09:19:05 XSign kernel: pci 0000:00:1d.7: System wakeup disabled by ACPI
10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: System wakeup disabled by ACPI
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.0: [8086:27b8] type 00 class 0x060100
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.0: address space collision: [io 0x0800-0x087f] conflicts with ACPI CPU throttle [??? 0x00000810-0x00000815 flags 0x80000000]
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.0: quirk: [io 0x0480-0x04bf] claimed by ICH6 GPIO
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0294 (mask 0003)
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.1: [8086:27df] type 00 class 0x01018a
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.1: reg 0x10: [io 0x0000-0x0007]
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.1: reg 0x14: [io 0x0000-0x0003]
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.1: reg 0x18: [io 0x08f0-0x08f7]
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.1: reg 0x1c: [io 0x08f8-0x08fb]
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.1: reg 0x20: [io 0xffa0-0xffaf]
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.2: [8086:27c0] type 00 class 0x01018f
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.2: reg 0x10: [io 0xd080-0xd087]
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.2: reg 0x14: [io 0xd000-0xd003]
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.2: reg 0x18: [io 0xcc00-0xcc07]
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xc880-0xc883]
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.2: reg 0x20: [io 0xc800-0xc80f]
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.2: PME# supported from D3hot
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.3: [8086:27da] type 00 class 0x0c0500
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.3: reg 0x20: [io 0x0400-0x041f]
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
10月 23 09:19:05 XSign kernel: pci 0000:01:00.0: [10ec:8136] type 00 class 0x020000
10月 23 09:19:05 XSign kernel: pci 0000:01:00.0: reg 0x10: [io 0xe800-0xe8ff]
10月 23 09:19:05 XSign kernel: pci 0000:01:00.0: reg 0x18: [mem 0xfdfff000-0xfdffffff 64bit pref]
10月 23 09:19:05 XSign kernel: pci 0000:01:00.0: reg 0x20: [mem 0xfdfe0000-0xfdfeffff 64bit pref]
10月 23 09:19:05 XSign kernel: pci 0000:01:00.0: reg 0x30: [mem 0xfebf0000-0xfebfffff pref]
10月 23 09:19:05 XSign kernel: pci 0000:01:00.0: supports D1 D2
10月 23 09:19:05 XSign kernel: pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: PCI bridge to [bus 01]
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: bridge window [io 0xe000-0xefff]
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: bridge window [mem 0xfeb00000-0xfebfffff]
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: bridge window [mem 0xfdf00000-0xfdffffff 64bit pref]
10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: PCI bridge to [bus 03] (subtractive decode)
10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: bridge window [mem 0x000d0000-0x000dffff] (subtractive decode)
10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: bridge window [mem 0xdf700000-0xffffffff] (subtractive decode)
10月 23 09:19:05 XSign kernel: pci_bus 0000:00: on NUMA node 0
10月 23 09:19:05 XSign kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
10月 23 09:19:05 XSign kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
10月 23 09:19:05 XSign kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 10 11 12 14 15)
10月 23 09:19:05 XSign kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 *7 10 11 12 14 15)
10月 23 09:19:05 XSign kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
10月 23 09:19:05 XSign kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
10月 23 09:19:05 XSign kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
10月 23 09:19:05 XSign kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 10 11 12 14 15)
10月 23 09:19:05 XSign kernel: ACPI: Enabled 2 GPEs in block 00 to 1F
10月 23 09:19:05 XSign kernel: ACPI: \_SB_.PCI0: notify handler is installed
10月 23 09:19:05 XSign kernel: Found 1 acpi root devices
10月 23 09:19:05 XSign kernel: vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
10月 23 09:19:05 XSign kernel: vgaarb: loaded
10月 23 09:19:05 XSign kernel: vgaarb: bridge control possible 0000:00:02.0
10月 23 09:19:05 XSign kernel: PCI: Using ACPI for IRQ routing
10月 23 09:19:05 XSign kernel: PCI: pci_cache_line_size set to 64 bytes
10月 23 09:19:05 XSign kernel: e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
10月 23 09:19:05 XSign kernel: e820: reserve RAM buffer [mem 0xdf690000-0xdfffffff]
10月 23 09:19:05 XSign kernel: NetLabel: Initializing
10月 23 09:19:05 XSign kernel: NetLabel: domain hash size = 128
10月 23 09:19:05 XSign kernel: NetLabel: protocols = UNLABELED CIPSOv4
10月 23 09:19:05 XSign kernel: NetLabel: unlabeled traffic allowed by default
10月 23 09:19:05 XSign kernel: HPET: 3 timers in total, 0 timers will be used for per-cpu timer
10月 23 09:19:05 XSign kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
10月 23 09:19:05 XSign kernel: hpet0: 3 comparators, 64-bit 14.318180 MHz counter
10月 23 09:19:05 XSign kernel: Switched to clocksource hpet
10月 23 09:19:05 XSign kernel: pnp: PnP ACPI init
10月 23 09:19:05 XSign kernel: ACPI: bus type PNP registered
10月 23 09:19:05 XSign kernel: system 00:00: [mem 0xfed14000-0xfed19fff] has been reserved
10月 23 09:19:05 XSign kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
10月 23 09:19:05 XSign kernel: pnp 00:01: [dma 4]
10月 23 09:19:05 XSign kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
10月 23 09:19:05 XSign kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
10月 23 09:19:05 XSign kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0800 (active)
10月 23 09:19:05 XSign kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0c04 (active)
10月 23 09:19:05 XSign kernel: system 00:05: [io 0x0290-0x0297] has been reserved
10月 23 09:19:05 XSign kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
10月 23 09:19:05 XSign kernel: system 00:06: [io 0x04d0-0x04d1] has been reserved
10月 23 09:19:05 XSign kernel: system 00:06: [io 0x0800-0x087f] could not be reserved
10月 23 09:19:05 XSign kernel: system 00:06: [io 0x0480-0x04bf] has been reserved
10月 23 09:19:05 XSign kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
10月 23 09:19:05 XSign kernel: system 00:06: [mem 0xfed20000-0xfed8ffff] has been reserved
10月 23 09:19:05 XSign kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
10月 23 09:19:05 XSign kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0103 (active)
10月 23 09:19:05 XSign kernel: pnp 00:08: Plug and Play ACPI device, IDs INT0800 (active)
10月 23 09:19:05 XSign kernel: system 00:09: [mem 0xffc00000-0xffefffff] has been reserved
10月 23 09:19:05 XSign kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
10月 23 09:19:05 XSign kernel: system 00:0a: [mem 0xfec00000-0xfec00fff] could not be reserved
10月 23 09:19:05 XSign kernel: system 00:0a: [mem 0xfee00000-0xfee00fff] has been reserved
10月 23 09:19:05 XSign kernel: system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active)
10月 23 09:19:05 XSign kernel: pnp 00:0b: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
10月 23 09:19:05 XSign kernel: pnp 00:0c: Plug and Play ACPI device, IDs PNP0f03 PNP0f13 (active)
10月 23 09:19:05 XSign kernel: pnp 00:0d: [dma 0 disabled]
10月 23 09:19:05 XSign kernel: pnp 00:0d: Plug and Play ACPI device, IDs PNP0501 (active)
10月 23 09:19:05 XSign kernel: system 00:0e: [mem 0xf0000000-0xf3ffffff] has been reserved
10月 23 09:19:05 XSign kernel: system 00:0e: Plug and Play ACPI device, IDs PNP0c02 (active)
10月 23 09:19:05 XSign kernel: system 00:0f: [mem 0x00000000-0x0009ffff] could not be reserved
10月 23 09:19:05 XSign kernel: system 00:0f: [mem 0x000c0000-0x000cffff] could not be reserved
10月 23 09:19:05 XSign kernel: system 00:0f: [mem 0x000e0000-0x000fffff] could not be reserved
10月 23 09:19:05 XSign kernel: system 00:0f: [mem 0x00100000-0xdf6fffff] could not be reserved
10月 23 09:19:05 XSign kernel: system 00:0f: Plug and Play ACPI device, IDs PNP0c01 (active)
10月 23 09:19:05 XSign kernel: pnp: PnP ACPI: found 16 devices
10月 23 09:19:05 XSign kernel: ACPI: bus type PNP unregistered
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 02] add_size 1000
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 02] add_size 200000
10月 23 09:19:05 XSign kernel: pci 0000:00:1f.0: BAR 13: [io 0x0800-0x087f] has bogus alignment
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 200000
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0xdf700000-0xdf8fffff]
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0xdf900000-0xdfafffff 64bit pref]
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: BAR 13: assigned [io 0x1000-0x1fff]
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: bridge window [io 0x1000-0x1fff]
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: bridge window [mem 0xdf700000-0xdf8fffff]
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: bridge window [mem 0xdf900000-0xdfafffff 64bit pref]
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: PCI bridge to [bus 01]
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: bridge window [io 0xe000-0xefff]
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: bridge window [mem 0xfeb00000-0xfebfffff]
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: bridge window [mem 0xfdf00000-0xfdffffff 64bit pref]
10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: PCI bridge to [bus 03]
10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: enabling device (0104 -> 0107)
10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: setting latency timer to 64
10月 23 09:19:05 XSign kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
10月 23 09:19:05 XSign kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
10月 23 09:19:05 XSign kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
10月 23 09:19:05 XSign kernel: pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000dffff]
10月 23 09:19:05 XSign kernel: pci_bus 0000:00: resource 8 [mem 0xdf700000-0xffffffff]
10月 23 09:19:05 XSign kernel: pci_bus 0000:02: resource 0 [io 0x1000-0x1fff]
10月 23 09:19:05 XSign kernel: pci_bus 0000:02: resource 1 [mem 0xdf700000-0xdf8fffff]
10月 23 09:19:05 XSign kernel: pci_bus 0000:02: resource 2 [mem 0xdf900000-0xdfafffff 64bit pref]
10月 23 09:19:05 XSign kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
10月 23 09:19:05 XSign kernel: pci_bus 0000:01: resource 1 [mem 0xfeb00000-0xfebfffff]
10月 23 09:19:05 XSign kernel: pci_bus 0000:01: resource 2 [mem 0xfdf00000-0xfdffffff 64bit pref]
10月 23 09:19:05 XSign kernel: pci_bus 0000:03: resource 4 [io 0x0000-0x0cf7]
10月 23 09:19:05 XSign kernel: pci_bus 0000:03: resource 5 [io 0x0d00-0xffff]
10月 23 09:19:05 XSign kernel: pci_bus 0000:03: resource 6 [mem 0x000a0000-0x000bffff]
10月 23 09:19:05 XSign kernel: pci_bus 0000:03: resource 7 [mem 0x000d0000-0x000dffff]
10月 23 09:19:05 XSign kernel: pci_bus 0000:03: resource 8 [mem 0xdf700000-0xffffffff]
10月 23 09:19:05 XSign kernel: NET: Registered protocol family 2
10月 23 09:19:05 XSign kernel: TCP established hash table entries: 8192 (order: 4, 65536 bytes)
10月 23 09:19:05 XSign kernel: TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
10月 23 09:19:05 XSign kernel: TCP: Hash tables configured (established 8192 bind 8192)
10月 23 09:19:05 XSign kernel: TCP: reno registered
10月 23 09:19:05 XSign kernel: UDP hash table entries: 512 (order: 2, 16384 bytes)
10月 23 09:19:05 XSign kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
10月 23 09:19:05 XSign kernel: NET: Registered protocol family 1
10月 23 09:19:05 XSign kernel: pci 0000:00:02.0: Boot video device
10月 23 09:19:05 XSign kernel: PCI: CLS 32 bytes, default 64
10月 23 09:19:05 XSign kernel: Unpacking initramfs...
10月 23 09:19:05 XSign kernel: Freeing initrd memory: 2624K (f756e000 - f77fe000)
10月 23 09:19:05 XSign kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
10月 23 09:19:05 XSign kernel: apm: disabled - APM is not SMP safe.
10月 23 09:19:05 XSign kernel: Scanning for low memory corruption every 60 seconds
10月 23 09:19:05 XSign kernel: audit: initializing netlink socket (disabled)
10月 23 09:19:05 XSign kernel: type=2000 audit(1382519941.199:1): initialized
10月 23 09:19:05 XSign kernel: bounce pool size: 64 pages
10月 23 09:19:05 XSign kernel: HugeTLB registered 4 MB page size, pre-allocated 0 pages
10月 23 09:19:05 XSign kernel: zbud: loaded
10月 23 09:19:05 XSign kernel: VFS: Disk quotas dquot_6.5.2
10月 23 09:19:05 XSign kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
10月 23 09:19:05 XSign kernel: msgmni has been set to 1688
10月 23 09:19:05 XSign kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
10月 23 09:19:05 XSign kernel: io scheduler noop registered
10月 23 09:19:05 XSign kernel: io scheduler deadline registered
10月 23 09:19:05 XSign kernel: io scheduler cfq registered (default)
10月 23 09:19:05 XSign kernel: pcieport 0000:00:1c.0: irq 40 for MSI/MSI-X
10月 23 09:19:05 XSign kernel: pcieport 0000:00:1c.1: irq 41 for MSI/MSI-X
10月 23 09:19:05 XSign kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
10月 23 09:19:05 XSign kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
10月 23 09:19:05 XSign kernel: intel_idle: does not run on family 6 model 15
10月 23 09:19:05 XSign kernel: GHES: HEST is not enabled!
10月 23 09:19:05 XSign kernel: isapnp: Scanning for PnP cards...
10月 23 09:19:05 XSign kernel: isapnp: No Plug & Play device found
10月 23 09:19:05 XSign kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
10月 23 09:19:05 XSign kernel: 00:0d: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
10月 23 09:19:05 XSign kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
10月 23 09:19:05 XSign kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
10月 23 09:19:05 XSign kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
10月 23 09:19:05 XSign kernel: mousedev: PS/2 mouse device common for all mice
10月 23 09:19:05 XSign kernel: rtc_cmos 00:02: RTC can wake from S4
10月 23 09:19:05 XSign kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
10月 23 09:19:05 XSign kernel: rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
10月 23 09:19:05 XSign kernel: cpuidle: using governor ladder
10月 23 09:19:05 XSign kernel: cpuidle: using governor menu
10月 23 09:19:05 XSign kernel: drop_monitor: Initializing network drop monitor service
10月 23 09:19:05 XSign kernel: TCP: cubic registered
10月 23 09:19:05 XSign kernel: NET: Registered protocol family 10
10月 23 09:19:05 XSign kernel: NET: Registered protocol family 17
10月 23 09:19:05 XSign kernel: Key type dns_resolver registered
10月 23 09:19:05 XSign kernel: Using IPI No-Shortcut mode
10月 23 09:19:05 XSign kernel: PM: Hibernation image not present or could not be loaded.
10月 23 09:19:05 XSign kernel: registered taskstats version 1
10月 23 09:19:05 XSign kernel: Magic number: 1:976:323
10月 23 09:19:05 XSign kernel: tty tty48: hash matches
10月 23 09:19:05 XSign kernel: rtc_cmos 00:02: setting system clock to 2013-10-23 09:19:02 UTC (1382519942)
10月 23 09:19:05 XSign kernel: Freeing unused kernel memory: 608K (c06e9000 - c0781000)
10月 23 09:19:05 XSign kernel: Write protecting the kernel text: 4264k
10月 23 09:19:05 XSign kernel: Write protecting the kernel read-only data: 1360k
10月 23 09:19:05 XSign systemd-udevd[47]: starting version 208
10月 23 09:19:05 XSign kernel: ACPI: bus type USB registered
10月 23 09:19:05 XSign kernel: usbcore: registered new interface driver usbfs
10月 23 09:19:05 XSign kernel: usbcore: registered new interface driver hub
10月 23 09:19:05 XSign kernel: usbcore: registered new device driver usb
10月 23 09:19:05 XSign kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
10月 23 09:19:05 XSign kernel: uhci_hcd: USB Universal Host Controller Interface driver
10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000d400
10月 23 09:19:05 XSign kernel: hub 1-0:1.0: USB hub found
10月 23 09:19:05 XSign kernel: hub 1-0:1.0: 2 ports detected
10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000d480
10月 23 09:19:05 XSign kernel: hub 2-0:1.0: USB hub found
10月 23 09:19:05 XSign kernel: hub 2-0:1.0: 2 ports detected
10月 23 09:19:05 XSign kernel: SCSI subsystem initialized
10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000d800
10月 23 09:19:05 XSign kernel: hub 3-0:1.0: USB hub found
10月 23 09:19:05 XSign kernel: hub 3-0:1.0: 2 ports detected
10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.3: setting latency timer to 64
10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.3: UHCI Host Controller
10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000d880
10月 23 09:19:05 XSign kernel: hub 4-0:1.0: USB hub found
10月 23 09:19:05 XSign kernel: hub 4-0:1.0: 2 ports detected
10月 23 09:19:05 XSign kernel: ehci-pci: EHCI PCI platform driver
10月 23 09:19:05 XSign kernel: ehci-pci 0000:00:1d.7: setting latency timer to 64
10月 23 09:19:05 XSign kernel: ehci-pci 0000:00:1d.7: EHCI Host Controller
10月 23 09:19:05 XSign kernel: ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 5
10月 23 09:19:05 XSign kernel: ehci-pci 0000:00:1d.7: debug port 1
10月 23 09:19:05 XSign kernel: ACPI: bus type ATA registered
10月 23 09:19:05 XSign kernel: ehci-pci 0000:00:1d.7: cache line size of 32 is not supported
10月 23 09:19:05 XSign kernel: ehci-pci 0000:00:1d.7: irq 23, io mem 0xfea77c00
10月 23 09:19:05 XSign kernel: libata version 3.00 loaded.
10月 23 09:19:05 XSign kernel: ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
10月 23 09:19:05 XSign kernel: hub 5-0:1.0: USB hub found
10月 23 09:19:05 XSign kernel: hub 5-0:1.0: 8 ports detected
10月 23 09:19:05 XSign kernel: hub 1-0:1.0: USB hub found
10月 23 09:19:05 XSign kernel: hub 1-0:1.0: 2 ports detected
10月 23 09:19:05 XSign kernel: hub 2-0:1.0: USB hub found
10月 23 09:19:05 XSign kernel: hub 2-0:1.0: 2 ports detected
10月 23 09:19:05 XSign kernel: hub 3-0:1.0: USB hub found
10月 23 09:19:05 XSign kernel: hub 3-0:1.0: 2 ports detected
10月 23 09:19:05 XSign kernel: hub 4-0:1.0: USB hub found
10月 23 09:19:05 XSign kernel: hub 4-0:1.0: 2 ports detected
10月 23 09:19:05 XSign kernel: ata_piix 0000:00:1f.1: version 2.13
10月 23 09:19:05 XSign kernel: ata_piix 0000:00:1f.1: setting latency timer to 64
10月 23 09:19:05 XSign kernel: scsi0 : ata_piix
10月 23 09:19:05 XSign kernel: scsi1 : ata_piix
10月 23 09:19:05 XSign kernel: ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
10月 23 09:19:05 XSign kernel: ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
10月 23 09:19:05 XSign kernel: ata_piix 0000:00:1f.2: MAP [
10月 23 09:19:05 XSign kernel: P0 P2 P1 P3 ]
10月 23 09:19:05 XSign kernel: ata_piix 0000:00:1f.2: setting latency timer to 64
10月 23 09:19:05 XSign kernel: scsi2 : ata_piix
10月 23 09:19:05 XSign kernel: scsi3 : ata_piix
10月 23 09:19:05 XSign kernel: ata3: SATA max UDMA/133 cmd 0xd080 ctl 0xd000 bmdma 0xc800 irq 19
10月 23 09:19:05 XSign kernel: ata4: SATA max UDMA/133 cmd 0xcc00 ctl 0xc880 bmdma 0xc808 irq 19
10月 23 09:19:05 XSign kernel: ata3.00: ATA-8: ST3500410AS, CC31, max UDMA/133
10月 23 09:19:05 XSign kernel: ata3.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
10月 23 09:19:05 XSign kernel: ata3.01: ATA-8: ST3500418AS, CC38, max UDMA/133
10月 23 09:19:05 XSign kernel: ata3.01: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
10月 23 09:19:05 XSign kernel: usb 5-2: new high-speed USB device number 2 using ehci-pci
10月 23 09:19:05 XSign kernel: ata3.00: configured for UDMA/133
10月 23 09:19:05 XSign kernel: ata3.01: configured for UDMA/133
10月 23 09:19:05 XSign kernel: scsi 2:0:0:0: Direct-Access ATA ST3500410AS CC31 PQ: 0 ANSI: 5
10月 23 09:19:05 XSign kernel: scsi 2:0:1:0: Direct-Access ATA ST3500418AS CC38 PQ: 0 ANSI: 5
10月 23 09:19:05 XSign kernel: sd 2:0:1:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
10月 23 09:19:05 XSign kernel: sd 2:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
10月 23 09:19:05 XSign kernel: sd 2:0:1:0: [sdb] Write Protect is off
10月 23 09:19:05 XSign kernel: sd 2:0:1:0: [sdb] Mode Sense: 00 3a 00 00
10月 23 09:19:05 XSign kernel: sd 2:0:0:0: [sda] Write Protect is off
10月 23 09:19:05 XSign kernel: sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
10月 23 09:19:05 XSign kernel: sd 2:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
10月 23 09:19:05 XSign kernel: sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
10月 23 09:19:05 XSign kernel: sdb: sdb1 sdb2 < sdb5 sdb6 sdb7 >
10月 23 09:19:05 XSign kernel: hidraw: raw HID events driver (C) Jiri Kosina
10月 23 09:19:05 XSign kernel: usbcore: registered new interface driver usbhid
10月 23 09:19:05 XSign kernel: usbhid: USB HID core driver
10月 23 09:19:05 XSign kernel: usb-storage 5-2:1.0: USB Mass Storage device detected
10月 23 09:19:05 XSign kernel: scsi4 : usb-storage 5-2:1.0
10月 23 09:19:05 XSign kernel: usbcore: registered new interface driver usb-storage
10月 23 09:19:05 XSign kernel: input: Smart KM Link as /devices/pci0000:00/0000:00:1d.7/usb5/5-2/5-2:1.1/input/input0
10月 23 09:19:05 XSign kernel: hid-generic 0003:0EA0:2211.0001: input,hidraw0: USB HID v1.00 Mouse [ Smart KM Link ] on usb-0000:00:1d.7-2/input1
10月 23 09:19:05 XSign kernel: input: Smart KM Link as /devices/pci0000:00/0000:00:1d.7/usb5/5-2/5-2:1.2/input/input1
10月 23 09:19:05 XSign kernel: hid-generic 0003:0EA0:2211.0002: input,hidraw1: USB HID v1.00 Keyboard [ Smart KM Link ] on usb-0000:00:1d.7-2/input2
10月 23 09:19:05 XSign kernel: sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
10月 23 09:19:05 XSign kernel: sd 2:0:1:0: [sdb] Attached SCSI disk
10月 23 09:19:05 XSign kernel: sd 2:0:0:0: [sda] Attached SCSI disk
10月 23 09:19:05 XSign kernel: usb 5-3: new high-speed USB device number 3 using ehci-pci
10月 23 09:19:05 XSign kernel: tsc: Refined TSC clocksource calibration: 3010.028 MHz
10月 23 09:19:05 XSign kernel: hub 5-3:1.0: USB hub found
10月 23 09:19:05 XSign kernel: hub 5-3:1.0: 2 ports detected
10月 23 09:19:05 XSign kernel: usb 5-3.1: new full-speed USB device number 4 using ehci-pci
10月 23 09:19:05 XSign kernel: input: Razer Razer Mamba as /devices/pci0000:00/0000:00:1d.7/usb5/5-3/5-3.1/5-3.1:1.0/input/input2
10月 23 09:19:05 XSign kernel: hid-generic 0003:1532:0024.0003: input,hidraw2: USB HID v1.11 Mouse [Razer Razer Mamba] on usb-0000:00:1d.7-3.1/input0
10月 23 09:19:05 XSign kernel: input: Razer Razer Mamba as /devices/pci0000:00/0000:00:1d.7/usb5/5-3/5-3.1/5-3.1:1.1/input/input3
10月 23 09:19:05 XSign kernel: hid-generic 0003:1532:0024.0004: input,hidraw3: USB HID v1.11 Keyboard [Razer Razer Mamba] on usb-0000:00:1d.7-3.1/input1
10月 23 09:19:05 XSign kernel: usb 5-3.2: new full-speed USB device number 5 using ehci-pci
10月 23 09:19:05 XSign kernel: input: Heng Yu Technology Poker Pro S as /devices/pci0000:00/0000:00:1d.7/usb5/5-3/5-3.2/5-3.2:1.0/input/input4
10月 23 09:19:05 XSign kernel: hid-generic 0003:0F39:0611.0005: input,hidraw4: USB HID v1.10 Keyboard [Heng Yu Technology Poker Pro S] on usb-0000:00:1d.7-3.2/input0
10月 23 09:19:05 XSign kernel: input: Heng Yu Technology Poker Pro S as /devices/pci0000:00/0000:00:1d.7/usb5/5-3/5-3.2/5-3.2:1.1/input/input5
10月 23 09:19:05 XSign kernel: hid-generic 0003:0F39:0611.0006: input,hidraw5: USB HID v1.10 Device [Heng Yu Technology Poker Pro S] on usb-0000:00:1d.7-3.2/input1
10月 23 09:19:05 XSign kernel: scsi 4:0:0:0: CD-ROM Smart KM Link 2.00 PQ: 0 ANSI: 0
10月 23 09:19:05 XSign kernel: sr0: scsi-1 drive
10月 23 09:19:05 XSign kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
10月 23 09:19:05 XSign kernel: sr 4:0:0:0: Attached scsi CD-ROM sr0
10月 23 09:19:05 XSign kernel: Switched to clocksource tsc
10月 23 09:19:05 XSign kernel: REISERFS (device sda2): found reiserfs format "3.6" with standard journal
10月 23 09:19:05 XSign kernel: REISERFS (device sda2): using ordered data mode
10月 23 09:19:05 XSign kernel: reiserfs: using flush barriers
10月 23 09:19:05 XSign kernel: REISERFS (device sda2): journal params: device sda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
10月 23 09:19:05 XSign kernel: REISERFS (device sda2): checking transaction log (sda2)
10月 23 09:19:05 XSign kernel: REISERFS (device sda2): Using r5 hash to sort names
10月 23 09:19:05 XSign systemd[1]: RTC configured in localtime, applying delta of 480 minutes to system time.
10月 23 09:19:05 XSign systemd[1]: systemd 208 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
10月 23 09:19:05 XSign systemd[1]: Set hostname to <XSign>.
10月 23 09:19:05 XSign systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
10月 23 09:19:05 XSign systemd[1]: Started Forward Password Requests to Wall Directory Watch.
10月 23 09:19:05 XSign systemd[1]: Starting Syslog Socket.
10月 23 09:19:05 XSign systemd[1]: Listening on Syslog Socket.
10月 23 09:19:05 XSign systemd[1]: Starting Remote File Systems.
10月 23 09:19:05 XSign systemd[1]: Reached target Remote File Systems.
10月 23 09:19:05 XSign systemd[1]: Starting Device-mapper event daemon FIFOs.
10月 23 09:19:05 XSign systemd[1]: Listening on Device-mapper event daemon FIFOs.
10月 23 09:19:05 XSign systemd[1]: Starting Delayed Shutdown Socket.
10月 23 09:19:05 XSign systemd[1]: Listening on Delayed Shutdown Socket.
10月 23 09:19:05 XSign systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
10月 23 09:19:05 XSign systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
10月 23 09:19:05 XSign systemd[1]: Starting LVM2 metadata daemon socket.
10月 23 09:19:05 XSign systemd[1]: Listening on LVM2 metadata daemon socket.
10月 23 09:19:05 XSign systemd[1]: Starting Encrypted Volumes.
10月 23 09:19:05 XSign systemd[1]: Reached target Encrypted Volumes.
10月 23 09:19:05 XSign systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
10月 23 09:19:05 XSign systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
10月 23 09:19:05 XSign systemd[1]: Starting Paths.
10月 23 09:19:05 XSign systemd[1]: Reached target Paths.
10月 23 09:19:05 XSign systemd[1]: Starting udev Kernel Socket.
10月 23 09:19:05 XSign systemd[1]: Listening on udev Kernel Socket.
10月 23 09:19:05 XSign systemd[1]: Starting udev Control Socket.
10月 23 09:19:05 XSign systemd[1]: Listening on udev Control Socket.
10月 23 09:19:05 XSign systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
10月 23 09:19:05 XSign systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
10月 23 09:19:05 XSign systemd[1]: Starting Journal Socket.
10月 23 09:19:05 XSign systemd[1]: Listening on Journal Socket.
10月 23 09:19:05 XSign systemd[1]: Starting Apply Kernel Variables...
10月 23 09:19:05 XSign systemd[1]: Mounting POSIX Message Queue File System...
10月 23 09:19:05 XSign systemd[1]: Starting Create list of required static device nodes for the current kernel...
10月 23 09:19:05 XSign systemd[1]: Starting udev Coldplug all Devices...
10月 23 09:19:05 XSign systemd[1]: Mounting Debug File System...
10月 23 09:19:05 XSign systemd[1]: Mounting Huge Pages File System...
10月 23 09:19:05 XSign systemd[1]: Starting Journal Service...
10月 23 09:19:05 XSign systemd[1]: Started Journal Service.
10月 23 09:19:05 XSign kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
10月 23 09:19:05 XSign kernel: r8169 0000:01:00.0: can't disable ASPM; OS doesn't have ASPM control
10月 23 09:19:05 XSign kernel: r8169 0000:01:00.0: irq 42 for MSI/MSI-X
10月 23 09:19:05 XSign kernel: r8169 0000:01:00.0 eth0: RTL8102e at 0xf8804000, 00:23:54:dd:9d:c4, XID 04a00000 IRQ 42
10月 23 09:19:05 XSign systemd-journal[105]: Journal started
10月 23 09:19:05 XSign systemd[1]: Starting Set Up Additional Binary Formats...
10月 23 09:19:05 XSign systemd[1]: Starting Load Kernel Modules...
10月 23 09:19:05 XSign systemd[1]: Starting Setup Virtual Console...
10月 23 09:19:05 XSign systemd[1]: Expecting device dev-disk-by\x2duuid-b9fe1d55\x2db46c\x2d45a1\x2da068\x2d9e754189e7f3.device...
10月 23 09:19:05 XSign systemd[1]: Starting File System Check on Root Device...
10月 23 09:19:05 XSign systemd[1]: Expecting device dev-disk-by\x2duuid-20723153\x2dd5da\x2d4091\x2d807d\x2d6a8d945f9b22.device...
10月 23 09:19:05 XSign systemd[1]: Expecting device dev-disk-by\x2duuid-61e54abe\x2d34cd\x2d4bd0\x2db225\x2dd187ac5137f2.device...
10月 23 09:19:05 XSign systemd[1]: Expecting device dev-disk-by\x2duuid-7f64c378\x2d6403\x2d4786\x2daec0\x2d1c6e42532175.device...
10月 23 09:19:05 XSign systemd[1]: Expecting device dev-disk-by\x2duuid-86b99089\x2d3393\x2d4c20\x2dbce8\x2d0018e6cf5c85.device...
10月 23 09:19:05 XSign systemd[1]: Expecting device dev-sdb1.device...
10月 23 09:19:05 XSign systemd[1]: Expecting device dev-sdb5.device...
10月 23 09:19:05 XSign systemd[1]: Expecting device dev-sdb6.device...
10月 23 09:19:05 XSign systemd-modules-load[108]: Inserted module 'r8169'
10月 23 09:19:05 XSign systemd[1]: Starting Root Slice.
10月 23 09:19:05 XSign systemd[1]: Created slice Root Slice.
10月 23 09:19:05 XSign systemd[1]: Starting User and Session Slice.
10月 23 09:19:05 XSign systemd[1]: Created slice User and Session Slice.
10月 23 09:19:05 XSign systemd[1]: Starting System Slice.
10月 23 09:19:05 XSign systemd[1]: Created slice System Slice.
10月 23 09:19:05 XSign systemd[1]: Starting system-getty.slice.
10月 23 09:19:05 XSign systemd[1]: Created slice system-getty.slice.
10月 23 09:19:05 XSign systemd[1]: Starting Slices.
10月 23 09:19:05 XSign systemd[1]: Reached target Slices.
10月 23 09:19:05 XSign systemd[1]: Expecting device dev-sdb7.device...
10月 23 09:19:05 XSign systemd[1]: Started Apply Kernel Variables.
10月 23 09:19:05 XSign systemd[1]: Mounted POSIX Message Queue File System.
10月 23 09:19:05 XSign systemd[1]: Mounted Debug File System.
10月 23 09:19:05 XSign systemd[1]: Mounted Huge Pages File System.
10月 23 09:19:05 XSign systemd[1]: Started Setup Virtual Console.
10月 23 09:19:05 XSign systemd[1]: Started File System Check on Root Device.
10月 23 09:19:05 XSign systemd[1]: Starting Remount Root and Kernel File Systems...
10月 23 09:19:05 XSign systemd[1]: Mounting Arbitrary Executable File Formats File System...
10月 23 09:19:05 XSign systemd-fsck[110]: Reiserfs super block in block 16 on 0x802 of format 3.6 with standard journal
10月 23 09:19:05 XSign systemd-fsck[110]: Blocks (total/free): 12500576/9229679 by 4096 bytes
10月 23 09:19:05 XSign systemd-fsck[110]: Filesystem is clean
10月 23 09:19:05 XSign kernel: vboxdrv: Found 2 processor cores.
10月 23 09:19:05 XSign systemd-modules-load[108]: Inserted module 'vboxdrv'
10月 23 09:19:05 XSign kernel: vboxdrv: fAsync=0 offMin=0x1c2 offMax=0xd5c
10月 23 09:19:05 XSign kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
10月 23 09:19:05 XSign kernel: vboxdrv: Successfully loaded version 4.3.0_OSE (interface 0x001a0005).
10月 23 09:19:05 XSign systemd-modules-load[108]: Inserted module 'vboxnetflt'
10月 23 09:19:05 XSign systemd-modules-load[108]: Inserted module 'vboxnetadp'
10月 23 09:19:05 XSign systemd[1]: Started Load Kernel Modules.
10月 23 09:19:05 XSign systemd[1]: Started udev Coldplug all Devices.
10月 23 09:19:05 XSign systemd[1]: Mounting Configuration File System...
10月 23 09:19:05 XSign systemd[1]: Mounted FUSE Control File System.
10月 23 09:19:05 XSign systemd[1]: Mounted Arbitrary Executable File Formats File System.
10月 23 09:19:05 XSign systemd[1]: Mounted Configuration File System.
10月 23 09:19:05 XSign systemd[1]: Started Set Up Additional Binary Formats.
10月 23 09:19:06 XSign systemd[1]: Started Create list of required static device nodes for the current kernel.
10月 23 09:19:06 XSign systemd[1]: Starting Create static device nodes in /dev...
10月 23 09:19:06 XSign kernel: reiserfs: enabling write barrier flush mode
10月 23 09:19:06 XSign systemd[1]: Started Create static device nodes in /dev.
10月 23 09:19:06 XSign systemd[1]: Starting udev Kernel Device Manager...
10月 23 09:19:06 XSign systemd[1]: Started udev Kernel Device Manager.
10月 23 09:19:06 XSign systemd-udevd[137]: starting version 208
10月 23 09:19:06 XSign systemd[1]: Started Remount Root and Kernel File Systems.
10月 23 09:19:06 XSign systemd[1]: Starting Local File Systems (Pre).
10月 23 09:19:06 XSign systemd[1]: Reached target Local File Systems (Pre).
10月 23 09:19:06 XSign kernel: ACPI: Requesting acpi_cpufreq
10月 23 09:19:06 XSign kernel: Linux agpgart interface v0.103
10月 23 09:19:06 XSign kernel: [drm] Initialized drm 1.1.0 20060810
10月 23 09:19:06 XSign kernel: agpgart-intel 0000:00:00.0: Intel G33 Chipset
10月 23 09:19:06 XSign kernel: agpgart-intel 0000:00:00.0: detected gtt size: 524288K total, 262144K mappable
10月 23 09:19:06 XSign kernel: agpgart-intel 0000:00:00.0: detected 8192K stolen memory
10月 23 09:19:06 XSign kernel: agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
10月 23 09:19:06 XSign kernel: input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input6
10月 23 09:19:06 XSign kernel: ACPI: Power Button [PWRB]
10月 23 09:19:06 XSign kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input7
10月 23 09:19:06 XSign kernel: ACPI: Power Button [PWRF]
10月 23 09:19:06 XSign kernel: [drm] Memory usable by graphics device = 512M
10月 23 09:19:06 XSign kernel: i915 0000:00:02.0: setting latency timer to 64
10月 23 09:19:06 XSign kernel: i915 0000:00:02.0: irq 43 for MSI/MSI-X
10月 23 09:19:06 XSign kernel: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
10月 23 09:19:06 XSign kernel: [drm] Driver supports precise vblank timestamp query.
10月 23 09:19:06 XSign kernel: vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
10月 23 09:19:06 XSign kernel: [drm] initialized overlay support
10月 23 09:19:06 XSign kernel: intel_rng: FWH not detected
10月 23 09:19:06 XSign kernel: fbcon: inteldrmfb (fb0) is primary device
10月 23 09:19:06 XSign kernel: Console: switching to colour frame buffer device 240x67
10月 23 09:19:06 XSign kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
10月 23 09:19:06 XSign kernel: i915 0000:00:02.0: registered panic notifier
10月 23 09:19:06 XSign kernel: i915: No ACPI video bus found
10月 23 09:19:06 XSign kernel: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
10月 23 09:19:06 XSign kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
10月 23 09:19:06 XSign kernel: input: PC Speaker as /devices/platform/pcspkr/input/input8
10月 23 09:19:06 XSign kernel: snd_hda_intel 0000:00:1b.0: irq 44 for MSI/MSI-X
10月 23 09:19:07 XSign kernel: leds_ss4200: no LED devices found
10月 23 09:19:07 XSign kernel: microcode: CPU0 sig=0x6fb, pf=0x1, revision=0xb6
10月 23 09:19:07 XSign kernel: iTCO_vendor_support: vendor-support=0
10月 23 09:19:07 XSign kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
10月 23 09:19:07 XSign kernel: iTCO_wdt: Found a ICH7 or ICH7R TCO device (Version=2, TCOBASE=0x0860)
10月 23 09:19:07 XSign kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
10月 23 09:19:07 XSign kernel: input: HDA Intel Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
10月 23 09:19:07 XSign kernel: input: HDA Intel Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
10月 23 09:19:07 XSign kernel: input: HDA Intel Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
10月 23 09:19:07 XSign kernel: input: HDA Intel Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
10月 23 09:19:07 XSign kernel: input: HDA Intel Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
10月 23 09:19:07 XSign kernel: i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt
10月 23 09:19:07 XSign systemd[1]: Starting Sound Card.
10月 23 09:19:07 XSign systemd[1]: Reached target Sound Card.
10月 23 09:19:07 XSign kernel: microcode: CPU1 sig=0x6fb, pf=0x1, revision=0xb6
10月 23 09:19:07 XSign kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
10月 23 09:19:07 XSign kernel: gpio_ich: GPIO from 206 to 255 on gpio_ich
10月 23 09:19:07 XSign kernel: coretemp coretemp.0: Using relative temperature scale!
10月 23 09:19:07 XSign kernel: coretemp coretemp.0: Using relative temperature scale!
10月 23 09:19:08 XSign systemd[1]: Found device ST3500418AS.
10月 23 09:19:08 XSign systemd[1]: Starting File System Check on /dev/sdb5...
10月 23 09:19:08 XSign systemd[1]: Found device ST3500410AS.
10月 23 09:19:08 XSign systemd[1]: Starting File System Check on /dev/disk/by-uuid/86b99089-3393-4c20-bce8-0018e6cf5c85...
10月 23 09:19:08 XSign systemd-fsck[211]: fsck: fsck.ntfs-3g: not found
10月 23 09:19:08 XSign systemd-fsck[211]: fsck: error 2 while executing fsck.ntfs-3g for /dev/sdb5
10月 23 09:19:08 XSign systemd-fsck[211]: fsck failed with error code 8.
10月 23 09:19:08 XSign systemd-fsck[211]: Ignoring error.
10月 23 09:19:08 XSign systemd[1]: Started File System Check on /dev/sdb5.
10月 23 09:19:08 XSign systemd[1]: Mounting /mnt/sdb5...
10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
10月 23 09:19:08 XSign kernel: Result: hostbyte=0x00 driverbyte=0x08
10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
10月 23 09:19:08 XSign kernel: Sense Key : 0x5 [current]
10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
10月 23 09:19:08 XSign kernel: ASC=0x21 ASCQ=0x0
10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0] CDB:
10月 23 09:19:08 XSign kernel: cdb[0]=0x28: 28 00 00 00 04 00 00 00 02 00
10月 23 09:19:08 XSign kernel: end_request: critical target error, dev sr0, sector 4096
10月 23 09:19:08 XSign kernel: Buffer I/O error on device sr0, logical block 512
10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
10月 23 09:19:08 XSign kernel: Result: hostbyte=0x00 driverbyte=0x08
10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
10月 23 09:19:08 XSign kernel: Sense Key : 0x5 [current]
10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
10月 23 09:19:08 XSign kernel: ASC=0x21 ASCQ=0x0
10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0] CDB:
10月 23 09:19:08 XSign kernel: cdb[0]=0x28: 28 00 00 00 04 00 00 00 02 00
10月 23 09:19:08 XSign kernel: end_request: critical target error, dev sr0, sector 4096
10月 23 09:19:08 XSign kernel: Buffer I/O error on device sr0, logical block 512
10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
10月 23 09:19:08 XSign kernel: Result: hostbyte=0x00 driverbyte=0x08
10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
10月 23 09:19:08 XSign kernel: Sense Key : 0x5 [current]
10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
10月 23 09:19:08 XSign kernel: ASC=0x21 ASCQ=0x0
10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0] CDB:
10月 23 09:19:08 XSign kernel: cdb[0]=0x28: 28 00 00 00 04 00 00 00 02 00
10月 23 09:19:08 XSign kernel: end_request: critical target error, dev sr0, sector 4096
10月 23 09:19:08 XSign kernel: Buffer I/O error on device sr0, logical block 512
10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
10月 23 09:19:08 XSign kernel: Result: hostbyte=0x00 driverbyte=0x08
10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
10月 23 09:19:08 XSign kernel: Sense Key : 0x5 [current]
10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
10月 23 09:19:08 XSign kernel: ASC=0x21 ASCQ=0x0
10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0] CDB:
10月 23 09:19:08 XSign kernel: cdb[0]=0x28: 28 00 00 00 04 00 00 00 02 00
10月 23 09:19:08 XSign kernel: end_request: critical target error, dev sr0, sector 4096
10月 23 09:19:08 XSign kernel: Buffer I/O error on device sr0, logical block 512
10月 23 09:19:08 XSign systemd-fsck[214]: Reiserfs super block in block 16 on 0x803 of format 3.6 with standard journal
10月 23 09: -
Support for operating system to load blackberry 8900
support for operating system to load blackberry 8900 javelin completely blank blank with no operating system and tries to desktop manager and nothing it can not reach by connecting with jvm and stops saying conmpletar could not load due to a connection of several steps someone could help me
Solved!
Go to Solution.claudia_0080 wrote:
does not work
But it does.
Your three word response lacks any clue to any error or issue you encounted, let along a civil thank you.
We're willing to help, but you need to cooperate.
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code -
How can i solve "could not load language and text preference "
how can i solve " could not load language and text preference ".. help everyone...
Please read this whole message before doing anything.
This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
Step 1
The purpose of this step is to determine whether the problem is localized to your user account.
Enable guest logins* and log in as Guest. For instructions, launch the System Preferences application, select Help from the menu bar, and enter “Set up guest users” (without the quotes) in the search box. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
Test while logged in as Guest. Same problem?
After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.
Step 2
The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:
Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
When you see the gray Apple logo, release the shift key.
If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs. The next normal boot may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
*Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode.
Test while in safe mode. Same problem?
After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of steps 1 and 2. -
during a update of apple my iphone 3GS crashed an now the operating system wont load up..ive tried to reset the phone to the factory settings using itunes it took 4 hours and completed but my phone still wont come on..what can i do to fix the problem? please help #
In trying to include what information all that I could I should have specified I DON'T KNOW THAT IT WAS DEFINATELY JAILBROKEN when I took it to the apple store they told me there's no way for them to tell if it was jail broken or not. I'm only going by what ppl have told me COULD HAVE BEEN DONE TO THE PHONE. With that said the only thing I know for sure is that the apple tech at the Genius Bar told me that someone took control of my root menu in February & I've had no control of my phone since. I asked him how to regain control & how he knew his exact words were "oh that is out of our scope of capabilities here at this level & you would need an apple engineer to fix it". I said ok then how do I get an apple eng then? He laughed & said you can't!!!! To which I was furious I came home & called apple requesting to speak w/the fraud dept to file a report they said we don't have a fraud dept!! So after a 45 mn phone call again I left w/no answers.
@TJBUSMC1973-
I DON'T HAVE THOUSANDS OF DOLLARS TO SPEND HIRING AN ATTORNEY & Although I appreciate your suggestion I fail to how an attorney would be able to facilitate in any way since there's no suspect. I cannot prove that it's him doing it so I certainly can't pursue legal action w/no proof & no money. :'((
Again I thank you for your advice but I don't think that will help.
I was looking more for a TECHNICAL way to avoid this happening w/a new phone should I buy one or trying to get them out of my phone now! Such as installing some kind of software protection?? Someway to clear out the entire phone (other than factory reset which was done 10 x's w/no success, etc. if this person got in then there HAS TO BE A WAY OF GETTING HIM OUT, right???? -
Trouble in a SAP system with load balancing
Hello masters:
I had a trouble with workitems that came from a SAP system with load balancing. They doesn't receive the workitem ID in the UWL.
I created another system in the portal as a "dedicated application server", and made the necessary configuration in order to replace the first one, and then my workitems worked fine.
However, I would like to know what appened with the first system created as "system with load balancing". Why this system didn´t pass the workitem ID to the application (web dynpro abap) that execute the workitems?
Thank you.I hope there was some missing configuration in the first case which was not replicating the workitem from SAP Inbox to UWL.
Thanks
Arghadip -
System with load balancing server
Hi All,
We are having SAP NW 7.0 Portal and back end we have R3 implemented in a cluster environment. The system object in EP have used "System with Load balancing" template; using the LOGON group and the other related parameters.
But we have some problem with the ITS and WAS parameters; since we are using some Transaction iViews.
Let me explain.. for the R3 cluster we have 2 systems PROD1.domain.ext and PROD2.domain.ext. Now in the system object in portal, how to specify the parameters for ITS and WAS parameters? Since the host name in these we need to specify a single server which defeats the basic purpose of having clustered environment.
Can any one please help in resolving this issue.
Thanks,
SravanthiHi Sravanthi,
Please check the below for finding ITS and WAS parameters from backend :
For ITS - Go to SE37 >> Utilities >> Setting >> Click on ICON Right Top Corner in popup window >> Select Internet Transaction Server >> you will find the Standard Path and HTTP URL.
For WAS - Go to SE37 >> Run FM - RSBB_URL_PREFIX_GET >> Execute it >> you will find PRefix and PAth paramter for WAS.
Please refer to this may help step-by-step : How-to create a portal system for using it in Visual Composer
Hope it helps
Regards
Arun -
Nintendo WII uses OPERA Browsers. The WII system should load the best opera browser. The problem is
Nintendo WII uses OPERA Browsers. The WII system should load the best opera browser. The problem is that it does not load flash player 8. [email protected] 619-366-9707
That's probably more a problem to ask Nintendo or Opera Software?
Mylenium -
System class loader vs application class loader
Hello
I have a class that uses a third partyjar which I have put in /jre/lit/ext. The class compiles but fails at runtime being unable to read the property files called in the class' constructor. I believe that is b/c the third party jars are loading w/ the system class loader and cannot "see" the property files "floating" at the same level as the class that is calling them.
So I created a jar, of the property files, with the same directory/package structure as the location of the property files and put that in the /jre/lib/ext and STILL the same problem; cannot read the property files, the constructor fails, fugly. There is an overloaded constructor that includes a parameter for the property files, but I need to get this to work as is first. What am I missing? Please edify me. tia.If the 3rd party jar needs a certain properties file to initialize correctly, I doubt it would be looking for it in the class hierarchy. I mean I doubt it does:
Properties p = new Properties();
p.load( getClass().getResourceAsStream() );It's more likely to do:
Properties p = new Properties();
p.load( new FileInputStream(...) );The reason is that the property file should be easily edited by the user and users know how to move around in the file system, not in the Java jars and classpaths.
Just a guess... -
How to configure R/3 System with Load Balancing?
Hello,
I've created a Web DynPro Application and I would like to case an iView on it. According to SAP tutorials I first need to configure an R/3 System with Load Balancing.
My problem is how to configure the "WAS Host Name".
According to the tutorial:
WAS Host Name = <host>.<domain>:port (this corresponds to the Web Dynpro server location and the port on which it is running eg. PXYZ.wdf.sap.corp:50000.)
I am using NW 04 and my portal is running on this address:
http://ep6sp9test:50000/irj/portal
When I set the WAS Host Name to ep6sp9test:50000 the Test connection fails (I have privildges and created an alias and User mapping). What should I put at this field then?Hi
I think you have to specify the HTTP port og the WAS running the R/3 system. The 50000 port is the HTTP port of your portal - not the R/3 system. You can see the HTTP port of the R/3 system using transactioncode SMICM - services in the R/3 system.
BR
Tom -
TA24260 My XP PC system stopped loading the iStore. I just get the store header screen with bl
My XP PC system stopped loading the iStore. I just get the store header screen with blank screen. The firewall settings are correct. I can access the store on the iPad. Any ideas? Thanks, Miki
Attached is Dennis Linam’s Audition – “Log File” and “Log – Last File”
Contact information Dennis [email protected]
Previous contact information with your organization (DURIM):
Dennis - i just finished my audition trial and bought the subscription the 2014 version.
created by durin in Audition CS5.5, CS6 & CC - View the full discussion
DURIM - Okay. I would expect the "Cache Warning" message because your default directories would not be the same as the ones in the settings file I generated.
If you go back to the "7.0" directory and open the "Logs" folder, can you copy the "Audition Log.txt" file and send it as an attachment to [email protected]? We'll take a look in that logfile and see if it gives us more information about why this is failing now.
Also, do you have any other Adobe applications installed on this machine, such as Premiere Pro? If so, do they launch as expected or fail as well?
I do have the trial Pro version of Adobe reader, but I have not activated it, because I fear the same thing will happen did it. I cannot afford to activate the subscription for that product and take the chance of it not working either. I depend on those two programs religiously. Here is the files that you requested. I appreciate any help you can give me to get this audition program started
Audition Log- file
Ticks = 16 C:\Program Files (x86)\Common Files\Adobe\dynamiclink\7.0\dynamiclinkmanager.exe
Sent from Windows Mail
Maybe you are looking for
-
Single Sign-On Netweaver Portal with Cornerstone On Demand
Hi Does someone experiences with Single Sign-On between SAP Netweaver Portal and the Learning Management System of Cornerstone On Demand? The options are: - SAML: but at this moment we don't have SAML provider. Is it easy to use this with Netweaver 7
-
Not Able to get to the values from applet while designing from xml
Hi All, I have a new problem, and i am new to this one. Like I have an XML file.Where in i am able to design the applet while getting the values from the xml and i am able to store also. But the problem comes over here.I have given out a type field i
-
Set "Payment Consolidation" for BP after we have added invoices for that BP
Dear Experts, Currently, I have 3 BPs; bp01. bp02, bp03. bp01 is the payment consolidation parent for bp02 and bp03, so I have also setup as accordingly in bp02 and bp03 to point to bp01. However, my problem was... before I set the setting above, I h
-
Carousel component, need help!?
Hi! I created master/detail form in JDeveloper! Where Carousel is detail form. I added bean to Carousel component: public class Carousel { public Carousel() { * Gets new carusel item and set current row of iterator. * @param event p
-
J2me cldc midlet for windows mobile(cdc) in netbeans
Hi, I have a midlet developed in Mobility Pack 5.0, and I have to change it so, that it works, and looks ok on Windows Mobile. That means that I have to port a cldc midlet to a cdc device. I've found two vm-s for windows mobile, for running midlets.