Btrfs kernel bug

I have just booted my system to be greated by error about bug in kernel (btrfs module).
My system is up to date, latest kernel, mkinitcpio etc. I upgraded after this bug with memory card reader hoping that it will be fixed.
And system crashed uppon inserting memory card, then I rebooted and got this btrfs bug. (yes, i checked all .pacnew files after upgrade)
I do not use compression, becouse there was bug with that in kernel .37
I booted in my install on usb disk to check it out. And when I mount that btrfs partition same error happens and system crashes.
Now I am downloading Linux Mint to inspect it from there. I can't post any logs becouse there is nothing relevant in there.
Please help, I need my system operational within hours.
All my config data and personal stuff is on seperate ext4 partition, so moving to other distro is easy. Im thinking about #! linux.
Do you think it is solid replacement for Arch?

No, I want to change distro because of need of frequent system maintenance and few situations like this one, when I really need something trivial (like mount SD card) and then you run into troubles. I'm using arch over 3 years now, and so far it worked that way. But as amount of my free time decreases, so my need for stable system increases.
However, about btrfs, I've been using it since kernel .36, I installed it just to give it a try. It worked well. Untill now.
My data is on separate partition using ext4, so no harm done with this, beside me booting from usb drive.
I still don't understand what happened to that btrfs partition. I can't mount it anyhow. Even Linux Mint freezes when I try to mount it (it uses .35 kernel).
So I will just format it and reinstall something over it.

Similar Messages

[Solved] Kernel BUG at include/linux/netdevice.h:501, and sky2?

So, ever since a certain point in time between kernel 3.11.x and now (3.12.5-1), I have been getting this strangely inconsistent error on bootup. I would estimate that about 3 out of every 4 reboots leads to this error message, and the bootup process terminates in a black screen and what (appears) to be a system hang. However I CTL+ALT+F2, log in, and I output dmesg to a boot log, and everything my eyes have seen is now your visual property as well. The remaining 25% of my reboots patches through and boots directly to my window manager successfully. Now the output seems to be screaming to me "sky2 is the culprit", as EIP seems to be pointing in its general direction at the time of error. However, I am more inclined to believe that my hardware's interaction with the driver is more likely to be responsible. If sky2 was actually a real problem, I doubt I would be the only one complaining about this. Nonetheless, I am quite vexed, and would greatly appreciate anbody's help here. Much appreciated, and perhaps I can provide you with some other (perhaps) useful information:
MotherBoard: Asus P5KE (with suspect ethernet controller built in)
Ethernet Controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)
Kernel: 3.12.5-1
CPU: Dual core 2.33 ghz
RAM: 2GB (recently has not passed a memtest)
[ 9.699863] sky2: driver version 1.30
[ 9.699960] sky2 0000:02:00.0: Yukon-2 EC Ultra chip revision 2
[ 9.700020] sky2 0000:02:00.0: irq 45 for MSI/MSI-X
[ 9.700498] ------------[ cut here ]------------
[ 9.703391] kernel BUG at include/linux/netdevice.h:501!
[ 9.703391] invalid opcode: 0000 [#1] PREEMPT SMP
[ 9.703391] Modules linked in: sky2(+) i2c_core snd_hda_codec_analog acpi_cpufreq processor button snd_hda_intel(+) snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore shpchp intel_agp asus_atk0110 intel_gtt agpgart ext4 crc16 mbcache jbd2 sd_mod hid_logitech ff_memless usbhid hid firewire_ohci ahci libahci firewire_core crc_itu_t libata scsi_mod ehci_pci uhci_hcd ehci_hcd usbcore usb_common
[ 9.703391] CPU: 0 PID: 155 Comm: dhcpcd Not tainted 3.12.5-1-ARCH #1
[ 9.703391] Hardware name: System manufacturer P5K-E/P5K-E, BIOS 0906 12/10/2007
[ 9.703391] task: f562f4d0 ti: f50fa000 task.ti: f50fa000
[ 9.703391] EIP: 0060:[<fa99372f>] EFLAGS: 00010246 CPU: 0
[ 9.703391] EIP is at sky2_setup_irq+0x9f/0xb0 [sky2]
[ 9.703391] EAX: 00000000 EBX: f51c8100 ECX: 00000089 EDX: 00000000
[ 9.703391] ESI: f5dfb000 EDI: 00000000 EBP: f50fbdf0 ESP: f50fbdd8
[ 9.703391] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 9.830016] sky2 0000:02:00.0 eth0: addr 00:1b:fc:61:1c:91
[ 9.830018] CR0: 80050033 CR2: f9133760 CR3: 356f4000 CR4: 000007d0
[ 9.830018] Stack:
[ 9.830018] 00000000 f51b1000 f51c8100 f51b1000 f51c8100 00000000 f50fbe2c fa996169
[ 9.830018] 00000020 00000000 c1007210 00000400 f51b15b4 00000000 f50fbe1c c1007210
[ 9.830018] f51b1500 000000e0 f51b1000 fa999f40 00000000 f50fbe50 c135ed4b 00000246
[ 9.830018] Call Trace:
[ 9.830018] [<fa996169>] sky2_open+0x309/0x360 [sky2]
[ 9.830018] [<c1007210>] ? via_no_dac+0x40/0x40
[ 9.830018] [<c1007210>] ? via_no_dac+0x40/0x40
[ 9.830018] [<c135ed4b>] __dev_open+0x9b/0x120
[ 9.830018] [<c1431cbe>] ? _raw_spin_unlock_bh+0x1e/0x20
[ 9.830018] [<c135efd9>] __dev_change_flags+0x89/0x150
[ 9.830018] [<c135f148>] dev_change_flags+0x18/0x50
[ 9.830018] [<c13bb8e0>] devinet_ioctl+0x5d0/0x6e0
[ 9.830018] [<c13bcced>] inet_ioctl+0x6d/0xa0
[ 9.830018] [<c1346094>] sock_ioctl+0x114/0x250
[ 9.830018] [<c1345f80>] ? sock_fasync+0x80/0x80
[ 9.830018] [<c1166416>] do_vfs_ioctl+0x2e6/0x4e0
[ 9.830018] [<c1435127>] ? __do_page_fault+0x2e7/0x580
[ 9.830018] [<c11576f6>] ? __fput+0x106/0x1f0
[ 9.830018] [<c116668f>] SyS_ioctl+0x7f/0x90
[ 9.830018] [<c143874d>] sysenter_do_call+0x12/0x28
[ 9.830018] Code: 8d 74 26 00 8b 86 d8 01 00 00 83 c6 64 89 34 24 c7 44 24 04 91 97 99 fa 89 44 24 08 e8 fb d1 95 c6 89 f8 83 c4 0c 5b 5e 5f 5d c3 <0f> 0b eb 0d 90 90 90 90 90 90 90 90 90 90 90 90 90 55 89 e5 53
[ 9.830018] EIP: [<fa99372f>] sky2_setup_irq+0x9f/0xb0 [sky2] SS:ESP 0068:f50fbdd8
[ 10.114977] ---[ end trace 6853181d11e5e45a ]---
[ 10.121597] [drm] Initialized drm 1.1.0 20060810
[ 10.598013] nvidia: module license 'NVIDIA' taints kernel.
[ 11.366133] ACPI Warning: 0x00000400-0x0000041f SystemIO conflicts with Region \SMRG 1 (20130725/utaddress-251)
[ 11.372053] input: PC Speaker as /devices/platform/pcspkr/input/input15
[ 11.389363] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 11.436774] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input18
[ 11.449056] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
[ 11.461240] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
[ 11.473379] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input14
[ 11.485835] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
[ 11.498462] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 0
[ 11.510829] NVRM: loading NVIDIA UNIX x86 Kernel Module 331.20 Wed Oct 30 16:59:55 PDT 2013
[ 11.523659] iTCO_vendor_support: vendor-support=0
[ 11.539930] gpio_ich: GPIO from 195 to 255 on gpio_ich
[ 11.714329] microcode: CPU0 sig=0x6fb, pf=0x1, revision=0xb6
[ 11.727418] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
[ 11.740101] iTCO_wdt: Found a ICH9R TCO device (Version=2, TCOBASE=0x0860)
[ 11.753434] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 11.767642] microcode: CPU1 sig=0x6fb, pf=0x1, revision=0xb6
[ 11.781056] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
[ 12.042064] coretemp coretemp.0: Using relative temperature scale!
[ 12.055598] coretemp coretemp.0: Using relative temperature scale!
[ 14.944832] systemd-journald[110]: File /var/log/journal/2e32c4787d3945018666d6257394d8b8/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[ 18.610023] nvidia 0000:01:00.0: irq 46 for MSI/MSI-X
[ 19.320584] NVRM: Your system is not currently configured to drive a VGA console
[ 19.320590] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[ 19.320593] NVRM: requires the use of a text-mode VGA console. Use of other console
[ 19.320595] NVRM: drivers including, but not limited to, vesafb, may result in
[ 19.320597] NVRM: corruption and stability problems, and is not supported.
Last edited by eazar001 (2014-01-24 22:02:50)

UPDATE: So I ran some low level troubleshooting and decided to test out the linux-lts (3.10.24-1-lts) kernel. No problems at all. Everything works fine with my ethernet adapter and the sky2 module. It just appears that something occurred in the newer kernels to break the interface for at least one Marvell adapter. This solution works for now, but I suppose I should file a bug report eventually. In the meantime, any insight is welcome.

Help to report a kernel bug (2.6.32, 2.6.31 and 2.6.33rc8)

Hi. I have problems with latest kernels. After suspend (to ram), wired connection doesn't work (eth0 doesn't connect). It occurs with those kernels in ArchLinux 32 bits and with 2.6.31 in Ubuntu Karmik.
The card is:
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8036 PCI-E Fast Ethernet Controller (rev 10)
and the sys log is:
Feb 23 18:50:01 eduardo crond[3083]: FILE /var/spool/cron/eduardo USER eduardo PID 4029 /usr/share/prey/prey.sh > /dev/null
Feb 23 18:50:01 eduardo crond[3083]: FILE /var/spool/cron/root USER root PID 4030 /usr/share/prey/prey.sh > /dev/null
Feb 23 18:50:57 eduardo NetworkManager: <info> Sleeping...
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth0): now unmanaged
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth0): device state change: 8 -> 1 (reason 37)
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth0): deactivating device (reason: 37).
Feb 23 18:50:57 eduardo avahi-daemon[3214]: Withdrawing address record for 192.168.1.11 on eth0.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.11.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: Interface eth0.IPv4 no longer relevant for mDNS.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: querier.c: querier_remove() called but no querier to remove.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: querier.c: querier_remove() called but no querier to remove.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: querier.c: querier_remove() called but no querier to remove.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: querier.c: querier_remove() called but no querier to remove.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: querier.c: querier_remove() called but no querier to remove.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: querier.c: querier_remove() called but no querier to remove.
Feb 23 18:50:57 eduardo dhcpcd: received SIGTERM, stopping
Feb 23 18:50:57 eduardo dhcpcd: eth0: removing interface
Feb 23 18:50:57 eduardo kernel: sky2 eth0: disabling interface
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth0): canceled DHCP transaction, dhcp client pid 3516
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth0): cleaning up...
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth0): taking down device.
Feb 23 18:50:57 eduardo avahi-daemon[3214]: Withdrawing address record for fe80::2a0:d1ff:fe2d:57b5 on eth0.
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth1): now unmanaged
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth1): device state change: 2 -> 1 (reason 37)
Feb 23 18:50:57 eduardo NetworkManager: <info> (eth0): carrier now OFF (device state 1)
Feb 23 18:50:57 eduardo NetworkManager: <WARN> nm_dhcp_manager_handle_event(): Received DHCP event from unexpected PID 3516 (expected 0)
Feb 23 18:50:57 eduardo kernel: [drm] Num pipes: 1
Feb 23 18:51:07 eduardo kernel: PM: Syncing filesystems ... done.
Feb 23 18:51:07 eduardo kernel: PM: Preparing system for mem sleep
Feb 23 18:51:07 eduardo kernel: Freezing user space processes ... (elapsed 0.00 seconds) done.
Feb 23 18:51:07 eduardo kernel: Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Feb 23 18:51:07 eduardo kernel: PM: Entering mem sleep
Feb 23 18:51:07 eduardo kernel: Suspending console(s) (use no_console_suspend to debug)
Feb 23 18:51:07 eduardo kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Feb 23 18:51:07 eduardo kernel: sd 0:0:0:0: [sda] Stopping disk
Feb 23 18:51:07 eduardo kernel: ACPI handle has no context!
Feb 23 18:51:07 eduardo kernel: ACPI handle has no context!
Feb 23 18:51:07 eduardo kernel: sdhci-pci 0000:06:06.4: PCI INT A disabled
Feb 23 18:51:07 eduardo kernel: ACPI handle has no context!
Feb 23 18:51:07 eduardo kernel: ACPI handle has no context!
Feb 23 18:51:07 eduardo kernel: tifm_7xx1 0000:06:06.3: PCI INT D disabled
Feb 23 18:51:07 eduardo kernel: ACPI handle has no context!
Feb 23 18:51:07 eduardo kernel: ACPI handle has no context!
Feb 23 18:51:07 eduardo kernel: eth1: Going into suspend...
Feb 23 18:51:07 eduardo kernel: ipw2200 0000:06:04.0: PCI INT A disabled
Feb 23 18:51:07 eduardo kernel: ACPI handle has no context!
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: PCI INT A disabled
Feb 23 18:51:07 eduardo kernel: ata_piix 0000:00:1f.2: PCI INT B disabled
Feb 23 18:51:07 eduardo kernel: Intel ICH Modem 0000:00:1e.3: PCI INT B disabled
Feb 23 18:51:07 eduardo kernel: Intel ICH 0000:00:1e.2: PCI INT A disabled
Feb 23 18:51:07 eduardo kernel: ehci_hcd 0000:00:1d.7: PCI INT A disabled
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.3: PCI INT D disabled
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.2: PCI INT C disabled
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.1: PCI INT B disabled
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.0: PCI INT A disabled
Feb 23 18:51:07 eduardo kernel: ACPI: Preparing to enter system sleep state S3
Feb 23 18:51:07 eduardo kernel: Disabling non-boot CPUs ...
Feb 23 18:51:07 eduardo kernel: Back to C!
Feb 23 18:51:07 eduardo kernel: Force enabled HPET at resume
Feb 23 18:51:07 eduardo kernel: ACPI: Waking up from system sleep state S3
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:01.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:1c.0: restoring config space at offset 0xf (was 0x2010b, writing 0x2010a)
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:1c.0: restoring config space at offset 0x9 (was 0x10001, writing 0x8ff18c01)
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:1c.0: restoring config space at offset 0x8 (was 0x0, writing 0xbff0bc00)
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:1c.0: restoring config space at offset 0x7 (was 0x0, writing 0xb0a0)
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:1c.0: restoring config space at offset 0x6 (was 0x0, writing 0x20200)
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:1c.0: restoring config space at offset 0x3 (was 0x810000, writing 0x810004)
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
Feb 23 18:51:07 eduardo kernel: pcieport 0000:00:1c.1: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.0: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.1: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.2: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.3: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
Feb 23 18:51:07 eduardo kernel: ehci_hcd 0000:00:1d.7: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900002)
Feb 23 18:51:07 eduardo kernel: pci 0000:00:1e.0: restoring config space at offset 0x6 (was 0x20060600, writing 0x200a0600)
Feb 23 18:51:07 eduardo kernel: Intel ICH 0000:00:1e.2: restoring config space at offset 0x1 (was 0x2900007, writing 0x2900003)
Feb 23 18:51:07 eduardo kernel: Intel ICH Modem 0000:00:1e.3: restoring config space at offset 0x1 (was 0x2900005, writing 0x2900001)
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: restoring config space at offset 0xf (was 0x1ff, writing 0x10b)
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: restoring config space at offset 0x6 (was 0x0, writing 0xc0000000)
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: restoring config space at offset 0x5 (was 0x1, writing 0xc001)
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: restoring config space at offset 0x4 (was 0x8, writing 0x90000008)
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x4)
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100003)
Feb 23 18:51:07 eduardo kernel: sky2 0000:02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
Feb 23 18:51:07 eduardo kernel: sky2 0000:02:00.0: restoring config space at offset 0x6 (was 0x1, writing 0xa001)
Feb 23 18:51:07 eduardo kernel: sky2 0000:02:00.0: restoring config space at offset 0x4 (was 0x4, writing 0xbc000004)
Feb 23 18:51:07 eduardo kernel: sky2 0000:02:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x4)
Feb 23 18:51:07 eduardo acpid: client 3452[0:0] has disconnected
Feb 23 18:51:07 eduardo kernel: sky2 0000:02:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100007)
Feb 23 18:51:07 eduardo kernel: ipw2200 0000:06:04.0: restoring config space at offset 0xf (was 0x18030100, writing 0x1803010b)
Feb 23 18:51:07 eduardo kernel: ipw2200 0000:06:04.0: restoring config space at offset 0x4 (was 0x0, writing 0xb000b000)
Feb 23 18:51:07 eduardo kernel: ipw2200 0000:06:04.0: restoring config space at offset 0x3 (was 0x0, writing 0x8000)
Feb 23 18:51:07 eduardo kernel: ipw2200 0000:06:04.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900006)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0xf (was 0x34001ff, writing 0x5c001ff)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0xe (was 0x0, writing 0x64fc)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0xd (was 0x0, writing 0x6400)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0xc (was 0x0, writing 0x60fc)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0xb (was 0x0, writing 0x6000)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0xa (was 0x0, writing 0xb7fff000)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0x9 (was 0x0, writing 0xb4000000)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0x8 (was 0x0, writing 0x83fff000)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0x7 (was 0x0, writing 0x80000000)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0x6 (was 0x40000000, writing 0xb00a0706)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0x4 (was 0x0, writing 0xb0001000)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0x3 (was 0x820000, writing 0x82a808)
Feb 23 18:51:07 eduardo kernel: yenta_cardbus 0000:06:06.0: restoring config space at offset 0x1 (was 0x2100000, writing 0x2100007)
Feb 23 18:51:07 eduardo kernel: firewire_ohci 0000:06:06.2: restoring config space at offset 0xf (was 0x4020300, writing 0x402030b)
Feb 23 18:51:07 eduardo kernel: firewire_ohci 0000:06:06.2: restoring config space at offset 0x5 (was 0x0, writing 0xb0004000)
Feb 23 18:51:07 eduardo kernel: firewire_ohci 0000:06:06.2: restoring config space at offset 0x4 (was 0x0, writing 0xb0000000)
Feb 23 18:51:07 eduardo kernel: firewire_ohci 0000:06:06.2: restoring config space at offset 0x3 (was 0x800000, writing 0x808004)
Feb 23 18:51:07 eduardo kernel: firewire_ohci 0000:06:06.2: restoring config space at offset 0x1 (was 0x2100000, writing 0x2100006)
Feb 23 18:51:07 eduardo kernel: tifm_7xx1 0000:06:06.3: restoring config space at offset 0xf (was 0x40704ff, writing 0x4070405)
Feb 23 18:51:07 eduardo kernel: tifm_7xx1 0000:06:06.3: restoring config space at offset 0x4 (was 0x0, writing 0xb0008000)
Feb 23 18:51:07 eduardo kernel: tifm_7xx1 0000:06:06.3: restoring config space at offset 0x3 (was 0x800000, writing 0x808004)
Feb 23 18:51:07 eduardo kernel: tifm_7xx1 0000:06:06.3: restoring config space at offset 0x1 (was 0x2100000, writing 0x2100006)
Feb 23 18:51:07 eduardo kernel: sdhci-pci 0000:06:06.4: restoring config space at offset 0xf (was 0x40701ff, writing 0x407010b)
Feb 23 18:51:07 eduardo kernel: sdhci-pci 0000:06:06.4: restoring config space at offset 0x6 (was 0x0, writing 0xb000a200)
Feb 23 18:51:07 eduardo kernel: sdhci-pci 0000:06:06.4: restoring config space at offset 0x5 (was 0x0, writing 0xb000a100)
Feb 23 18:51:07 eduardo kernel: sdhci-pci 0000:06:06.4: restoring config space at offset 0x4 (was 0x0, writing 0xb000a000)
Feb 23 18:51:07 eduardo kernel: sdhci-pci 0000:06:06.4: restoring config space at offset 0x3 (was 0x800000, writing 0x808004)
Feb 23 18:51:07 eduardo kernel: sdhci-pci 0000:06:06.4: restoring config space at offset 0x1 (was 0x2100000, writing 0x2100006)
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.0: PCI INT A -> Link[LNKH] -> GSI 10 (level, low) -> IRQ 10
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: usb usb2: root hub lost power or was reset
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.1: PCI INT B -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: usb usb3: root hub lost power or was reset
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.2: PCI INT C -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: usb usb4: root hub lost power or was reset
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.3: PCI INT D -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
Feb 23 18:51:07 eduardo kernel: uhci_hcd 0000:00:1d.3: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: usb usb5: root hub lost power or was reset
Feb 23 18:51:07 eduardo kernel: ehci_hcd 0000:00:1d.7: PCI INT A -> Link[LNKH] -> GSI 10 (level, low) -> IRQ 10
Feb 23 18:51:07 eduardo kernel: ehci_hcd 0000:00:1d.7: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: pci 0000:00:1e.0: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: Intel ICH 0000:00:1e.2: PCI INT A -> Link[LNKB] -> GSI 10 (level, low) -> IRQ 10
Feb 23 18:51:07 eduardo kernel: Intel ICH 0000:00:1e.2: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: Intel ICH Modem 0000:00:1e.3: PCI INT B -> Link[LNKE] -> GSI 5 (level, low) -> IRQ 5
Feb 23 18:51:07 eduardo kernel: Intel ICH Modem 0000:00:1e.3: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: ata_piix 0000:00:1f.2: PCI INT B -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
Feb 23 18:51:07 eduardo kernel: ata_piix 0000:00:1f.2: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
Feb 23 18:51:07 eduardo kernel: pci 0000:01:00.0: setting latency timer to 64
Feb 23 18:51:07 eduardo kernel: sky2 0000:02:00.0: ignoring stuck error report bit
Feb 23 18:51:07 eduardo kernel: eth1: Coming out of suspend...
Feb 23 18:51:07 eduardo kernel: ipw2200 0000:06:04.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
Feb 23 18:51:07 eduardo kernel: ipw2200: Radio Frequency Kill Switch is On:
Feb 23 18:51:07 eduardo kernel: Kill switch must be turned off for wireless networking to work.
Feb 23 18:51:07 eduardo kernel: ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
Feb 23 18:51:07 eduardo kernel: ata2.00: ACPI cmd ef/03:42:00:00:00:a0 (SET FEATURES) filtered out
Feb 23 18:51:07 eduardo kernel: ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
Feb 23 18:51:07 eduardo kernel: ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
Feb 23 18:51:07 eduardo kernel: ata1.00: configured for UDMA/100
Feb 23 18:51:07 eduardo kernel: ata2.00: configured for UDMA/33
Feb 23 18:51:07 eduardo kernel: firewire_core: skipped bus generations, destroying all nodes
Feb 23 18:51:07 eduardo kernel: tifm_7xx1 0000:06:06.3: PCI INT D -> Link[LNKE] -> GSI 5 (level, low) -> IRQ 5
Feb 23 18:51:07 eduardo kernel: sdhci-pci 0000:06:06.4: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
Feb 23 18:51:07 eduardo kernel: sd 0:0:0:0: [sda] Starting disk
Feb 23 18:51:07 eduardo kernel: firewire_core: rediscovered device fw0
Feb 23 18:51:07 eduardo kernel: usb 2-1: reset low speed USB device using uhci_hcd and address 2
Feb 23 18:51:07 eduardo kernel: PM: Finishing wakeup.
Feb 23 18:51:07 eduardo kernel: Restarting tasks ... done.
Feb 23 18:51:07 eduardo logger: ACPI action undefined: BAT1
Feb 23 18:51:08 eduardo acpid: client connected from 3452[0:0]
Feb 23 18:51:08 eduardo acpid: 1 client rule loaded
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo NetworkManager: <info> Waking up...
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth0): now managed
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth0): device state change: 1 -> 2 (reason 2)
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth0): bringing up device.
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth0): preparing device.
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth0): deactivating device (reason: 2).
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth1): now managed
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth1): device state change: 1 -> 2 (reason 2)
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth1): bringing up device.
Feb 23 18:51:08 eduardo NetworkManager: <info> (eth1): deactivating device (reason: 2).
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 0000:02:00.0: eth0: phy I/O error
Feb 23 18:51:08 eduardo kernel: sky2 eth0: enabling interface
Feb 23 18:51:08 eduardo kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Due to this problem affects ubuntu and arch I suppose that there is a problem in kernel (or in my laptop, but with 2.6.30 works fine). I would report this to kernel bugs but I don't know how. Thanks

Hi. I have a problem. bisected kernel between ------------[ cut here ]------------ WARNING: at arch/x86/kernel/apic/apic.c:249 Hardware name: Satellite M40 Modules linked in: Pid: 0, comm: swapper Not tainted 2.6.30-ARCH-05856-g925d74a Call Trace: [<c104275a>] ? ret_point+0x41684/0x2f79f9 [<c101cc8b>] ? ret_point+0x1bbb5/0x2f79f9 [<c10427c0>] ? ret_point+0x416ea/0x2f79f9 [<c101cc8b>] ? ret_point+0x1bbb5/0x2f79f9 [<c10139b1>] ? ret_point+0x128db/0x2f79f9 [<c1012313>] ? ret_point+0x1123d/0x2f79f9 [<c10e23f3>] ? ret_point+0xe131d/0x2f79f9 [<c1013805>] ? ret_point+0x1272f/0x2f79f9 [<c12f0314>] ? ret_point+0x2ef23e/0x2f79f9 [<c12ee422>] ? ret_point+0x2ed34c/0x2f79f9 [<c1418d66>] ? __smp_locks_end+0x843e/0x34c98 [<c1418f65>] ? __smp_locks_end+0x863d/0x34c98 [<c1095dd0>] ? ret_point+0x94cfa/0x2f79f9 [<c1411a18>] ? __smp_locks_end+0x10f0/0x34c98 [<c14114dc>] ? __smp_locks_end+0xbb4/0x34c98 ---[ end trace a7919e7f17c0a725 ]---
What do in this case??
Also this:
Pid: 25, comm: udevd Tainted: G W Call Trace: [<c11891f1>] ? ret_point+0x18811b/0x2f79f9 [<c111acac>] ? ret_point+0x119bd6/0x2f79f9 [<c111e0b0>] ? ret_point+0x11cfda/0x2f79f9 [<c111b8ed>] ? ret_point+0x11a817/0x2f79f9 [<c111e163>] ? ret_point+0x11d08d/0x2f79f9 [<c1003c73>] ? ret_point+0x2b9d/0x2f79f9

ret_point+0x1bbb5/0x2f79f9()

#1

2.6.30-ARCH-05856-g925d74a #1

/> 20:25:40)

Random system freezes - "kernel BUG at fs/inode.c:427!"

Hi there,
I got some weird problem: From time to time my system freezes randomly (and completely - hard reset). This was not always the case. Unfortunately I can't remember the exact date of the beginning of this freezes (and if I could I wouldn't know what I had done before), but in my humble oppinion the problem occurs since the upgrade to linux-3.1.6. Right now I'm running 3.1.9
After shutting down my notebook (a Thinkpad L520, Sandy Bridge), often I can't even properly start it again (mostly just black screen - does nothing). In that case I usually remove the battery, wait a few seconds, put it back in and then the computer boots without problems.
Sometimes (e.g. at the time of writing this) this problem occurs more often than usual.
Until today I had no clue what caused this. I disabled a lot of functionalities in the BIOS, unplugged everything (second monitor, etc.), did a memtest86 (without errors). A few hours ago I luckily got a kernel panic message on my screen (I assume it got there "before it was too late"). See a "screenshot" of here: http://i.imgur.com/LdgFE.jpg
The "kernel BUG at fs/inode.c:427!" line got my attention - could this be a filesystem bug? I got an Intel 310 Series SSD in my notebook, running ext4 on it. Could it be possible that there is some issue with that or just an annoying bug?
Maybe someone can help
For the curious:
My fstab:
/dev/sdb1 /boot ext2 defaults 0 1
/dev/sdb2 / ext4 defaults,noatime,discard,user_xattr 0 1
/dev/sda1 /mnt/data ntfs-3g uid=mlux,gid=users 0 0
rc.conf MODULES
MODULES=(acpi-cpufreq cpufreq_ondemand cpufreq_powersave ac battery button fan thinkpad_acpi)
rc.conf DAEMONS
DAEMONS=(syslog-ng @crond @cpufreq @tlp @acpid @cupsd @privoxy dbus networkmanager slim)
uname -a
rc.conf MODULES
Linux luxbox 3.1.9-2-ARCH #1 SMP PREEMPT Sat Jan 14 09:11:37 CET 2012 x86_64 Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz GenuineIntel GNU/Linux
lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b4)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000
04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5116 PCI Express Card Reader (rev 01)
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)

helloworld1 wrote:Have you tried fsck you disk?
Yep - did that - nothing suspicious.

[SOLVED] Kernel bug fix, works for me!

Having been hit by the kernel bug that interferes with internet access & having to downgrade the kernel to escape the bug. I am happy to say that after reading a bug report on the subject here:
http://bugzilla.kernel.org/show_bug.cgi?id=11721
Courtesy of a link posted by Misfit138, I found deep down in the report dialogue that the following command as root, worked for the poster of the bug:
echo 0 > /proc/sys/net/ipv4/tcp_timestamps
So I did a yaourt -Syu & found amongst other packages a minor kernel update, which did not solve my internet problems, but after su, & then entering the above command in the Terminal my internet works as it should!
If this solution works for you, then add the following to your /etc/sysctl.conf:
#Temporary workaround for tcp issue with 2.6.27
net.ipv4.tcp_timestamps = 0
Thanks again Misfit138
I hope this solution works for all of the other bug bitten members of the Arch (& Linux) community!
Last edited by handy (2008-10-21 05:19:03)

THANX !!! Works like normal again
I saw that bug report too, just didnt know how to try it out, thanx so much for the helpful explanation.
Regards,
rabid0
Last edited by RabidWolf (2008-10-21 20:26:23)

Kernel BUG at include/linux/netdevice.h:472!

After updating to Linux 3.10.5, i'm getting so much garbage at startup and at shutdown and most of the times system won't work at all.
I'm posting some of the output from journalctl that might be of general interest:
perf_event_intel: PEBS disabled due to CPU errata
[Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service
WARNING: at drivers/iommu/dmar.c:484 warn_invalid_dmar+0x8d/0xa0()
ACPI Warning: SystemIO conflicts with Region \PMIO 1
kernel BUG at include/linux/netdevice.h:472!
ACPI Error: Method parse/execution failed [\_SB_.PCI0.GFX0._DOD] (Node f5c28858), AE_AML_PACKAGE_LIMIT
pam_systemd(login:session): Failed to connect to system bus: Did not receive a reply.
Problem persists in linux-3.10.5 [core] & linux-3.11 [testing]
Now, For the time being i'm using linux-lts "which is working fine" but i want to know, if there is any fix for linux-3.10.5??
If Not!! Then, if somebody knows how to make it work please!! tell me or are there any patches that can fix these kernel issues.

You'd better post more of the dmesg, giving parts of it is not really useful.

[SOLVED] Virtual Box Kernel Bug?

I'm using virtualbox_bin 3.2.8-5 from the AUR & kernel26 2.6.35.6-1.
I boot the machine clean. It starts the bare essentials. I open a terminal, /etc/rc.d/vboxdrv setup && modprobe vboxdrv. It is not vboxdrv that is the issue, but I'll recompile it anyway to make sure.
I start VirtualBox and it either:
A) Locks up the entire system
B) Gives me some error that says Component: ProgressProxy, Interface: IProgress
C) Force reboots my PC
Only other things in in the /var/log/errors.log besides this:
Sep 29 15:54:51 localhost kernel: BUG: scheduling while atomic: VBoxXPCOMIPCD/5464/0x00000003
Sep 29 15:54:52 localhost kernel: BUG: scheduling while atomic: VirtualBox/5541/0x00000002
Sep 29 15:54:52 localhost kernel: BUG: scheduling while atomic: pidgin/5808/0x00000002
Sep 29 15:55:08 localhost kernel: BUG: scheduling while atomic: bash/5566/0x00000002
Sep 29 15:55:21 localhost kernel: BUG: scheduling while atomic: X/4067/0x00000002
is "Assuming drive cache: write through" warnings.
Not sure if this should be in the kernel section or not.
Last edited by Jimi (2010-09-29 22:11:11)

Thanks for the very quick response.
I didn't realize I wasn't running the latest. Internet's been going in and out frequently. Once I've confirmed this is it (after yaourt finished upgrading everything), I'll change the title to solved.
Last edited by Jimi (2010-09-29 20:43:13)

[SOLVED] Kernel bug? Need help soon!

After a reboot my arch linux install wont log in anymore... When I enter my username and password at the prompt I get a flash of a screen and then the login prompt again, if I type in my username and such again it doesn't do anything... It just sits there...
The same goes for gdm and such.
I think the screen that flashes up (it's only a second there) is this one:
May 2 16:22:27 icarus Assertion failure in dx_probe() at fs/ext3/namei.c:384: "dx_get_limit(entries) == dx_root_limit(dir, root->info.info_length)"
May 2 16:22:27 icarus ------------[ cut here ]------------
May 2 16:22:27 icarus kernel BUG at fs/ext3/namei.c:384!
May 2 16:22:27 icarus invalid opcode: 0000 [#1]
Which is a snippet from my kernel.log. Does anyone know how to solve this? I really need to get into arch...
Last edited by Ramses de Norre (2007-05-02 17:29:35)

It seems like the above is an incredible obscure error message which should tell you that you've got a corrupted file system...
I had already ran fsck a couple of times and it always told me all my filesystems were ok, but desperate as I was I ran it once more on all my filesystems and now it fixed a bunch of errors on my home partition and arch booted... I don't really understand why fsck didn't do so the first time, but I'm happy I can finally boot arch again and continue working.
Sorry for this useless-after-all post.

[SOLVED] Kernel Bug on CIFS.umount

Hello there,
my PC's been haunted by this for at least a year, I suspect it has something to do with removed support for '_netdev' mount options in cifs mounts,
anyways
1. what is the/a appropriate way to mount and umount a samba share on startup/shutdown using a persistent wired ethernet connection
2. does this kernel bug log mean anything to anyone (esp why is the sound timer involved ?) http://pastebin.com/tuxZse6z
thx
Last edited by birdspider (2010-05-14 16:50:23)

right now I have a network share in fstab
fstab:
//40.40.0.4/SHARE /media/SHARE cifs defaults,_netdev,iocharset=utf8,rw,exec,workgroup=GUILD 0 0
rc.conf:
DAEMONS=(syslog-ng hal fam network @opennptd @acpid @sshd @netfs @crond @cpufreq @alsa @cups @actkbd)
it mounts correctly but fails to umount on reboot/shutdown
@Zariel: does backgrounding apply to shutdown(umount) also ?

OEM12c agents high CPU usage alerts fix (leap second Linux kernel bug)

Just throwing this out here in case anyone else spent the weekend pulling their hair out and hasn't resolved this yet.
Due to the leap second that occurred at midnight UTC going into July 1st, most of my OEM 12c BP1 agents on Linux servers went haywire, taking up 100%+ CPU on monitored servers. This appears to be due to a bug triggered by the leap second.
The following seems to fix the issue without requiring a server reboot.
as root:
/etc/init.d/ntp stop
date `date +"%m%d%H%M%C%y.%S"`
/etc/init.d/ntp start
as OEM agent user:
$AGENT_HOME/bin/emctl stop agent ; $AGENT_HOME/bin/emctl start agent
I didn't discover the fix, but I've confirmed it works.
Edited by: BrianP on Jul 2, 2012 11:53 AM -- subject changed to note this is a Linux kernel bug, not a Java bug... kernel bug causes software using futexes (like Java) to spin and timeout repeatedly

See MOS note "Enterprise Manager Management Agent or OMS CPU Use Is Excessive on or around July 1, 2012 [ID 1472651.1]" for more information on this issue. Oracle notes it may occur from versions 10.2.0.5 through 12.1.0.1.0.
See also "Leap Second Hang - CPU Can Be Seen at 100% [ID 1472421.1]" and bug 14264454.
Thanks abulloch for getting the note out there!

[SOLVED] SATA not working on Macbook Pro 7.1, (kernel bug 15923)

I ran into this bug while trying to install Arch as a single-os install on my new 13'' Macbook Pro 7.1:
https://bugzilla.kernel.org/show_bug.cgi?id=15923
It appears there is a problem with the current kernel and the MCP89 chipset so SATA is not recognized. There is a patch out but it still leaves ahci disabled and therefore NCQ causing slow performing harddisks.
I am wondering what to do. I've never done any kernel patching.
- use an SSD instead of a harddisk because of the lack of NCQ?
- and somehow create a net install with a patched current kernel (and how)?
- or wait for the patch to reach the next version of the Arch install image (How long would that take)?
- perform the install on my other notebook? Would that interfere with EFI partition already on it?
questions questions...
Last edited by rwd (2010-09-06 10:33:47)

atcq wrote:it worked, as far as kernel bug 15923 is concerned, but after booting into the newly installed system i don't have a working keyboard. usbinput is set in HOOKS.
any suggestions?
I know very little about kernel and booting stuff, but this is how I made booting work from memory, in case it helps someone:
- I installed using the archboot cd, using the whole harddisk and chose a MBR partition table (not GPT)
- booted from the archboot cd once more but only did the 'prepare harddisk' part where I only chose the mount points, and exited the menu to shell
- edited /tmp/install/etc/mkinitcpio.conf (on the mounted harddisk) as described above
- I followed the instructions here http://wiki.archlinux.org/index.php/Kernel_Panics for chrooting:
mount -t proc none /tmp/install/proc
mount -t sysfs none /tmp/install/sys
mount --bind /dev /tmp/install/dev
chroot /tmp/install
mkinitcpio -g /boot/kernel26.img
exit
sync
reboot
I also chose ext4 for all my partitions. So possibly with a different filesystem the according kernelmodule must be used. I tried the same procedure with a OCZ Vertex 2 ssd by the way but that one fails to boot with errors that are very similar to what's in this bug description.
Some other Macbook Pro 7.1 related things not mentioned in the wiki:
- Sound:
worked after putting this in /etc/modprobe.d/modprobe.conf:
options snd_hda_intel model=mbp55
and blacklisting OSS related modules in /etc/rc.conf:
MODULES=(!snd_pcm_oss !snd_mixer_oss !snd_seq_oss pcspkr hid_apple libphy tg3 snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-codec snd-hda-intel soundcore)
- Backlight and keyboard leds:
install nvidia-bl ( mbp-nvidia-blg doesn't seem to work) from the AUR and follow the instructions in the install messages. Manually adjusting is now possible. For example:
# echo 22000 > /sys/class/backlight/nvidia_backlight/brightness
# echo 44000 > /sys/class/backlight/nvidia_backlight/brightness
# echo 50 > /sys/class/leds/smc::kbd_backlight/brightness
# echo 255 > /sys/class/leds/smc::kbd_backlight/brightness
I couldn't get the 'pommed' package to work, which is supposed to handle all the media keys. With 'xev' I verified that the keys were active without needing any mapping using 'xmodmap'. But since they weren't bound to any particular action I cobbled together a few scripts. They're crude so maybe someone with some actual bash skills can clean these up.
to allow non-root write access to the backlight and keyboard led devices I put this in in /etc/rc.local:
chmod go+w /sys/class/backlight/nvidia_backlight/brightness
chmod go+w /sys/class/leds/smc::kbd_backlight/brightness
In my desktopenvironment I bound the corresponding media keys to these scripts with 'up', 'down' or 'mute' as arguments
mbp_keyboard_led.sh:
#!/bin/bash
LIGHTLEVEL=$(cat /sys/class/leds/smc::kbd_backlight/brightness)
LEVELDIFFERENCE=15
MAXVALUE=255
MINVALUE=0
if [ $LIGHTLEVEL -ge $MINVALUE ] && [ $LIGHTLEVEL -le $MAXVALUE ]
then
TOTAL=`expr $MAXVALUE`
case $1 in
up)
TOTAL=`expr $LIGHTLEVEL + $LEVELDIFFERENCE`;;
down)
TOTAL=`expr $LIGHTLEVEL - $LEVELDIFFERENCE`;;
esac
if [ $TOTAL -ge $MINVALUE ] && [ $TOTAL -le $MAXVALUE ]
then
echo $TOTAL > /sys/class/leds/smc::kbd_backlight/brightness
notify-send -i gtk-dialog-info.png -t 1000 "Keyboard led brightness:" "$TOTAL"
else
notify-send -i gtk-dialog-info.png -t 1000 "Keyboard led brightness:" "maximum"
echo "New value out of range: $TOTAL";
fi
else
echo 'System light level out of min/max range (Hardware might not be matching script)';
fi
mbp_lcd_backlight.sh:
#!/bin/bash
LIGHTLEVEL=$(cat /sys/class/backlight/nvidia_backlight/brightness)
LEVELDIFFERENCE=400
MAXVALUE=44000
MINVALUE=0
if [ $LIGHTLEVEL -ge $MINVALUE ] && [ $LIGHTLEVEL -le $MAXVALUE ]
then
TOTAL=`expr $MAXVALUE`
case $1 in
up)
TOTAL=`expr $LIGHTLEVEL + $LEVELDIFFERENCE`;;
down)
TOTAL=`expr $LIGHTLEVEL - $LEVELDIFFERENCE`;;
esac
if [ $TOTAL -ge $MINVALUE ] && [ $TOTAL -le $MAXVALUE ]
then
echo $TOTAL > /sys/class/backlight/nvidia_backlight/brightness
notify-send -i gtk-dialog-info.png -t 1000 "Screen brightness:" "$TOTAL"
else
notify-send -i gtk-dialog-info.png -t 1000 "Screen brightness:" "maximum"
echo "New value out of range: $TOTAL";
fi
else
echo 'System light level out of min/max range (Hardware might not be matching script)';
fi
mbp_sound_volume.sh:
#!/bin/bash
SOUNDLEVEL=`amixer get Master | grep dB | sed 's/.*\[$[0-9]\{1,3\}$\%\].*/\1/'`
MUTED=`amixer get Master | grep dB | sed 's/.*\[$[a-z]\{2,3\}$\].*/\1/'`
MINVALUE=0
MAXVALUE=96
LEVELDIFFERENCE=5
case $1 in
up)
if [ $SOUNDLEVEL -le $MAXVALUE ]
then
amixer set Master "$LEVELDIFFERENCE+" unmute
fi;;
down)
if [ $SOUNDLEVEL -ge $MINVALUE ]
then
amixer set Master "$LEVELDIFFERENCE-" unmute
fi;;
mute)
if [ "$MUTED" = on ]
then
amixer set Master mute
notify-send -i gtk-dialog-info.png -t 1000 "Master sound volume:" "muted"
exit 0
else
amixer set Master unmute
fi;;
esac
SOUNDLEVEL=`amixer get Master | grep dB | sed 's/.*\[$[0-9]\{1,3\}$\%\].*/\1/'`
notify-send -i gtk-dialog-info.png -t 1000 "Master sound volume:" "$SOUNDLEVEL %"
Last edited by rwd (2010-10-08 13:19:10)

What does 'kernel bug in process suhelperd' mean in very simple terms please

what does 'kernel bug in process suhelperd' mean in very simple terms please

Hi,
Any that ends in a "d" tends to be a dameon process used by the System as a whole.
As in launchd is the process that make sure all the Extensions and Kexts that run the OS are started.
helper would refer to a specific thing (the info you posted offers no reference to that and I don't know off the top of my head)
The su would probably refer to the permissions this item has at that moment in time (su is normally a Terminal Instruction allowing temporary but high level access).
Without more info about a possible link to an action within the OS or an app it would be hard to say if it is a real concern.
It seems to refer to a conflict. It could be that the item is not written for the current OS, is outdated via Upgrades for instance, or written in a way that is now Protected by the way the current OS works.
Console Messages can be helpful when you can attribute them to specific events such as a Crash Log or the Action in an App matching a Time in the Log (you generally have to be watching).
9:18 pm Tuesday; January 6, 2015
 iMac 2.5Ghz i5 2011 (Mavericks 10.9)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad

Kernel BUG at skbuff.c.... In interrupt handler - not syncing

Hello,
VERSION: ZENWorks Imaging Server v6.50
I am trying to create an image of a workstation. After I boot up with the
Boot CD and input the proper settings (prompts by SETTINGS.TXT) the
workstation gets an IP and everything works fine. At the moment when I try
to create the image:
img mp <IP address of imaging server> <//path/imagefilename>
I get the following error:
~~~~~~~~~~~~
Kernel BUG at skbuff.c :92!
invalid operand: 0000
<0> Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
~~~~~~~~~~~~~
The error is much bigger, but I only included the first two and last two
lines of it.
I am not sure how to resolve this. If I made a mistake with the commands
please let me know, although I think they are correct. I also tried
creating an image through the user interface but I got the same error.
Any solution, recommendation, or advice is greatly appreciated.
Sincerely,
Steve O.

Marcus,
Thank you for the response.
Sorry to ask again, I am new to Novell. I simply want to make sure. Do you
mean downloading and installing the following patch for ZENWorks 6.5
desktop management?
zen65sp2.exe
I found this file from the "Download - patches" website.
Thanks for the help.
Steve O.
> [email protected] wrote:
>
> > I am not sure how to resolve this. If I made a mistake with the commands
> > please let me know, although I think they are correct. I also tried
> > creating an image through the user interface but I got the same error.
> >
> try the iso from sp2..
> --
> If you have already compiled drivers or have linux.2 please put them on
> http://forge.novell.com/modules/xfmo...ect/?zfdimgdrv
> Live BootCd and USB Disk from Mike Charles
> http://forge.novell.com/modules/xfmod/project/?imagingx
> eZie http://forge.novell.com/modules/xfmod/project/?ezie
>
> Marcus Breiden
>
> If you are asked to email me information please change -- to - in my e-mail
> address.
> The content of this mail is my private and personal opinion.
> http://www.edu-magic.net

Kernel bug on running clyde

I'm not sure whether the kernel or clyde is at fault, but lately when I do a "clyde -Sauy" I get a kernel bug, stating something like
BUG in fs/inode.c
Wrong opcode 0000
This might not be exactly what it said as I didn't write it down, I'll try to get it more literally if it happens again. My filesystem on both / and /home is ext4. Is this a kernel or a clyde bug?
I'm running a 32bit userland on a 64bit kernel, in case that's relevant.

Yeah, I'm going to do that, but I'm not sure whether this is a clyde or a kernel bug and thus I'm not sure to which upstream I should report this. Hence the question.

Cannot get slmodem working, kernel BUG

Hello,
I'm trying to get the dial-up modem on my old computer working, to have a backup in case my DSL goes down. The modem is an LG LM-I56N, which uses a SmartLink chipset. I have used the same modem successfully on Linux, but a long time ago, with Ubuntu 5.10.
[root@kirlian ~]# lspci | grep -i modem
00:0c.0 Modem: Smart Link Ltd. LM-I56N (rev 02)
So I installed the slmodem package, but when I try to load the module slamr, I get this:
[root@kirlian ~]# modprobe slamr
Morto
On dmesg there is a kernel BUG:
slamr: SmartLink AMRMO modem.
BUG: unable to handle kernel paging request at 75626564
IP: [<c026fe45>] strnlen+0x15/0x40
*pde = 00000000
Oops: 0000 [#1] PREEMPT SMP
last sysfs file: /sys/devices/platform/w83627hf.656/pwm2
Modules linked in: slamr(P+) nfnetlink_queue nfnetlink fuse xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 vboxnetadp vboxnetflt iptable_filter ip_tables vboxdrv xt_state nf_conntrack xt_NFQUEUE x_tables vmnet vsock vmci vmmon w83627hf hwmon_vid nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc ipv6 ufs ext2 mbcache ppdev nvidia(P) ohci_hcd lp i2c_core psmouse parport_pc ehci_hcd parport sis_agp serio_raw sg pcspkr usbcore agpgart shpchp pci_hotplug thermal processor evdev fan button battery ac snd_intel8x0 snd_ac97_codec snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_pcm snd_timer snd_page_alloc snd_mixer_oss snd soundcore ac97_bus slhc sis900 mii rtc_cmos rtc_core rtc_lib reiserfs sr_mod floppy cdrom sd_mod ata_generic pata_sis libata scsi_mod
Pid: 1313, comm: modprobe Tainted: P (2.6.30-ARCH #1) To Be Filled By O.E.M.
EIP: 0060:[<c026fe45>] EFLAGS: 00010097 CPU: 1
EIP is at strnlen+0x15/0x40
EAX: 75626564 EBX: c05d7260 ECX: 75626564 EDX: fffffffe
ESI: c05d6e7a EDI: 75626564 EBP: ffffffff ESP: f6915c90
DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Process modprobe (pid: 1313, ti=f6914000 task=f5f9d800 task.ti=f6914000)
Stack:
98180e36 c026e462 804b2b2e 00000000 ffffea4c 00000004 00000000 ffffffff
0000000a ffffffff ffffffff 98180e36 c05d6e7a f8856cbe f6915ddc f8856cc0
c026f10f 00000004 00000000 ffffffff 0000000a ffffffff ffffffff ffffffff
Call Trace:
[<c026e462>] ? string+0x62/0x110
[<c026f10f>] ? vsnprintf+0x22f/0x450
[<c026f481>] ? vscnprintf+0x21/0x40
[<c013be4f>] ? vprintk+0x8f/0x3b0
[<c022ab71>] ? sysfs_find_dirent+0x31/0x50
[<c01e5b3b>] ? iput+0x2b/0x70
[<c03cec94>] ? printk+0x23/0x3f
[<f801f03e>] ? amrmo_pci_probe+0x3e/0x410 [slamr]
[<c028134a>] ? local_pci_probe+0x1a/0x40
[<c0282611>] ? pci_device_probe+0x81/0xb0
[<c0302559>] ? driver_probe_device+0x89/0x170
[<c03026d1>] ? __driver_attach+0x91/0xa0
[<c0302640>] ? __driver_attach+0x0/0xa0
[<c0301bf2>] ? bus_for_each_dev+0x62/0xa0
[<c0302382>] ? driver_attach+0x22/0x40
[<c0302640>] ? __driver_attach+0x0/0xa0
[<c030135e>] ? bus_add_driver+0xce/0x2b0
[<c02824f0>] ? pci_device_remove+0x0/0x60
[<c0302a4f>] ? driver_register+0x6f/0x130
[<c0282aa9>] ? __pci_register_driver+0x49/0xd0
[<f801f4c2>] ? amrmo_init+0xb2/0x106 [slamr]
[<c010115f>] ? do_one_initcall+0x3f/0x190
[<c018c927>] ? tracepoint_module_notify+0x47/0x50
[<c0159ff6>] ? notifier_call_chain+0x46/0x80
[<f801f410>] ? amrmo_init+0x0/0x106 [slamr]
[<c015a43d>] ? __blocking_notifier_call_chain+0x6d/0xa0
[<c016e4c7>] ? sys_init_module+0xb7/0x1f0
[<c01257ec>] ? do_page_fault+0xfc/0x330
[<c0103c93>] ? sysenter_do_call+0x12/0x28
Code: 83 c4 04 5f c3 e8 0c b4 ec ff 8d b6 00 00 00 00 8d bf 00 00 00 00 83 ec 04 65 8b 0d 14 00 00 00 89 0c 24 31 c9 89 c1 89 c8 eb 06 <80> 38 00 74 07 40 4a 83 fa ff 75 f4 29 c8 8b 14 24 65 33 15 14
EIP: [<c026fe45>] strnlen+0x15/0x40 SS:ESP 0068:f6915c90
CR2: 0000000075626564
---[ end trace 648535fe9605c368 ]---
note: modprobe[1313] exited with preempt_count 2
Any ideas? I know not much can be done since it's a closed-source module, but anyway I'd like to try to fix it.
Thanks!

Hello Renan!
It seems worse because of oops messages after a simple modprobe
I think you need for reporting it to the author if it's really closed driver. Could you try it with another kernel version, or other distribution, can it work?

Btrfs kernel bug

Similar Messages

Maybe you are looking for