Deployment hangs after boot

Hello Forum, I've run into a weird issue. Only one of my images will not deploy. It doesn't boot to the PXE environment, it hangs at the windows screen(see screenshot). I figured, maybe it's a driver thing, so I went to the manufacturer's site and grabbed
the latest drivers as well as the Winpe drivers, still no go. Next, I deleted the deployment's boot folder contents and completely regenerated the boot files, still no go. I've also, rebuilt the wim file from scratch, still at a dead end. I'm totally baffled
because only one of our models has this problem.
version: MDT 2012 6.1.2373.0
Hosted on Windows Server 2008 R2 VM
WDS: NO
Since it's not booting to the PXE environment, it's not generating any logs files. Please Help
IT Support " Scripting Noob "

Sorry for the wait guys, I'm totally stuck now. Ok, here we go.
1.) I moved the OS to a test deployment share, it booted to PE but failed due to no network driver. I added the drivers and tried again, it went back to hanging at boot. So, I removed ALL the drivers,
verified the Out-Of-Box drivers folder was empty, and completely regenerated the boot files, it still hangs at boot.
2.) I thought the deployment share was caching the MAC or something so checked the deployment folder in the %temp% directory, it was empty.
IT Support " Scripting Noob "

Similar Messages

[SOLVED]Hanging after booting from installation media

Yesterday I booted from a rw-DVD got to the terminal and could execute commands, connect to the internet and use elink etc no problem. I didn't go through with installation as I wanted to read up more on partitioning my drives for dual booting before actually doing so.
Trying the same thing today, and it hangs soon after I boot, regardless of whether I do anything. Printing the following:
nouveau E[ DRM] failed to idle channel 0xcccc0000 [DRM]
pci_pm_runtime_suspend(): nouveau_pmops_runtime_suspend+0x0/0xf0 [nouveau] returns -16
INFO: rcu_preempt detected stalls on CPUs/tasks: { 6} (detected by 1, t=18002 jiffiess, g=974, c=973, q=604)
This is without me typing anything. If I try to execute a command quickly after booting it sometimes works, but after a couple of minutes it will complain of a soft lockup.
I've tried burning another disk, and using a USB installation media, but the same thing happens. Any thoughts?
Edit: Trying to run it on a laptop with i7-4700MQ, 16GB ram, and Intel(R) HD Graphics 4600 / NVIDIA GeForce GTX 770M
Second Edit: Booted with nomodeset, which worked and allowed me to install. Just trying to sort out the sodding boot loaders now...
Last edited by glfharris (2014-07-11 22:42:31)

Welcome to the forum.
First of all, you should get in the habit of using [ code ] tags when posting code, not [ quote ] tags (well, unless you want to apply some styling to it, like bold, italic, etc).
This is wrong:
# umount /dev/sdc
This is correct:
# umount /dev/sdc1
You were trying to unmount the drive as a whole, which obviously isn't mounted, instead of the first (and probably only) partition. Had you followed the advice from the note to use blkid and check if it's mounted, this wouldn't have happened. But the fact that a DVD produced that error puzzles me... I have no experience with UEFI, but I think you need to press F10, F11, or something like that, to able able to get to a UEFI boot menu, and choose the optical unit as source.
I hope you used a BitTorrent client when downloading the ISO, and not some direct link (which are prone to CRC errors). If you used a direct link, then check the MD5 and make sure that it matches the one from the Download page. For future reference, torrents are checked while they're being downloaded.

8900 Smartphone getting hang after boot

I had problem with the 8900 Smartphone, All Contacts, Call logs used to get erase after i boot up the bb after removing the battery. so I upgraded the bb with 8900jEastAsia_PBr5.0.0_rel1168_PL5.2.0.67_A5.0.0.681_Redington__India__Limited. But after installing this version my bb takes long time to boot and get hang on white screen with BB logo. I'm trying to downgrade the version but not able to do so.. Please advise soon.

In that case, have you try updating the latest BIOS, chipset driver, USB driver(if any) from your mainboard website.
Jason

Deployment hangs after importing metadata OWB 10gR2

Hi folks,
in development I created a new mapping with I exported/imported into test enviroment.
I did this using "import all objects, update metadata, match by UID".
When I try to deploy the imported mapping ControlCenter hangs showing the green arrow.
In the DOS box where I started the client it says:
</OBJECT>
</OBJECT>
</OBJECT>
</NAMESPACE>
RUNTIME_SERVICES_DEBUG [WhValidationGenerationTransaction] DeploymentUtils.isAda
pterFCO(WBGeneratedObject): Not found objectTypeName CMPMap defaulting to FCO
RUNTIME_SERVICES_DEBUG [WhValidationGenerationTransaction] DeploymentSpecificati
onImpl.addToUnitSpecificationImplArrayList: created UnitSpecification for Deploy
mentAdapterName DDLDeployment StoreUOID= 9B7415EC7AB94F54824DF5F57D502828 Action
= 1 FCO list= M_FUNDSTRUCT_DWH,
Runtime Parameters for : M_FUNDSTRUCT_DWH
SYSTEM: DEFAULT_OPERATING_MODE: SET_BASED_FAIL_OVER_TO_ROW_BASED
SYSTEM: DEFAULT_AUDIT_LEVEL: ERROR_DETAILS
SYSTEM: MAXIMUM_NUMBER_OF_ERRORS: 50
SYSTEM: COMMIT_FREQUENCY: 1000
SYSTEM: BULK_SIZE: 1000
SYSTEM: DEFAULT_PURGE_GROUP: WB
SYSTEM: ANALYZE_TABLE_SAMPLE_PERCENTAGE: 5
RUNTIME_SERVICES_DEBUG [WhValidationGenerationTransaction] ExecutionUtils.decode
SystemParameter: Unexpected parameter ANALYZE_TABLE_SAMPLE_PERCENTAGE
Notification (Unit): start VEVA_LOCATION (Erstellen) - 0 (Adapter=DDLDeployment
Location=VEVA_LOCATION)
MEM:GenerationValidationService:internalCompile:after transaction:U: 65237816%IN
CR:2538296:INCREASE
What is the problem?
Michael

The error is due to the corrupted MDL file. MDL is getting corrupted because there is not enough memory for java VM. To fix the MDL corruption increase memory parameters.
1. On client PC: XXXX\owb\bin\win32\owbclient.bat change
java -Xms64M -Xmx768M -Dlimit=768M -XX:MaxPermSize=256M
to
java -Xms64M -Xmx1024M -Dlimit=1024M -XX:MaxPermSize=512M
Restart client session.
It did fix the problem in my case.
Oracle also recommends changing memory parameters on the server side (UNIX in my case)
2.On server side XXXX/owb/bin/unix/run_service.sh
$JAVAPATH/bin/java -Xmx768M
to
$JAVAPATH/bin/java -Xmx1024M

Hang on boot after upgrade to kernel 2.6.31 [SOLVED]

hey all,
My system hangs after installing 2.6.31. the message is this:
pci 0000:00:00.0: BAR 3: address space collision on of device [0xe0000000-0xffffffff]
i tried 2.6.30, but compiz was too slow, so i went back to 2.6.29. dmesg:
Linux version 2.6.29-ARCH (root@T-POWA-LX) (gcc version 4.4.0 (GCC) ) #1 SMP PREEMPT Wed May 20 07:06:02 UTC 2009
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
NSC Geode by NSC
Cyrix CyrixInstead
Centaur CentaurHauls
Transmeta GenuineTMx86
Transmeta TransmetaCPU
UMC UMC UMC UMC
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e6000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000cfda0000 (usable)
BIOS-e820: 00000000cfda0000 - 00000000cfdae000 (ACPI data)
BIOS-e820: 00000000cfdae000 - 00000000cfdf0000 (ACPI NVS)
BIOS-e820: 00000000cfdf0000 - 00000000cff00000 (reserved)
BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000130000000 (usable)
DMI present.
AMI BIOS detected: BIOS may corrupt low RAM, working around it.
last_pfn = 0xcfda0 max_arch_pfn = 0x100000
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Scanning 0 areas for low memory corruption
modified physical RAM map:
modified: 0000000000000000 - 0000000000010000 (reserved)
modified: 0000000000010000 - 000000000009f000 (usable)
modified: 000000000009f000 - 00000000000a0000 (reserved)
modified: 00000000000e6000 - 0000000000100000 (reserved)
modified: 0000000000100000 - 00000000cfda0000 (usable)
modified: 00000000cfda0000 - 00000000cfdae000 (ACPI data)
modified: 00000000cfdae000 - 00000000cfdf0000 (ACPI NVS)
modified: 00000000cfdf0000 - 00000000cff00000 (reserved)
modified: 00000000fff00000 - 0000000100000000 (reserved)
modified: 0000000100000000 - 0000000130000000 (usable)
kernel direct mapping tables up to 377fe000 @ 10000-15000
RAMDISK: 7fbab000 - 7ffef415
Allocated new RAMDISK: 005a6000 - 009ea415
Move RAMDISK from 000000007fbab000 - 000000007ffef414 to 005a6000 - 009ea414
ACPI: RSDP 000F9410, 0014 (r0 ACPIAM)
ACPI: RSDT CFDA0000, 003C (r1 7577MS A7577100 20090427 MSFT 97)
ACPI: FACP CFDA0200, 0084 (r1 7577MS A7577100 20090427 MSFT 97)
ACPI Warning (tbfadt-0596): Optional field Pm2ControlBlock has zero address or length: 0000000000000000/1 [20081204]
FADT: X_PM1a_EVT_BLK.bit_width (16) does not match PM1_EVT_LEN (4)
ACPI: DSDT CFDA0440, A216 (r1 A7577 A7577100 100 INTL 20051117)
ACPI: FACS CFDAE000, 0040
ACPI: APIC CFDA0390, 006C (r1 7577MS A7577100 20090427 MSFT 97)
ACPI: MCFG CFDA0400, 003C (r1 7577MS OEMMCFG 20090427 MSFT 97)
ACPI: OEMB CFDAE040, 0072 (r1 7577MS A7577100 20090427 MSFT 97)
ACPI: HPET CFDAA660, 0038 (r1 7577MS OEMHPET 20090427 MSFT 97)
ACPI: SSDT CFDAA6A0, 088C (r1 A M I POWERNOW 1 AMD 1)
ACPI: Local APIC address 0xfee00000
2437MB HIGHMEM available.
887MB LOWMEM available.
mapped low ram: 0 - 377fe000
low ram: 00000000 - 377fe000
bootmap 00011000 - 00017f00
(9 early reservations) ==> bootmem [0000000000 - 00377fe000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
#2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
#3 [0000100000 - 00005a2604] TEXT DATA BSS ==> [0000100000 - 00005a2604]
#4 [00005a3000 - 00005a6000] INIT_PG_TABLE ==> [00005a3000 - 00005a6000]
#5 [000009f000 - 0000100000] BIOS reserved ==> [000009f000 - 0000100000]
#6 [0000010000 - 0000011000] PGTABLE ==> [0000010000 - 0000011000]
#7 [00005a6000 - 00009ea415] NEW RAMDISK ==> [00005a6000 - 00009ea415]
#8 [0000011000 - 0000018000] BOOTMAP ==> [0000011000 - 0000018000]
found SMP MP-table at [c00ff780] 000ff780
Zone PFN ranges:
DMA 0x00000010 -> 0x00001000
Normal 0x00001000 -> 0x000377fe
HighMem 0x000377fe -> 0x000cfda0
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x00000010 -> 0x0000009f
0: 0x00000100 -> 0x000cfda0
On node 0 totalpages: 851247
free_area_init_node: node 0, pgdat c0430600, node_mem_map c1000200
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 3951 pages, LIFO batch:0
Normal zone: 1744 pages used for memmap
Normal zone: 221486 pages, LIFO batch:31
HighMem zone: 4876 pages used for memmap
HighMem zone: 619158 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 4, version 33, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8300 base: 0xfed00000
SMP: Allowing 4 CPUs, 0 hotplug CPUs
nr_irqs_gsi: 24
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000e6000
PM: Registered nosave memory: 00000000000e6000 - 0000000000100000
Allocating PCI resources starting at d0000000 (gap: cff00000:30000000)
NR_CPUS:16 nr_cpumask_bits:16 nr_cpu_ids:4 nr_node_ids:1
PERCPU: Allocating 36864 bytes of per cpu data
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 844595
Kernel command line: root=/dev/disk/by-uuid/deebdc30-3ac7-4de2-81d2-eb4d199468b9 ro quiet vga=792 splash
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Fast TSC calibration using PIT
Detected 3214.713 MHz processor.
Console: colour dummy device 80x25
console [tty0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 3367428k/3405440k available (2363k kernel code, 36780k reserved, 1059k data, 340k init, 2496136k highmem)
virtual kernel memory layout:
fixmap : 0xffee8000 - 0xfffff000 (1116 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
.init : 0xc045d000 - 0xc04b2000 ( 340 kB)
.data : 0xc034ec74 - 0xc0457a88 (1059 kB)
.text : 0xc0100000 - 0xc034ec74 (2363 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
hpet clockevent registered
HPET: 4 timers in total, 1 timers will be used for per-cpu timer
Calibrating delay loop (skipped), value calculated using timer frequency.. 6431.31 BogoMIPS (lpj=10715710)
Security Framework initialized
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
using C1E aware idle routine
Checking 'hlt' instruction... OK.
ACPI: Core revision 20081204
ACPI: Checking initramfs for custom DSDT
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: AMD Phenom(tm) II X4 955 Processor stepping 02
Booting processor 1 APIC 0x1 ip 0x6000
Initializing CPU#1
Calibrating delay using timer specific routine.. 6431.80 BogoMIPS (lpj=10714888)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
CPU1: AMD Phenom(tm) II X4 955 Processor stepping 02
checking TSC synchronization [CPU#0 -> CPU#1]: passed.
System has AMD C1E enabled
Switch to broadcast mode on CPU1
Booting processor 2 APIC 0x2 ip 0x6000
Initializing CPU#2
Calibrating delay using timer specific routine.. 6431.79 BogoMIPS (lpj=10714876)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 2
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#2.
x86 PAT enabled: cpu 2, old 0x7040600070406, new 0x7010600070106
CPU2: AMD Phenom(tm) II X4 955 Processor stepping 02
checking TSC synchronization [CPU#0 -> CPU#2]: passed.
Switch to broadcast mode on CPU2
Booting processor 3 APIC 0x3 ip 0x6000
Initializing CPU#3
Calibrating delay using timer specific routine.. 6431.80 BogoMIPS (lpj=10714888)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 3
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#3.
x86 PAT enabled: cpu 3, old 0x7040600070406, new 0x7010600070106
CPU3: AMD Phenom(tm) II X4 955 Processor stepping 02
checking TSC synchronization [CPU#0 -> CPU#3]: passed.
Brought up 4 CPUs
Total of 4 processors activated (25726.72 BogoMIPS).
Switch to broadcast mode on CPU3
Switch to broadcast mode on CPU0
net_namespace: 1016 bytes
Booting paravirtualized kernel on bare hardware
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
PCI: Not using MMCONFIG.
PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=6
PCI: Using configuration type 1 for base access
PCI: Using configuration type 1 for extended access
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
PCI: MCFG area at e0000000 reserved in ACPI motherboard resources
PCI: Using MMCONFIG for extended config space
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:00.0: reg 1c 64bit mmio: [0xe0000000-0xffffffff]
pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
pci 0000:00:02.0: PME# disabled
pci 0000:00:05.0: PME# supported from D0 D3hot D3cold
pci 0000:00:05.0: PME# disabled
pci 0000:00:06.0: PME# supported from D0 D3hot D3cold
pci 0000:00:06.0: PME# disabled
pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
pci 0000:00:07.0: PME# disabled
pci 0000:00:09.0: PME# supported from D0 D3hot D3cold
pci 0000:00:09.0: PME# disabled
pci 0000:00:11.0: reg 10 io port: [0x8000-0x8007]
pci 0000:00:11.0: reg 14 io port: [0x7000-0x7003]
pci 0000:00:11.0: reg 18 io port: [0x6000-0x6007]
pci 0000:00:11.0: reg 1c io port: [0x5000-0x5003]
pci 0000:00:11.0: reg 20 io port: [0x3000-0x300f]
pci 0000:00:11.0: reg 24 32bit mmio: [0xf9fffc00-0xf9ffffff]
pci 0000:00:11.0: set SATA to AHCI mode
pci 0000:00:12.0: reg 10 32bit mmio: [0xf9ffe000-0xf9ffefff]
pci 0000:00:12.1: reg 10 32bit mmio: [0xf9ffd000-0xf9ffdfff]
pci 0000:00:12.2: reg 10 32bit mmio: [0xf9fff800-0xf9fff8ff]
pci 0000:00:12.2: supports D1 D2
pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
pci 0000:00:12.2: PME# disabled
pci 0000:00:13.0: reg 10 32bit mmio: [0xf9ffc000-0xf9ffcfff]
pci 0000:00:13.1: reg 10 32bit mmio: [0xf9ffb000-0xf9ffbfff]
pci 0000:00:13.2: reg 10 32bit mmio: [0xf9fff400-0xf9fff4ff]
pci 0000:00:13.2: supports D1 D2
pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
pci 0000:00:13.2: PME# disabled
pci 0000:00:14.1: reg 10 io port: [0x00-0x07]
pci 0000:00:14.1: reg 14 io port: [0x00-0x03]
pci 0000:00:14.1: reg 18 io port: [0x00-0x07]
pci 0000:00:14.1: reg 1c io port: [0x00-0x03]
pci 0000:00:14.1: reg 20 io port: [0xff00-0xff0f]
pci 0000:00:14.2: reg 10 64bit mmio: [0xf9ff4000-0xf9ff7fff]
pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
pci 0000:00:14.2: PME# disabled
pci 0000:00:14.5: reg 10 32bit mmio: [0xf9ffa000-0xf9ffafff]
pci 0000:01:00.0: reg 10 32bit mmio: [0xfd000000-0xfdffffff]
pci 0000:01:00.0: reg 14 64bit mmio: [0xd0000000-0xdfffffff]
pci 0000:01:00.0: reg 1c 64bit mmio: [0xfa000000-0xfbffffff]
pci 0000:01:00.0: reg 24 io port: [0x9800-0x987f]
pci 0000:01:00.0: reg 30 32bit mmio: [0xfe7e0000-0xfe7fffff]
pci 0000:00:02.0: bridge io port: [0x9000-0x9fff]
pci 0000:00:02.0: bridge 32bit mmio: [0xfa000000-0xfe7fffff]
pci 0000:00:02.0: bridge 64bit mmio pref: [0xd0000000-0xdfffffff]
pci 0000:02:00.0: reg 10 io port: [0xa800-0xa8ff]
pci 0000:02:00.0: reg 18 64bit mmio: [0xf8eff000-0xf8efffff]
pci 0000:02:00.0: reg 20 64bit mmio: [0xf8ef8000-0xf8efbfff]
pci 0000:02:00.0: reg 30 32bit mmio: [0xfe8e0000-0xfe8fffff]
pci 0000:02:00.0: supports D1 D2
pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:02:00.0: PME# disabled
pci 0000:00:05.0: bridge io port: [0xa000-0xafff]
pci 0000:00:05.0: bridge 32bit mmio: [0xfe800000-0xfe8fffff]
pci 0000:00:05.0: bridge 64bit mmio pref: [0xf8e00000-0xf8efffff]
pci 0000:03:00.0: reg 10 io port: [0xb800-0xb8ff]
pci 0000:03:00.0: reg 18 64bit mmio: [0xf8fff000-0xf8ffffff]
pci 0000:03:00.0: reg 20 64bit mmio: [0xf8ff8000-0xf8ffbfff]
pci 0000:03:00.0: reg 30 32bit mmio: [0xfe9e0000-0xfe9fffff]
pci 0000:03:00.0: supports D1 D2
pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:03:00.0: PME# disabled
pci 0000:00:06.0: bridge io port: [0xb000-0xbfff]
pci 0000:00:06.0: bridge 32bit mmio: [0xfe900000-0xfe9fffff]
pci 0000:00:06.0: bridge 64bit mmio pref: [0xf8f00000-0xf8ffffff]
pci 0000:04:00.0: reg 10 64bit mmio: [0xfeaff800-0xfeafffff]
pci 0000:04:00.0: reg 18 io port: [0xc800-0xc8ff]
pci 0000:04:00.0: supports D2
pci 0000:04:00.0: PME# supported from D2 D3hot D3cold
pci 0000:04:00.0: PME# disabled
pci 0000:00:07.0: bridge io port: [0xc000-0xcfff]
pci 0000:00:07.0: bridge 32bit mmio: [0xfea00000-0xfeafffff]
pci 0000:05:00.0: reg 24 32bit mmio: [0xfebfe000-0xfebfffff]
pci 0000:05:00.0: PME# supported from D3hot
pci 0000:05:00.0: PME# disabled
pci 0000:05:00.1: reg 10 io port: [0xe800-0xe807]
pci 0000:05:00.1: reg 14 io port: [0xe400-0xe403]
pci 0000:05:00.1: reg 18 io port: [0xe000-0xe007]
pci 0000:05:00.1: reg 1c io port: [0xd800-0xd803]
pci 0000:05:00.1: reg 20 io port: [0xd400-0xd40f]
pci 0000:00:09.0: bridge io port: [0xd000-0xefff]
pci 0000:00:09.0: bridge 32bit mmio: [0xfeb00000-0xfebfffff]
pci 0000:00:14.4: transparent bridge
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCE2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCE5._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCE6._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCE7._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCE9._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0PC._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 4 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 4 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 4 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 4 *7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 4 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 4 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs 4 7 10 11 12 14 15) *0, disabled.
ACPI Warning (tbutils-0242): Incorrect checksum in table [OEMB] - 47, should be 46 [20081204]
PCI: Using ACPI for IRQ routing
pci 0000:00:00.0: BAR 3: can't allocate resource
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
hpet: hpet2 irq 24 for MSI
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp 00:0d: mem resource (0x0-0x9ffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
pnp 00:0d: mem resource (0xc0000-0xcffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
pnp 00:0d: mem resource (0xe0000-0xfffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
pnp 00:0d: mem resource (0x100000-0xcfefffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
pnp: PnP ACPI: found 14 devices
ACPI: ACPI bus type pnp unregistered
system 00:09: iomem range 0xfec00000-0xfec00fff has been reserved
system 00:09: iomem range 0xfee00000-0xfee00fff has been reserved
system 00:0a: ioport range 0x4d0-0x4d1 has been reserved
system 00:0a: ioport range 0x40b-0x40b has been reserved
system 00:0a: ioport range 0x4d6-0x4d6 has been reserved
system 00:0a: ioport range 0xc00-0xc01 has been reserved
system 00:0a: ioport range 0xc14-0xc14 has been reserved
system 00:0a: ioport range 0xc50-0xc51 has been reserved
system 00:0a: ioport range 0xc52-0xc52 has been reserved
system 00:0a: ioport range 0xc6c-0xc6c has been reserved
system 00:0a: ioport range 0xc6f-0xc6f has been reserved
system 00:0a: ioport range 0xcd0-0xcd1 has been reserved
system 00:0a: ioport range 0xcd2-0xcd3 has been reserved
system 00:0a: ioport range 0xcd4-0xcd5 has been reserved
system 00:0a: ioport range 0xcd6-0xcd7 has been reserved
system 00:0a: ioport range 0xcd8-0xcdf has been reserved
system 00:0a: ioport range 0x800-0x89f has been reserved
system 00:0a: ioport range 0xb00-0xb0f has been reserved
system 00:0a: ioport range 0xb20-0xb3f has been reserved
system 00:0a: ioport range 0x900-0x90f has been reserved
system 00:0a: ioport range 0x910-0x91f has been reserved
system 00:0a: ioport range 0xfe00-0xfefe has been reserved
system 00:0a: iomem range 0xffb80000-0xffbfffff has been reserved
system 00:0a: iomem range 0xfec10000-0xfec1001f has been reserved
system 00:0b: ioport range 0x600-0x6df has been reserved
system 00:0b: ioport range 0x6e0-0x6ef has been reserved
system 00:0c: iomem range 0xe0000000-0xefffffff has been reserved
system 00:0d: iomem range 0xfec00000-0xffffffff could not be reserved
Switched to high resolution mode on CPU 3
Switched to high resolution mode on CPU 1
Switched to high resolution mode on CPU 2
Switched to high resolution mode on CPU 0
pci 0000:00:02.0: PCI bridge, secondary bus 0000:01
pci 0000:00:02.0: IO window: 0x9000-0x9fff
pci 0000:00:02.0: MEM window: 0xfa000000-0xfe7fffff
pci 0000:00:02.0: PREFETCH window: 0x000000d0000000-0x000000dfffffff
pci 0000:00:05.0: PCI bridge, secondary bus 0000:02
pci 0000:00:05.0: IO window: 0xa000-0xafff
pci 0000:00:05.0: MEM window: 0xfe800000-0xfe8fffff
pci 0000:00:05.0: PREFETCH window: 0x000000f8e00000-0x000000f8efffff
pci 0000:00:06.0: PCI bridge, secondary bus 0000:03
pci 0000:00:06.0: IO window: 0xb000-0xbfff
pci 0000:00:06.0: MEM window: 0xfe900000-0xfe9fffff
pci 0000:00:06.0: PREFETCH window: 0x000000f8f00000-0x000000f8ffffff
pci 0000:00:07.0: PCI bridge, secondary bus 0000:04
pci 0000:00:07.0: IO window: 0xc000-0xcfff
pci 0000:00:07.0: MEM window: 0xfea00000-0xfeafffff
pci 0000:00:07.0: PREFETCH window: disabled
pci 0000:00:09.0: PCI bridge, secondary bus 0000:05
pci 0000:00:09.0: IO window: 0xd000-0xefff
pci 0000:00:09.0: MEM window: 0xfeb00000-0xfebfffff
pci 0000:00:09.0: PREFETCH window: disabled
pci 0000:00:14.4: PCI bridge, secondary bus 0000:06
pci 0000:00:14.4: IO window: disabled
pci 0000:00:14.4: MEM window: disabled
pci 0000:00:14.4: PREFETCH window: disabled
pci 0000:00:02.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
pci 0000:00:02.0: setting latency timer to 64
pci 0000:00:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:05.0: setting latency timer to 64
pci 0000:00:06.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
pci 0000:00:06.0: setting latency timer to 64
pci 0000:00:07.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
pci 0000:00:07.0: setting latency timer to 64
pci 0000:00:09.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:09.0: setting latency timer to 64
pci_bus 0000:00: resource 0 io: [0x00-0xffff]
pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
pci_bus 0000:01: resource 0 io: [0x9000-0x9fff]
pci_bus 0000:01: resource 1 mem: [0xfa000000-0xfe7fffff]
pci_bus 0000:01: resource 2 mem: [0xd0000000-0xdfffffff]
pci_bus 0000:01: resource 3 mem: [0x0-0x0]
pci_bus 0000:02: resource 0 io: [0xa000-0xafff]
pci_bus 0000:02: resource 1 mem: [0xfe800000-0xfe8fffff]
pci_bus 0000:02: resource 2 mem: [0xf8e00000-0xf8efffff]
pci_bus 0000:02: resource 3 mem: [0x0-0x0]
pci_bus 0000:03: resource 0 io: [0xb000-0xbfff]
pci_bus 0000:03: resource 1 mem: [0xfe900000-0xfe9fffff]
pci_bus 0000:03: resource 2 mem: [0xf8f00000-0xf8ffffff]
pci_bus 0000:03: resource 3 mem: [0x0-0x0]
pci_bus 0000:04: resource 0 io: [0xc000-0xcfff]
pci_bus 0000:04: resource 1 mem: [0xfea00000-0xfeafffff]
pci_bus 0000:04: resource 2 mem: [0x0-0x0]
pci_bus 0000:04: resource 3 mem: [0x0-0x0]
pci_bus 0000:05: resource 0 io: [0xd000-0xefff]
pci_bus 0000:05: resource 1 mem: [0xfeb00000-0xfebfffff]
pci_bus 0000:05: resource 2 mem: [0x0-0x0]
pci_bus 0000:05: resource 3 mem: [0x0-0x0]
pci_bus 0000:06: resource 0 mem: [0x0-0x0]
pci_bus 0000:06: resource 1 mem: [0x0-0x0]
pci_bus 0000:06: resource 2 mem: [0x0-0x0]
pci_bus 0000:06: resource 3 io: [0x00-0xffff]
pci_bus 0000:06: resource 4 mem: [0x000000-0xffffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
NET: Registered protocol family 1
Unpacking initramfs... done
Freeing initrd memory: 4369k freed
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: disabled - APM is not SMP safe.
Scanning for low memory corruption every 60 seconds
audit: initializing netlink socket (disabled)
type=2000 audit(1252627399.657:1): initialized
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 1711
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci 0000:01:00.0: Boot video device
pcieport-driver 0000:00:02.0: setting latency timer to 64
pcieport-driver 0000:00:02.0: irq 25 for MSI/MSI-X
pcieport-driver 0000:00:05.0: setting latency timer to 64
pcieport-driver 0000:00:05.0: irq 26 for MSI/MSI-X
pcieport-driver 0000:00:06.0: setting latency timer to 64
pcieport-driver 0000:00:06.0: irq 27 for MSI/MSI-X
pcieport-driver 0000:00:07.0: setting latency timer to 64
pcieport-driver 0000:00:07.0: irq 28 for MSI/MSI-X
pcieport-driver 0000:00:09.0: setting latency timer to 64
pcieport-driver 0000:00:09.0: irq 29 for MSI/MSI-X
vesafb: framebuffer at 0xfb000000, mapped to 0xf8080000, using 6144k, total 14336k
vesafb: mode is 1024x768x32, linelength=4096, pages=1
vesafb: protected mode interface info at c000:b2e0
vesafb: pmi: set display start = c00cb343, set palette = c00cb39e
vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da
vesafb: scrolling: redraw
vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
input: Macintosh mouse button emulation as /devices/virtual/input/input0
PNP: PS/2 Controller [PNP0303:PSKE,PNP0f03:PSMS] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
NET: Registered protocol family 17
Using IPI No-Shortcut mode
registered taskstats version 1
Freeing unused kernel memory: 340k freed
SCSI subsystem initialized
libata version 3.00 loaded.
pata_acpi 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pata_acpi 0000:00:14.1: setting latency timer to 64
pata_acpi 0000:05:00.1: enabling device (0000 -> 0001)
pata_acpi 0000:05:00.1: PCI INT B -> GSI 18 (level, low) -> IRQ 18
pata_acpi 0000:05:00.1: setting latency timer to 64
pata_acpi 0000:05:00.1: PCI INT B disabled
ahci 0000:00:11.0: version 3.0
ahci 0000:00:11.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
ahci 0000:00:11.0: irq 30 for MSI/MSI-X
ahci 0000:00:11.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 abar m1024@0xf9fffc00 port 0xf9fffd00 irq 30
ata2: SATA max UDMA/133 abar m1024@0xf9fffc00 port 0xf9fffd80 irq 30
ata3: SATA max UDMA/133 abar m1024@0xf9fffc00 port 0xf9fffe00 irq 30
ata4: SATA max UDMA/133 abar m1024@0xf9fffc00 port 0xf9fffe80 irq 30
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pata_jmicron 0000:05:00.1: PCI INT B -> GSI 18 (level, low) -> IRQ 18
pata_jmicron 0000:05:00.1: setting latency timer to 64
scsi4 : pata_jmicron
scsi5 : pata_jmicron
ata5: PATA max UDMA/100 cmd 0xe800 ctl 0xe400 bmdma 0xd400 irq 18
ata6: PATA max UDMA/100 cmd 0xe000 ctl 0xd800 bmdma 0xd408 irq 18
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ata1: SATA link down (SStatus 0 SControl 300)
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATAPI: TSSTcorp CD-RW/DVD-ROM TS-H493A, D200, max UDMA/33, ATAPI AN
ata2.00: configured for UDMA/33
scsi 1:0:0:0: CD-ROM TSSTcorp CDRWDVD TS-H493A D200 PQ: 0 ANSI: 5
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
ata4.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata4.00: configured for UDMA/133
scsi 3:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
ahci 0000:05:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
scsi6 : pata_atiixp
scsi7 : pata_atiixp
ata7: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xff00 irq 14
ata8: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xff08 irq 15
ahci 0000:05:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
ahci 0000:05:00.0: flags: 64bit ncq pm led clo pmp pio slum part
ahci 0000:05:00.0: setting latency timer to 64
scsi8 : ahci
scsi9 : ahci
ata9: SATA max UDMA/133 abar m8192@0xfebfe000 port 0xfebfe100 irq 17
ata10: SATA max UDMA/133 abar m8192@0xfebfe000 port 0xfebfe180 irq 17
ata9: SATA link down (SStatus 0 SControl 300)
ata8.01: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
ata8.01: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata8.01: configured for UDMA/100
scsi 7:0:1:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
ehci_hcd 0000:00:12.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
ehci_hcd 0000:00:12.2: EHCI Host Controller
ehci_hcd 0000:00:12.2: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:12.2: debug port 1
ehci_hcd 0000:00:12.2: irq 17, io mem 0xf9fff800
ehci_hcd 0000:00:12.2: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ohci_hcd 0000:00:12.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ohci_hcd 0000:00:12.0: OHCI Host Controller
ohci_hcd 0000:00:12.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:12.0: irq 16, io mem 0xf9ffe000
Driver 'sd' needs updating - please use bus_type methods
sd 3:0:0:0: [sda] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 3:0:0:0: [sda] Write Protect is off
sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:0:0:0: [sda] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 3:0:0:0: [sda] Write Protect is off
sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3
sd 3:0:0:0: [sda] Attached SCSI disk
sd 7:0:1:0: [sdb] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 7:0:1:0: [sdb] Write Protect is off
sd 7:0:1:0: [sdb] Mode Sense: 00 3a 00 00
sd 7:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 7:0:1:0: [sdb] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 7:0:1:0: [sdb] Write Protect is off
sd 7:0:1:0: [sdb] Mode Sense: 00 3a 00 00
sd 7:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
sd 7:0:1:0: [sdb] Attached SCSI disk
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
ehci_hcd 0000:00:13.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ehci_hcd 0000:00:13.2: EHCI Host Controller
ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 3
ehci_hcd 0000:00:13.2: debug port 1
ehci_hcd 0000:00:13.2: irq 19, io mem 0xf9fff400
ehci_hcd 0000:00:13.2: USB 2.0 started, EHCI 1.00
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 6 ports detected
ohci_hcd 0000:00:12.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ohci_hcd 0000:00:12.1: OHCI Host Controller
ohci_hcd 0000:00:12.1: new USB bus registered, assigned bus number 4
ohci_hcd 0000:00:12.1: irq 16, io mem 0xf9ffd000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 3 ports detected
ohci_hcd 0000:00:13.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
ohci_hcd 0000:00:13.0: OHCI Host Controller
ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 5
ohci_hcd 0000:00:13.0: irq 18, io mem 0xf9ffc000
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 3 ports detected
ohci_hcd 0000:00:13.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
ohci_hcd 0000:00:13.1: OHCI Host Controller
ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 6
ohci_hcd 0000:00:13.1: irq 18, io mem 0xf9ffb000
ata10: SATA link down (SStatus 0 SControl 300)
usb usb6: configuration #1 chosen from 1 choice
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 3 ports detected
ohci_hcd 0000:00:14.5: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ohci_hcd 0000:00:14.5: OHCI Host Controller
ohci_hcd 0000:00:14.5: new USB bus registered, assigned bus number 7
ohci_hcd 0000:00:14.5: irq 18, io mem 0xf9ffa000
usb usb7: configuration #1 chosen from 1 choice
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
Driver 'sr' needs updating - please use bus_type methods
sr0: scsi3-mmc drive: 8x/48x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
usb 3-2: new high speed USB device using ehci_hcd and address 3
usb 3-2: configuration #1 chosen from 1 choice
hub 3-2:1.0: USB hub found
hub 3-2:1.0: 4 ports detected
usb 5-1: new low speed USB device using ohci_hcd and address 2
usb 5-1: configuration #1 chosen from 1 choice
usbcore: registered new interface driver hiddev
input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as /devices/pci0000:00/0000:00:13.0/usb5/5-1/5-1:1.0/input/input1
generic-usb 0003:045E:0040.0001: input,hidraw0: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-0000:00:13.0-1/input0
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
usb 3-2.4: new high speed USB device using ehci_hcd and address 4
usb 3-2.4: configuration #1 chosen from 1 choice
hub 3-2.4:1.0: USB hub found
hub 3-2.4:1.0: 4 ports detected
usb 3-2.4.1: new low speed USB device using ehci_hcd and address 5
usb 3-2.4.1: configuration #1 chosen from 1 choice
input: Microsoft Comfort Curve Keyboard 2000 as /devices/pci0000:00/0000:00:13.2/usb3/3-2/3-2.4/3-2.4.1/3-2.4.1:1.0/input/input2
generic-usb 0003:045E:00DD.0002: input,hidraw1: USB HID v1.11 Keyboard [Microsoft Comfort Curve Keyboard 2000] on usb-0000:00:13.2-2.4.1/input0
input: Microsoft Comfort Curve Keyboard 2000 as /devices/pci0000:00/0000:00:13.2/usb3/3-2/3-2.4/3-2.4.1/3-2.4.1:1.1/input/input3
generic-usb 0003:045E:00DD.0003: input,hidraw2: USB HID v1.11 Device [Microsoft Comfort Curve Keyboard 2000] on usb-0000:00:13.2-2.4.1/input1
SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
SGI XFS Quota Management subsystem
XFS mounting filesystem sda3
Ending clean XFS mount for filesystem: sda3
rtc_cmos 00:04: RTC can wake from S4
rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
udev: starting version 146
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
r8169 0000:02:00.0: setting latency timer to 64
r8169 0000:02:00.0: irq 31 for MSI/MSI-X
eth0: RTL8168d/8111d at 0xf888c000, 00:24:21:b7:ca:4d, XID 281000c0 IRQ 31
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
r8169 0000:03:00.0: setting latency timer to 64
r8169 0000:03:00.0: irq 32 for MSI/MSI-X
eth1: RTL8168d/8111d at 0xf8696000, 00:24:21:b7:ca:4c, XID 281000c0 IRQ 32
HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
usbcore: registered new interface driver snd-usb-audio
input: Power Button (FF) as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input5
ACPI: Power Button (CM) [PWRB]
processor ACPI_CPU:00: registered as cooling_device0
ACPI: Processor [P001] (supports 8 throttling states)
processor ACPI_CPU:01: registered as cooling_device1
processor ACPI_CPU:02: registered as cooling_device2
processor ACPI_CPU:03: registered as cooling_device3
sr 1:0:0:0: Attached scsi generic sg0 type 5
sd 3:0:0:0: Attached scsi generic sg1 type 0
sd 7:0:1:0: Attached scsi generic sg2 type 0
Linux agpgart interface v0.103
ohci1394 0000:04:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
ohci1394 0000:04:00.0: setting latency timer to 64
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[19] MMIO=[feaff800-feafffff] Max Packet=[2048] IR/IT contexts=[4/8]
input: PC Speaker as /devices/platform/pcspkr/input/input6
ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SOR1 [0xb00-0xb0f]
ACPI: Device needs an ACPI driver
piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
nvidia: module license 'NVIDIA' taints kernel.
ACPI: WMI: Mapper loaded
nvidia 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
nvidia 0000:01:00.0: setting latency timer to 64
NVRM: loading NVIDIA UNIX x86 Kernel Module 180.44 Mon Mar 23 14:59:10 PST 2009
ieee1394: Host added: ID:BUS[0-00:1023] GUID[0010dc0001947652]
Adding 996020k swap on /dev/sda2. Priority:-1 extents:1 across:996020k
r8169: eth0: link up
r8169: eth0: link up
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
nvclock:4989 freeing invalid memtype fd000000-fd010000
nvclock:4989 freeing invalid memtype fd010000-fd030000
nvclock:4989 freeing invalid memtype fd010000-fd030000
IRQ 18/nvidia: IRQF_DISABLED is not guaranteed on shared IRQs
eth0: no IPv6 routers present
ideas?
Last edited by pnatural (2009-09-17 19:59:58)

pnatural wrote:
hi,
I was able to install 2.6.31 by setting the motherboards E-SATA/RAID mode to "ACPI" instead of "PCI". I first tried to disable the motherboard raid completely, but the system would not boot at all that way; setting the mode to "ACPI" did the trick.
I would say thanks, but I did all the work! But thanks to the Arch folks for a great distribution.
Hi,I got the follow message,much same with you,could you tell me how to deal?thx.
Nov 3 23:00:06 ArchLinux kernel: pci 0000:00:14.2: BAR 0: address space collision on of device [0xd4408000-0xd440bfff]

Hangs during boot after upgrading to Kernel 2.6.39

I have just installed Arch on a new computer. It works fine until I upgrade to Kernel 2.6.39. After that it hangs on boot.
The end of /var/log/everything.log is posted below.
Jul 26 23:52:06 localhost kernel: [ 6.036766] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table at offset 0x85F3
Jul 26 23:52:06 localhost kernel: [ 6.129046] adt7475 1-002e: ADT7473 device, revision 1
Jul 26 23:52:06 localhost kernel: [ 6.138997] [drm] nouveau 0000:04:00.0: Detected monitoring device: adt7473
Jul 26 23:52:06 localhost kernel: [ 6.139000] [drm] nouveau 0000:04:00.0: 1 available performance level(s)
Jul 26 23:52:06 localhost kernel: [ 6.139002] [drm] nouveau 0000:04:00.0: 0: memory 405MHz core 270MHz shader 540MHz
Jul 26 23:52:06 localhost kernel: [ 6.139233] [TTM] Zone kernel: Available graphics memory: 12371030 kiB.
Jul 26 23:52:06 localhost kernel: [ 6.139236] [TTM] Zone dma32: Available graphics memory: 2097152 kiB.
Jul 26 23:52:06 localhost kernel: [ 6.139238] [TTM] Initializing pool allocator.
Jul 26 23:52:06 localhost kernel: [ 6.139252] [drm] nouveau 0000:04:00.0: Detected 5376MiB VRAM
Jul 26 23:52:06 localhost kernel: [ 6.139260] mtrr: type mismatch for d0000000,8000000 old: write-back new: write-combining
Jul 26 23:52:06 localhost kernel: [ 6.150626] [drm] nouveau 0000:04:00.0: 512 MiB GART (aperture)
Jul 26 23:52:06 localhost kernel: [ 6.152371] [drm] nouveau 0000:04:00.0: failed to load fuc409d
Jul 26 23:52:06 localhost kernel: [ 6.176193] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
Jul 26 23:52:06 localhost kernel: [ 6.176195] [drm] No driver support for vblank timestamp query.
Jul 26 23:52:06 localhost kernel: [ 6.228800] No connectors reported connected with modes
Jul 26 23:52:06 localhost kernel: [ 6.228802] [drm] Cannot find any crtc or sizes - going 1024x768
Jul 26 23:52:06 localhost kernel: [ 6.231002] [drm] nouveau 0000:04:00.0: allocated 1024x768 fb: 0x8020000, bo ffff880608d97800
Jul 26 23:52:06 localhost kernel: [ 6.233786] Console: switching to colour frame buffer device 128x48
Jul 26 23:52:06 localhost kernel: [ 6.235094] fb0: nouveaufb frame buffer device
Jul 26 23:52:06 localhost kernel: [ 6.235094] drm: registered panic notifier
Jul 26 23:52:06 localhost kernel: [ 6.235098] [drm] Initialized nouveau 0.0.16 20090420 for 0000:04:00.0 on minor 0
Jul 26 23:52:06 localhost kernel: [ 6.255449] HDA Intel 0000:04:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Jul 26 23:52:06 localhost kernel: [ 6.255451] hda_intel: Disable MSI for Nvidia chipset
Jul 26 23:52:06 localhost kernel: [ 6.255599] HDA Intel 0000:04:00.1: setting latency timer to 64
Jul 26 23:52:06 localhost kernel: [ 7.663482] EXT4-fs (sda3): re-mounted. Opts: (null)
Jul 26 23:52:06 localhost kernel: [ 7.807508] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 23:52:06 localhost kernel: [ 7.851401] Adding 265068k swap on /dev/sda2. Priority:-1 extents:1 across:265068k
Jul 26 23:52:06 localhost kernel: [ 8.569682] r8169 0000:08:00.0: eth0: link down
Jul 26 23:52:06 localhost kernel: [ 8.569687] r8169 0000:08:00.0: eth0: link down
Jul 26 23:52:06 localhost dhcpcd[747]: eth0: waiting for carrier
Jul 26 23:52:08 localhost dhcpcd[747]: eth0: carrier acquired
Jul 26 23:52:08 localhost kernel: [ 10.301736] r8169 0000:08:00.0: eth0: link up
Jul 26 23:52:08 localhost dhcpcd[747]: eth0: broadcasting for a lease
Jul 26 23:52:12 localhost dhcpcd[747]: eth0: offered 131.181.53.42 from 131.181.127.32
Jul 26 23:52:13 localhost dhcpcd[747]: eth0: acknowledged 131.181.53.42 from 131.181.59.48
Jul 26 23:52:13 localhost dhcpcd[747]: eth0: checking for 131.181.53.42
Jul 26 23:52:18 localhost dhcpcd[747]: eth0: leased 131.181.53.42 for 43200 seconds
Jul 26 23:52:18 localhost dhcpcd[747]: forked to background, child pid 774
Jul 26 23:52:18 localhost crond[823]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel info
Jul 26 23:53:01 localhost crond[823]: FILE /etc/cron.d/prune-cronstamps USER root PID 835 job prune-cronstamps
Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 836 job sys-hourly
Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 837 job sys-daily
Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 838 job sys-weekly
Any help fixing this would be greatly appreciated.

I have been trying to isolate the problem a little further. I re-installed (with just the base and sudo) and after upgrading pacman rebooted and it worked without fail. Then I installed libusb and libusb-compat which where required when I tried to upgrade just the kernel using
pacman -S kernel26
which initially failed because of the missing dependencies libusb and libusb-compat. I then re-booted and that worked without a problem.
I then upgraded to Kernel 2.6.39 using the above command and then it hung on rebooting. I saved the logs at each stage.
The additional logs in errors.log in the reboot that failed are as follows.
ul 26 16:28:39 O313 kernel: [ 5.120698] [drm] nouveau 0000:04:00.0: Pointer to BIT loadval table invalid
Jul 26 16:28:39 O313 kernel: [ 5.360508] [drm] nouveau 0000:04:00.0: failed to load fuc409d
Jul 26 16:28:39 O313 kernel: [ 5.808016] sd 20:0:0:0: [sdb] Assuming drive cache: write through
Jul 26 16:28:39 O313 kernel: [ 5.809960] sd 20:0:0:0: [sdb] Assuming drive cache: write through
Jul 26 16:28:39 O313 kernel: [ 5.812116] sd 20:0:0:0: [sdb] Assuming drive cache: write through
Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
The end of kernel.log is as follows:
Sat Jul 9 14:57:41 CEST 2011
Jul 26 16:28:39 O313 kernel: [ 0.000000] Command line: root=/dev/disk/by-uuid/e4733c60-3e54-4001-a83e-415b690dfcb0 ro
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-provided physical RAM map:
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 00000000cfed0000 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed0000 - 00000000cfed1000 (ACPI NVS)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed1000 - 00000000cfee0000 (ACPI data)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfee0000 - 00000000cff00000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000100000000 - 0000000630000000 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] NX (Execute Disable) protection: active
Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI 2.4 present.
Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI: Gigabyte Technology Co., Ltd. X58A-UD5/X58A-UD5, BIOS FD 02/01/2011
Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] No AGP bridge found
Jul 26 16:28:39 O313 kernel: [ 0.000000] last_pfn = 0x630000 max_arch_pfn = 0x400000000
And this is the end of daemon.log
Jul 26 16:27:49 O313 init: Switching to runlevel: 6
Jul 26 16:27:50 O313 dhcpcd: received SIGTERM, stopping
Jul 26 16:27:50 O313 dhcpcd: eth0: removing interface
Jul 26 16:28:39 O313 2.352592] udevd[87]: starting version 171
Jul 26 16:28:39 O313 4.531007] udevd[370]: starting version 171
Jul 26 16:28:39 O313 dhcpcd: version 5.2.2 starting
Jul 26 16:28:39 O313 dhcpcd: eth0: waiting for carrier
Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
Jul 26 16:28:39 O313 init: Entering runlevel: 3
Please let me know if any further information would be useful in tracking down this problem. Also ignore any timings in my initial post they were incorrect.
Last edited by TheStatsMan (2011-07-26 07:40:48)

Arch hangs on boot after system update

After I ran 'pacman -Syyu' yesterday, my Arch install won't boot anymore. Instead, it hangs after 'Reached target Graphical Interface' with a blinking underscore. It is the first time I've encountered such problems after running Arch for almost a year and frequently updating. Am I right to assume it might have something to do with the recent kernel/nvidia drivers update?

Keep checking archlinux site - information was posted here https://www.archlinux.org/news/nvidia-340xx-and-nvidia/
PS. mark as [SOLVED]

Yosemite hangs in booting after applying Update 2015-003.

I have applied Update 2015-003 to Yosemite.
After booting the progress bar hangs at about 30% for over an hour.
The hardware is a MacBook Pro with a SSD harddrive.

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.
Step 10
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 11
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 12
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 13
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

[SOLVED]Boot hang after recent updating issues

I am having issues after the last update. First, I made a mistake of holding back the filesystem package. Because of this (at least I think so) I was having an error that said it could not boot because at boot it said "/sbin/init does not exist". I solved this by upgrading the filesystem package by chrooting from a live arch usb. Now I am having an issue where my system hangs at boot, I believe it is right after systemd runs fsck although I might be wrong. But after maybe 5 minutes it just starts as usual... my ususal boot time is less than a minute. What should I do?
This is from a thread i accidentally hijacked:
cfr wrote:
Try systemctl --failed and or examine the journal for clues.
Post fstab. Are all of the disks referred to there available when you boot? If systemd can't find them, it will basically wait until it times out and I think that's about 5 minutes and then it will continue booting (assuming it isn't missing anything critical, of course).
My fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda6
UUID=5dc84b70-a9f9-42eb-981c-40e84f7e9e75 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda6
UUID=5dc84b70-a9f9-42eb-981c-40e84f7e9e75 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda5
UUID=f7bccd4f-4b47-4dbb-a8f8-d8e374bb9867 /home ext4 rw,relatime,data=ordered 0 2
# /dev/sda7
UUID=07dcd099-50c4-4c35-a102-10a39b74ac0b none swap defaults 0 0
Would deleting the second /dev/sda6 fix it?
Last edited by life_enjoyer (2013-06-10 20:24:14)

Thanks jasonwryan So my exact boot time was 1 minute and 34.151 seconds (which is not unbearable but like i said it used to be in a matter of seconds)... The kernel took 2.790 seconds and userspace took 1 minute and 31.361 Output of systemd-analyze blame :
922ms systemd-logind.service
832ms systemd-modules-load.service
774ms systemd-fsck@dev-disk-by\x2duuid-f7bccd4f\x2d4b47\x2d4dbb\x2da8f8\x2dd8e374bb9867.service
614ms udisks2.service
545ms dev-mqueue.mount
509ms sys-kernel-debug.mount
499ms dev-hugepages.mount
499ms systemd-udev-trigger.service
497ms systemd-vconsole-setup.service
478ms systemd-remount-fs.service
477ms tmp.mount
439ms systemd-tmpfiles-setup-dev.service
365ms dhcpcd.service
218ms temp-links-catalyst.service
192ms upower.service
169ms polkit.service
165ms systemd-journal-flush.service
151ms systemd-sysctl.service
149ms systemd-udevd.service
113ms systemd-update-utmp.service
105ms gpm.service
68ms home.mount
68ms systemd-tmpfiles-setup.service
57ms systemd-random-seed-load.service
30ms systemd-user-sessions.service
1ms sys-kernel-config.mount
Now maybe I am wrong, but these don't add up to 1 min 31 seconds...It actually adds to about 9 seconds which is probably my old boot time.. What am I missing here?
Last edited by life_enjoyer (2013-06-09 03:36:53)

[Solved] UEFI. System hangs on boot after successfully activating swap

Alright.
Unnecessary Background:
I've been using Arch for years. I just bought a stupidly good computer with a bunch of specs that I don't think are relevant, except for the fact that I am using an X99-pro. It has RAID support, but I am not using that currently. I bought all the parts and finished constructing it this morning (I live in Japan, so that was a while ago). Normally, I have no problems with installation; however, I wanted to do this one UEFI mode. After booting into the live disk, I checked to make sure everything was working as it should. Arch recognized my graphics card, most of my ram (one of the cards is a bit finicky for some reason), my SSD and HDD, along with the built-in WiFi (although it is an annoying broadcom one, so I need to install the driver separately later). Now, there are plenty of sources of error in here:
Problem:
I got through the arch installation and tried gummiboot. It would hang every time after successfully activating swap. I tried grub, too, but had the same problem. Because gummiboot is much less cumbersome, I switched back to that. Interestingly, systemd will sometimes recognize my drive twice before activating swap, and if I edit my fstab to ignore the swap completely, it hangs on the next step with is mounting the boot partition. I would like to point out that because I am not able to successfully boot my system, I cannot provide the exact messages for you guys, which may pose a problem.
Solutions I have tried:
1. Chrooting / mkinitcpio -p linux
2. modifying fstab / removing swap from it completely
3. fresh re-install
Sources of error:
1. Construction. Everything seems appropriate on the live usb, but maybe there is a problem in which ports I used for the SSD and HDD
2. UEFI. It could be that UEFI just doesn't like mounting multiple things and freezes up when put on the spot.
3. Legacy. It could be that this is not a problem with UEFI or my construction, but something I missed in the installation.
Additional info:
Partitioning scheme:
sda1: ~500MiB boot / EFI partition
sda2: ~4G swap
sda3: ~110G /
sdb: ~2T, untouched (for storage later)
I apologize for any typos and hope it was readable. I am super exhausted and going to take a nap. I'll check back in on this in the morning.
Last edited by Leios (2015-02-08 00:16:27)

Please post the output of:
# gdisk -l /dev/sda
lsblk -f
And the contents of your gummiboot loader.conf and arch.conf (or whatever you've called it).
Post the output of the commands after you have mounted all your partitions and (arch-)chroot'd into your system.
You can use wgetpaste to post the outputs, as described by @ewaller here:
https://bbs.archlinux.org/viewtopic.php … 8#p1500528
Alternatively, pipe the command output to a text file and export it (using a live distribution or a USB stick).
You should remove swap from your fstab -- systemd mounts it automatically anyway.

W520 - BIOS update (8buj19uc.iso) hangs after PXE booting

After PXE booting the latest 1.40 BIOS bootable CD,
the system hangs after pressing "2. Update system program"
Here my setup:
LABEL w520bios
MENU LABEL ^w. BIOS V1.40 W520 - 32bit - Normal    - ISO - (EN)
TEXT HELP
* Boot the W520 BIOS ISO image over PXE
ENDTEXT
LINUX memdisk
INITRD ../isos/bios/w520/8buj19uc.iso
APPEND iso raw
I need this feature, because we have several thinkpads to update!
Any help regard this topic is greatly appreciated

I had no clue what PXE is, so I looked it up:
The Preboot eXecution Environment (PXE, also known as Pre-Execution Environment; sometimes pronounced "pixie") is an environment to bootcomputers using a network interface independently of data storage devices (like hard disks) or installed operating systems.
http://en.wikipedia.org/wiki/Preboot_Execution_Environment
W520 4270CTO i7-2820QM Quadro2000M 1920x1080 Display 16GB RAM 2x240GB Intel 510 SSDs (RAID 0) - BIOS 1.42 - PCMark7:4,568
Samsung Series 9 15-inch NP900X4C-A03US - PCMark7: 4674

V210 hangs after "Hardware Watchdog Enabled" on boot

Hello,
as I wrote in the subject my SUN V210 hangs after "Hardware Watchdog Enabled" on boot. If I want to shutdown the system with the "power button" I am getting the message "WARNING: Failed to shut down the system!"..
This failure occures after I mounted the harddisk in another hardware enviroment.
I am administrating the SUN temporarily over a HyperTerminal connection to the serial management port.
What could the reason of this problem, and did someone know what I could do?
Thanks and Best Regards

Hi,
now I booted the system with one Solaris cdrom in the single user mode.
First I try a fsck:
# fsck -F ufs -o b=32 /dev/rdsk/c0t0d0s0
Alternate super block location: 32.
** /dev/rdsk/c0t0d0s0 (NO WRITE)
BAD SUPER BLOCK: MAGIC NUMBER WRONG
USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION;
eg. fsck [-F ufs] -o b=# [special ...]
where # is the alternate super block. SEE fsck_ufs(1M).So I try to find the next superblock.
# newfs -N /dev/rdsk/c0t0d0s0
mkfs: bad value for size: 640 must be between 1024 and 640
mkfs: size reset to default 640
Warning: inode blocks/cyl group (42) >= data blocks (40) in last
    cylinder group. This implies 640 sector(s) cannot be allocated.
/dev/rdsk/c0t0d0s0:     0 sectors in 0 cylinders of 1 tracks, 640 sectors
        0.0MB in 0 cyl groups (16 c/g, 5.00MB/g, 2432 i/g)
super-block backups (for fsck -F ufs -o b=#) at:But I did not get an alternative super-block no..
Did I have another chance?
To run installboot just for kicks. What do you mean with this?
To reinstall the bootblock with:
installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t0d0s0
Rgds
Message was edited by:
NetCohort

Mountain Lion hangs during boot sequence after reinstall

I am running Mountain Lion on a late-2012 Mac Mini (the newest one at this writing), and my system got messed up after I tried to reset my primary uid to 501 (I know, first mistake) after having migrated the system from an older Mac Mini. This worked partially, but I continued to have issues accessing some files and got tired of resetting the permissions manually.
I tried reinstalling Mountain Lion and since then, the system fails to boot completely. I can get as far as seeing the desktop, Finder menu, Dock, etc., but then one or more error windows pop up relating to specific resources (I think Calendar Agent was one of them, I can't remember because I then saw the spinning disk icon and the system stopped responding). I tried restarting by turning the computer off and then on again, but continue to get similar errors after it gets almost all the way through booting.
Although I have much of my data on the hard drive backed up to an external Seagate drive on my home network, I had not been able to do a complete backup because I have many old (pre-OS X) files that contain slashes or other characters no longer allowed in filenames, and it has proven too cumbersome to update all the filenames to make it worthwhile. Thus, I am not able to wipe the hard drive and start from scratch.
I know how to boot in Single-User mode, which does work, but don't know enough BSD/Darwin to pinpoint the source of this problem and fix it.
Any advice about how to diagnose and/or solve this problem? I would like to be able to correct any uid and gid conflicts that may be causing this, which I believe would work, but am not sure how to do this. I am writing this from Safari after booting in Recovery mode.
Thanks for any help with this. - Klingon725

Back up all data.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -Rh $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
The first step should give you usable permissions in your home folder. This step will restore special attributes set by OS X on some user folders to protect them from unintended deletion or renaming. You can skip this step if you don't consider that protection to be necessary.
Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
resetpassword
That's one word, all lower case, with no spaces. Then press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

P205-s6237 Hangs during boot to recovery after replace HDD

I replaced a bad HDD and the machine hangs during boot to the recovery disk. it gets past the inspecting screen and then hangs when the VISTA dots appear. the dots continue to scroll left to right but nothing ever happens. Any ideads on getting it past this point?

I replaced a bad HDD and the machine hangs during boot to the recovery disk. it gets past the inspecting screen and then hangs when the VISTA dots appear. the dots continue to scroll left to right but nothing ever happens. Any ideads on getting it past this point?

Hangs on boot after lion upgrade

I've upgraded to Lion and since upgrading my macbook pro hangs when booting about 4 out of 10 times. I get to the desktop and then get a never-ending spinning color wheel.
2.8 Gb core 2 duo
8 GB ram
Summer 2009 model

When you boot in single user or safe mode, all third party software is prevented from started. So it is possbile one of your third party party applications that are starting at boot is not compatable with the new RAM. I would try turning it all off and then test them all each in turn.
Allan

Deployment hangs after boot

Similar Messages

Maybe you are looking for