Makepkg Kernel 2.6.23.16 -- How to
Hi... I want some help to build PKBUILD for 2.6.23.16 kernel.
I've downloaded the 2.6.23.14 PKBUILD file from Arch CVS ( http://cvs.archlinux.org/cgi-bin/viewcv … cvs-markup ) and I want to modify it to build de 2.6.23.16 kernel.
How can I do it?
And what about the patches? Are the patches the same as 2.6.24.1?
Of course, I don't want to update my kernel to 2.6.24.1 version (I could do it with pacman -Syu)!
Thanks...
Hi
I'm also having that issue.
My kernel: 2.6.23.8-1
My Processor: Pentium 4 mobile (using acpi-cpufreq...)
My dmesg code:
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c010ac33>] sched_clock+0x13/0x30
[<c0104ee7>] common_interrupt+0x23/0x28
[<dcf460b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
Similar Messages
-
powerbook g4 - does not start up...it shows kernel panic screen...how do i fix/resolve this problem?
In the overwhelming majority of cases, kernel panic indicates a severe hardware problem. Braby and Allan pointed to useful things. If you can boot from CD / DVD and reinstall without any kernel panic, then may be a software problem, but this is less probable. You must check, anyway.
If you have a 2nd mac around and a firewire cable, you may try to restart the ill mac in target mode and connect it to a healthy mac to see whether it may be used in target mode. -
Mid 2010 Macbook Pro Keeps Restarting due to Kernel Panic. Ideas for how to fix?
So my Mid 2010 Macbook Pro keeps randomly restarting, and giving me a screen that says something like "your computer restarted due to a problem."
Looks like it as a kernel panic, but I have no idea what this is. Seems to be no pattern for when it crashes. Used to do it maybe once a month and now this is the 5th time in two days.
Any idea what might be going on? Looked at past threads but nothing seemed to apply.
Here's the issue report:
Interval Since Last Panic Report: 3966250 sec
Panics Since Last Report: 13
Anonymous UUID: 7A9C4557-3A15-F201-C5F0-248B698BCE76
Sun Mar 3 14:26:35 2013
panic(cpu 3 caller 0xffffff7f85c9bb25): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff811930d000 0x0a5480a2, D0, P2/4
Backtrace (CPU 3), Frame : Return Address
0xffffff80edd0b260 : 0xffffff800541d626
0xffffff80edd0b2d0 : 0xffffff7f85c9bb25
0xffffff80edd0b360 : 0xffffff7f85d954b3
0xffffff80edd0b3c0 : 0xffffff7f85d95527
0xffffff80edd0b430 : 0xffffff7f860aa853
0xffffff80edd0b570 : 0xffffff7f85dbb659
0xffffff80edd0b5a0 : 0xffffff7f85ca58da
0xffffff80edd0b650 : 0xffffff7f85ca0fac
0xffffff80edd0b840 : 0xffffff7f85ca2ade
0xffffff80edd0b920 : 0xffffff7f86dccad5
0xffffff80edd0b960 : 0xffffff7f86de2507
0xffffff80edd0b980 : 0xffffff7f86e01353
0xffffff80edd0b9c0 : 0xffffff7f86e013b1
0xffffff80edd0ba00 : 0xffffff7f86de7c43
0xffffff80edd0ba50 : 0xffffff7f86da20fc
0xffffff80edd0bae0 : 0xffffff7f86d9defa
0xffffff80edd0bb10 : 0xffffff7f86d9baab
0xffffff80edd0bb40 : 0xffffff80058650c3
0xffffff80edd0bbc0 : 0xffffff8005867153
0xffffff80edd0bc20 : 0xffffff8005864b8f
0xffffff80edd0bd70 : 0xffffff80054981e1
0xffffff80edd0be80 : 0xffffff8005420aed
0xffffff80edd0beb0 : 0xffffff8005410448
0xffffff80edd0bf00 : 0xffffff800541961b
0xffffff80edd0bf70 : 0xffffff80054a5b16
0xffffff80edd0bfb0 : 0xffffff80054ced53
Kernel Extensions in backtrace:
com.apple.NVDAResman(8.0)[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f85c34 000->0xffffff7f85f36fff
dependency: com.apple.iokit.IOPCIFamily(2.7.1)[9901C237-547C-3B52-99DE-C4870A19E2B5]@0xffff ff7f859bf000
dependency: com.apple.iokit.IONDRVSupport(2.3.5)[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xff ffff7f85c20000
dependency: com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7f85bdd000
com.apple.nvidia.nv50hal(8.0)[9F3D09B5-3158-3D9E-BDA3-E71576AAD3B7]@0xffffff7f8 5f44000->0xffffff7f86266fff
dependency: com.apple.NVDAResman(8.0.0)[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f85c 34000
dependency: com.apple.iokit.IOPCIFamily(2.7.1)[9901C237-547C-3B52-99DE-C4870A19E2B5]@0xffff ff7f859bf000
com.apple.GeForce(8.0)[2E56ED9A-D848-3795-9E52-56BABDC9000C]@0xffffff7f86d83000 ->0xffffff7f86e45fff
dependency: com.apple.NVDAResman(8.0.0)[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f85c 34000
dependency: com.apple.iokit.IONDRVSupport(2.3.5)[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xff ffff7f85c20000
dependency: com.apple.iokit.IOPCIFamily(2.7.1)[9901C237-547C-3B52-99DE-C4870A19E2B5]@0xffff ff7f859bf000
dependency: com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7f85bdd000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
12C54
Kernel version:
Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333
Kernel slide: 0x0000000005200000
Kernel text base: 0xffffff8005400000
System model name: MacBookPro6,2 (Mac-F22586C8)
System uptime in nanoseconds: 13893412243014
last loaded kext at 739492449806: com.apple.filesystems.smbfs 1.8 (addr 0xffffff7f8793f000, size 229376)
last unloaded kext at 341224120991: com.apple.driver.AppleUSBUHCI 5.2.5 (addr 0xffffff7f86496000, size 65536)
loaded kexts:
com.silex.driver.sxuptp 1.5.1
com.jft.driver.PdaNetDrv 1.0.64
com.apple.filesystems.smbfs 1.8
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AGPM 100.12.69
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleHDA 2.3.1f2
com.apple.driver.AppleMikeyHIDDriver 122
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.AppleSMCLMU 2.0.2d0
com.apple.driver.AppleUpstreamUserClient 3.5.10
com.apple.driver.AppleMCCSControl 1.0.33
com.apple.driver.AppleIntelHDGraphics 8.0.0
com.apple.driver.AppleIntelHDGraphicsFB 8.0.0
com.apple.driver.AppleMuxControl 3.2.11
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.iokit.IOBluetoothSerialManager 4.0.9f33
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.ApplePolicyControl 3.2.11
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleMikeyDriver 2.3.1f2
com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport 4.0.9f33
com.apple.GeForce 8.0.0
com.apple.driver.AppleLPC 1.6.0
com.apple.driver.SMCMotionSensor 3.0.2d6
com.apple.driver.AppleUSBTCButtons 235.4
com.apple.driver.AppleUSBCardReader 3.1.0
com.apple.driver.AppleUSBTCKeyboard 235.4
com.apple.driver.AppleIRController 320.15
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 34
com.apple.iokit.SCSITaskUserClient 3.5.1
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.2.2
com.apple.driver.AppleUSBHub 5.2.5
com.apple.driver.AirPort.Brcm4331 602.15.22
com.apple.driver.AppleFWOHCI 4.9.6
com.apple.driver.AppleAHCIPort 2.4.1
com.apple.iokit.AppleBCM5701Ethernet 3.2.5b3
com.apple.driver.AppleUSBEHCI 5.4.0
com.apple.driver.AppleEFINVRAM 1.6.1
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleACPIButtons 1.6
com.apple.driver.AppleRTC 1.5
com.apple.driver.AppleHPET 1.7
com.apple.driver.AppleSMBIOS 1.9
com.apple.driver.AppleACPIEC 1.6
com.apple.driver.AppleAPIC 1.6
com.apple.driver.AppleIntelCPUPowerManagementClient 196.0.0
com.apple.nke.applicationfirewall 4.0.39
com.apple.security.quarantine 2
com.apple.driver.AppleIntelCPUPowerManagement 196.0.0
com.apple.kext.triggers 1.0
com.apple.driver.DspFuncLib 2.3.1f2
com.apple.iokit.IOAudioFamily 1.8.9fc10
com.apple.kext.OSvKernDSPLib 1.6
com.apple.iokit.IOFireWireIP 2.2.5
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.iokit.IOSurface 86.0.3
com.apple.iokit.IOSerialFamily 10.0.6
com.apple.iokit.IOBluetoothFamily 4.0.9f33
com.apple.driver.AppleGraphicsControl 3.2.11
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.AppleSMBusController 1.0.10d0
com.apple.driver.AppleSMBusPCI 1.0.10d0
com.apple.iokit.AppleBluetoothHCIControllerUSBTransport 4.0.9f33
com.apple.nvidia.nv50hal 8.0.0
com.apple.NVDAResman 8.0.0
com.apple.iokit.IONDRVSupport 2.3.5
com.apple.driver.AppleHDAController 2.3.1f2
com.apple.iokit.IOGraphicsFamily 2.3.5
com.apple.iokit.IOHDAFamily 2.3.1f2
com.apple.driver.IOPlatformPluginFamily 5.2.0d16
com.apple.driver.AppleSMC 3.1.4d2
com.apple.iokit.IOSCSIBlockCommandsDevice 3.5.1
com.apple.iokit.IOUSBMassStorageClass 3.5.0
com.apple.driver.AppleUSBMultitouch 235.7
com.apple.iokit.IOUSBHIDDriver 5.2.5
com.apple.driver.AppleUSBMergeNub 5.2.5
com.apple.driver.AppleUSBComposite 5.2.5
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.5.1
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOAHCISerialATAPI 2.5.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.5.1
com.apple.iokit.IOUSBUserClient 5.2.5
com.apple.iokit.IO80211Family 500.15
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.iokit.IOAHCIFamily 2.2.1
com.apple.iokit.IOEthernetAVBController 1.0.2b1
com.apple.iokit.IONetworkingFamily 3.0
com.apple.iokit.IOUSBFamily 5.4.0
com.apple.driver.AppleEFIRuntime 1.6.1
com.apple.iokit.IOHIDFamily 1.8.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 220
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.DiskImages 344
com.apple.iokit.IOStorageFamily 1.8
com.apple.driver.AppleKeyStore 28.21
com.apple.driver.AppleACPIPlatform 1.6
com.apple.iokit.IOPCIFamily 2.7.1
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
Model: MacBookPro6,2, BootROM MBP61.0057.B0F, 2 processors, Intel Core i5, 2.4 GHz, 8 GB, SMC 1.58f16
Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB
Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 256 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x857F, 0x483634353155363446373036364700000000
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x8634, 0x535550455254414C454E5430310000000000
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.81.22)
Bluetooth: Version 4.0.9f33 10885, 2 service, 18 devices, 1 incoming serial ports
Network Service: Ethernet Adaptor (en2), Ethernet, en2
Network Service: AirPort, AirPort, en1
Serial ATA Device: TOSHIBA MK3255GSXF, 320.07 GB
Serial ATA Device: HL-DT-ST DVDRW GS23N
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfa100000 / 2
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0236, 0xfa120000 / 5
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8218, 0xfa113000 / 8
USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfa130000 / 3
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2
USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0xfd110000 / 4
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 3So my Mid 2010 Macbook Pro keeps randomly restarting, and giving me a screen that says something like "your computer restarted due to a problem."
Looks like it as a kernel panic, but I have no idea what this is. Seems to be no pattern for when it crashes. Used to do it maybe once a month and now this is the 5th time in two days.
Any idea what might be going on? Looked at past threads but nothing seemed to apply.
Here's the issue report:
Interval Since Last Panic Report: 3966250 sec
Panics Since Last Report: 13
Anonymous UUID: 7A9C4557-3A15-F201-C5F0-248B698BCE76
Sun Mar 3 14:26:35 2013
panic(cpu 3 caller 0xffffff7f85c9bb25): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff811930d000 0x0a5480a2, D0, P2/4
Backtrace (CPU 3), Frame : Return Address
0xffffff80edd0b260 : 0xffffff800541d626
0xffffff80edd0b2d0 : 0xffffff7f85c9bb25
0xffffff80edd0b360 : 0xffffff7f85d954b3
0xffffff80edd0b3c0 : 0xffffff7f85d95527
0xffffff80edd0b430 : 0xffffff7f860aa853
0xffffff80edd0b570 : 0xffffff7f85dbb659
0xffffff80edd0b5a0 : 0xffffff7f85ca58da
0xffffff80edd0b650 : 0xffffff7f85ca0fac
0xffffff80edd0b840 : 0xffffff7f85ca2ade
0xffffff80edd0b920 : 0xffffff7f86dccad5
0xffffff80edd0b960 : 0xffffff7f86de2507
0xffffff80edd0b980 : 0xffffff7f86e01353
0xffffff80edd0b9c0 : 0xffffff7f86e013b1
0xffffff80edd0ba00 : 0xffffff7f86de7c43
0xffffff80edd0ba50 : 0xffffff7f86da20fc
0xffffff80edd0bae0 : 0xffffff7f86d9defa
0xffffff80edd0bb10 : 0xffffff7f86d9baab
0xffffff80edd0bb40 : 0xffffff80058650c3
0xffffff80edd0bbc0 : 0xffffff8005867153
0xffffff80edd0bc20 : 0xffffff8005864b8f
0xffffff80edd0bd70 : 0xffffff80054981e1
0xffffff80edd0be80 : 0xffffff8005420aed
0xffffff80edd0beb0 : 0xffffff8005410448
0xffffff80edd0bf00 : 0xffffff800541961b
0xffffff80edd0bf70 : 0xffffff80054a5b16
0xffffff80edd0bfb0 : 0xffffff80054ced53
Kernel Extensions in backtrace:
com.apple.NVDAResman(8.0)[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f85c34 000->0xffffff7f85f36fff
dependency: com.apple.iokit.IOPCIFamily(2.7.1)[9901C237-547C-3B52-99DE-C4870A19E2B5]@0xffff ff7f859bf000
dependency: com.apple.iokit.IONDRVSupport(2.3.5)[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xff ffff7f85c20000
dependency: com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7f85bdd000
com.apple.nvidia.nv50hal(8.0)[9F3D09B5-3158-3D9E-BDA3-E71576AAD3B7]@0xffffff7f8 5f44000->0xffffff7f86266fff
dependency: com.apple.NVDAResman(8.0.0)[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f85c 34000
dependency: com.apple.iokit.IOPCIFamily(2.7.1)[9901C237-547C-3B52-99DE-C4870A19E2B5]@0xffff ff7f859bf000
com.apple.GeForce(8.0)[2E56ED9A-D848-3795-9E52-56BABDC9000C]@0xffffff7f86d83000 ->0xffffff7f86e45fff
dependency: com.apple.NVDAResman(8.0.0)[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f85c 34000
dependency: com.apple.iokit.IONDRVSupport(2.3.5)[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xff ffff7f85c20000
dependency: com.apple.iokit.IOPCIFamily(2.7.1)[9901C237-547C-3B52-99DE-C4870A19E2B5]@0xffff ff7f859bf000
dependency: com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7f85bdd000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
12C54
Kernel version:
Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333
Kernel slide: 0x0000000005200000
Kernel text base: 0xffffff8005400000
System model name: MacBookPro6,2 (Mac-F22586C8)
System uptime in nanoseconds: 13893412243014
last loaded kext at 739492449806: com.apple.filesystems.smbfs 1.8 (addr 0xffffff7f8793f000, size 229376)
last unloaded kext at 341224120991: com.apple.driver.AppleUSBUHCI 5.2.5 (addr 0xffffff7f86496000, size 65536)
loaded kexts:
com.silex.driver.sxuptp 1.5.1
com.jft.driver.PdaNetDrv 1.0.64
com.apple.filesystems.smbfs 1.8
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AGPM 100.12.69
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleHDA 2.3.1f2
com.apple.driver.AppleMikeyHIDDriver 122
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.AppleSMCLMU 2.0.2d0
com.apple.driver.AppleUpstreamUserClient 3.5.10
com.apple.driver.AppleMCCSControl 1.0.33
com.apple.driver.AppleIntelHDGraphics 8.0.0
com.apple.driver.AppleIntelHDGraphicsFB 8.0.0
com.apple.driver.AppleMuxControl 3.2.11
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.iokit.IOBluetoothSerialManager 4.0.9f33
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.ApplePolicyControl 3.2.11
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleMikeyDriver 2.3.1f2
com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport 4.0.9f33
com.apple.GeForce 8.0.0
com.apple.driver.AppleLPC 1.6.0
com.apple.driver.SMCMotionSensor 3.0.2d6
com.apple.driver.AppleUSBTCButtons 235.4
com.apple.driver.AppleUSBCardReader 3.1.0
com.apple.driver.AppleUSBTCKeyboard 235.4
com.apple.driver.AppleIRController 320.15
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 34
com.apple.iokit.SCSITaskUserClient 3.5.1
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.2.2
com.apple.driver.AppleUSBHub 5.2.5
com.apple.driver.AirPort.Brcm4331 602.15.22
com.apple.driver.AppleFWOHCI 4.9.6
com.apple.driver.AppleAHCIPort 2.4.1
com.apple.iokit.AppleBCM5701Ethernet 3.2.5b3
com.apple.driver.AppleUSBEHCI 5.4.0
com.apple.driver.AppleEFINVRAM 1.6.1
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleACPIButtons 1.6
com.apple.driver.AppleRTC 1.5
com.apple.driver.AppleHPET 1.7
com.apple.driver.AppleSMBIOS 1.9
com.apple.driver.AppleACPIEC 1.6
com.apple.driver.AppleAPIC 1.6
com.apple.driver.AppleIntelCPUPowerManagementClient 196.0.0
com.apple.nke.applicationfirewall 4.0.39
com.apple.security.quarantine 2
com.apple.driver.AppleIntelCPUPowerManagement 196.0.0
com.apple.kext.triggers 1.0
com.apple.driver.DspFuncLib 2.3.1f2
com.apple.iokit.IOAudioFamily 1.8.9fc10
com.apple.kext.OSvKernDSPLib 1.6
com.apple.iokit.IOFireWireIP 2.2.5
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.iokit.IOSurface 86.0.3
com.apple.iokit.IOSerialFamily 10.0.6
com.apple.iokit.IOBluetoothFamily 4.0.9f33
com.apple.driver.AppleGraphicsControl 3.2.11
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.AppleSMBusController 1.0.10d0
com.apple.driver.AppleSMBusPCI 1.0.10d0
com.apple.iokit.AppleBluetoothHCIControllerUSBTransport 4.0.9f33
com.apple.nvidia.nv50hal 8.0.0
com.apple.NVDAResman 8.0.0
com.apple.iokit.IONDRVSupport 2.3.5
com.apple.driver.AppleHDAController 2.3.1f2
com.apple.iokit.IOGraphicsFamily 2.3.5
com.apple.iokit.IOHDAFamily 2.3.1f2
com.apple.driver.IOPlatformPluginFamily 5.2.0d16
com.apple.driver.AppleSMC 3.1.4d2
com.apple.iokit.IOSCSIBlockCommandsDevice 3.5.1
com.apple.iokit.IOUSBMassStorageClass 3.5.0
com.apple.driver.AppleUSBMultitouch 235.7
com.apple.iokit.IOUSBHIDDriver 5.2.5
com.apple.driver.AppleUSBMergeNub 5.2.5
com.apple.driver.AppleUSBComposite 5.2.5
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.5.1
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOAHCISerialATAPI 2.5.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.5.1
com.apple.iokit.IOUSBUserClient 5.2.5
com.apple.iokit.IO80211Family 500.15
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.iokit.IOAHCIFamily 2.2.1
com.apple.iokit.IOEthernetAVBController 1.0.2b1
com.apple.iokit.IONetworkingFamily 3.0
com.apple.iokit.IOUSBFamily 5.4.0
com.apple.driver.AppleEFIRuntime 1.6.1
com.apple.iokit.IOHIDFamily 1.8.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 220
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.DiskImages 344
com.apple.iokit.IOStorageFamily 1.8
com.apple.driver.AppleKeyStore 28.21
com.apple.driver.AppleACPIPlatform 1.6
com.apple.iokit.IOPCIFamily 2.7.1
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
Model: MacBookPro6,2, BootROM MBP61.0057.B0F, 2 processors, Intel Core i5, 2.4 GHz, 8 GB, SMC 1.58f16
Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB
Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 256 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x857F, 0x483634353155363446373036364700000000
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x8634, 0x535550455254414C454E5430310000000000
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.81.22)
Bluetooth: Version 4.0.9f33 10885, 2 service, 18 devices, 1 incoming serial ports
Network Service: Ethernet Adaptor (en2), Ethernet, en2
Network Service: AirPort, AirPort, en1
Serial ATA Device: TOSHIBA MK3255GSXF, 320.07 GB
Serial ATA Device: HL-DT-ST DVDRW GS23N
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfa100000 / 2
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0236, 0xfa120000 / 5
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8218, 0xfa113000 / 8
USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfa130000 / 3
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2
USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0xfd110000 / 4
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 3 -
This has to be my all time biggest screw up to date since using Linux!
WHY:
I've had one of my Ubuntu installs hacked and patched to support Nvidia GT220 HDMI audio out months ago, but thought I'd just wait for nvidia, alsa and/or the Linux kernel for support in the future for my Arch install. Well today, I read that the new 2.6.34 kernel has built in support for it....WooHoo!!
I thought I just had to enable the testing repo and upgrade the kernel. etc...
HOW:
So I temporarily enabled testing, and using my handy GTKPacman, upgraded to 2.6.34, or so I thought.
Upon rebooting, I discovered that I was still running 2.6.32, so next I install all the 2.6.34 stuff and delete all the 2.6.33 stuff.
Reboot error to kernel is now MISSING! Oh S%$T, now what!
HOW I Restored It:
After a quick attempt to use a Ubuntu kernel copied to Arch on the same computer and failure.....
I googled arch kernel restore. with my other computer, which leads me to http://wiki.archlinux.org/index.php/Ker … all_kernel
As always when I screw something up, Arch WIKI to the rescue!!! Boot into my Arch live CD.
Next problem, I don't remember what partition numbers are boot and root, so boot back to Ubuntu, get partition info, back to live CD.
Now I get chrooted into my Arch install, but don't know the exact kernel file details....back to ........
So I finally get all the info to restore Arch via the chroot live CD method.
I'm thinking that I should have known, and should have just navigated the file system for the info I needed via chroot live CD, but it didn't sink in till it was all over. Chroot/live CD = installed Arch file system.
I also know that Arch is directed more towards "experienced" Linux users, and they know all this, but....
Would it benefit anyone other than me, for the above mentioned WIKI, to remind or hint, along with instructions, at getting the required info via as part of the live CD kernel restore process??
Just a thought....
Last edited by jeff story (2010-05-31 21:10:03)Figured out the kernel upgrade issue I had.
GTK pacman did not indicate any problems but the command line did.
[root@Arch2009p2 jeff]# pacman -S testing/kernel26
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: nvidia: requires kernel26<2.6.34
So I
[root@Arch2009p2 jeff]# pacman -S testing/nvidia
resolving dependencies...
looking for inter-conflicts...
Targets (4): kernel26-firmware-2.6.34-1 kernel26-2.6.34-1 nvidia-utils-195.36.24-2 nvidia-195.36.24-2
Total Download Size: 35.52 MB
Total Installed Size: 172.96 MB
Proceed with installation? [Y/n] y
:: Retrieving packages from testing...
kernel26-firmware-2... 804.9K 151.2K/s 00:00:05 [################################################################] 100%
kernel26-2.6.34-1-x... 22.8M 139.4K/s 00:02:47 [################################################################] 100%
nvidia-utils-195.36... 9.8M 130.0K/s 00:01:17 [################################################################] 100%
nvidia-195.36.24-2-... 2.1M 106.4K/s 00:00:21 [################################################################] 100%
checking package integrity...
(4/4) checking for file conflicts [################################################################] 100%
(1/4) upgrading kernel26-firmware [################################################################] 100%
(2/4) upgrading kernel26 [################################################################] 100%
>>> Updating module dependencies. Please wait ...
>>> MKINITCPIO SETUP
>>> ----------------
>>> If you use LVM2, Encrypted root or software RAID,
>>> Ensure you enable support in /etc/mkinitcpio.conf .
>>> More information about mkinitcpio setup can be found here:
>>> http://wiki.archlinux.org/index.php/Mkinitcpio
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.34-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
WARNING: All config files need .conf: /etc/modprobe.d/framebuffer_blacklist.pacsave, it will be ignored in a future release.
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26.img'...SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.34-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26-fallback.img'...SUCCESS
==> SUCCESS
(3/4) upgrading nvidia-utils [################################################################] 100%
(4/4) upgrading nvidia [################################################################] 100%
ERROR: Module nvidia is in use
In order to use the new nvidia module, exit Xserver and unload it manually.
Upon reboot I get
[jeff@Arch2009p2 ~]$ uname -a
Linux Arch2009p2 2.6.34-ARCH #1 SMP PREEMPT Mon May 17 09:29:00 CEST 2010 x86_64 AMD Phenom(tm) 9850 Quad-Core Processor AuthenticAMD GNU/Linux
Now going to test HDMI audio output.
And it works great!!!
Last edited by jeff story (2010-06-01 02:08:37) -
How to delay for 1 millisecond in the kernel?
I've been using the delay(9F) but the timer resolution is in ticks (which from what I understand one tick is 1/100 second). There's another call drv_usecwait(9F) I can wait for a number of microseconds. Unfortunately the drv_usecwait() is a busy-wait delay which I don't like. Does anyone know of a way for delaying a number of milliseconds in the kernel?
-- jienhuaHi Divija,
>><i>how can i check for the field lengths</i>
Since you need to basically check if the field has a value or not, i dnt think you need to check for the length of the field. Instead, you can use any one of the booloean functions available in the graphical mapping editor to check if the field has a value or not(filed value true or false)
>><i>how do i send it back to the original folder.</i>
You can maintain a flag variable in the target structure such that if any of the source fields donot have values, the flag's value becomes 1 else it remains 0.
Now, you can check if the value of flag is equal to 1/0 in the bpm and accordingly send the data.
If in case, you donot want the flag to come in the target file that is loaded/sent from the bpm in the end, i think even tat can be taklen care of.
You can create two receiver communication channels and define one file adapter in each such that one has the destination as the actual target directory and the other has the original source directory as the destination.
Regards,
Sushumna -
How to communicate wite kernel module
After a kernel module was loaded successfully, how to communicate wite this kernel module like change the status of the kernel module.
In Linux, I can use /proc file to do that. But, In solaris, /proc file is just used for processors.
Now, how can I communicate write my kernel module? Can I use /proc file to do that like in Linux?Hello,
<ul>
<li>forget /proc, the procfs is for process table only on solaris
<li>if the kernel module is "driver" type you can use standard read/write/ioctl ... on block/charcter in dev (see OpenSolaris community and documentation Writing Device Drivers)
<li>there are other types of kernel modules such as streams, filesystems, schedulers ...
<li>the kernel module can export some symbols to see it from mdb (see blog)
<li>...
</ul>
<br>
M.C> -
Hello,
in Vision Assistant it is possible to create filter kernel of arbitrary size, like e.g. a 75x75 Gaussian kernel. These kernels feature integer-only elements. I tried to find a function in the Vision Development Module, but have been unable to find something so far. So I still create a Vision Assistant script with such a kernel and export it to a LabVIEW VI in order to abtain such a kernel. Any ideas on how to create such kernels programmatically?-You can generate custom kernels in LabVIEW also, but you need to have either string or numerical of that kernels. Without these two, i am not sure of how to do this.
-Please check this for building kernels.
http://zone.ni.com/reference/en-XX/help/370281M-01/imaqvision/imaq_buildkernel/
-Let's say you are able to programmatically generate kernel string, it will convert to kernel in double format automatically and connect this to convolute vi.
Thanks
uday,
Please Mark the solution as accepted if your problem is solved and help author by clicking on kudoes
Certified LabVIEW Associate Developer (CLAD) Using LV13 -
Hi!
I wan't to edit and compile my own kernel, so I got even more structure on my machine - and I hope to get a little more performance.
How do I edit and Compile a custom kernel?
[EDIT] And maybe how I make all my own-compiled programs to be compiled to a Pentium4 processor As i could when I was a Gentoo userKris;
There is a wiki for custom kernel generation.
Basically, you can use ABS to obtain the basic kernel and its accompanying patches and config file. ABS is Arch Build System which somewhat automates the making of packages, including custom kernels.
Just run abs in CL and find the download in /var/abs/kernels.
The kernel you desire to customize is found therein.
You customize it by modifying the kernelconfig and setup PKGBUILD file.
Run "makepkg" on the PKGBUILD and then run pacman -A (name of custom kernel.pkg.tar.gz). If using lilo run/sbin/lilo before reboot.
The steps are outlined in the wikis.
Best of luck!!! -
Hi there.
Yesterday about at the same time I had a first kernel panic about 1-2 min after gnome loaded (my caps-lock and scroll-lock blinked).
Today during the boot I had a kernel panic after the line "Doing something with ACPI" - there was a long message and after 30 (60?) seconds the pc rebooted. I dug all the logs I have and couldn't fine anything related, if you could point me to a specific log to look at would be nice.
Last updates:
[2010-02-01 21:29] synchronizing package lists
[2010-02-01 21:29] starting full system upgrade
[2010-02-01 21:30] removed firefox-branded (3.5.7-1)
[2010-02-01 21:30] synchronizing package lists
[2010-02-01 21:33] installed firefox (3.5.7-1)
[2010-02-01 21:34] synchronizing package lists
[2010-02-01 21:34] starting full system upgrade
[2010-02-01 21:37] upgraded bash (4.0.035-1 -> 4.1.002-1)
[2010-02-01 21:43] upgraded bash (4.1.002-1 -> 4.0.033-1)
[2010-02-01 21:45] upgraded bash (4.0.033-1 -> 4.1.002-1)
[2010-02-01 21:47] upgraded bash (4.1.002-1 -> 4.0.033-1)
[2010-02-01 22:04] installed automake (1.11.1-1)
uname -a
Linux werewolf 2.6.31-ARCH #1 SMP PREEMPT Tue Nov 10 19:48:17 CET 2009 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux
everything.log for today
Feb 4 08:32:49 werewolf syslog-ng[3239]: syslog-ng starting up; version='3.0.4'
Feb 4 08:32:49 werewolf kernel: Linux version 2.6.31-ARCH (root@architect) (gcc version 4.4.2 (GCC) ) #1 SMP PREEMPT Tue Nov 10 19:48:17 CET 2009
Feb 4 08:32:49 werewolf kernel: KERNEL supported cpus:
Feb 4 08:32:49 werewolf kernel: Intel GenuineIntel
Feb 4 08:32:49 werewolf kernel: AMD AuthenticAMD
Feb 4 08:32:49 werewolf kernel: NSC Geode by NSC
Feb 4 08:32:49 werewolf kernel: Cyrix CyrixInstead
Feb 4 08:32:49 werewolf kernel: Centaur CentaurHauls
Feb 4 08:32:49 werewolf kernel: Transmeta GenuineTMx86
Feb 4 08:32:49 werewolf kernel: Transmeta TransmetaCPU
Feb 4 08:32:49 werewolf kernel: UMC UMC UMC UMC
Feb 4 08:32:50 werewolf kernel: BIOS-provided physical RAM map:
Feb 4 08:32:50 werewolf kernel: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
Feb 4 08:32:50 werewolf kernel: BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
Feb 4 08:32:50 werewolf kernel: BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
Feb 4 08:32:50 werewolf kernel: BIOS-e820: 0000000000100000 - 000000003ffb0000 (usable)
Feb 4 08:32:50 werewolf kernel: BIOS-e820: 000000003ffb0000 - 000000003ffc0000 (ACPI data)
Feb 4 08:32:50 werewolf kernel: BIOS-e820: 000000003ffc0000 - 000000003fff0000 (ACPI NVS)
Feb 4 08:32:50 werewolf kernel: BIOS-e820: 000000003fff0000 - 0000000040000000 (reserved)
Feb 4 08:32:50 werewolf kernel: BIOS-e820: 00000000ffba0000 - 0000000100000000 (reserved)
Feb 4 08:32:50 werewolf kernel: DMI 2.3 present.
Feb 4 08:32:50 werewolf kernel: AMI BIOS detected: BIOS may corrupt low RAM, working around it.
Feb 4 08:32:50 werewolf kernel: e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
Feb 4 08:32:50 werewolf kernel: last_pfn = 0x3ffb0 max_arch_pfn = 0x100000
Feb 4 08:32:50 werewolf kernel: MTRR default type: uncachable
Feb 4 08:32:50 werewolf kernel: MTRR fixed ranges enabled:
Feb 4 08:32:50 werewolf kernel: 00000-9FFFF write-back
Feb 4 08:32:50 werewolf kernel: A0000-DFFFF uncachable
Feb 4 08:32:50 werewolf kernel: E0000-EFFFF write-through
Feb 4 08:32:50 werewolf kernel: F0000-FFFFF write-protect
Feb 4 08:32:50 werewolf kernel: MTRR variable ranges enabled:
Feb 4 08:32:50 werewolf kernel: 0 base 000000000 mask FC0000000 write-back
Feb 4 08:32:50 werewolf kernel: 1 disabled
Feb 4 08:32:50 werewolf kernel: 2 disabled
Feb 4 08:32:50 werewolf kernel: 3 disabled
Feb 4 08:32:50 werewolf kernel: 4 disabled
Feb 4 08:32:50 werewolf kernel: 5 disabled
Feb 4 08:32:50 werewolf kernel: 6 disabled
Feb 4 08:32:50 werewolf kernel: 7 disabled
Feb 4 08:32:50 werewolf kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Feb 4 08:32:50 werewolf kernel: Scanning 0 areas for low memory corruption
Feb 4 08:32:50 werewolf kernel: modified physical RAM map:
Feb 4 08:32:50 werewolf kernel: modified: 0000000000000000 - 0000000000010000 (reserved)
Feb 4 08:32:50 werewolf kernel: modified: 0000000000010000 - 000000000009fc00 (usable)
Feb 4 08:32:50 werewolf kernel: modified: 000000000009fc00 - 00000000000a0000 (reserved)
Feb 4 08:32:50 werewolf kernel: modified: 00000000000e0000 - 0000000000100000 (reserved)
Feb 4 08:32:50 werewolf kernel: modified: 0000000000100000 - 000000003ffb0000 (usable)
Feb 4 08:32:50 werewolf kernel: modified: 000000003ffb0000 - 000000003ffc0000 (ACPI data)
Feb 4 08:32:50 werewolf kernel: modified: 000000003ffc0000 - 000000003fff0000 (ACPI NVS)
Feb 4 08:32:50 werewolf kernel: modified: 000000003fff0000 - 0000000040000000 (reserved)
Feb 4 08:32:50 werewolf kernel: modified: 00000000ffba0000 - 0000000100000000 (reserved)
Feb 4 08:32:50 werewolf kernel: initial memory mapped : 0 - 01800000
Feb 4 08:32:50 werewolf kernel: init_memory_mapping: 0000000000000000-00000000377fe000
Feb 4 08:32:50 werewolf kernel: 0000000000 - 0000400000 page 4k
Feb 4 08:32:50 werewolf kernel: 0000400000 - 0037400000 page 2M
Feb 4 08:32:50 werewolf kernel: 0037400000 - 00377fe000 page 4k
Feb 4 08:32:50 werewolf kernel: kernel direct mapping tables up to 377fe000 @ 10000-15000
Feb 4 08:32:50 werewolf kernel: RAMDISK: 3ff00000 - 3ff9fae9
Feb 4 08:32:50 werewolf kernel: Allocated new RAMDISK: 00100000 - 0019fae9
Feb 4 08:32:50 werewolf kernel: Move RAMDISK from 000000003ff00000 - 000000003ff9fae8 to 00100000 - 0019fae8
Feb 4 08:32:50 werewolf kernel: ACPI: RSDP 000fac50 00014 (v00 ACPIAM)
Feb 4 08:32:50 werewolf kernel: ACPI: RSDT 3ffb0000 00030 (v01 A M I OEMRSDT 05000529 MSFT 00000097)
Feb 4 08:32:50 werewolf kernel: ACPI: FACP 3ffb0200 00081 (v02 A M I OEMFACP 05000529 MSFT 00000097)
Feb 4 08:32:50 werewolf kernel: ACPI: DSDT 3ffb03f0 03864 (v01 A0165 A0165011 00000011 INTL 02002026)
Feb 4 08:32:50 werewolf kernel: ACPI: FACS 3ffc0000 00040
Feb 4 08:32:50 werewolf kernel: ACPI: APIC 3ffb0390 0005C (v01 A M I OEMAPIC 05000529 MSFT 00000097)
Feb 4 08:32:50 werewolf kernel: ACPI: OEMB 3ffc0040 0003F (v01 A M I OEMBIOS 05000529 MSFT 00000097)
Feb 4 08:32:50 werewolf kernel: ACPI: Local APIC address 0xfee00000
Feb 4 08:32:50 werewolf kernel: 135MB HIGHMEM available.
Feb 4 08:32:50 werewolf kernel: 887MB LOWMEM available.
Feb 4 08:32:50 werewolf kernel: mapped low ram: 0 - 377fe000
Feb 4 08:32:50 werewolf kernel: low ram: 0 - 377fe000
Feb 4 08:32:50 werewolf kernel: node 0 low ram: 00000000 - 377fe000
Feb 4 08:32:50 werewolf kernel: node 0 bootmap 00011000 - 00017f00
Feb 4 08:32:50 werewolf kernel: (9 early reservations) ==> bootmem [0000000000 - 00377fe000]
Feb 4 08:32:50 werewolf kernel: #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
Feb 4 08:32:50 werewolf kernel: #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
Feb 4 08:32:50 werewolf kernel: #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
Feb 4 08:32:50 werewolf kernel: #3 [0001000000 - 000156da44] TEXT DATA BSS ==> [0001000000 - 000156da44]
Feb 4 08:32:50 werewolf kernel: #4 [000009fc00 - 0000100000] BIOS reserved ==> [000009fc00 - 0000100000]
Feb 4 08:32:50 werewolf kernel: #5 [000156e000 - 0001574228] BRK ==> [000156e000 - 0001574228]
Feb 4 08:32:50 werewolf kernel: #6 [0000010000 - 0000011000] PGTABLE ==> [0000010000 - 0000011000]
Feb 4 08:32:50 werewolf kernel: #7 [0000100000 - 000019fae9] NEW RAMDISK ==> [0000100000 - 000019fae9]
Feb 4 08:32:50 werewolf kernel: #8 [0000011000 - 0000018000] BOOTMAP ==> [0000011000 - 0000018000]
Feb 4 08:32:50 werewolf kernel: found SMP MP-table at [c00ff780] ff780
Feb 4 08:32:50 werewolf kernel: Zone PFN ranges:
Feb 4 08:32:50 werewolf kernel: DMA 0x00000010 -> 0x00001000
Feb 4 08:32:50 werewolf kernel: Normal 0x00001000 -> 0x000377fe
Feb 4 08:32:50 werewolf kernel: HighMem 0x000377fe -> 0x0003ffb0
Feb 4 08:32:50 werewolf kernel: Movable zone start PFN for each node
Feb 4 08:32:50 werewolf kernel: early_node_map[2] active PFN ranges
Feb 4 08:32:50 werewolf kernel: 0: 0x00000010 -> 0x0000009f
Feb 4 08:32:50 werewolf kernel: 0: 0x00000100 -> 0x0003ffb0
Feb 4 08:32:50 werewolf kernel: On node 0 totalpages: 261951
Feb 4 08:32:50 werewolf kernel: free_area_init_node: node 0, pgdat c141b740, node_mem_map c1575200
Feb 4 08:32:50 werewolf kernel: DMA zone: 32 pages used for memmap
Feb 4 08:32:50 werewolf kernel: DMA zone: 0 pages reserved
Feb 4 08:32:50 werewolf kernel: DMA zone: 3951 pages, LIFO batch:0
Feb 4 08:32:50 werewolf kernel: Normal zone: 1744 pages used for memmap
Feb 4 08:32:50 werewolf kernel: Normal zone: 221486 pages, LIFO batch:31
Feb 4 08:32:50 werewolf kernel: HighMem zone: 272 pages used for memmap
Feb 4 08:32:50 werewolf kernel: HighMem zone: 34466 pages, LIFO batch:7
Feb 4 08:32:50 werewolf kernel: Using APIC driver default
Feb 4 08:32:50 werewolf kernel: ACPI: PM-Timer IO Port: 0x808
Feb 4 08:32:50 werewolf kernel: ACPI: Local APIC address 0xfee00000
Feb 4 08:32:50 werewolf kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Feb 4 08:32:50 werewolf kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Feb 4 08:32:50 werewolf kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
Feb 4 08:32:50 werewolf kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Feb 4 08:32:50 werewolf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 4 08:32:50 werewolf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 4 08:32:50 werewolf kernel: ACPI: IRQ0 used by override.
Feb 4 08:32:50 werewolf kernel: ACPI: IRQ2 used by override.
Feb 4 08:32:50 werewolf kernel: ACPI: IRQ9 used by override.
Feb 4 08:32:50 werewolf kernel: Enabling APIC mode: Flat. Using 1 I/O APICs
Feb 4 08:32:50 werewolf kernel: Using ACPI (MADT) for SMP configuration information
Feb 4 08:32:50 werewolf kernel: SMP: Allowing 2 CPUs, 0 hotplug CPUs
Feb 4 08:32:50 werewolf kernel: nr_irqs_gsi: 24
Feb 4 08:32:50 werewolf kernel: PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
Feb 4 08:32:50 werewolf kernel: PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
Feb 4 08:32:50 werewolf kernel: PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
Feb 4 08:32:50 werewolf kernel: Allocating PCI resources starting at 40000000 (gap: 40000000:bfba0000)
Feb 4 08:32:50 werewolf kernel: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
Feb 4 08:32:50 werewolf kernel: PERCPU: Embedded 14 pages at c1d7a000, static data 34332 bytes
Feb 4 08:32:50 werewolf kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 259903
Feb 4 08:32:50 werewolf kernel: Kernel command line: root=/dev/disk/by-uuid/4733c52b-9f33-47c5-aa40-7deb3c9ff6b3 ro vga=773
Feb 4 08:32:50 werewolf kernel: PID hash table entries: 4096 (order: 12, 16384 bytes)
Feb 4 08:32:50 werewolf kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Feb 4 08:32:50 werewolf kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Feb 4 08:32:50 werewolf kernel: Enabling fast FPU save and restore... done.
Feb 4 08:32:50 werewolf kernel: Enabling unmasked SIMD FPU exception support... done.
Feb 4 08:32:50 werewolf kernel: Initializing CPU#0
Feb 4 08:32:50 werewolf kernel: Initializing HighMem for node 0 (000377fe:0003ffb0)
Feb 4 08:32:50 werewolf kernel: Memory: 1032144k/1048256k available (3111k kernel code, 15364k reserved, 1120k data, 416k init, 138952k highmem)
Feb 4 08:32:50 werewolf kernel: virtual kernel memory layout:
Feb 4 08:32:50 werewolf kernel: fixmap : 0xfff1e000 - 0xfffff000 ( 900 kB)
Feb 4 08:32:50 werewolf kernel: pkmap : 0xff800000 - 0xffc00000 (4096 kB)
Feb 4 08:32:50 werewolf kernel: vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
Feb 4 08:32:50 werewolf kernel: lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
Feb 4 08:32:50 werewolf kernel: .init : 0xc1422000 - 0xc148a000 ( 416 kB)
Feb 4 08:32:50 werewolf kernel: .data : 0xc1309ddd - 0xc1421ea8 (1120 kB)
Feb 4 08:32:50 werewolf kernel: .text : 0xc1000000 - 0xc1309ddd (3111 kB)
Feb 4 08:32:50 werewolf kernel: Checking if this processor honours the WP bit even in supervisor mode...Ok.
Feb 4 08:32:50 werewolf kernel: SLUB: Genslabs=13, HWalign=128, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Feb 4 08:32:50 werewolf kernel: NR_IRQS:512
Feb 4 08:32:50 werewolf kernel: Fast TSC calibration using PIT
Feb 4 08:32:50 werewolf kernel: Detected 2998.577 MHz processor.
Feb 4 08:32:50 werewolf kernel: Console: colour dummy device 80x25
Feb 4 08:32:50 werewolf kernel: console [tty0] enabled
Feb 4 08:32:50 werewolf kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 5999.03 BogoMIPS (lpj=9995256)
Feb 4 08:32:50 werewolf kernel: Security Framework initialized
Feb 4 08:32:50 werewolf kernel: Mount-cache hash table entries: 512
Feb 4 08:32:50 werewolf kernel: CPU: Trace cache: 12K uops, L1 D cache: 16K
Feb 4 08:32:50 werewolf kernel: CPU: L2 cache: 2048K
Feb 4 08:32:50 werewolf kernel: CPU: Physical Processor ID: 0
Feb 4 08:32:50 werewolf kernel: CPU: Processor Core ID: 0
Feb 4 08:32:50 werewolf kernel: mce: CPU supports 4 MCE banks
Feb 4 08:32:50 werewolf kernel: Disabling lock debugging due to kernel taint
Feb 4 08:32:50 werewolf kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 4 08:32:50 werewolf kernel: using mwait in idle threads.
Feb 4 08:32:50 werewolf kernel: Performance Counters: no PMU driver, software counters only.
Feb 4 08:32:50 werewolf kernel: Checking 'hlt' instruction... OK.
Feb 4 08:32:50 werewolf kernel: ACPI: Core revision 20090521
Feb 4 08:32:50 werewolf kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Feb 4 08:32:50 werewolf kernel: CPU0: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 03
Feb 4 08:32:50 werewolf kernel: APIC calibration not consistent with PM-Timer: 313ms instead of 100ms
Feb 4 08:32:50 werewolf kernel: APIC delta adjusted to PM-Timer: 1249396 (3914523)
Feb 4 08:32:50 werewolf kernel: Booting processor 1 APIC 0x1 ip 0x6000
Feb 4 08:32:50 werewolf kernel: Initializing CPU#1
Feb 4 08:32:50 werewolf kernel: Calibrating delay using timer specific routine.. 5999.95 BogoMIPS (lpj=9995124)
Feb 4 08:32:50 werewolf kernel: CPU: Trace cache: 12K uops, L1 D cache: 16K
Feb 4 08:32:50 werewolf kernel: CPU: L2 cache: 2048K
Feb 4 08:32:50 werewolf kernel: CPU: Physical Processor ID: 0
Feb 4 08:32:50 werewolf kernel: CPU: Processor Core ID: 0
Feb 4 08:32:50 werewolf kernel: mce: CPU supports 4 MCE banks
Feb 4 08:32:50 werewolf kernel: CPU1: Thermal monitoring enabled (TM1)
Feb 4 08:32:50 werewolf kernel: x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
Feb 4 08:32:50 werewolf kernel: CPU1: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 03
Feb 4 08:32:50 werewolf kernel: checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Feb 4 08:32:50 werewolf kernel: Brought up 2 CPUs
Feb 4 08:32:50 werewolf kernel: Total of 2 processors activated (11999.98 BogoMIPS).
Feb 4 08:32:50 werewolf kernel: CPU0 attaching sched-domain:
Feb 4 08:32:50 werewolf kernel: domain 0: span 0-1 level SIBLING
Feb 4 08:32:50 werewolf kernel: groups: 0 1
Feb 4 08:32:50 werewolf kernel: CPU1 attaching sched-domain:
Feb 4 08:32:50 werewolf kernel: domain 0: span 0-1 level SIBLING
Feb 4 08:32:50 werewolf kernel: groups: 1 0
Feb 4 08:32:50 werewolf kernel: Booting paravirtualized kernel on bare hardware
Feb 4 08:32:50 werewolf kernel: NET: Registered protocol family 16
Feb 4 08:32:50 werewolf kernel: ACPI: bus type pci registered
Feb 4 08:32:50 werewolf kernel: PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=2
Feb 4 08:32:50 werewolf kernel: PCI: Using configuration type 1 for base access
Feb 4 08:32:50 werewolf kernel: bio: create slab <bio-0> at 0
Feb 4 08:32:50 werewolf kernel: ACPI: EC: Look up EC in DSDT
Feb 4 08:32:50 werewolf kernel: ACPI: Interpreter enabled
Feb 4 08:32:50 werewolf kernel: ACPI: (supports S0 S1 S3 S4 S5)
Feb 4 08:32:50 werewolf kernel: ACPI: Using IOAPIC for interrupt routing
Feb 4 08:32:50 werewolf kernel: ACPI Warning: Incorrect checksum in table [OEMB] - 08, should be FB 20090521 tbutils-246
Feb 4 08:32:50 werewolf kernel: ACPI: No dock devices found.
Feb 4 08:32:50 werewolf kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
Feb 4 08:32:50 werewolf kernel: pci 0000:00:00.0: Enabling MCH 'Overflow' Device
Feb 4 08:32:50 werewolf kernel: pci 0000:00:00.0: reg 10 32bit mmio: [0xdc000000-0xdfffffff]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:06.0: reg 10 32bit mmio: [0xfecf0000-0xfecf0fff]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1d.0: reg 20 io port: [0xc480-0xc49f]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1d.1: reg 20 io port: [0xc800-0xc81f]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1d.2: reg 20 io port: [0xc880-0xc89f]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1d.3: reg 20 io port: [0xcc00-0xcc1f]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1d.7: reg 10 32bit mmio: [0xf8fffc00-0xf8ffffff]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1d.7: PME# disabled
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.0: Force enabled HPET at 0xfed00000
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.0: quirk: region 0800-087f claimed by ICH4 ACPI/GPIO/TCO
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.0: quirk: region 0480-04bf claimed by ICH4 GPIO
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.1: reg 10 io port: [0x00-0x07]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.1: reg 14 io port: [0x00-0x03]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.1: reg 18 io port: [0x00-0x07]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.1: reg 1c io port: [0x00-0x03]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.1: reg 20 io port: [0xfc00-0xfc0f]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.1: reg 24 32bit mmio: [0x000000-0x0003ff]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.2: reg 10 io port: [0xbc00-0xbc07]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.2: reg 14 io port: [0xb880-0xb883]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.2: reg 18 io port: [0xb800-0xb807]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.2: reg 1c io port: [0xb480-0xb483]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.2: reg 20 io port: [0xb400-0xb40f]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.3: reg 20 io port: [0x400-0x41f]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.5: reg 10 io port: [0xc000-0xc0ff]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.5: reg 14 io port: [0xc400-0xc43f]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.5: reg 18 32bit mmio: [0xf8fff800-0xf8fff9ff]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.5: reg 1c 32bit mmio: [0xf8fff400-0xf8fff4ff]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.5: PME# supported from D0 D3hot D3cold
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1f.5: PME# disabled
Feb 4 08:32:50 werewolf kernel: pci 0000:01:00.0: reg 10 32bit mmio: [0xfa000000-0xfaffffff]
Feb 4 08:32:50 werewolf kernel: pci 0000:01:00.0: reg 14 32bit mmio: [0xe0000000-0xefffffff]
Feb 4 08:32:50 werewolf kernel: pci 0000:01:00.0: reg 18 32bit mmio: [0xf9000000-0xf9ffffff]
Feb 4 08:32:50 werewolf kernel: pci 0000:01:00.0: reg 30 32bit mmio: [0xfbee0000-0xfbefffff]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:01.0: bridge io port: [0xd000-0xdfff]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:01.0: bridge 32bit mmio: [0xf9000000-0xfbefffff]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:01.0: bridge 32bit mmio pref: [0xe0000000-0xf7ffffff]
Feb 4 08:32:50 werewolf kernel: pci 0000:02:05.0: reg 10 io port: [0xe800-0xe8ff]
Feb 4 08:32:50 werewolf kernel: pci 0000:02:05.0: reg 14 32bit mmio: [0xfbfffc00-0xfbfffcff]
Feb 4 08:32:50 werewolf kernel: pci 0000:02:05.0: supports D1 D2
Feb 4 08:32:50 werewolf kernel: pci 0000:02:05.0: PME# supported from D1 D2 D3hot D3cold
Feb 4 08:32:50 werewolf kernel: pci 0000:02:05.0: PME# disabled
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1e.0: transparent bridge
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1e.0: bridge io port: [0xe000-0xefff]
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1e.0: bridge 32bit mmio: [0xfbf00000-0xfbffffff]
Feb 4 08:32:50 werewolf kernel: pci_bus 0000:00: on NUMA node 0
Feb 4 08:32:50 werewolf kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Feb 4 08:32:50 werewolf kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT]
Feb 4 08:32:50 werewolf kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Feb 4 08:32:50 werewolf kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Feb 4 08:32:50 werewolf kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
Feb 4 08:32:50 werewolf kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 7 10 11 12 14 15)
Feb 4 08:32:50 werewolf kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Feb 4 08:32:50 werewolf kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Feb 4 08:32:50 werewolf kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Feb 4 08:32:50 werewolf kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Feb 4 08:32:50 werewolf kernel: PCI: Using ACPI for IRQ routing
Feb 4 08:32:50 werewolf kernel: NetLabel: Initializing
Feb 4 08:32:50 werewolf kernel: NetLabel: domain hash size = 128
Feb 4 08:32:50 werewolf kernel: NetLabel: protocols = UNLABELED CIPSOv4
Feb 4 08:32:50 werewolf kernel: NetLabel: unlabeled traffic allowed by default
Feb 4 08:32:50 werewolf kernel: hpet clockevent registered
Feb 4 08:32:50 werewolf kernel: HPET: 3 timers in total, 0 timers will be used for per-cpu timer
Feb 4 08:32:50 werewolf kernel: pnp: PnP ACPI init
Feb 4 08:32:50 werewolf kernel: ACPI: bus type pnp registered
Feb 4 08:32:50 werewolf kernel: pnp: PnP ACPI: found 13 devices
Feb 4 08:32:50 werewolf kernel: ACPI: ACPI bus type pnp unregistered
Feb 4 08:32:50 werewolf kernel: system 00:09: ioport range 0x290-0x297 has been reserved
Feb 4 08:32:50 werewolf kernel: system 00:0a: ioport range 0x4d0-0x4d1 has been reserved
Feb 4 08:32:50 werewolf kernel: system 00:0a: ioport range 0x800-0x87f has been reserved
Feb 4 08:32:50 werewolf kernel: system 00:0a: ioport range 0x480-0x4bf has been reserved
Feb 4 08:32:50 werewolf kernel: system 00:0a: iomem range 0xfed20000-0xfed8ffff has been reserved
Feb 4 08:32:50 werewolf kernel: system 00:0a: iomem range 0xffb00000-0xffbfffff could not be reserved
Feb 4 08:32:50 werewolf kernel: system 00:0b: iomem range 0xfec00000-0xfec00fff could not be reserved
Feb 4 08:32:50 werewolf kernel: system 00:0b: iomem range 0xfee00000-0xfee00fff has been reserved
Feb 4 08:32:50 werewolf kernel: system 00:0c: iomem range 0x0-0x9ffff could not be reserved
Feb 4 08:32:50 werewolf kernel: system 00:0c: iomem range 0xc0000-0xdffff could not be reserved
Feb 4 08:32:50 werewolf kernel: system 00:0c: iomem range 0xe0000-0xfffff could not be reserved
Feb 4 08:32:50 werewolf kernel: system 00:0c: iomem range 0x100000-0x3ffeffff could not be reserved
Feb 4 08:32:50 werewolf kernel: system 00:0c: iomem range 0xfff00000-0xffffffff has been reserved
Feb 4 08:32:50 werewolf kernel: pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
Feb 4 08:32:50 werewolf kernel: pci 0000:00:01.0: IO window: 0xd000-0xdfff
Feb 4 08:32:50 werewolf kernel: pci 0000:00:01.0: MEM window: 0xf9000000-0xfbefffff
Feb 4 08:32:50 werewolf kernel: pci 0000:00:01.0: PREFETCH window: 0xe0000000-0xf7ffffff
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1e.0: PCI bridge, secondary bus 0000:02
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1e.0: IO window: 0xe000-0xefff
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1e.0: MEM window: 0xfbf00000-0xfbffffff
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1e.0: PREFETCH window: disabled
Feb 4 08:32:50 werewolf kernel: pci 0000:00:1e.0: setting latency timer to 64
Feb 4 08:32:50 werewolf kernel: pci_bus 0000:00: resource 0 io: [0x00-0xffff]
Feb 4 08:32:50 werewolf kernel: pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
Feb 4 08:32:50 werewolf kernel: pci_bus 0000:01: resource 0 io: [0xd000-0xdfff]
Feb 4 08:32:50 werewolf kernel: pci_bus 0000:01: resource 1 mem: [0xf9000000-0xfbefffff]
Feb 4 08:32:50 werewolf kernel: pci_bus 0000:01: resource 2 pref mem [0xe0000000-0xf7ffffff]
Feb 4 08:32:50 werewolf kernel: pci_bus 0000:02: resource 0 io: [0xe000-0xefff]
Feb 4 08:32:50 werewolf kernel: pci_bus 0000:02: resource 1 mem: [0xfbf00000-0xfbffffff]
Feb 4 08:32:50 werewolf kernel: pci_bus 0000:02: resource 3 io: [0x00-0xffff]
Feb 4 08:32:50 werewolf kernel: pci_bus 0000:02: resource 4 mem: [0x000000-0xffffffff]
Feb 4 08:32:50 werewolf kernel: NET: Registered protocol family 2
Feb 4 08:32:50 werewolf kernel: IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
Feb 4 08:32:50 werewolf kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
Feb 4 08:32:50 werewolf kernel: TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
Feb 4 08:32:50 werewolf kernel: TCP: Hash tables configured (established 131072 bind 65536)
Feb 4 08:32:50 werewolf kernel: TCP reno registered
Feb 4 08:32:50 werewolf kernel: NET: Registered protocol family 1
Feb 4 08:32:50 werewolf kernel: Unpacking initramfs...
Feb 4 08:32:50 werewolf kernel: Freeing initrd memory: 638k freed
Feb 4 08:32:50 werewolf kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
Feb 4 08:32:50 werewolf kernel: apm: disabled - APM is not SMP safe.
Feb 4 08:32:50 werewolf kernel: Scanning for low memory corruption every 60 seconds
Feb 4 08:32:50 werewolf kernel: audit: initializing netlink socket (disabled)
Feb 4 08:32:50 werewolf kernel: type=2000 audit(1265272359.270:1): initialized
Feb 4 08:32:50 werewolf kernel: highmem bounce pool size: 64 pages
Feb 4 08:32:50 werewolf kernel: VFS: Disk quotas dquot_6.5.2
Feb 4 08:32:50 werewolf kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Feb 4 08:32:50 werewolf kernel: msgmni has been set to 1746
Feb 4 08:32:50 werewolf kernel: alg: No test for stdrng (krng)
Feb 4 08:32:50 werewolf kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
Feb 4 08:32:50 werewolf kernel: io scheduler noop registered
Feb 4 08:32:50 werewolf kernel: io scheduler anticipatory registered
Feb 4 08:32:50 werewolf kernel: io scheduler deadline registered
Feb 4 08:32:50 werewolf kernel: io scheduler cfq registered (default)
Feb 4 08:32:50 werewolf kernel: pci 0000:01:00.0: Boot video device
Feb 4 08:32:50 werewolf kernel: vesafb: framebuffer at 0xe0000000, mapped to 0xf8080000, using 1536k, total 262144k
Feb 4 08:32:50 werewolf kernel: vesafb: mode is 1024x768x8, linelength=1024, pages=3
Feb 4 08:32:50 werewolf kernel: vesafb: protected mode interface info at c000:d600
Feb 4 08:32:50 werewolf kernel: vesafb: pmi: set display start = c00cd636, set palette = c00cd6a0
Feb 4 08:32:50 werewolf kernel: vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da
Feb 4 08:32:50 werewolf kernel: vesafb: scrolling: redraw
Feb 4 08:32:50 werewolf kernel: vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0
Feb 4 08:32:50 werewolf kernel: Console: switching to colour frame buffer device 128x48
Feb 4 08:32:50 werewolf kernel: fb0: VESA VGA frame buffer device
Feb 4 08:32:50 werewolf kernel: isapnp: Scanning for PnP cards...
Feb 4 08:32:50 werewolf kernel: isapnp: No Plug & Play device found
Feb 4 08:32:50 werewolf kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Feb 4 08:32:50 werewolf kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Feb 4 08:32:50 werewolf kernel: 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Feb 4 08:32:50 werewolf kernel: input: Macintosh mouse button emulation as /devices/virtual/input/input0
Feb 4 08:32:50 werewolf kernel: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
Feb 4 08:32:50 werewolf kernel: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Feb 4 08:32:50 werewolf kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 4 08:32:50 werewolf kernel: mice: PS/2 mouse device common for all mice
Feb 4 08:32:50 werewolf kernel: cpuidle: using governor ladder
Feb 4 08:32:50 werewolf kernel: cpuidle: using governor menu
Feb 4 08:32:50 werewolf kernel: TCP cubic registered
Feb 4 08:32:50 werewolf kernel: NET: Registered protocol family 17
Feb 4 08:32:50 werewolf kernel: Using IPI No-Shortcut mode
Feb 4 08:32:50 werewolf kernel: registered taskstats version 1
Feb 4 08:32:50 werewolf kernel: Initalizing network drop monitor service
Feb 4 08:32:50 werewolf kernel: Freeing unused kernel memory: 416k freed
Feb 4 08:32:50 werewolf kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
Feb 4 08:32:50 werewolf kernel: Switched to high resolution mode on CPU 1
Feb 4 08:32:50 werewolf kernel: Switched to high resolution mode on CPU 0
Feb 4 08:32:50 werewolf kernel: SCSI subsystem initialized
Feb 4 08:32:50 werewolf kernel: libata version 3.00 loaded.
Feb 4 08:32:50 werewolf kernel: Floppy drive(s): fd0 is 1.44M
Feb 4 08:32:50 werewolf kernel: pata_acpi 0000:00:1f.1: enabling device (0005 -> 0007)
Feb 4 08:32:50 werewolf kernel: pata_acpi 0000:00:1f.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Feb 4 08:32:50 werewolf kernel: pata_acpi 0000:00:1f.1: setting latency timer to 64
Feb 4 08:32:50 werewolf kernel: pata_acpi 0000:00:1f.1: PCI INT A disabled
Feb 4 08:32:50 werewolf kernel: pata_acpi 0000:00:1f.2: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Feb 4 08:32:50 werewolf kernel: pata_acpi 0000:00:1f.2: setting latency timer to 64
Feb 4 08:32:50 werewolf kernel: pata_acpi 0000:00:1f.2: PCI INT A disabled
Feb 4 08:32:50 werewolf kernel: ata_piix 0000:00:1f.1: version 2.13
Feb 4 08:32:50 werewolf kernel: ata_piix 0000:00:1f.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Feb 4 08:32:50 werewolf kernel: ata_piix 0000:00:1f.1: setting latency timer to 64
Feb 4 08:32:50 werewolf kernel: scsi0 : ata_piix
Feb 4 08:32:50 werewolf kernel: scsi1 : ata_piix
Feb 4 08:32:50 werewolf kernel: FDC 0 is a post-1991 82077
Feb 4 08:32:50 werewolf kernel: ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xfc00 irq 14
Feb 4 08:32:50 werewolf kernel: ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xfc08 irq 15
Feb 4 08:32:50 werewolf kernel: ata_piix 0000:00:1f.2: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Feb 4 08:32:50 werewolf kernel: ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ]
Feb 4 08:32:50 werewolf kernel: ata_piix 0000:00:1f.2: setting latency timer to 64
Feb 4 08:32:50 werewolf kernel: scsi2 : ata_piix
Feb 4 08:32:50 werewolf kernel: scsi3 : ata_piix
Feb 4 08:32:50 werewolf kernel: ata3: SATA max UDMA/133 cmd 0xbc00 ctl 0xb880 bmdma 0xb400 irq 18
Feb 4 08:32:50 werewolf kernel: ata4: SATA max UDMA/133 cmd 0xb800 ctl 0xb480 bmdma 0xb408 irq 18
Feb 4 08:32:50 werewolf kernel: ata1.00: ATA-7: ExcelStor Technology J880, PF2OA21B, max UDMA/133
Feb 4 08:32:50 werewolf kernel: ata1.00: 160836480 sectors, multi 16: LBA48
Feb 4 08:32:50 werewolf kernel: ata1.01: ATA-6: HDS722516VLAT80, V34OA6EA, max UDMA/100
Feb 4 08:32:50 werewolf kernel: ata1.01: 321672960 sectors, multi 16: LBA48
Feb 4 08:32:50 werewolf kernel: ata3.00: ATAPI: HL-DT-ST DVDRAM GH20NS10, EL00, max UDMA/100
Feb 4 08:32:50 werewolf kernel: ata3.00: configured for UDMA/100
Feb 4 08:32:50 werewolf kernel: ata1.00: configured for UDMA/100
Feb 4 08:32:50 werewolf kernel: ata1.01: configured for UDMA/100
Feb 4 08:32:50 werewolf kernel: scsi 0:0:0:0: Direct-Access ATA ExcelStor Techno PF2O PQ: 0 ANSI: 5
Feb 4 08:32:50 werewolf kernel: scsi 0:0:1:0: Direct-Access ATA HDS722516VLAT80 V34O PQ: 0 ANSI: 5
Feb 4 08:32:50 werewolf kernel: scsi 2:0:0:0: CD-ROM HL-DT-ST DVDRAM GH20NS10 EL00 PQ: 0 ANSI: 5
Feb 4 08:32:50 werewolf kernel: sd 0:0:0:0: [sda] 160836480 512-byte logical blocks: (82.3 GB/76.6 GiB)
Feb 4 08:32:50 werewolf kernel: sd 0:0:1:0: [sdb] 321672960 512-byte logical blocks: (164 GB/153 GiB)
Feb 4 08:32:50 werewolf kernel: sd 0:0:1:0: [sdb] Write Protect is off
Feb 4 08:32:50 werewolf kernel: sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
Feb 4 08:32:50 werewolf kernel: sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 4 08:32:50 werewolf kernel: sdb: sdb1 sdb2 sdb3 sdb4
Feb 4 08:32:50 werewolf kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 4 08:32:50 werewolf kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 4 08:32:50 werewolf kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 4 08:32:50 werewolf kernel: sda: sda1 sda2 < sda5 >
Feb 4 08:32:50 werewolf kernel: sd 0:0:1:0: [sdb] Attached SCSI disk
Feb 4 08:32:50 werewolf kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 4 08:32:50 werewolf kernel: sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 4 08:32:50 werewolf kernel: Uniform CD-ROM driver Revision: 3.20
Feb 4 08:32:50 werewolf kernel: sr 2:0:0:0: Attached scsi CD-ROM sr0
Feb 4 08:32:50 werewolf kernel: EXT3-fs: mounted filesystem with writeback data mode.
Feb 4 08:32:50 werewolf kernel: kjournald starting. Commit interval 5 seconds
Feb 4 08:32:50 werewolf kernel: rtc_cmos 00:02: RTC can wake from S4
Feb 4 08:32:50 werewolf kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Feb 4 08:32:50 werewolf kernel: rtc0: alarms up to one month, 114 bytes nvram, hpet irqs
Feb 4 08:32:50 werewolf kernel: udev: starting version 146
Feb 4 08:32:50 werewolf kernel: usbcore: registered new interface driver usbfs
Feb 4 08:32:50 werewolf kernel: usbcore: registered new interface driver hub
Feb 4 08:32:50 werewolf kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Feb 4 08:32:50 werewolf kernel: sd 0:0:1:0: Attached scsi generic sg1 type 0
Feb 4 08:32:50 werewolf kernel: sr 2:0:0:0: Attached scsi generic sg2 type 5
Feb 4 08:32:50 werewolf kernel: Linux agpgart interface v0.103
Feb 4 08:32:50 werewolf kernel: agpgart-intel 0000:00:00.0: Intel 865 Chipset
Feb 4 08:32:50 werewolf kernel: agpgart-intel 0000:00:00.0: AGP aperture is 64M @ 0xdc000000
Feb 4 08:32:50 werewolf kernel: usbcore: registered new device driver usb
Feb 4 08:32:50 werewolf kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 4 08:32:50 werewolf kernel: ehci_hcd 0000:00:1d.7: PCI INT D -> GSI 23 (level, low) -> IRQ 23
Feb 4 08:32:50 werewolf kernel: ehci_hcd 0000:00:1d.7: setting latency timer to 64
Feb 4 08:32:50 werewolf kernel: ehci_hcd 0000:00:1d.7: EHCI Host Controller
Feb 4 08:32:50 werewolf kernel: ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
Feb 4 08:32:50 werewolf kernel: ehci_hcd 0000:00:1d.7: debug port 1
Feb 4 08:32:50 werewolf kernel: ehci_hcd 0000:00:1d.7: cache line size of 128 is not supported
Feb 4 08:32:50 werewolf kernel: ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf8fffc00
Feb 4 08:32:50 werewolf kernel: ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
Feb 4 08:32:50 werewolf kernel: usb usb1: configuration #1 chosen from 1 choice
Feb 4 08:32:50 werewolf kernel: hub 1-0:1.0: USB hub found
Feb 4 08:32:50 werewolf kernel: hub 1-0:1.0: 8 ports detected
Feb 4 08:32:50 werewolf kernel: uhci_hcd: USB Universal Host Controller Interface driver
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.0: irq 16, io base 0x0000c480
Feb 4 08:32:50 werewolf kernel: usb usb2: configuration #1 chosen from 1 choice
Feb 4 08:32:50 werewolf kernel: hub 2-0:1.0: USB hub found
Feb 4 08:32:50 werewolf kernel: hub 2-0:1.0: 2 ports detected
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000c800
Feb 4 08:32:50 werewolf kernel: usb usb3: configuration #1 chosen from 1 choice
Feb 4 08:32:50 werewolf kernel: hub 3-0:1.0: USB hub found
Feb 4 08:32:50 werewolf kernel: hub 3-0:1.0: 2 ports detected
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000c880
Feb 4 08:32:50 werewolf kernel: usb usb4: configuration #1 chosen from 1 choice
Feb 4 08:32:50 werewolf kernel: hub 4-0:1.0: USB hub found
Feb 4 08:32:50 werewolf kernel: hub 4-0:1.0: 2 ports detected
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.3: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.3: setting latency timer to 64
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.3: UHCI Host Controller
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
Feb 4 08:32:50 werewolf kernel: uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000cc00
Feb 4 08:32:50 werewolf kernel: usb usb5: configuration #1 chosen from 1 choice
Feb 4 08:32:50 werewolf kernel: hub 5-0:1.0: USB hub found
Feb 4 08:32:50 werewolf kernel: hub 5-0:1.0: 2 ports detected
Feb 4 08:32:50 werewolf kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Feb 4 08:32:50 werewolf kernel: intel_rng: FWH not detected
Feb 4 08:32:50 werewolf kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Feb 4 08:32:50 werewolf kernel: usb 1-1: new high speed USB device using ehci_hcd and address 2
Feb 4 08:32:50 werewolf kernel: i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Feb 4 08:32:50 werewolf kernel: lp: driver loaded but no devices found
Feb 4 08:32:50 werewolf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
Feb 4 08:32:50 werewolf kernel: ACPI: Power Button [PWRF]
Feb 4 08:32:50 werewolf kernel: input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
Feb 4 08:32:50 werewolf kernel: ACPI: Power Button [PWRB]
Feb 4 08:32:50 werewolf kernel: parport_pc 00:08: reported by Plug and Play ACPI
Feb 4 08:32:50 werewolf kernel: parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA]
Feb 4 08:32:50 werewolf kernel: ACPI: SSDT 3ffb3c60 002FC (v01 AMI CPU1PM 00000001 INTL 02002026)
Feb 4 08:32:50 werewolf kernel: processor LNXCPU:00: registered as cooling_device0
Feb 4 08:32:50 werewolf kernel: ACPI: Processor [CPU0] (supports 8 throttling states)
Feb 4 08:32:50 werewolf kernel: ACPI Warning: Incorrect checksum in table [SSDT] - C5, should be E7 20090521 tbutils-246
Feb 4 08:32:50 werewolf kernel: ACPI: SSDT 3ffb3f60 002FC (v01 AMI CPU2PM 00000001 INTL 02002026)
Feb 4 08:32:50 werewolf kernel: processor LNXCPU:01: registered as cooling_device1
Feb 4 08:32:50 werewolf kernel: iTCO_vendor_support: vendor-support=0
Feb 4 08:32:50 werewolf kernel: lp0: using parport0 (interrupt-driven).
Feb 4 08:32:50 werewolf kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
Feb 4 08:32:50 werewolf kernel: iTCO_wdt: Found a ICH5 or ICH5R TCO device (Version=1, TCOBASE=0x0860)
Feb 4 08:32:50 werewolf kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Feb 4 08:32:50 werewolf kernel: usb 1-1: configuration #1 chosen from 1 choice
Feb 4 08:32:50 werewolf kernel: Intel ICH 0000:00:1f.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Feb 4 08:32:50 werewolf kernel: Intel ICH 0000:00:1f.5: setting latency timer to 64
Feb 4 08:32:50 werewolf kernel: <6>8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
Feb 4 08:32:50 werewolf kernel: 8139cp 0000:02:05.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too
Feb 4 08:32:50 werewolf kernel: ppdev: user-space parallel port driver
Feb 4 08:32:50 werewolf kernel: 8139too Fast Ethernet driver 0.9.28
Feb 4 08:32:50 werewolf kernel: 8139too 0000:02:05.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
Feb 4 08:32:50 werewolf kernel: eth0: RealTek RTL8139 at 0xf857ac00, 00:11:d8:41:89:b6, IRQ 22
Feb 4 08:32:50 werewolf kernel: usb 3-2: new low speed USB device using uhci_hcd and address 2
Feb 4 08:32:50 werewolf kernel: intel8x0_measure_ac97_clock: measured 51251 usecs (2470 samples)
Feb 4 08:32:50 werewolf kernel: intel8x0: clocking to 48000
Feb 4 08:32:50 werewolf kernel: usb 3-2: configuration #1 chosen from 1 choice
Feb 4 08:32:50 werewolf kernel: nvidia: module license 'NVIDIA' taints kernel.
Feb 4 08:32:50 werewolf kernel: Linux video capture interface: v2.00
Feb 4 08:32:50 werewolf kernel: uvcvideo: Found UVC 1.00 device Vega USB 2.0 Camera. (0ac8:332d)
Feb 4 08:32:50 werewolf kernel: input: Vega USB 2.0 Camera. as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/input/input4
Feb 4 08:32:50 werewolf kernel: usbcore: registered new interface driver uvcvideo
Feb 4 08:32:50 werewolf kernel: USB Video Class driver (v0.1.0)
Feb 4 08:32:50 werewolf kernel: usbcore: registered new interface driver snd-usb-audio
Feb 4 08:32:50 werewolf kernel: usbcore: registered new interface driver hiddev
Feb 4 08:32:50 werewolf kernel: input: Dell Dell USB Optical Mouse as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input5
Feb 4 08:32:50 werewolf kernel: generic-usb 0003:413C:3012.0001: input,hidraw0: USB HID v1.11 Mouse [Dell Dell USB Optical Mouse] on usb-0000:00:1d.1-2/input0
Feb 4 08:32:50 werewolf kernel: usbcore: registered new interface driver usbhid
Feb 4 08:32:50 werewolf kernel: usbhid: v2.6:USB HID core driver
Feb 4 08:32:50 werewolf kernel: nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Feb 4 08:32:50 werewolf kernel: NVRM: loading NVIDIA UNIX x86 Kernel Module 190.42 Tue Oct 20 20:18:32 PDT 2009
Feb 4 08:32:50 werewolf kernel: EXT3 FS on sdb3, internal journal
Feb 4 08:32:50 werewolf kernel: kjournald starting. Commit interval 5 seconds
Feb 4 08:32:50 werewolf kernel: EXT3 FS on sdb4, internal journal
Feb 4 08:32:50 werewolf kernel: EXT3-fs: mounted filesystem with writeback data mode.
Feb 4 08:32:50 werewolf kernel: Adding 1132572k swap on /dev/sdb2. Priority:-1 extents:1 across:1132572k
Feb 4 08:32:50 werewolf kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Feb 4 08:32:43 werewolf load-modules.sh: Not loading module alias 'pcspkr' because it is blacklisted
Feb 4 08:32:43 werewolf load-modules.sh: 'acpi:LNXSYSTM:' is not a valid module or alias name
Feb 4 08:32:43 werewolf load-modules.sh: 'dmi:bvnAmericanMegatrendsInc.:bvr1004.001:bd05/29/2005:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnP5P800S:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'pci:v00008086d00002576sv00000000sd00000000bc08sc80i00' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'acpi:PNP0000:' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: Not loading module 'pcspkr' for alias 'platform:pcspkr' because it is blacklisted
Feb 4 08:32:44 werewolf load-modules.sh: 'acpi:PNP0200:' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'acpi:PNP0501:' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'acpi:PNP0303:PNP030B:' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'acpi:PNP0C04:' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'acpi:PNP0800:' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'acpi:PNP0100:' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'platform:parport_pc' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'platform:parport_pc' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'platform:parport_pc' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'platform:iTCO_wdt' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'usb:v0AC8p332Dd0100dcEFdsc02dp01ic01isc02ip00' is not a valid module or alias name
Feb 4 08:32:44 werewolf load-modules.sh: 'usb:v0AC8p332Dd0100dcEFdsc02dp01ic0Eisc02ip00' is not a valid module or alias name
Feb 4 08:32:49 werewolf init: Entering runlevel: 3
Feb 4 08:32:57 werewolf kernel: NET: Registered protocol family 10
Feb 4 08:32:57 werewolf kernel: lo: Disabled Privacy Extensions
Feb 4 08:33:03 werewolf kernel: agpgart-intel 0000:00:00.0: AGP 3.0 bridge
Feb 4 08:33:03 werewolf kernel: agpgart-intel 0000:00:00.0: putting AGP V3 device into 8x mode
Feb 4 08:33:03 werewolf kernel: nvidia 0000:01:00.0: putting AGP V3 device into 8x mode
Feb 4 08:33:06 werewolf kernel: CPU0 attaching NULL sched-domain.
Feb 4 08:33:06 werewolf kernel: CPU1 attaching NULL sched-domain.
Feb 4 08:33:06 werewolf kernel: CPU0 attaching sched-domain:
Feb 4 08:33:06 werewolf kernel: domain 0: span 0-1 level SIBLING
Feb 4 08:33:06 werewolf kernel: groups: 0 1
Feb 4 08:33:06 werewolf kernel: CPU1 attaching sched-domain:
Feb 4 08:33:06 werewolf kernel: domain 0: span 0-1 level SIBLING
Feb 4 08:33:06 werewolf kernel: groups: 1 0
Feb 4 08:33:08 werewolf gdm-simple-greeter[3554]: GLib-GObject-CRITICAL: g_param_spec_flags: assertion `G_TYPE_IS_FLAGS (flags_type)' failed
Feb 4 08:33:08 werewolf gdm-simple-greeter[3554]: GLib-GObject-CRITICAL: g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed
Feb 4 08:33:08 werewolf kernel: eth0: no IPv6 routers present
Feb 4 08:33:09 werewolf gdm-simple-greeter[3554]: WARNING: Unable to read from file /etc/arch-release
Feb 4 08:33:09 werewolf gdm-simple-greeter[3554]: Pango-WARNING: Invalid UTF-8 string passed to pango_layout_set_text()
Feb 4 08:34:33 werewolf kernel: fuse init (API version 7.12)
Feb 4 08:37:38 werewolf kernel: Machine check events logged
Thanks for any help!
Last edited by skwo (2010-02-04 06:44:23)Ok one more update.
Kernel panic occurs only first time I boot the pc. I.E. I woke up today, turned the pc on and got kernel panic. No matter how much times Il reboot today, or even if I power down the pc it wont happen anymore. Next panic will be tomorrow after Ill turn the pc (after night that it was off). I know it sounds strange but this is the behavior.
Now the error:
During boot looks like this:
a lot of sutff.
Arch linux welcome screen
::Starting udev events
::Triggering udev events
::Loading modules
::Loading standard acpi modules
::Waiting for udev event to be processed
KERNEL PANIC
The title of the panic says Hardware Error
There is a lot info, with hexadecimal numbers, and a stack-trace in the end, but I was able to retrieve only few line (well after 30s it will reboot)
Hardware Error
CPU Machine check exception
????? processor context corrupt
Kernel Panic: ???? not syncing
Where dots represent a lot of info, and question marks a words that I probably missed.
I wouldn't worry that much if it was after I changed the hardware, or installed some new kernel, but i DIDN'T :( Its just happend 4-5days ago and keeps happening every day, once a day.
Any help please?
Last edited by skwo (2010-02-06 12:15:46) -
Finding a PKGBUILD for the 2.6.21.4 kernel (for Asus EEE )
I'm trying to build a kernel that will support the Asus Eee's non-source drivers out of the box without ndiswrapper. I also would like to install the whole thing using my pacman. Is there any way to get a complete PKGBUILD for this kernel? If possible, I'd also like to get the associated patches, etc if possible.
I'm basing my hack on some things listed here:
http://cliffhacks.blogspot.com
I played with the CVS for awhile, but couldn't find a way to get the kernel 2.6.21.4 PKGBUILD, and I'm not sure if CVS would even do this.
After this, I'll have to compare the PKGBUILD with the config that Asus used on their kernel. We'll see how it goes. Thanks for any help or tips.lilsirecho wrote:
beniro;
Normally PKGBUILDS for kernels are not provided in arch.
However, one has been inserted into the aur mix by raymano and it is for kernel 2.6.23.9-1.
What are you talking about - I thought the PKGBUILDs were publicly available. Atleast I can see them - and you could certainly create your own although with a little difficulty for such an early kernel - but It should be possible -
Hi, everyone, does anyone know how to get the size of the disk, say hard disk? In the Writing Device Driver it says that the block device driver must create an 'nblocks' property for each minor block device. I want to get the size of the block device in another driver. Is there any DDI/DKI kernel function for this?
How to get the same thing in a user mode application? Is there any API to do this?
Thank you very much.I just found a function in include/sys/conf.h. The prototype is:
extern int bdev_size(dev_t);
Can I use this function to get the disk size of the device dev_t? I couldn't find the documentation of this function.
Thanks -
[SOLVED-in-PART] recompiling kernel images, boot diferent from chroot
Hi, I got into an dead end. Two days ago I was trying to solve some small annoying problems (ethernet driver, dkms not compiling automatically and difference in time hwclock and software clock) with my recent arch installation. I started with the time difference problem, for which I followed some solutions which I found in the internet, but all for no avail. So I postponed this for later and started to tackle the ethernet driver problem (Atheros AR8161) [https://wiki.archlinux.org/index.php/Ne … ros_AR8161]. I followed all described steps, I also did the mentioned hack. After all, I turned my note at work off and at home on and surprise it found the GRUB menu, I started the option for the system, the disk was checked but, no system came up. It even messed up my window8 system as well. But that is now up and working. After windows came back GRUB was loading and I can start it from GRUB, but not Arch.
I looked at the grub menu and as far as I could see and understand everything was pointing and the right direction. So I supposed that during the network driver compilation and module load, something went wrong with the images or images source (if they are important for booting). So reading around I got pointed to how to rebuild the kernel images (http://riskofruin.markmccracken.net/201 … image.html). I know the blog title is kreepy... but the procedure sounds very logic, correct and quite strait forward. So I got the latest Arch image, put it on an usb stick and chroot into my installed system.
When I started the /sbin/depmod I immediately got an error saying that two files where missing for the kernels 3.7.9-2-ARCH. Well as far as I remember my installed system has the latest kernel (3.7.10-1-ARCH). So I though to update my pendrive system and so restart an both kernels would be equal. After restarting, I repeated al chroot protocol and then I saw that I still had the wrong kernel images. I suspect why, but I am not sure, may be the system is all memory loaded when it is booted up? Also, if I saw right, even the images are quite different (pendrive and harddrive). I surfed around to see how can I, in an chroot environment, where the hardrive installed system has an different kernel from the booted system, generate new kernel images for the hardrive system, soin a hope that I can initialize my hardrive installed system? Is there someone that could guide me through this?
PS.: Remember I suppose the problem is in the kernel, I do not not how to check for sure.
Last edited by camarao (2013-03-10 03:10:56)Hi Trilby,
No, just the initramfs. Because I think when I tryed to install my Atheros AR8161 drive I guess that something went wrong with the image or it could be something else.
Do you think the vmlinuz-linux should also be reconstructed?
Yesterday at night I found in the internet, someone using the "-k" option, of mkinitcpio, and pointing to the /boot/vmlinuz.linux directory. So if I understood well mkinitcpio using the options "-k", "-c" and "-g" you can point where to put the reconstructed images, vmlinuz and the initramfs, according to the "-c" pointed mkinitcpio.conf. This would allow me to reconstruct both images for the broken system which are from a different kernel version, than the one used to boot up and repair the broken system.
Two last questions:
1. Is it necessary to run /sbin/depmod before reconstructiong the images, as mentioned in the link (http://riskofruin.markmccracken.net/201 … image.html)?
2. Will the two new images be automatically replaced in /boot?
Sorry for asking this, but IT is just an hobby for me, and my IT knowledge is limited to what I read and understand. I like adventures and sometime dangerous one as well, I learn a lot. But if sometimes I can get a small help I like.
Well thanks for everything -
Since I'm too noobish to understand the code for the various kernel schedulers... How does the I/O scheduler CFQ work?
If I had to guess, I would say it might:
- Somehow merge I/O requests to consecutive/arbitrarily nearby sectors
- Divide available I/O bandwidth by the number of requests
- Assign each request a random position in line, and service the lower numbers first
- Switch to the next request and assign the prior one a new random number once the bandwidth limit has been used up (assuming the old request isn't finished)
I'm betting it's much more complicated than that though, else CFQ would actually be fair. So... how does it really work? And how do schedulers like Con Kolivas' BFS improve on it (assuming they work as intended)?I don't know specifics, but I'll point out the following:
- CFQ detects the media type (rotating vs non-rotating .. think SSD) and tunes its rules accordingly.
- It's definitely a fair queue mechanism (that's what the F in CFQ is for). It uses timeslicing which is affected by cgroups and a process's I/O priority.
- BFS is a CPU scheduler, not an I/O scheduler. If you use a kernel patched with BFS, you can use both BFS and CFQ at the same time. -
[solved] makepkg.conf + local path
Hi!
I would like to create two packages that are needed to run my printer (canon).
From the canon website, after long passages, I downloaded two .tar.gz packages with the necessary sources.
From wiki, I refer to the page that explains how to create the PKGBUILD, I realized that you can
also specify a local directory as url to find the source package.
To do this, however, you must edit the file makepkg.conf.
The question is: how do I change the file makepkg.conf?
Thank you!
Last edited by trevi (2011-12-29 15:19:55)Just put the tarball names in the source= array, put the tarballs and PKGBUILD in the same dir, and run makepkg in that dir. No need to edit makepkg.conf.
-
How Long Will Arch last?
Hi, my question here is not to ridicule (or otherwise designed to offend anyone) but one of concern. Many distributions have a viable economic model which helps ensure that the distro can survive (Fedora is one prime example). The fact that Fedora has the backing of Red Hat means that it is almost always asured funding. Ubuntu is also moving in this general direction (although their model does not seem as reliable as Red Hat's yet.) What gurrantee do we have that Arch can last for many decades to come? The Arch devs are real people with real jobs. As far as I know they do not actually get and money from Arch Linux. What sustains Arch ( pays for servers etc.) Is it simply donations? Can Arch survive soley off of donations?
What are your thoughts and ideas do you have on how to make Arch a self sustaining distro while also keeping it free? Finally if Arch falls apart what would you do?
THIS IS HYPOTHETICAL THIS IN NO MEANS IMPLIES THAT ARCH IS GOING UNDER ANY TIME SOON!
( I would also like to take this time to conragulate the Arch devs for coming this far and thank them for all their work it is much appreciated.)Gullible Jones wrote:... There's also Unununium (no kernel, damned if I know how!) ...
Read the FAQ (Introduction page) for more info about Unununium:
http://unununium.org/introduction
Something interesting:
On what platforms does Unununium run?
The latest plan is to implement Unununium as a Linux userspace process. Linux is a stable, available, well documented program which eliminates most of the mundane, uncreative aspects of usual OS development such as writing hardware drivers. It also provides an easy mode of execution, with a developed debugger such as gdb, and fast boot times, since there is no need for a full hardware reboot. This makes development much easier.
Running on Linux has disadvantages as well. Probably most significantly, some things are slower. For a slower speed in execution, we get a faster speed in development. Some day it would be nice to reduce overhead, but that's something that will wait until there is something running.
For some reason or another, this choice of platform leads people to question if Unununium can really be an OS. Of course, it really depends on how "OS" is defined. Unununium is an environment and a design common to all programs which depend on it, and in this sense might be considered an OS.
Maybe you are looking for
-
Jtable: display sortable columns
Hi all, As I undersatnd, by default jtable shows the sorting triangle only after you click on the column header. I wonder how you could display a disabled sorting triangle icon on sortable columns which becomes enabled after you click on the column h
-
How to configure XI and BI for proxy connection?
Hi BI guruz! I am trying to set up a proxy connection between SAP BI (Vr7.0 SPS 09) and SAP XI (3.0 SPS 19). for this i am planning to follow the How to document (How to Integrate XI and BI in SAP NetWeaver 2004s.pdf) as given by SAP. I am new to the
-
Cannot see the whole page but size is right for word, games, and other applications on my computer.
-
Make (RTL) direction function in PS cc 2014 not found!
u can see this to know what is the problem
-
Can't install from disk on clean Lion install
Doing the lion upgrade caused a slew of problems on my machine (as well as many others from the look of the discussion boards) So I did a clean install. Everything is working beautifully, except when I try to install Remote Desktop 3. I just purchase