Boot/Kernel issue

Hello -
On a vanilla install from the CD version (2008.06) everything works. When I upgrade everything, the 2.6.28.4-1 kernel seems to cause problems. I can get things working again by downgrading the kernel but this seems inelegant (and I'd like the nvidia 96XX driver which apparently requires 2.6.28).
The error message I get is:
request_module: runaway loop moprobe binfmt_ffff
5 or 6 times then:
input: AT Translated Set 2 Keyboard as /class/input/input1
I'm really struggling with this - I've searched the forums and google and I'm at a dead end.
Anyone have any ideas?

Not a solution, but your second line there is not relevant to your problem.

Similar Messages

Anyone having kernel issues at boot up with mountain lion?

Having kernel issues at boot up after upgrading from lion to mountain lion. Anyone else having same issue?

If you can't boot in the usual way, try a safe boot. The instructions provided by Apple are as follows:
Be sure your Mac is shut down.
Press the power button.
Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
During startup, you’ll see a progress bar, and then the login screen, which appears even if you normally log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Safe mode is slower than normal, and some things won’t work at all.
Note: If FileVault is enabled under OS X 10.7 or later, or if a firmware password is set, you can’t boot in safe mode.
If you're able to boot, launch the Console 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 Console in the page that opens.
Select the most recent panic log under System Diagnostic Reports. Post the contents — the text, please, not a screenshot. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header and body of the report, if it’s present (it may not be.) Please don't post shutdownStall, spin, or hang reports.

Settting boot kernel architecture with Apple Script

Ok, so on three different sites, I've got a total of about fifty Macs, the majority of which run 10.6.8. I need to install a remote monitoring application on the machines, but the application only runs on the 64 bit kernel. I'd really like to set the kernel to 64 from Remote Desktop's send unix command feature, but it looks like it can't run with sudo. So after some poking around, I've come up with the following Applescript:
property myUserName : "<admin login>"
property myPassword : "<admin pass>"
do shell script "sudo systemsetup -setbootkernelarchitecture x86_64" user name myUserName password myPassword with administrator privileges
My goal here would be to run the script remotely with ARD. It copmpiles and runs fine, but doesn't acually change the boot kernel. I don't get any errors, so I've got nothign to go on here as to why it's not working.
Can anyone offer some insight on this? Would a different approach work better? I really don't want to go sit at each desktop and set the kernel manually.

I'd really like to set the kernel to 64 from Remote Desktop's send unix command feature, but it looks like it can't run with sudo
You don't need to use sudo with Remote Desktop's 'send UNIX' command.
When you choose to send a command you get to nominate what user it should run as - either root or the current logged-in user. Just set it to run as root and omit the sudo prefix and you should be fine.

How to set the default boot kernel in /etc/default/grub or /etc/grub.d

and without messing with /boot/grub/grub.cfg ?
I need this so that new kernels show up but do not change the default boot kernel
Is there a way to do it by file name instead of position within the menuentry / submenu list?
I found some ubuntu and fedora sugestions but all by position, none by name
AND how to set the kdump kernel as the default?
Arch is putting this kernel under a submenu - would this pose problems for setting it as the default?
Last edited by Sanjeev K Sharma (2015-04-06 12:59:22)

Sanjeev K Sharma wrote:
and without messing with /boot/grub/grub.cfg ?
I need this so that new kernels show up but do not change the default boot kernel
Is there a way to do it by file name instead of position within the menuentry / submenu list?
I found some ubuntu and fedora sugestions but all by position, none by name
AND how to set the kdump kernel as the default?
Arch is putting this kernel under a submenu - would this pose problems for setting it as the default?
In /etc/default/grub you can use the name of your entry you wish to use as default
GRUB_DEFAULT='Arch Linux, with Linux core repo kernel'
You can tell grub to stop using submenus by doing:
GRUB_DISABLE_SUBMENU=y
Or you can just make a purely custom menuentry in /etc/grub.d/40_custom if you'd like:
menuentry "Other Linux" {
linux <KERNEL IMAGE HERE>
initrd <INITRD IMAGE HERE>
EDIT: /etc/grub/default -> /etc/default/grub
Last edited by Slabity (2015-04-07 11:16:22)

Kernel Issue while USB tethering iPhone 4 to Macbook pro

My 2011 macbook pro has been having the kernel issue with the iPhone 4 but thats not all. I got it exchanged for a new one today and noticing the hard drive is still running a little loud. Its not too loud, but loud enough that if the room is silent, you can hear it and it gets slightly annoying. I dont know if this is normal or not? They definitely need to fix the tethering issue. other than that. I love it and am super happy with it. I also have a MacBook 13" 2010 model. But this hard drive is not as loud. Maybe its normal...I dont know.

Ok I can try that for next time...but is there any way I can get my other files to work properly? They play fine in iPhoto but I'd like to be able to save them to a USB drive.

X220 and z230 ThinkPad boot up issues

We have ran into the same recurring issue with the x220 and x230's. We are running windows 7 pro 64bit, and on a consistent basis we have boot up issues, were windows gets stuck after the bios. The computer needs to be rebooted several times for it to fully boot up. Our users do have docking stations as well, anyone else having this issue?

Hi
If you're hearing noises coming from the hard drive area chances are it is failing hard drive. In which case it may be possible to target disk mode to another mac and try and recover what you can using either drag/drop methods or something like DataRescue:
http://www.prosofteng.com/products/data_rescue.php
This ultimately could be a painfully slow experience. It really does depend on how 'screwed' the hard drive is? Only you can decide how important your data is and how much time you want to spend on it. There is a good possibility (if your data is absolutely vital) that a Data Recovery Specialist can recover the data for you? It can be very expensive. It all depends on what value you place on your data?
If your mac is still in Warranty you have an added dilemma. To qualify for a warranty replacement drive you have to send the drive back to Apple. Neither can you send it to the Data Recovery Specialist first and then send it to Apple. The reason being in all probability the Data Recovery Specialist will have to tamper with the drive in some way to stand a chance of recovering your valuable data. Tampering voids the warranty. Of course if you value your data higher than the cost of a new 3rd-party (cheap) or an Apple branded drive (ridiculously more expensive) then don't bother and replace the drive at your own expense.
Tony

Booting kernel from UEFI Shell - no console?

Hello ALL,
I'm trying to boot kernel from uefi shell w/o a bootloader like this:
fs1:> \efi\arch\vmlinuz-linux.efi root=/dev/sdc3 initrd=\efi\arch\initramfs-linux.img
All goes well, I see all the usual boot messages until at some point my screen turns black.
I saw this warning in the kernel.log: Warning: unable to open an initial console.
Do I need to use some special console=... or video=... parameter to get the console? If so which one?
Thanks for your help.

Fixed this following begginer guide with reFINd, keypont was to check efibootmgr output before writing efibootmgr -c -g -d ... command. then run it again and check for the added option.

MSI z87 g45 Boot up issues

So I built a computer for my sister and her husband and it has been having some boot up issues,Here are the computer parts:
wiindows 7 64bit
MSI Z87 G45 Gaming motherboard
INTEL CORE I-7 4770K 3.5GHZ
RADEON HD 5700 GPU
G.SKILL Ripjaws X Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1866
kINGSTON 64 GB SSD ( spare part, not sure the numbers)
Sunbeam PSU-H680-REV-US 680W ATX 12V 2.0 Power Supply - OEM
Seagate Barracuda ST2000DM001 2TB 7200 RPM
ASUS Black 12X BD-ROM 16X DVD-ROM 48X CD-ROM SATA Internal Blu-ray Drive Model BC-12B1ST/BLK/B/AS
I've cleared both the HDD and SSD and now I'm looking to check the msi z87 g45 mobo, The computer starts up and sits on a2 for a while and then sometimes it fails to detect the SSD and says a0 and then I have to go back into the bios after I reset the computer again and maybe it detected the SSD and I can set it to boot from that again because it constantly changes the boot order, and sometimes it gives a blue screen when nearly into windows and then restarts, I had transferred some data from their old computer to this one and the data had virus's in it and I didnt know so I eventually found out and a day later and got rid of them all and the computer started behaving better but not fixed, faster mainly, I don't know if the virus may have altered some files so, I have a few more things to try, any help would be appreciated.
(Something I forgot to mention is that when I unplugg the HDD all the issues go away, the computer seems to work fine, But there are no issues with the hdd, ive tested it with seatools and I plugged it into my computer and restarted mant times as well as used my computer for a while and nothing, the HDD is fine, the start up on their computer sits on a2 for a long time when it isnt going to work and it only happens with the 2tb seagate HDD plugged in)

which storage drive holds the boot files the SSD or the HDD? the ATA mode of the BIOS needs to remain in the same mode it was when Windows was deployed to the storage drive. next the only way a BIOS settings will change with out user input is if the Li cell battery is going dead/the BIOS is getting reset frequently. sounds like you're about at square one, I'd format the Seagate 2TB HDD, install windows onto that either in RAID or AHCI mode whichever your preference, you can use the 64GB SSD as caching later if you use RAID mode, if AHCI the 64GB could be spare. I don't understand the SSD as boot drive method, it doesn't make sense the solid state storage is volatile meaning it degrades over time, the HDD isn't and the performance gain isn't going to change the way you use your PC. AHCI has it's advantages it's up to you. Following those steps is the only way you're going to keep the computer booting on a regular basis. You shouldn't need to manually configure which storage drive to initialize/boot from first, the BIOS automatically goes through your devices to find boot files then boots from the first one with boot files, it won't even try to boot from a device without boot files, because it can't. Just to reiterate the BSOD you speak of sounds similar to the ATA mode changing to something other than what it was when Windows was deployed to the device.

[SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

Edit: this issue has been resolved with VirtualBox version 3.2.12
About 1 - 2 minutes after launching a Windows VM vbox crashes and causes a hard reboot. I've recompiled the modules and completely reinstalled the package from AUR with no joy. Below are the package versions and segments of log files that are relatively pertinent to the issue.
virtualbox_bin 3.2.10-2
kernel26 2.6.36-3
depends:
'libidl2' 0.8.14-1
'libxcursor' 1.1.11-1
'libxinerama' 1.1.1-1
'libxslt' 1.1.26-2
'curl' 7.21.2-2
'gcc' 4.5.1-1
'make' 3.82-2
'kernel26-headers' 2.6.36-3
'python2' 2.7-3
Seems very similar to this issue: https://bbs.archlinux.org/viewtopic.php?id=105631
vbox-install.log
ld -r -m elf_x86_64 -T /usr/src/linux-2.6.36-ARCH/scripts/module-common.lds --build-id -o /tmp/vbox.0/vboxdrv.ko /tmp/vbox.0/vboxdrv.o /tmp/vbox.0/vboxdrv.mod.o
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.36-ARCH/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo; \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f scripts/Makefile.build obj=/tmp/vbox.0
ld -r -m elf_x86_64 -T /usr/src/linux-2.6.36-ARCH/scripts/module-common.lds --build-id -o /tmp/vbox.0/vboxnetflt.ko /tmp/vbox.0/vboxnetflt.o /tmp/vbox.0/vboxnetflt.mod.o
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.36-ARCH/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo; \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
kernel.log/dmesg.log/errrors.log
Nov 8 09:51:06 athos kernel: vboxdrv: Trying to deactivate the NMI watchdog permanently...
Nov 8 09:51:06 athos kernel: vboxdrv: Warning: 2.6.31+ kernel detected. Most likely the hardware performance
Nov 8 09:51:06 athos kernel: vboxdrv: counter framework which can generate NMIs is active. You have to prevent
Nov 8 09:51:06 athos kernel: vboxdrv: the usage of hardware performance counters by
Nov 8 09:51:06 athos kernel: vboxdrv: echo 2 > /proc/sys/kernel/perf_counter_paranoid
Nov 8 09:51:06 athos kernel: vboxdrv: Found 2 processor cores.
Nov 8 09:51:06 athos kernel: VBoxDrv: dbg - g_abExecMemory=ffffffffa105f580
Nov 8 09:51:06 athos kernel: vboxdrv: fAsync=0 offMin=0x18f offMax=0x87f
Nov 8 09:51:06 athos kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
Nov 8 09:51:06 athos kernel: vboxdrv: Successfully loaded version 3.2.10 (interface 0x00140001).
Nov 8 09:52:25 athos kernel: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
everything.log
Nov 8 11:29:31 athos kernel: vboxdrv: Trying to deactivate the NMI watchdog permanently...
Nov 8 11:29:31 athos kernel: vboxdrv: Warning: 2.6.31+ kernel detected. Most likely the hardware performance
Nov 8 11:29:31 athos kernel: vboxdrv: counter framework which can generate NMIs is active. You have to prevent
Nov 8 11:29:31 athos kernel: vboxdrv: the usage of hardware performance counters by
Nov 8 11:29:31 athos kernel: vboxdrv: echo 2 > /proc/sys/kernel/perf_counter_paranoid
Nov 8 11:29:31 athos kernel: vboxdrv: Found 2 processor cores.
Nov 8 11:29:31 athos kernel: VBoxDrv: dbg - g_abExecMemory=ffffffffa0126580
Nov 8 11:29:31 athos kernel: vboxdrv: fAsync=0 offMin=0x198 offMax=0x1342
Nov 8 11:29:31 athos kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
Nov 8 11:29:31 athos kernel: vboxdrv: Successfully loaded version 3.2.10 (interface 0x00140001).
cpu info
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU P8700 @ 2.53GHz
stepping : 10
cpu MHz : 2526.876
cache size : 3072 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida dts tpr_shadow vnmi flexpriority
bogomips : 5055.32
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU P8700 @ 2.53GHz
stepping : 10
cpu MHz : 2526.876
cache size : 3072 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida dts tpr_shadow vnmi flexpriority
bogomips : 5055.55
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
Last edited by moted (2010-12-04 00:19:53)

I am having a similar issue, I haven't used vbox for a few days, until just now, several upgrades have taken place.
Namely the kernel upgrade and udev come to mind, however after I rebuilt the kernel modules and attempted to use vbox puel it seems to have stopped all events and thrown the laptop on a "loop" type thing. That's the best I can describe it coming from a programming point of view, where it blocks all events until vbox finishes or something it is doing finishes but it never finishes causing me to hard reboot because no key events or mouse events get through(just freezes). Normally in a program I'd just control-c it, for my own that is, and then hunt down the loop, although this loop seems to be at a much deeper level.
Although my issue doesn't happen in any given timeframe, just at a specific point, when it gets to the Windows Logo during the boot after it gets through grub and all of that(I have a dual boot vbox setup).
I was going to post my own bug report here, although since I'm new at this, I'll just share my thoughts in your thread(Hope I'm not breaking any rules or disturbing anyone by posting in your thread, although I didn't see any rules in this forum)
I'm using the same virtualbox_bin version.
Most of the packages are the same version as your except kernel26-headers 2.6.36.1-3 & kernel26 2.6.361-3
Pulled the versions from pacman -Qi <package>
Cpu info(underclocked using cpufrequtils ondemand) pulled from lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
CPU(s): 4
Thread(s) per core: 2
Core(s) per socket: 2
CPU socket(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 37
Stepping: 2
CPU MHz: 1199.000
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache:
Anyhow hope I helped in some way.
Last edited by Max__ (2010-11-24 20:02:30)

PKGBUILD for custom kernel issue

Hi all,
Last night I was putting together a PKGBUILD for a kernel I'd like to compile that has the ck patchset, grsecurity (latest testing), and had broadcom-wl on it already so I don't have to keep reinstalling it from AUR and doing depmod each time as it keeps making me have to find an ethernet cable. I used the kerne26 Arch PKGBUILD as a base and included parts of kernel-netbook for broadcom-wl, kernel26-grsecurity, and kernel26-ck and altered name variables and links etc so it all works and all sources are downloaded. I also got the two .patch files (semaphore and something else) from the kernel-netbook tarball to build the thing with, I don't know if it would work without them.
However when I get into the build() a few patches are applied before I get messages about patches already applied or reversed, and then it says build failed because of an error, I can't tell which package is causing thins or why (it all goes by too fast, and the error says failed without reason, and the reversed patch messages are what is immediately previous to it). I have not yet gone all the way through the pkgbuild - especially towards the end, and I felt that the standard setup of init file system creation and such were ok, and if anything does need altering about it, I can deal with it once I get these first troubles solved.
Below is my pkgbuild so far. Hopefully there are people out there who can aid me with this.
Thanks,
Ben.
# Maintainer: Ben Ward <[email protected]>
pkgbase="kernel26"
# pkgname=('kernel26' 'kernel26-headers' 'kernel26-docs') # Build stock -ARCH kernel
pkgname=kernel26-custom # Build kernel with a different name
#Base kernel info
_kernelname=${pkgname#kernel26}
_basekernel=2.6.38
pkgver=${_basekernel}.3
pkgrel=1
#ARCH patch info
_archpatchver=1
_archpatchname="patch-${pkgver}-${_archpatchver}-ARCH"
#_archpatchname="patch-${pkgver}-1-ARCH"
#grsecurity info
_grsec=2.2.2
_timestamp=201104182227
#Broadcom-wl info
_broadcom_ver=5.100.82.38
_broadcom="hybrid-portsrc_x86_32-v${_broadcom_ver//./_}"
#ck-patch info
_ckpatchversion=3
_ckpatchname="patch-${_basekernel}-ck${_ckpatchversion}"
arch=(i686 x86_64)
license=('GPL2')
url="http://www.kernel.org"
options=(!strip)
source=(ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-$_basekernel.tar.bz2
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/patch-${pkgver}.bz2
ftp://ftp.archlinux.org/other/kernel26/${_archpatchname}.bz2
http://grsecurity.net/test/grsecurity-${_grsec}-${pkgver}-${_timestamp}.patch
http://www.broadcom.com/docs/linux_sta/${_broadcom}.tar.gz
http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/${_basekernel}/${_basekernel}-ck${_ckpatchversion}/${_ckpatchname}.bz2
"semaphore.patch"
"mutex-sema.patch"
# the main kernel config files
config config.x86_64
# standard config files for mkinitcpio ramdisk
kernel26.preset)
md5sums=('7d471477bfa67546f902da62227fa976'
'b3677121c4b5efcb8128c2000788d0aa'
'5b14b6eb2cdcb074905d4974437c4df6'
'a19024797f192fe21a468de80c101d8a'
'c0074a1622c75916442e26763ddf47d0'
'88d5b3e0622f8c48dad19ab9ac3c16f0'
'aee89fe7f034aea2f2ca95322774c1b5'
'21ce3f7967d7305064bf7eb60030ffea'
'f66543886835ab8599b29cd0c48aa66d'
'd866bcc06672fee17736bd5022f700fe'
'25584700a0a679542929c4bed31433b6')
build() {
cd ${srcdir}/linux-$_basekernel
# Apply kernel.org patch to basekernel
msg "Checking basekernel is ip to date..."
if [[ "${_basekernel}" != "${pkgver}" ]]; then
msg "Patching source with upstream patch..."
patch -Np1 -i "${srcdir}/patch-${pkgver}" || return 1
fi
# Add -ARCH patches
# See http://projects.archlinux.org/linux-2.6-ARCH.git/
msg "Patching Kernel with ARCH patches..."
patch -Np1 -i ${srcdir}/${_archpatchname}
# Add ck patch
msg "Patching Kernel with ck patches..."
patch -Np1 -i ${srcdir}/${_ckpatchname}
# Add grsecurity patch
msg "Patching kernel with grsecurity testing branch..."
if [ "$CARCH" = "x86_64" ]; then
cat ../config.x86_64 >./.config
else
cat ../config >./.config
fi
if [ "${_kernelname}" != "" ]; then
sed -i "s|CONFIG_LOCALVERSION=.*|CONFIG_LOCALVERSION=\"${_kernelname}\"|g" ./.config
fi
# get kernel version
make prepare
# load configuration
# Configure the kernel. Replace the line below with one of your choice.
#make menuconfig # CLI menu for configuration
make nconfig # new CLI menu for configuration
#make xconfig # X-based configuration
#make oldconfig # using old config from previous kernel version
# ... or manually edit .config
# stop here
# this is useful to configure the kernel
#msg "Stopping build"
#return 1
yes "" | make config
# build!
make ${MAKEFLAGS} bzImage modules
package_kernel26() {
pkgdesc="The Linux Kernel and modules"
groups=('base')
backup=(etc/mkinitcpio.d/${pkgname}.preset)
depends=('coreutils' 'linux-firmware' 'module-init-tools>=3.12-2' 'mkinitcpio>=0.6.8-2')
# pwc, ieee80211 and hostap-driver26 modules are included in kernel26 now
# nforce package support was abandoned by nvidia, kernel modules should cover everything now.
# kernel24 support is dropped since glibc24
replaces=('kernel24' 'kernel24-scsi' 'kernel26-scsi'
'alsa-driver' 'ieee80211' 'hostap-driver26'
'pwc' 'nforce' 'squashfs' 'unionfs' 'ivtv'
'zd1211' 'kvm-modules' 'iwlwifi' 'rt2x00-cvs'
'gspcav1' 'atl2' 'wlan-ng26' 'rt2500' 'nouveau-drm')
install=kernel26.install
optdepends=('crda: to set the correct wireless channels of your country')
KARCH=x86
cd ${srcdir}/linux-$_basekernel
# get kernel version
_kernver="$(make kernelrelease)"
mkdir -p ${pkgdir}/{lib/modules,lib/firmware,boot}
make INSTALL_MOD_PATH=${pkgdir} modules_install
cp System.map ${pkgdir}/boot/System.map26${_kernelname}
cp arch/$KARCH/boot/bzImage ${pkgdir}/boot/vmlinuz26${_kernelname}
# # add vmlinux
install -m644 -D vmlinux ${pkgdir}/usr/src/linux-${_kernver}/vmlinux
# install fallback mkinitcpio.conf file and preset file for kernel
install -m644 -D ${srcdir}/kernel26.preset ${pkgdir}/etc/mkinitcpio.d/${pkgname}.preset
# set correct depmod command for install
sed \
-e "s/KERNEL_NAME=.*/KERNEL_NAME=${_kernelname}/g" \
-e "s/KERNEL_VERSION=.*/KERNEL_VERSION=${_kernver}/g" \
-i $startdir/kernel26.install
sed \
-e "s|source .*|source /etc/mkinitcpio.d/kernel26${_kernelname}.kver|g" \
-e "s|default_image=.*|default_image=\"/boot/${pkgname}.img\"|g" \
-e "s|fallback_image=.*|fallback_image=\"/boot/${pkgname}-fallback.img\"|g" \
-i ${pkgdir}/etc/mkinitcpio.d/${pkgname}.preset
echo -e "# DO NOT EDIT THIS FILE\nALL_kver='${_kernver}'" > ${pkgdir}/etc/mkinitcpio.d/${pkgname}.kver
# remove build and source links
rm -f ${pkgdir}/lib/modules/${_kernver}/{source,build}
# remove the firmware
rm -rf ${pkgdir}/lib/firmware
# gzip -9 all modules to safe 100MB of space
find "$pkgdir" -name '*.ko' -exec gzip -9 {} \;
##Section: Broadcom-wl
msg "Compiling broadcom-wl module:"
cd ${srcdir}/
#patching broadcom as broadcom-wl package on AUR
patch -p1 < license.patch
patch -p1 < semaphore.patch
patch -p1 < mutex-sema.patch
make -C ${srcdir}/linux-$_basekernel M=`pwd`
install -D -m 755 wl.ko ${pkgdir}/lib/modules/$_kernver/kernel/drivers/net/wireless/wl.ko
package_kernel26-headers() {
pkgdesc="Header files and scripts for building modules for kernel26"
mkdir -p ${pkgdir}/lib/modules/${_kernver}
cd ${pkgdir}/lib/modules/${_kernver}
ln -sf ../../../usr/src/linux-${_kernver} build
cd ${srcdir}/linux-$_basekernel
install -D -m644 Makefile \
${pkgdir}/usr/src/linux-${_kernver}/Makefile
install -D -m644 kernel/Makefile \
${pkgdir}/usr/src/linux-${_kernver}/kernel/Makefile
install -D -m644 .config \
${pkgdir}/usr/src/linux-${_kernver}/.config
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/include
for i in acpi asm-generic config generated linux math-emu media net pcmcia scsi sound trace video xen; do
cp -a include/$i ${pkgdir}/usr/src/linux-${_kernver}/include/
done
# copy arch includes for external modules
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/arch/x86
cp -a arch/x86/include ${pkgdir}/usr/src/linux-${_kernver}/arch/x86/
# copy files necessary for later builds, like nvidia and vmware
cp Module.symvers ${pkgdir}/usr/src/linux-${_kernver}
cp -a scripts ${pkgdir}/usr/src/linux-${_kernver}
# fix permissions on scripts dir
chmod og-w -R ${pkgdir}/usr/src/linux-${_kernver}/scripts
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/.tmp_versions
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/arch/$KARCH/kernel
cp arch/$KARCH/Makefile ${pkgdir}/usr/src/linux-${_kernver}/arch/$KARCH/
if [ "$CARCH" = "i686" ]; then
cp arch/$KARCH/Makefile_32.cpu ${pkgdir}/usr/src/linux-${_kernver}/arch/$KARCH/
fi
cp arch/$KARCH/kernel/asm-offsets.s ${pkgdir}/usr/src/linux-${_kernver}/arch/$KARCH/kernel/
# add headers for lirc package
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/drivers/media/video
cp drivers/media/video/*.h ${pkgdir}/usr/src/linux-${_kernver}/drivers/media/video/
for i in bt8xx cpia2 cx25840 cx88 em28xx et61x251 pwc saa7134 sn9c102; do
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/drivers/media/video/$i
cp -a drivers/media/video/$i/*.h ${pkgdir}/usr/src/linux-${_kernver}/drivers/media/video/$i
done
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/drivers/staging/usbvideo/
cp -a drivers/staging/usbvideo/*.h ${pkgdir}/usr/src/linux-${_kernver}/drivers/staging/usbvideo/
# add docbook makefile
install -D -m644 Documentation/DocBook/Makefile \
${pkgdir}/usr/src/linux-${_kernver}/Documentation/DocBook/Makefile
# add dm headers
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/drivers/md
cp drivers/md/*.h ${pkgdir}/usr/src/linux-${_kernver}/drivers/md
# add inotify.h
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/include/linux
cp include/linux/inotify.h ${pkgdir}/usr/src/linux-${_kernver}/include/linux/
# add wireless headers
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/net/mac80211/
cp net/mac80211/*.h ${pkgdir}/usr/src/linux-${_kernver}/net/mac80211/
# add dvb headers for external modules
# in reference to:
# http://bugs.archlinux.org/task/9912
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb/dvb-core
cp drivers/media/dvb/dvb-core/*.h ${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb/dvb-core/
# add dvb headers for external modules
# in reference to:
# http://bugs.archlinux.org/task/11194
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/include/config/dvb/
cp include/config/dvb/*.h ${pkgdir}/usr/src/linux-${_kernver}/include/config/dvb/
# add dvb headers for http://mcentral.de/hg/~mrec/em28xx-new
# in reference to:
# http://bugs.archlinux.org/task/13146
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb/frontends/
cp drivers/media/dvb/frontends/lgdt330x.h ${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb/frontends/
cp drivers/media/video/msp3400-driver.h ${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb/frontends/
# add dvb headers
# in reference to:
# http://bugs.archlinux.org/task/20402
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb/dvb-usb
cp drivers/media/dvb/dvb-usb/*.h ${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb/dvb-usb/
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb/frontends
cp drivers/media/dvb/frontends/*.h ${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb/frontends/
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/drivers/media/common/tuners
cp drivers/media/common/tuners/*.h ${pkgdir}/usr/src/linux-${_kernver}/drivers/media/common/tuners/
# add xfs and shmem for aufs building
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/fs/xfs
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/mm
cp fs/xfs/xfs_sb.h ${pkgdir}/usr/src/linux-${_kernver}/fs/xfs/xfs_sb.h
# add headers vor virtualbox
# in reference to:
# http://bugs.archlinux.org/task/14568
cp -a include/drm $pkgdir/usr/src/linux-${_kernver}/include/
# add headers for broadcom wl
# in reference to:
# http://bugs.archlinux.org/task/14568
cp -a include/trace $pkgdir/usr/src/linux-${_kernver}/include/
# add headers for crypto modules
# in reference to:
# http://bugs.archlinux.org/task/22081
cp -a include/crypto $pkgdir/usr/src/linux-${_kernver}/include/
# copy in Kconfig files
for i in `find . -name "Kconfig*"`; do
mkdir -p ${pkgdir}/usr/src/linux-${_kernver}/`echo $i | sed 's|/Kconfig.*||'`
cp $i ${pkgdir}/usr/src/linux-${_kernver}/$i
done
chown -R root.root ${pkgdir}/usr/src/linux-${_kernver}
find ${pkgdir}/usr/src/linux-${_kernver} -type d -exec chmod 755 {} \;
# strip scripts directory
find ${pkgdir}/usr/src/linux-${_kernver}/scripts -type f -perm -u+w 2>/dev/null | while read binary ; do
case "$(file -bi "$binary")" in
*application/x-sharedlib*) # Libraries (.so)
/usr/bin/strip $STRIP_SHARED "$binary";;
*application/x-archive*) # Libraries (.a)
/usr/bin/strip $STRIP_STATIC "$binary";;
*application/x-executable*) # Binaries
/usr/bin/strip $STRIP_BINARIES "$binary";;
esac
done
# remove unneeded architectures
rm -rf ${pkgdir}/usr/src/linux-${_kernver}/arch/{alpha,arm,arm26,avr32,blackfin,cris,frv,h8300,ia64,m32r,m68k,m68knommu,mips,microblaze,mn10300,parisc,powerpc,ppc,s390,sh,sh64,sparc,sparc64,um,v850,xtensa}
package_kernel26-docs() {
pkgdesc="Kernel hackers manual - HTML documentation that comes with the Linux kernel."
cd ${srcdir}/linux-$_basekernel
mkdir -p $pkgdir/usr/src/linux-$_kernver
mv Documentation $pkgdir/usr/src/linux-$_kernver
find $pkgdir -type f -exec chmod 444 {} \;
find $pkgdir -type d -exec chmod 755 {} \;
# remove a file already in kernel26 package
rm -f $pkgdir/usr/src/linux-$_kernver/Documentation/DocBook/Makefile
I wonder if localyesconfig would take care of broadcom-wl for me...
Last edited by Ben9250 (2011-04-20 00:12:44)

Thank you. I guess trying the abs method wouldn't hurt. My main issue was configuration. I've only just skimmed the PKGBUILD so I'm not aware of how it handles it. I suppose I could write my own as described in the wiki as well. Thanks again.
Edit: Further research has revealed to me that the kernel headers are merely there for when the full source tree isn't. Seeing as the full tree is present in my case, the headers are unnecessary. I may take graysky's advice though and use pacman to manage my kernel.
Last edited by smithr.michael1997 (2011-03-31 02:17:29)

Sporadic Boot Kernel Panic

Hi all,
Looking for some advice, as I've tried searching for this specific problem but can only find 'similar' and nothing exactly like what I'm experiencing.
About a week ago, I booted up my Mac, and it gave me the startup sound and the Apple logo came on, then I got the 'You need to restart your computer...' message (which through a later search I learned was a "kernel panic" message). So I did as instructed and the second time it booted fine.
Next day, I had the same issue, only this time it took me about five or six goes before it got to the loading page, but eventually it came on.
Since then, it's been doing this every time on boot, and only ever on boot. Once it loads up, everything is fine, it doesn't crash or anything.
From reading other kernal panic messages, it seems to be suggesting that it is a problem with the RAM? I haven't touched anything to do with the system itself (I know better than to mess around with hardware =p) so before I take this to a repair shop, I was wondering if there is anything else that could be causing this?
Many thanks.

Although it certainly could be a problem with RAM, it could also be a software problem. Unfortunately, startup panics such as yours frequently are caused by corrupted system files required during startup. However, it's possible that it's a corrupted cache file causing the problem. There are some things you can do that may fix it.
First is to do the following:
Delete caches to resolve some startup problems:
Open the Terminal application in the Utilities folder. At the prompt enter or paste the following commands pressing return at the end of each:
sudo rm -rf /System/Library/Caches/com.apple.kernelcaches
You will be asked to enter your admin password. It will not be echoed.
sudo rm -rf /System/Library/Extensions.kextcache
sudo rm -rf /System/Library/Extensions.mkext
sudo rm -rf /Library/Caches/com.apple.ATS
sudo rm -rf /Library/Caches/com.apple.LaunchServices*
Quit the Terminal application and immediately restart your computer.
Second, download a utility such as TinkerTool System - VersionTracker or MacUpdate - and use it to clean all browser, user, system, and font caches; clear temp and log files. Do an immediate Restart.

Unable to boot kernel 3.9.x on Toshiba NB510 Netbook

Hi,
I'm going to start with a quick question first not related to the title:
what is the difference between the modesetting package in the official repos and the one in the AUR (git) version?
It looks as though the AUR version hasn't been updated since 2012 so I'm just wondering if for HD playback it's worth installing that over the official version?
Will that give me 1920x1080 resolution on external HDMI screen?? My Lenovo X220 with supported hardware has no issues at all with HD playback or HD res on external screens using up to date Arch stock components; so is this just a simple case of gma500 HELL??
Now for the issue that I'm having, as these things are all related to HD playback using the gma500 driver, which I'm currently going through this to help:
https://wiki.archlinux.org/index.php/Poulsbo
For some reason I'm unable to boot the 3.9.x kernel.... I've updated to all of the patch varients in the official repos and per the link above tried to build the lqx version...
I ran:
makepkg -s
pacman -U linux-lqx....tar.xz
grub-mkconfig -o /boot/grub/grub.cfg
to build and install the 64bit version. All went fine but when booting it as per all the stock kernels I get the same error:
echo 'Loading Linux lqx kernel ...'
linux /boot/vmlinuz-linux-lqx root=UUID=65811fe0-5600-4ad8-8a53-f43c89af0fad ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux-lqx-fallback.img
the system hangs right at the above....
Loading initial ramdisk ...
section.
Using kernel 3.8.11-1 64bit I'm up and running and using X11 with no problem but the newer kernels don't do anything??
This is strange as my other machine running Arch x64 also works fine with stock kernels and latest patch revision 3.9.4.
Could anyone suggest anything to resolve the issue or will I need to wait until the next generation kernel 3.10 or 4.0??
Thanks

med1972 wrote:
Same problem here. Running on a Dell E6320, UEFI boot with rEFInd. Ran my updates, copied vmlinuz and the initramfs files from /boot to /boot/efi/EFI/arch. Rebooted and I get the same error. I am pulling down a copy of the systemrescuecd now.
::running early hook [udev]
::running hook [udev]
::Triggering uevents...
Waiting 10 seconds for device /dev/sda3
ERROR: device '/dev/sda3' not found. Skipping fsck.
ERROR: Unable to find root device '/dev/sda3'.
and then it drops me into the recovery shell. There are no /dev/sd* devices. I am guessing I need to refer to the partitions by UUID instead but /dev/sda3 was working before. Actually, I don't see any disk devices under /dev at all (no /dev/disk).
- Mark
Looking through the threads, I would venture to guess that this might actually be an issue that has been discussed where recent kernels (efistub) in various combinations with rEFInd/UEFI Shell v1/UEFI Shell v2 are sometimes unbootable. Search the threads for these issues... maybe you can participate in debugging, and find a workaround along the way.

Why Multiple Kernel "issues" w/G4 iMac/Tiger?

Folks:
Lately have had a run of KPs in my ten year old +- G4 iMac . . . so we know it's "old" but overall when it's running well, it's fine. I ran the Apple Hardware test and that shows "OK" . . . I have SmartReporter and that shows fine. I booted up in ext HD and ran DU to Repair Disk, and I ran Onyx as well . . . . Today, I was trying to see if it was related to the browser, lately Ten4Fox, so I switched back to Camino but got the same "we don't support your browser" and KP there as well . . . . Then I tried to not use the internet at all and things were going well for awhile, but then got another KP that way. The computer has stopped generating "Crash Reports" to send to Apple and now just gives the kernel panic in a CLI note in black bars with white text that drops down over the desktop; multiple times the "grey" screen with the "You need to restart" happened, we aren't wasting time doing that now . . . the mouse and screen freezes and the CLI kernel trap info shows up. BTW, I also had done a PRAM reset, and then I saw BDAqua's post here about doing it three times, which I did the other day and it seemed like the problem was fixed . . . until today with 3 of them. Seems like it can happen right on revive from sleep or after running the computer for awhile. Any thoughts? I've been told already, "It's time for a new computer" and I'm reconciled to that in the near-long term as the "answer" . . . just wondering if I can get some insight into troubleshooting my dear old G4 friend and keep it going for awhile longer??? Can anybody hep me? Final note, I've got the int HD partitioned and running Xu/Lu 12.0.4, the crash problem started there and that's not new, but then continued over into the OSX side. Today, I was logged into Xu/Lu and did not have any KP while there . . . but did again back in OSX . . . . Is it "soft" or "hard" ware issue? I can't tell . . . . Many thanks for any insights.
e.e.p.

BDAqua:
Ah, "thermal paste" . . . Austin Powers didn't think about that one . . . possibly there is a flaw in the thermal paste . . . .   BTW, I did get some expert feedback on one of my earlier crash reports and the different RAM types was pointed out as a possible source of problems . . . and indeed it might be, but that difference has been there since the very first day . . . ten + years ago??? Would that suddenly become a problem? The previous reports didn't seem to offer much in terms of clues . . . this is the first time I saw "uncorrectable machine check" . . . that sounds more serious . . . even ominous . . . maybe this is all due to the impending Halloween????? Hmmmmmmmm . . . .
e.e.p.
panic(cpu 0 caller 0x000A8C00): Uncorrectable machine check: pc = 00000000000A3650, msr = 0000000000141000, dsisr = 40000000, dar = 00000000000BD000
AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000
     L2FIR = 0000000000000000, BusFir = 0000000000000000
Latest stack backtrace for cpu 0:
      Backtrace:
         0x000954F8 0x00095A10 0x00026898 0x000A8C00 0x000A7E90 0x000ABB80
Proceeding back via exception chain:
   Exception state (sv=0x2D62E500)
      PC=0x000A3650; MSR=0x00141000; DAR=0x000BD000; DSISR=0x40000000; LR=0x0009D0EC; R1=0x0CED3C50; XCP=0x00000008 (0x200 - Machine check)
      Backtrace:
0x00000000 0x0009A1FC 0x00098F78 0x00062AC8 0x000A865C 0x000ABB80
   Exception state (sv=0x2D5EC500)
      PC=0xFFFF8A50; MSR=0x0200D030; DAR=0x000BD000; DSISR=0x40000000; LR=0x00024638; R1=0xBFFF6FD0; XCP=0x0000000C (0x300 - Data access)
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPCModel: PowerMac4,2, BootROM 4.3.4f2, 1 processors, PowerPC G4 (2.1), 800 MHz, 512 MB
Graphics: NVIDIA GeForce2 MX, GeForce2 MX, AGP, 32 MB
Memory Module: DIMM0/J12, 256 MB, SDRAM, PC100-322S
Memory Module: DIMM1/J13, 256 MB, SDRAM, PC133-333
AirPort: AirPort, 9.52
Modem: Dash2, UCJ, V.92, 1.0F, APPLE VERSION 2.6.6
Network Service: Built-in Ethernet, Ethernet, en0
Parallel ATA Device: ST360020A, 55.9 GB
Parallel ATA Device: PIONEER DVD-RW DVR-104
USB Device: Keyboard Hub, Apple, Inc., Up to 12 Mb/sec, 500 mA
USB Device: USB/PS2 Wheel Mouse, Kensington, Up to 1.5 Mb/sec, 100 mA
USB Device: Apple Keyboard, Apple, Inc, Up to 1.5 Mb/sec, 220 mA
Model: PowerMac4,2, BootROM 4.3.4f2, 1 processors, PowerPC G4 (2.1), 800 MHz, 512 MB
Graphics: NVIDIA GeForce2 MX, GeForce2 MX, AGP, 32 MB
Memory Module: DIMM0/J12, 256 MB, SDRAM, PC100-322S
Memory Module: DIMM1/J13, 256 MB, SDRAM, PC133-333
AirPort: AirPort, 9.52
Modem: Dash2, UCJ, V.92, 1.0F, APPLE VERSION 2.6.6
Network Service: Built-in Ethernet, Ethernet, en0
Parallel ATA Device: ST360020A, 55.9 GB
Parallel ATA Device: PIONEER DVD-RW DVR-104
USB Device: Keyboard Hub, Apple, Inc., Up to 12 Mb/sec, 500 mA
USB Device: USB/PS2 Wheel Mouse, Kensington, Up to 1.5 Mb/sec, 100 mA
USB Device: Apple Keyboard, Apple, Inc, Up to 1.5 Mb/sec, 220 mA

New installation - Kernel Issues

Well im out of options for my server, it keeps freezing and spitting out kernel errors after a while. have tried kernel26-2.6.37.5, .38.8, lts-2.6.32.40, .41, kernel26-ck kernel26-lts-ck kernel-ck-k8. all give similar results. memtest(14Hours) and mprime(4Hours) shows no errors. It appears quickly (1-20min) when i put some load on the system (make, torrenting, mkinitcpio). The fact that i cant get 1 action to instantly result in the error has made my own error searching difficult. I have disabled most services to try to narrow down the issue but to no avail.
The hardware has been running fine for 2 years with "Mandriva Linux 2010 x86". I run archlinux on my laptop and last week i decided to install archlinux on the server, the installer went along and everything seemed fine. Then i suddenly go a freeze (same day). During boot i get an error due to udev trying to use mdadm but the binary is not there, but the 6 disk raid still mounts correctly.
The system is fully up to date. Mirror = Server = http://mirror.archlinux.no/$repo/os/x86_64
# pacman -Syyu
:: Synchronizing package databases...
core 36.0K 633.0K/s 00:00:00 [#############################################] 100%
extra 465.6K 3.5M/s 00:00:00 [#############################################] 100%
community 445.7K 3.4M/s 00:00:00 [#############################################] 100%
kernel26-ck 3.9K 29.8K/s 00:00:00 [#############################################] 100%
:: Starting full system upgrade...
there is nothing to do
DAEMONS=(hwclock syslog-ng !iptables network !openvpn !sshguard sshd mdadm !netfs !crond samba !sensors !hddtemp !mysqld !eagledns !tomcat6 !svnserve)
System info:
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ 3GHz
RAM: MemTotal: 6050888 kB
Motherboard: Asus M4A785-M
A few of the stacktraces. If anyone could understand these it would be helpful, as i am unable to:
not a complete lockup could still use ssh and dmesg
[ 387.777824] general protection fault: 0000 [#1] SMP
[ 387.786327] last sysfs file: /sys/devices/pci0000:00/0000:00:12.2/usb1/1-6/1-6:1.0/host6/target6:0:0/6:0:0:0/block/sdg/uevent
[ 387.786327] CPU 0
[ 387.786327] Modules linked in: ipv6 usb_storage ohci_hcd pata_acpi ata_generic ide_pci_generic pata_atiixp evdev i2c_piix4 asus_atk0110 ehci_hcd atiixp i2c_core shpchp edac_core ide_core usbcore edac_mce_amd k8temp pci_hotplug wmi r8169 thermal button mii processor sg ext4 mbcache jbd2 crc16 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 md_mod sd_mod ahci libata scsi_mod
[ 387.868834] Pid: 1301, comm: java Not tainted 2.6.32-lts #1 System Product Name
[ 387.868834] RIP: 0010:[<ffffffff8120627f>] [<ffffffff8120627f>] rb_erase+0x20f/0x310
[ 387.868834] RSP: 0018:ffff880194a35e98 EFLAGS: 00010206
[ 387.868834] RAX: 0000000000000000 RBX: 00ff8800cf924000 RCX: ffff8801986798e8
[ 387.868834] RDX: 00ff8800cf924000 RSI: ffff880192cfb078 RDI: ffff88019784f700
[ 387.868834] RBP: ffff880194a35ea8 R08: 0000000000000000 R09: 2222222222222222
[ 387.868834] R10: 0000000000000000 R11: 0000000000000000 R12: ffff880192cfb078
[ 387.868834] R13: ffff880198679840 R14: 000000000000003e R15: ffff880192cfb000
[ 387.868834] FS: 00007f1b70449700(0000) GS:ffff880006e00000(0000) knlGS:0000000000000000
[ 387.868834] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 387.868834] CR2: 00007f1b5d5d2718 CR3: 000000019518d000 CR4: 00000000000006f0
[ 387.868834] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 387.868834] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 388.117928] Process java (pid: 1301, threadinfo ffff880194a34000, task ffff8801994f5d70)
[ 388.117928] Stack:
[ 388.117928] ffff88019784f700 ffff880192cfb000 ffff880194a35ed8 ffffffff811827de
[ 388.117928] <0> ffff880194a35ed8 ffff880198679840 ffff880192cfbb40 0000000000000002
[ 388.117928] <0> ffff880194a35f78 ffffffff81183432 ffff880194a35f78 ffff880000000000
[ 388.117928] Call Trace:
[ 388.117928] [<ffffffff811827de>] ep_remove+0x5e/0xc0
[ 388.117928] [<ffffffff81183432>] sys_epoll_ctl+0x3b2/0x590
[ 388.117928] [<ffffffff81182630>] ? ep_ptable_queue_proc+0x0/0xc0
[ 388.117928] [<ffffffff81012072>] system_call_fastpath+0x16/0x1b
[ 388.117928] Code: 8b 47 08 4c 89 c2 41 83 e0 01 48 83 e2 fc 48 85 c0 48 89 d3 74 0c 48 8b 08 83 e1 03 48 09 d1 48 89 08 48 85 d2 0f 84 ba 00 00 00 <48> 39 7a 10 0f 84 b9 00 00 00 48 89 42 08 e9 8f fe ff ff 4c 8b
[ 388.117928] RIP [<ffffffff8120627f>] rb_erase+0x20f/0x310
[ 388.117928] RSP <ffff880194a35e98>
[ 388.435560] ---[ end trace e9bef56bd87d805e ]---
#Had to copy this by hand so i skipped some parts.
general protection fault: 0000 [#1] PREEMPT SMP
last sysfs file: /sys/devices/pci0000:00/0000:00:0a.0/0000:02:00.00/firmware/0000:02:00.0/loading
CPU 1
Modules linked in: ...
Pid: 1224, comm: java Not tianted 2.6.39-ARCH #1 System manufacturer System Product Name/M4A785-M
RIP 0010:[<ffffffff8113d669>] [<ffffffff8113d669>] kmem_cache_alloc+0x49/0x160
RSP: 0018:ffff88019523dd38 EFLAGS: 00010202
Process java (pid: 1224, threadinfo ffff88019523c000, task ffff880194c846a0)
Stack ffff88019523dda8 0000000000001000 0000000000000000 000080d000000000
ffff88019523df28 0000000000000001 ffff880194dc6180 ffff880037ff3000
00000000ffffff9c 0000000000000041 ffff88019523dda8 ffffffff811532db
Call Trace:
[] get_empty_filp+0x5b/0x170
[] path_openat+0x3d/0x3c0
[] ? putname+0x35/0x50
[] ? user_path_at+0x64/0xa0
[] do_filp_open+0x42/0xa0
[] ? alloc_fd+0xec/0x140
[] do_sys_open+0xf7/0x1d0
[] sys_open+0x20/0x30
[] system_call_fastpath+0x16/0x1b
Code: 75 cc 49 8b 45 00 65 48 03 04 25 10 dc 00 00 48 8b 50 08 4c 8b 20 4d 85 e4 0f 84 fb 00 00 00 49 63 45 20 49 8b 75 00
#Had to copy this by hand so i skipped some parts.
kernel26-lts seems to have a lower resolution so top is not visible. ca 5min this time before error using vuze (torrenting).
cs:..
process md2_raid5 (pid: 390, threadinfo ffff880195b3a000, task ffff880197248730)
Stack:
ffff880195b3bc40 0000000000000086 ffff880199454de0 0000000000000003
<0> ffff880195f08db0 ffff880195b3bd78 ffff880195d14e00 ffff880195d14f88
<0> ffff880195b3bc70 ffffffffa00791d7 ffff880195b3bbcd0 ffffffffa00cda52
Call Trace:
md_write_end+0x47/0x60 [md_mod]
handle_stripe_clean_event+0x102/0x1d0 [raid456]
handle_stripe+0xf1e/ox1c70 [raid456]
? __wake_up+0x64/0x70
raid5d+0x363/0x4a0 [raid456]
? process_timeout+0x0/0x10
md_thread+0x4b/0x120 [md_mod]
? autoremove_wake_function+0x0/0x40
? md_thread+0x0/0x120 [md_mod]
kthread+0x88/0x90
? finish_task_switch+0x48/0xd0
child_rip+0xa/0x20
?kthread+0x0/0x90
? child_rip+0x0/0x20
Code: 8b 03 48 85 c0 74 3e 44 8b 0d d4 23 58 00 45 85 c9 0f 85 7a 01 00 00 48 8b 53 08 49 b8 00 02 20 00 00 00 ad de 41 be 01 00 00 00 <48> 89 50 08 48 89 02 4c 89 43 08 49 8b 44 24 18 48 39 43 10 0f
RIP: [<ffffffff810720d1>] mod_timer+0x91/0x230
RSP <ffff880195b3bc20>
CR2: ffff88ff81788458
--[ end trace 079c6e93730f5131 ]---
Any help is appreciated!
Last edited by exuvo (2011-07-05 23:03:09)

Your mdadm error on boot is unrelated, and a non-issue. We package mdadm's udev rule in the initcpio, which does autodetection and autoassembly of mdadm arrays via the mdadm binary. However, our mdadm initcpio hook uses /etc/mdadm.conf based assembly with mdassemble instead. You can safely ignore this "error".
All the activities you mention are disk related, and all of the crashes you post are from the VFS or block layer. You're got a disk problem somewhere. I'm sorry I can't be more specific than that.
Last edited by falconindy (2011-07-06 01:04:16)

2.6.30 kernel issues

Hi all,
This is just a report that I've had several issues with the new 2.6.30 kernel that have been most unwelcome. Two of my systems were affected:
1) My dual-processor server started hard-locking during any spike in I/O, be it on one of my multiple harddrives or the ethernet card. I spent several hours trying to fix this, thinking it was a hardware issue. The ultimate resolution was to boot with "noapic nolapic", which stopped the hardlocks completely. However, this also disabled the smp in the kernel, so is a suboptimal solution. This is the first kernel I have ever had this problem with.
2) My laptop no longer boots after the kernel upgrade. It decompresses the kernel image and then immediately reboots. I've seen a mention of similar issues on the forums here. My suspicion is that the mkinitcpio had some bad configuration and nuked the image. I'll look into this later.
The hardware and setup of these two systems are quite different and both took a hit with the new kernel. Has anyone considered downgrading the kernel since many users are reporting problems?
Cheers.

sekaino_ai wrote:The hardware and setup of these two systems are quite different and both took a hit with the new kernel. Has anyone considered downgrading the kernel since many users are reporting problems?
Not meaning to be mean or anything, but most users (including those who used the kernel while it was in [testing]) did not have those issues, or they would have been resolved before being released into [core]. With rolling release, it doesn't make sense to downgrade the repo's versions just because SOME users are having problems, since this effects everyone using Arch, including the 'most' who are not having problems.
That having been said, if you were speaking of an individualized downgrading of the kernel (as mentioned in the first response) instead of a general change in the version available in the repos, then my apologies, you are of course free to do that, there's even a nice wiki page on the procedure.

Boot/Kernel issue

Similar Messages

Maybe you are looking for