System Hangs after kernel update

Hi Experts,
Client side, they did kernel upgrade in production system . After this upgrade , they are not able to execute any RFCs. Whenever they are executing RFCs , it keep on running continuously (hangs long time).. Not able to get any results.
Please guide me how to handle this problem.
Thanks
Silviya

Hi,
Thanks for your reply.Just forget about kernel upgrade.In my client production, they are trying to execute RFC "RFC_ABAP_INSTALL_AND_RUN",,but the system continuously hanging for one week. They are not able to do anything with RFC. Other ABAP normal programs are working fine.
They creating invoice by RFCs. Whenever they running this RFC , system gets hanging continuously. what may be the reason..and how to correct it .please guide me ASAP. I couldnt get content of sapnote 1151775. If you have sapnote 1151775 details , please give me.
Thanks a lot
Silviya

Similar Messages

System unbootable after kernel update

Please read last post: http://bbs.archlinux.org/viewtopic.php?pid=544212

mcloaked wrote:Thanks Rod. A question - once the GNU-EFI zip file for the build is downloaded I presume that I can simply replace the existing refind_x64.efi in my system with the one from the refind-bin-gnuefi-0.7.8.zip and simply reboot to try it - without changing any of the other rEFInd files?
Yes.
This bug seems to have been running for quite a while, and I would really like to know if there is any way to generate some directly useful diagnostics that could point to where the problem originates.
There probably is, but that's a topic about which I know relatively little.
To those discussing changes in recent kernels (like 3.13.6->3.13.7), forget it. This problem goes all the way back to the 3.7 kernel series. That said, it's conceivable that there are actually two or more bugs with similar symptoms, but the problem comes and goes -- that is, kernel A is buggy, kernel B is fine, kernel C is fine, kernel D is buggy, and so on. Another computer will experience a different pattern (say, A is fine, B is fine, C is buggy, and D is fine). This makes it very difficult to discern patterns, and it means that a person might have a run of several working kernels that actually contain the bug, making that person focus on a much more recent change that's actually irrelevant to the bug.
My own hypothesis is that it has something to do with alignment of the code in memory, or perhaps some other memory access issue. This could explain the near-randomness of the symptoms because this detail would vary depending on tiny differences between kernel builds and even between computers. Unfortunately, I have yet to encounter this problem myself, so I can't dig in and track it down.

Automatically build kernel module after kernel update

Hello. Everytime kernel is updated, my wifi drivers don't work. I need to use this to get my adapter working: https://aur.archlinux.org/packages/8192cu-dkms/ .
After kernel update, I have to manually reinstall the package, so the kernel module gets rebuilt. Is there any way to make it automatic?

I noticed it, but your script doesn't run at all when I type `mkinitcpio -p linux`. And wifi still works after reboot. Same for graphics driver, it has a hook at shutdown, that rebuilds its module after kernel update, it haven't run too and graphics driver works. It's like 'mkinitcpio -p linux' does nothing to the system.
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 4.0.4-2-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 4.0.4-2-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
Last edited by kox (2015-06-02 07:18:24)

Automatic recompiling of kernel module after kernel update.

Hello everyone,
i tried to search for it but without success...
my question is - is it possible to set it up somehow that aur package would recompile after kernel update?
The package I would like to rebuild is rt3090 which is module for my wifi card. It is very annoying to rebuild it manually. I know that my fglrx module does it automaticaly but how to set it?
Thank all of you for any advise.

Thank you :-) It looks ok, I will try DKMS as soon as I get some free time. If there was any problem, I would tell you.
BTW: I use catalyst mainly because of saving energy management, which is of course better for my netbook. My card is too new to be fully supported by the opensource driver.
EDIT:
I solved the situation by upgrading my system, I tried in-kernel module rt2800pci. In the previous kernels it didn't work well with my crappy ralink rt3090 wifi card, but that's been improved :-) so I do not need rebuild the package anymore even because this module isn't compatible with newest kernel.
I also learnt how to write my own hook from archwiki (https://wiki.archlinux.org/index.php/Mkinitcpio) so if the new module didn't work I would try it.
The final solution = replace module rt3090sta by rt2800pci.
Thanks! Arch has very powerful community :-)
Last edited by h@lf@rk (2012-06-02 18:34:17)

VMware player won't start after kernel update

Hi,
today I've updated to 3.9.6-1 kernel and all went good. So I wanted to start my vmware player to start a vm. Of course I've done the needed steps in the vmplayer wiki page to setup the new headers and stuff after kernel update for vmplayer. Also I've ran "vmware-patch -f" and ran trough. But still get an error when I wanted to start the player in the "/tmp/vmware-root/vmware-modconfig-11986.log":
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Log for VMware Workstation pid=11986 version=9.0.2 build=build-1031769 option=Release
2013-06-16T13:03:51.680+01:00| vthread-3| I120: The process is 64-bit.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Host is Linux 3.9.6-1-ARCH 2013.04.01
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Msg_Reset:
2013-06-16T13:03:51.680+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: ----------------------------------------
2013-06-16T13:03:51.680+01:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Msg_Reset:
2013-06-16T13:03:51.680+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: ----------------------------------------
2013-06-16T13:03:51.680+01:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Msg_Reset:
2013-06-16T13:03:51.680+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": No such file or directory.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: ----------------------------------------
2013-06-16T13:03:51.680+01:00| vthread-3| I120: PREF Failed to load user preferences.
2013-06-16T13:03:51.680+01:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-11986.log
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Reading in info for the vmmon module.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Reading in info for the vmnet module.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Reading in info for the vmblock module.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Reading in info for the vmci module.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Reading in info for the vsock module.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Setting vsock to depend on vmci.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Created new pathsHash.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Invoking modinfo on "vmmon".
2013-06-16T13:03:51.689+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-06-16T13:03:51.689+01:00| vthread-3| I120: Invoking modinfo on "vmnet".
2013-06-16T13:03:51.690+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-06-16T13:03:51.690+01:00| vthread-3| I120: Invoking modinfo on "vmblock".
2013-06-16T13:03:51.691+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-06-16T13:03:51.691+01:00| vthread-3| I120: Invoking modinfo on "vmci".
2013-06-16T13:03:51.693+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-06-16T13:03:51.693+01:00| vthread-3| I120: Invoking modinfo on "vsock".
2013-06-16T13:03:51.696+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
Maybe it has something to do with the last filesystem update?
But I don't know what to do really and couldn't found anything on that.
thanks

sorry, found something now in another thread here. this fix works just fyi:
kokoko3k wrote:
Quick and dirty workaround to fully update your system
sudo pacman -Suy #update everything
sudo mkdir -p /usr/local/lib/gtkmm && cd /usr/local/lib/gtkmm
sudo wget http://arm.konnichi.com/2013/01/05/extra/os/x86_64/gtkmm-2.24.2-2-x86_64.pkg.tar.xz
#sudo wget http://arm.konnichi.com/2013/01/05/extra/os/i686/gtkmm-2.24.2-2-i686.pkg.tar.xz #The bug affects i686 too.
sudo tar -xvf ./gtkmm-2.24.2-2-x86_64.pkg.tar.xz
#sudo tar -xvf ./gtkmm-2.24.2-2-i686.pkg.tar.xz #The bug affects i686 too.
LD_LIBRARY_PATH=/usr/local/lib/gtkmm/usr/lib/ vmplayer #start it with old libraries

[Solved] Can not build modules for VMware Player after kernel updates

I have a problem generating the modules for VMware Player after kernel updates. I am using VMware Player version 5.02 (without patches) and the softlink according to the Wiki.
When I start the installation of the modules from the GUI, the program just closes. Running vmware-modconfig in the CLI generates the following log file:
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Log for VMware Workstation pid=7478 version=9.0.2 build=build-1031769 option=Release
2013-04-29T09:49:27.891+01:00| vthread-3| I120: The process is 64-bit.
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Host is Linux 3.8.10-1-ARCH 2012.11.29
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Msg_Reset:
2013-04-29T09:49:27.891+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": Datei oder Verzeichnis nicht gefunden.
2013-04-29T09:49:27.891+01:00| vthread-3| I120: ----------------------------------------
2013-04-29T09:49:27.891+01:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Msg_Reset:
2013-04-29T09:49:27.891+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": Datei oder Verzeichnis nicht gefunden.
2013-04-29T09:49:27.891+01:00| vthread-3| I120: ----------------------------------------
2013-04-29T09:49:27.891+01:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2013-04-29T09:49:27.891+01:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-7478.log
2013-04-29T09:49:27.892+01:00| vthread-3| W110: Icon name must be set.
Interestingly, after deinstallation and reinstallation the VMWare Player works fine.
Any hint, what's going wrong?
Last edited by Thomas_Do (2013-08-07 07:25:51)

Today, (Kernel 3.10.5-1, VMware Player version 5.02 with kernel patches) the modules could successful be generated from the CLI:
vmware-modconfig --console --install-all
Solved (somehow).

Lost network after kernel update

Hi
I have lost my network after kernel updating the kernel [2.6.35.7]
I downgraded to kernel 2.6.35.6
Serge

krychle wrote:
Hi,
I'm just reporting that I had this issue today too. I rebooted my computer from Win7 to Arch64 and I was left without network. Also it doesn't work in windows after rebooting back. I thought that It is something with connection so I tried to recoonect cable and also tryied to swap it in switch/adsl gateway. It started working after several switches (not on 1st!) It looks like interface is repeating on and off. So I rebooted to Arch and it stops working again...
I fixed it by reinstalling kernel26 package. But it is strange because it works yesterday, last thing what I did with kernel and modules was update of gc nvidia drivers... I don't know when I updated kernel last time
I'm using same network driver as Karol - r8169
lsmod | less
mii 3826 1 r8169
I'm using this card as well. I upgraded yesterday and I can't get wireless with WICD. Windows and normal network daemon work fine. I use kernel26. What other info can I provide? If a bug report needs to be filed, would it be WICD, kernel26 or other?
Also, I forgot, but I'm not using normal Wicd, I'm using wicd-nogtk from AUR. Krychle, are you using this also?
Edit: I think this has to do with the python update. I updated wicd-nogtk and its good now. I am online.
Last edited by Anonymo (2010-10-19 18:10:23)

After kernel update, anything i should do for my arch system in vbox

Hi all:
I've installed arch as a vbox guest system. The host system is windows 7.
After Archlinux kernel updates, do i need to re-install the guest add-on modules ?
or is there anything necessary after each kernel update ?
Best Regards,

Thanks for the reply.
I've already installed the virtualbox-archlinux-additions.
So after the kernel update there's nothing i need to do ?

After kernel update system dont boots

i updated my kernel, update process was ok but now when i try to boot my system i got these types of errors in middle of the booting:
ERROR: Failed to parse device name for '/dev/disk/by-uuid/[many symbols which i didnt copied]
it looks like it cant find root, but it found it before update, please help because i dont wanna reinstall system.

EVRAMP wrote:Try to edit grub boot menu: instead of "/dev/disk/by-uuid/[many symbols which you didnt copied]" write your root partition path "/dev/sda2" (where sda2 points to your root partition).
You can edit your grub boot menu entry by presing "e".
didnt help, i tried that at first. now when i booted ubuntu from live cd to look whats inside arch linux partition, i went to /dev/ and ive seen only three files, no sda* or somethink, just three empty text files. i tried to look at this folder as a root, but still theres only three files. so maybe theres problem? man i will need to reinstall everythink again :(
Last edited by syms (2009-01-02 20:30:46)

Mkinitcpio hanging on kernel update

I'm getting the latest packages and I'm running into an issue where the image keeps hanging after I install the latest linux kernel.
$ sudo pacman -S linux
warning: linux-4.0.4-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) linux-4.0.4-2
Total Installed Size: 73.08 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring [###############################################] 100%
(1/1) checking package integrity [###############################################] 100%
(1/1) loading package files [###############################################] 100%
(1/1) checking for file conflicts [###############################################] 100%
(1/1) checking available disk space [###############################################] 100%
(1/1) reinstalling linux [###############################################] 100%
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 4.0.4-2-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
This is where it hangs. I let it sit for about 10 minutes when I did the full system upgrade, and then killed it when it looked like it wasn't doing anything. The output above is from the second time this has happened, and I'm not so sure I want to reboot without this getting built correctly.
Any ideas?

OK, I switched to the pacman package cache directory and ran pacman -U linux-4.0.1... linux-headers-4.0.1... (can't copy and paste from the busted machine, so know that I typed out the full package correctly)
Output:
(2/2) checking for file conflicts
error: failed to commit transaction (conflicting files)
linux: /usr/lib/modules/4.0.1-1-ARCH/modules.alias exists in filesystem
linux: /usr/lib/modules/4.0.1-1-ARCH/modules.alias.bin exists in filesystem
linux: /usr/lib/modules/4.0.1-1-ARCH/modules.builtin.bin exists in filesystem
linux: /usr/lib/modules/4.0.1-1-ARCH/modules.dep exists in filesystem
linux: /usr/lib/modules/4.0.1-1-ARCH/modules.dep.bin exists in filesystem
linux: /usr/lib/modules/4.0.1-1-ARCH/modules.devname exists in filesystem
linux: /usr/lib/modules/4.0.1-1-ARCH/modules.softdep exists in filesystem
linux: /usr/lib/modules/4.0.1-1-ARCH/modules.symbols exists in filesystem
linux: /usr/lib/modules/4.0.1-1-ARCH/modules.symbols.bin exists in filesystem
I figure these are the files created by the install process (built or moved, i dunno). Safe to remove?
I'm about to wipe the machine and start from scratch unless someone says otherwise.

[SOLVED]Boot hang after recent updating issues

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

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

System crash after recent update

Hi all,
As of yesterday, my laptop has started crashing after a little while open (sometimes right away, sometimes ten minutes in, sometimes right after bios). I believed it was to do with the recent alsa-utils update and I downgraded that package which helped for a little bit. When it updated again and the core dump from the previous update disappeared, I upgraded and the problem starting happening again. Then I downgraded and no change.
So I think it is not to do with alsa anymore...but I can find no information at all in dmesg or journalctl. There seem to be no errors, warnings whatsoever. I have tried chrooting in and looking at all the logs but to no avail.
The update that broke my system installed the following:
alsa-lib alsa-utils gcc-libs gcc isl kmod libcdio-paranoia pyalpm namcap
I have since downgraded both isl and kmod and it looks my laptop is running okay so far. After this update I also updated the kernel, but running from the fallback initramfs did not change the issue so I don't think it was that either.
I have trawled the forums for recent problems with recent updates .ut did not find anything apart from the alsactl core dump.
Does anyone know if there are any problems with the above packages? Or if there are other important logs other than journactl, dmesg, and pacman.log I can try looking at to troubleshoot this? I apologise for not being able to provide much more information, as I said I can't seem to find anything out of the ordinary in the aforementioned logs.
Any help would be appreciated.

Crash still occurs...now found this in dmesg
[ 2.425173] ACPI Warning: 0x000000000000f040-0x000000000000f05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20121018/utaddress-251)
[ 2.425179] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.425250] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20121018/utaddress-251)
[ 2.425254] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.425258] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
[ 2.425260] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.425261] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
[ 2.425263] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.425264] lpc_ich: Resource conflict(s) found affecting gpio_ich
I have looked online about these though, and so far it looks like it doesn't actually make anyone crash
EDIT: Also found that this is not actually a kernel bug...hmm.
Last edited by thesystematic (2013-04-16 00:51:03)

Wireless issues after kernel update

Hi,
after I updated my kernel yesterday, I've been having some issues with my wireless. I'm on a dell inspiron 1545, using kde and I use the broadcom-wl driver form the AUR.
Anyways. After I did a system update yesterday, it would refuse to load the wl module. So I recompiled the driver and that was fine. But still my laptop refuses to use its wireless card. At first I just couldn't connect to any wireless, now the networkmanager just claims that my WLAN Interface is unavailable.
the output of iwconfig:
lo no wireless extensions.
eth0 IEEE 802.11bg ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:off
Retry min limit:7 RTS thr:off Fragment thr:off
Power Managementmode:All packets received
Link Quality=5/5 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
eth1 no wireless extensions.
but if I try to run 'iwlist eth0 scan' it states:
eth0 Failed to read scan data : Invalid argument
I'm not that experienced with wireless, so I did what https://wiki.archlinux.org/index.php/Broadcom_BCM43XX says and some other pages I found on google. 'iwconfig eth0 up' doesn't have any influence.
As I said, before the upgrade it worked fine and I also had configured it as it is described in the link above.
thanks for any inputs,
tobi

litemotiv: 'lspci | grep Network' :
0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
.:B:. : I guess (and hope) that's the only relevant part (at the top and bottom):
at the bottom what's that "wl taints kernel"
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
input: PC Speaker as /devices/platform/pcspkr/input/input1
usbcore: registered new device driver usb
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 22 (level, low) -> IRQ 22
ehci_hcd 0000:00:1a.7: setting latency timer to 64
ehci_hcd 0000:00:1a.7: EHCI Host Controller
ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1a.7: debug port 1
lib80211_crypt: registered algorithm 'TKIP'
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ehci_hcd 0000:00:1a.7: cache line size of 64 is not supported
ehci_hcd 0000:00:1a.7: irq 22, io mem 0xfed1c400
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
iTCO_wdt: Found a ICH9M TCO device (Version=2, TCOBASE=0x1060)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
sd 0:0:0:0: Attached scsi generic sg0 type 0
dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 20 (level, low) -> IRQ 20
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
ehci_hcd 0000:00:1d.7: debug port 1
sr 1:0:0:0: Attached scsi generic sg1 type 5
ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
ehci_hcd 0000:00:1d.7: irq 20, io mem 0xfed1c000
uhci_hcd: USB Universal Host Controller Interface driver
input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2
ACPI: acpi_idle registered with cpuidle
ACPI: Lid Switch [LID]
input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
ACPI: Power Button [PBTN]
input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input4
ACPI: Sleep Button [SBTN]
ACPI: AC Adapter [AC] (off-line)
Monitor-Mwait will be used to enter C-1 state
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 6 ports detected
i801_smbus 0000:00:1f.3: PCI INT B -> GSI 18 (level, low) -> IRQ 18
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
uhci_hcd 0000:00:1a.0: setting latency timer to 64
uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1a.0: irq 20, io base 0x00006f60
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:1a.1: setting latency timer to 64
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
Monitor-Mwait will be used to enter C-2 state
Marking TSC unstable due to TSC halts in idle
Switching to clocksource hpet
uhci_hcd 0000:00:1a.1: irq 21, io base 0x00006f80
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.2: PCI INT C -> GSI 22 (level, low) -> IRQ 22
uhci_hcd 0000:00:1a.2: setting latency timer to 64
uhci_hcd 0000:00:1a.2: UHCI Host Controller
uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
wmi: Mapper loaded
uhci_hcd 0000:00:1a.2: irq 22, io base 0x00006fa0
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
uhci_hcd 0000:00:1d.0: irq 20, io base 0x00006f00
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
uhci_hcd 0000:00:1d.1: irq 21, io base 0x00006f20
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 22 (level, low) -> IRQ 22
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
uhci_hcd 0000:00:1d.2: irq 22, io base 0x00006f40
hub 8-0:1.0: USB hub found
hub 8-0:1.0: 2 ports detected
wl: module license 'Mixed/Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
wl 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
wl 0000:0c:00.0: setting latency timer to 64
usb 1-5: new high speed USB device using ehci_hcd and address 2
atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
atkbd serio0: Use 'setkeycodes e00d <keycode>' to make it known.
eth0: Broadcom BCM4315 802.11 Hybrid Wireless Controller 5.100.82.38
thermal LNXTHERM:00: registered as thermal_zone0
and maybe
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth1: link is not ready
start_kdeinit (3367): /proc/3367/oom_adj is deprecated, please use /proc/3367/oom_score_adj instead.
sky2 0000:09:00.0: eth1: Link is up at 100 Mbps, full duplex, flow control rx
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present
tobi

Itunes hang after latest updates

Since the last updates to my iMac iI find that the iTunes is constantly Hanging. It does not matter if I'm not using iTunes, as soon as its working in the background it hangs sooner or later. When I work with my music files in iTunes it usually hangs after less than 30 minutes.
How can this be?
I do not want to start with a new music player since I have used iTunes for the last 10 years and I have all my music in it.
But the way its acting now it seem like I have to use something else since iTunes is simply not working properly.

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.
The test works on OS X 10.7 ("Lion") and later. I don't recommend running it on older versions of OS X. It will do no harm, but it won't do much good either.
Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.
2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.
You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.
In this case, however, there are a couple of ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone with the necessary skill can verify what it does.
You may not be able to understand the script yourself. But variations of it have been posted on this website thousands of times over a period of years. The site is hosted by Apple, which does not allow it to be used to distribute harmful software. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message. See, for example, this discussion.
Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.
4. Here's a general summary of what you need to do, if you choose to proceed:
☞ Copy a particular line of text to the Clipboard.
☞ Paste into the window of another application.
☞ Wait for the test to run. It usually takes a few minutes.
☞ Paste the results, which will have been copied automatically, back into a reply on this page.
These are not specific instructions; just an overview. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait, paste again. You don't need to copy a second time.
5. Try to test under conditions that reproduce the problem, as far as possible. For example, if the computer is sometimes, but not always, slow, run the test during a slowdown.
You may have started up in "safe" mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
6. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
7. Load this linked web page (on the website "Pastebin.") The title of the page is "Diagnostic Test." Below the title is a text box headed by three small icons. The one on the right represents a clipboard. Click that icon to select the text, then copy it to the Clipboard on your computer by pressing the key combination command-C.
If the text doesn't highlight when you click the icon, select it by triple-clicking anywhere inside the box. Don't select the whole page, just the text in the box.
8. Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing command-V, then press return. The text you pasted should vanish immediately.
9. If you see an error message in the Terminal window such as "Syntax error" or "Event not found," enter
exec bash
and press return. Then paste the script again.
10. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. If you don't know the password, or if you prefer not to enter it, just press return three times at the password prompt. Again, the script will still run.
If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
11. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, a series of lines will appear in the Terminal window like this:
[Process started]
        Part 1 of 8 done at … sec
        Part 8 of 8 done at … sec
        The test results are on the Clipboard.
        Please close this window.
[Process completed]
The intervals between parts won't be exactly equal, but they give a rough indication of progress. The total number of parts may be different from what's shown here.
Wait for the final message "Process completed" to appear. If you don't see it within about ten minutes, the test probably won't complete in a reasonable time. In that case, press the key combination control-C or command-period to stop it and go to the next step. You'll have incomplete results, but still something.
12. When the test is complete, or if you stopped it because it was taking too long, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "Process completed" message to appear in the Terminal window. Please wait for it and try again.
If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
13. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the test results on Pastebin, then post a link here to the page you created.
14. This is a public forum, and others may give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but whatever else you're told to do may not be. For others who choose to run it, I don't recommend that you post the test results on this website unless I asked you to.
Copyright © 2014, 2015 by Linc Davis. As the sole author of this work (including the referenced "Diagnostic Test"), I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

[Solved] Nvidia after kernel update

The nvidia wiki clearly states that: "Every time the kernel26 package is updated, it is a requirement to reinstall the nvidia package and rebooting afterwards. "
But my question is, why? I mean, if the module was to be recompiled, that would make sense. But what does just reinstalling the driver accomplish? In my system, pacman -Ql nvidia shows:
$ pacman -Ql nvidia
nvidia /etc/
nvidia /etc/modprobe.d/
nvidia /etc/modprobe.d/nouveau_blacklist.conf
nvidia /lib/
nvidia /lib/modules/
nvidia /lib/modules/2.6.35-ARCH/
nvidia /lib/modules/2.6.35-ARCH/kernel/
nvidia /lib/modules/2.6.35-ARCH/kernel/drivers/
nvidia /lib/modules/2.6.35-ARCH/kernel/drivers/video/
nvidia /lib/modules/2.6.35-ARCH/kernel/drivers/video/nvidia.ko
From what I've read, I think the kernel update process copies the compiled modules into the proper folder (inside /lib) named by the kernel version. Should this not be the case with nvidia? If it is not, then is this why the reinstall is needed?
Thanks in advance (and my apologies if I've glossed over something that's patently obvious --- while I've searched for the answer before posting, I am still quite the novice at tinkering with the kernel)
EDIT: just after posting I've realized that maybe this post belongs in "Kernel and Hardware Issues" subforum. But the truth is this isn't really an "issue"... it's more a question from, well, a newbie :-)
Last edited by gauthma (2010-09-28 21:53:04)

gauthma wrote:
Thank you for the feedback.
ngoonee wrote:Of course, if you're using nvidia-beta or some other AUR nvidia driver, you need to reinstall it.
Running the risk of asking what might be obvious to some, why?
The driver speaks to the kernel. When the kernel updates, the language used might have changed in various ways. Since nvidia is closed-source, its not always obvious whether what has changed affects it. The same applies to xorg-server, when it updates you should recompile your nvidia driver. Its SOMETIMES not needed, but when it is, would you rather be solving it from the tty?
quathma wrote:
ngoonee wrote:That's what the wiki is referring to. Even if the kernel major version has not updated (for example 2.6.35.5 to 2.6.35.6 is only a minor version bump) the driver may need to be recompiled. Safer to just do it everytime and restart the machine.
Now I'm confused. Are you saying that the safest approach is to recompile and (re)install the nvidia module after each kernel update? And does this only apply to modules from beta & AUR, or [extra] as well? And shouldn't all this issue of recompiling modules also apply to every other module installed in the system?
Yes that's the safest approach. [extra] is taken care of by the devs, the simple way is to assume they'll bump it if needed (and you don't need to do anything).
The same thing applies to almost any kernel module (AFAIK). It applies to virtualbox's modules, for sure, as well as phc-intel (the only other 2 external modules I use). Most kernel modules are actually compiled in to the kernel26 package anyway, so its not very many. I just automatically recompile the ones I use whenever I notice a kernel/xorg update.

System Hangs after kernel update

Similar Messages

Maybe you are looking for