Airport causes the system freeze.

I purchased this 17" iMac Core Duo less than one week ago, and I've updated the firmware to the latest for Boot Camp the day before yesterday. Everything looks fine, but sometimes, Airport cannot find any wireless services (there are half a dozen around me here), this not happens every time, the Airport usually works fine. But if the Airport fails, the system freeze several seconds after I enable the Airport. I do not remember if this happen before update the firmware, but I reinstalled the system today, at the welcome screen of the first boot, the welcome program requires me to select a wireless service, and after I enter the wireless password, the system freezes, the mouse cursor does not move, keyboard does not responding. So this can be happened in a new operating system, I think there might be two reasons, hardware problems, or firmware problems. Do anyone here encountered a similar problem?

I have the exact same problem. Have seen a lot of similar issues as well but not exactly the same until now. I also get the freeze and can't pick up any wireless networks. From reading through quite a few discussion groups, the only thing I haven't tried is replacing the Airport Extreme card. This is my next step.
I've done basically everything else. Seems like some issues with the AE and Wireless networks does get resolved by upgrading to 10.4.6, or resetting PMU or deleting System Configuration files or upgrading the router firmware, or ensuring your Service Provider allows multiple MAC addresses or you can repair your disk permissions, or ask Santa Clause to bring you a new AE
But like I said, you are one of the first guys I've heard of having the exact same problem. I'm gonna have my AE replaced and try again. Will let you know.

Similar Messages

Satellite A210-1UP - Every few minutes the system freezes

Hi,
I just installed windows 7 32 bit on a satellite A210-1UP
Every few minutes the system freezes and then continues as if nothing happened.
No errors or blue screens are displayed
I would like to know if windows 7 can run without problems on this system ?
Which is the recommended bios version to run windows 7 ?
Thanks in advance !
Kind Regards
Stijn

Hi buddy,
Yes, Windows 7 works on Satellite A210 properly, the hardware is powerful enough.
I dont think the freezes are problem of Windows 7 or your notebook itself, I think its a software malfunction Have you installed all drivers and are yellow exclamation marks in device manager?
Such freezes could be also caused by security software or if you run a lot of background processes. Good security software is AntiVir in my opinion so I can recommend this program to you.
Also check the startup folder and msconfig (start > run > msconfig). There are all programs listed they startup with Windows and you can disable the programs that you dont need at startup like Adobe Reader, Java Updater, Nero tools, etc. but thats depending on installed software. ;)

Error message: "Warning: unresponsive script". Afterward, the system freezes and will then crash. Crash reports have been submitted many, many times without response. I have tried the fore-mentioned solutions with either no results or very bad results

Error message: "Warning: unresponsive script". Afterward, the system freezes and will then crash. Crash reports have been submitted many, many times without response. I have tried the fore-mentioned solutions with either no results or very bad results which I filed a report but did not receive an answer. The application to block scripts actually worsened the problem and I could not correct the situation for a while (no response from Firefox, at all). I have also been through this procedure without any one contacting me, AT ALL.
== URL of affected sites ==
http://http://www.facebook.com (always) and www.YouTube.com (sometimes)

There does appear to be any support whatsoever from mighty "non caring" FIREFOX & people are getting fed up. We may as well try another system, if they can't be bothered to provide any support for their system, we can't be bothered to use their system.
Brianeng

I cannot pay for subscription cause the system says the address for the invoice doesn't correspond to my credit card

i cannot pay for subscription cause the system says the address for the invoice doesn't correspond to my credit card. It's not possible, my credit card doesn't correspond to any address

These transactions help Adobe confirm that the credit card used is valid and not reported as lost or stolen. The transaction isn't charged to your account, and once your credit card company verifies it, Adobe removes the charge.
http://helpx.adobe.com/x-productkb/policy-pricing/adobe-stores-online-order-payment-faq.ht ml
You can also contact Adobe Support to place the order.
Regards
Rajshree

Last software update of OS X Lion: the system freezes before the end.

I was doing the last update of OS X Lion on a MacBook Pro (10.7.3). Before the end of the process, the system freezed. The only solution was the off button of the desktop. But after it was impossible to open it again. I had to restore OS X from the Time Machine backup. Can you help me? What is the problem? What do I have to do?

Just fixed this myself.
SWUPD is expecting a directory within the one you chose, called "html".
Example: /Volumes/XSAN/SWUPD/html
It will not create "html" if the directory doesn't exist.
Create the folder "html" then in terminal do this:
sudo chown -R _softwareupdate:_softwareupdate /path/to/the/folder
Example: sudo chown -R _softwareupdate:_softwareupate /Volumes/XSAN/SWUPD
##do not include/html. the -R means recursive and forces the same ownership on all contained directories.

Sometimes at startup the system freezes

sometimes not always the system after i enter the login password the system freezes why this happening?

the output of journalctl --since=2014-05-14 is
May 14 01:07:56 archkostas systemd[943]: Starting Paths.
May 14 01:07:56 archkostas systemd[943]: Reached target Paths.
May 14 01:07:56 archkostas systemd[943]: Starting Timers.
May 14 01:07:56 archkostas systemd[943]: Reached target Timers.
May 14 01:07:56 archkostas systemd[943]: Starting Sockets.
May 14 01:07:56 archkostas systemd[943]: Reached target Sockets.
May 14 01:07:56 archkostas systemd[943]: Starting Basic System.
May 14 01:07:56 archkostas systemd[943]: Reached target Basic System.
May 14 01:07:56 archkostas systemd[943]: Starting Default.
May 14 01:07:56 archkostas systemd[943]: Reached target Default.
May 14 01:07:56 archkostas systemd[943]: Startup finished in 67ms.
May 14 01:08:13 archkostas org.kde.kuiserver[956]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
May 14 01:08:13 archkostas org.kde.kuiserver[956]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
May 14 01:14:30 archkostas org.kde.ApperSentinel[956]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
May 14 01:14:30 archkostas org.kde.ApperSentinel[956]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
May 14 02:08:11 archkostas org.kde.kuiserver[956]: kuiserver: Fatal IO error: client killed
May 14 02:08:12 archkostas systemd[943]: Stopping Default.
May 14 02:08:12 archkostas systemd[943]: Stopped target Default.
May 14 02:08:12 archkostas systemd[943]: Stopping Basic System.
May 14 02:08:12 archkostas systemd[943]: Stopped target Basic System.
May 14 02:08:12 archkostas systemd[943]: Stopping Paths.
May 14 02:08:12 archkostas systemd[943]: Stopped target Paths.
May 14 02:08:12 archkostas systemd[943]: Stopping Timers.
May 14 02:08:12 archkostas systemd[943]: Stopped target Timers.
May 14 02:08:12 archkostas systemd[943]: Stopping Sockets.
May 14 02:08:12 archkostas systemd[943]: Stopped target Sockets.
May 14 02:08:12 archkostas systemd[943]: Starting Shutdown.
May 14 02:08:12 archkostas systemd[943]: Reached target Shutdown.
May 14 02:08:12 archkostas systemd[943]: Starting Exit the Session...
May 14 02:08:12 archkostas systemd[943]: Received SIGRTMIN+24 from PID 2887 (kill).
-- Reboot --
May 16 16:04:58 archkostas systemd[1109]: Reached target Paths.
May 16 16:04:58 archkostas systemd[1109]: Starting Timers.
May 16 16:04:58 archkostas systemd[1109]: Reached target Timers.
May 16 16:04:58 archkostas systemd[1109]: Starting Sockets.
May 16 16:04:58 archkostas systemd[1109]: Reached target Sockets.
May 16 16:04:58 archkostas systemd[1109]: Starting Basic System.
May 16 16:04:58 archkostas systemd[1109]: Reached target Basic System.
May 16 16:04:58 archkostas systemd[1109]: Starting Default.
May 16 16:04:58 archkostas systemd[1109]: Reached target Default.
May 16 16:04:58 archkostas systemd[1109]: Startup finished in 67ms.
May 16 16:05:15 archkostas org.kde.kuiserver[1123]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
May 16 16:05:15 archkostas org.kde.kuiserver[1123]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
May 16 16:11:32 archkostas org.kde.ApperSentinel[1123]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
May 16 16:11:32 archkostas org.kde.ApperSentinel[1123]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
May 16 16:48:41 archkostas org.kde.ApperSentinel[1123]: apper-sentinel: Fatal IO error: client killed
May 16 16:48:41 archkostas systemd[1109]: Stopping Default.
May 16 16:48:41 archkostas systemd[1109]: Stopped target Default.
May 16 16:48:41 archkostas systemd[1109]: Stopping Basic System.
May 16 16:48:41 archkostas systemd[1109]: Stopped target Basic System.
May 16 16:48:41 archkostas systemd[1109]: Stopping Paths.
-- Reboot --
May 16 17:30:54 archkostas systemd[1063]: Starting Paths.
May 16 17:30:54 archkostas systemd[1063]: Reached target Paths.
May 16 17:30:54 archkostas systemd[1063]: Starting Timers.
May 16 17:30:54 archkostas systemd[1063]: Reached target Timers.
May 16 17:30:54 archkostas systemd[1063]: Starting Sockets.
May 16 17:30:54 archkostas systemd[1063]: Reached target Sockets.
May 16 17:30:54 archkostas systemd[1063]: Starting Basic System.
May 16 17:30:54 archkostas systemd[1063]: Reached target Basic System.
May 16 17:30:54 archkostas systemd[1063]: Starting Default.
May 16 17:30:54 archkostas systemd[1063]: Reached target Default.
May 16 17:30:54 archkostas systemd[1063]: Startup finished in 78ms.
-- Reboot --
May 16 16:04:58 archkostas systemd[1109]: Starting Paths.
May 16 17:33:29 archkostas systemd[1371]: Reached target Paths.
May 16 17:33:29 archkostas systemd[1371]: Starting Timers.
May 16 17:33:29 archkostas systemd[1371]: Reached target Timers.
May 16 17:33:29 archkostas systemd[1371]: Starting Sockets.
May 16 17:33:29 archkostas systemd[1371]: Reached target Sockets.
May 16 17:33:29 archkostas systemd[1371]: Starting Basic System.
May 16 17:33:29 archkostas systemd[1371]: Reached target Basic System.
May 16 17:33:29 archkostas systemd[1371]: Starting Default.
May 16 17:33:29 archkostas systemd[1371]: Reached target Default.
May 16 17:33:29 archkostas systemd[1371]: Startup finished in 78ms.
May 16 17:33:46 archkostas org.kde.kuiserver[1416]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
May 16 17:33:46 archkostas org.kde.kuiserver[1416]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
May 16 17:40:02 archkostas org.kde.ApperSentinel[1416]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
May 16 17:40:02 archkostas org.kde.ApperSentinel[1416]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
May 16 17:40:48 archkostas org.kde.kuiserver[1416]: kuiserver: Fatal IO error: client killed
May 16 17:40:48 archkostas org.kde.ApperSentinel[1416]: apper-sentinel: Fatal IO error: client killed
May 16 17:40:48 archkostas org.a11y.Bus[1416]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async re
May 16 17:40:48 archkostas systemd[1371]: Stopping Default.
May 16 17:40:48 archkostas systemd[1371]: Stopped target Default.
May 16 17:40:48 archkostas systemd[1371]: Stopping Basic System.
May 16 17:40:48 archkostas systemd[1371]: Stopped target Basic System.
May 16 17:40:48 archkostas systemd[1371]: Stopping Paths.
May 16 17:40:48 archkostas systemd[1371]: Stopped target Paths.
May 16 17:40:48 archkostas systemd[1371]: Stopping Timers.
May 16 17:40:48 archkostas systemd[1371]: Stopped target Timers.
May 16 17:40:48 archkostas systemd[1371]: Stopping Sockets.
May 16 17:40:48 archkostas systemd[1371]: Stopped target Sockets.
May 16 17:40:48 archkostas systemd[1371]: Starting Shutdown.
May 16 17:40:48 archkostas systemd[1371]: Reached target Shutdown.
May 16 17:40:48 archkostas systemd[1371]: Starting Exit the Session...
May 16 17:40:48 archkostas systemd[1372]: pam_unix(systemd-user:session): session closed for user kostas
-- Reboot --
May 16 21:36:59 archkostas systemd[1049]: Starting Paths.

The system freezes a lot and dmesg gives an error in Nvidia drivers

I faced constant system freezing in Ubuntu under both Unity and Gnome shell. So I came to Arch. In Arch also im facing the same issue. I tried many things in these forums but nothing helped. Please help me. The system hangs constantly and the mouse barely moves. When I press ctrl+alt+f2 it takes several minutes to go to the terminal and then I can reboot. Please help. Here's the output of dmesg :
[ 1.826414] systemd[1]: Starting Login Prompts.
[ 1.826435] systemd[1]: Reached target Login Prompts.
[ 1.826449] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[ 1.826519] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 1.826533] systemd[1]: Starting Remote File Systems.
[ 1.826547] systemd[1]: Reached target Remote File Systems.
[ 1.826572] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[ 1.826666] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 1.826685] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
[ 1.826720] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 1.826732] systemd[1]: Starting Paths.
[ 1.826744] systemd[1]: Reached target Paths.
[ 1.826755] systemd[1]: Starting Encrypted Volumes.
[ 1.826767] systemd[1]: Reached target Encrypted Volumes.
[ 1.826780] systemd[1]: Expecting device dev-disk-by\x2duuid-c11bdfb5\x2db15e\x2d473a\x2d8cf8\x2d020715616bde.device...
[ 1.826793] systemd[1]: Expecting device dev-disk-by\x2duuid-8ada8f05\x2d1853\x2d45c7\x2da302\x2d7d11869fd5bd.device...
[ 1.826805] systemd[1]: Expecting device dev-disk-by\x2duuid-E8D0\x2d38A9.device...
[ 1.826816] systemd[1]: Starting Root Slice.
[ 1.834477] systemd[1]: Created slice Root Slice.
[ 1.834493] systemd[1]: Starting User and Session Slice.
[ 1.834670] systemd[1]: Created slice User and Session Slice.
[ 1.834684] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[ 1.834712] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 1.834724] systemd[1]: Starting Device-mapper event daemon FIFOs.
[ 1.834752] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 1.834764] systemd[1]: Starting Delayed Shutdown Socket.
[ 1.834790] systemd[1]: Listening on Delayed Shutdown Socket.
[ 1.834805] systemd[1]: Starting udev Control Socket.
[ 1.834829] systemd[1]: Listening on udev Control Socket.
[ 1.834843] systemd[1]: Starting udev Kernel Socket.
[ 1.834868] systemd[1]: Listening on udev Kernel Socket.
[ 1.834880] systemd[1]: Starting LVM2 metadata daemon socket.
[ 1.834907] systemd[1]: Listening on LVM2 metadata daemon socket.
[ 1.834921] systemd[1]: Starting Journal Socket.
[ 1.834967] systemd[1]: Listening on Journal Socket.
[ 1.834986] systemd[1]: Starting System Slice.
[ 1.835160] systemd[1]: Created slice System Slice.
[ 1.835179] systemd[1]: Started File System Check on Root Device.
[ 1.835191] systemd[1]: Starting system-systemd\x2dfsck.slice.
[ 1.835379] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[ 1.835393] systemd[1]: Mounting Temporary Directory...
[ 1.835993] systemd[1]: Starting system-getty.slice.
[ 1.836195] systemd[1]: Created slice system-getty.slice.
[ 1.837686] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[ 1.838280] systemd[1]: Starting udev Coldplug all Devices...
[ 1.838810] systemd[1]: Mounting Huge Pages File System...
[ 1.839349] systemd[1]: Mounting POSIX Message Queue File System...
[ 1.841338] systemd[1]: Starting Apply Kernel Variables...
[ 1.841909] systemd[1]: Starting Setup Virtual Console...
[ 1.842552] systemd[1]: Mounting Debug File System...
[ 1.844757] systemd[1]: Started Load Kernel Modules.
[ 1.844789] systemd[1]: Mounting Configuration File System...
[ 1.845225] systemd[1]: Mounted FUSE Control File System.
[ 1.846612] systemd[1]: Starting Set Up Additional Binary Formats...
[ 1.847351] systemd[1]: Starting Journal Service...
[ 1.848175] systemd[1]: Started Journal Service.
[ 1.861600] EXT4-fs (sda6): re-mounted. Opts: data=ordered
[ 1.865901] systemd[1]: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 141 (systemd-binfmt)
[ 1.919562] systemd-udevd[165]: starting version 212
[ 1.974653] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 1.981863] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
[ 1.981873] ACPI: Power Button [PWRB]
[ 1.981971] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[ 1.981976] ACPI: Power Button [PWRF]
[ 1.983340] parport_pc 00:08: reported by Plug and Play ACPI
[ 1.983390] parport0: PC-style at 0x378, irq 5 [PCSPP]
[ 1.983777] i8042: PNP: No PS/2 controller found. Probing ports directly.
[ 1.986033] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.986096] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.990191] mei_me 0000:00:16.0: irq 43 for MSI/MSI-X
[ 1.990406] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 1.990820] acpi device:43: registered as cooling_device4
[ 1.990950] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input5
[ 1.991137] [drm] Initialized drm 1.1.0 20060810
[ 1.993033] wmi: Mapper loaded
[ 2.014083] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\PMIO) (20131218/utaddress-258)
[ 2.014092] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.014097] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20131218/utaddress-258)
[ 2.014103] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.014105] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20131218/utaddress-258)
[ 2.014110] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.014112] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 2.016081] thermal LNXTHERM:00: registered as thermal_zone0
[ 2.016084] ACPI: Thermal Zone [TZ00] (28 C)
[ 2.016323] thermal LNXTHERM:01: registered as thermal_zone1
[ 2.016325] ACPI: Thermal Zone [TZ01] (30 C)
[ 2.016391] ACPI: Fan [FAN0] (off)
[ 2.016435] ACPI: Fan [FAN1] (off)
[ 2.016476] ACPI: Fan [FAN2] (off)
[ 2.016517] ACPI: Fan [FAN3] (off)
[ 2.016555] ACPI: Fan [FAN4] (off)
[ 2.027162] ACPI Warning: SystemIO range 0x000000000000f040-0x000000000000f05f conflicts with OpRegion 0x000000000000f040-0x000000000000f04f (\_SB_.PCI0.SBUS.SMBI) (20131218/utaddress-258)
[ 2.027171] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.027373] input: PC Speaker as /devices/platform/pcspkr/input/input6
[ 2.036735] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 2.036746] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 2.037012] r8169 0000:03:00.0: irq 44 for MSI/MSI-X
[ 2.037275] r8169 0000:03:00.0 eth0: RTL8168f/8111f at 0xffffc900059b6000, 60:a4:4c:3d:76:fa, XID 08000800 IRQ 44
[ 2.037279] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 2.041327] snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
[ 2.042605] snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X
[ 2.042682] snd_hda_intel 0000:01:00.1: enabling device (0000 -> 0002)
[ 2.042728] hda_intel: Disabling MSI
[ 2.042735] hda-intel 0000:01:00.1: Handle VGA-switcheroo audio client
[ 2.047515] mousedev: PS/2 mouse device common for all mice
[ 2.058597] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x28
[ 2.059406] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x28
[ 2.059423] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x28
[ 2.059438] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x28
[ 2.059519] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
[ 2.070989] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[ 2.071058] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 2.071112] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 2.071164] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[ 2.071216] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[ 2.071268] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
[ 2.096085] kvm: disabled by bios
[ 2.113324] ppdev: user-space parallel port driver
[ 2.118467] iTCO_vendor_support: vendor-support=0
[ 2.119501] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
[ 2.119535] iTCO_wdt: Found a Panther Point TCO device (Version=2, TCOBASE=0x0460)
[ 2.120228] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 2.122797] asus_wmi: ASUS WMI generic driver loaded
[ 2.123577] asus_wmi: Initialization: 0x0
[ 2.123593] asus_wmi: BIOS WMI version: 0.9
[ 2.123620] asus_wmi: SFUN value: 0x0
[ 2.123943] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input14
[ 2.124655] asus_wmi: Backlight controlled by ACPI video driver
[ 2.139754] systemd-udevd[172]: renamed network interface eth0 to enp3s0
[ 2.159402] Adding 4882428k swap on /dev/sdb6. Priority:-1 extents:1 across:4882428k FS
[ 2.173202] nvidia: module license 'NVIDIA' taints kernel.
[ 2.173206] Disabling lock debugging due to kernel taint
[ 2.179335] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
[ 2.179471] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 0
[ 2.179477] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 337.12 Fri Apr 4 14:51:15 PDT 2014
[ 2.292323] Switched to clocksource tsc
[ 2.369970] EXT4-fs (sdb8): mounted filesystem with ordered data mode. Opts: data=ordered
[ 2.380040] systemd-journald[142]: Received request to flush runtime journal from PID 1
[ 2.398821] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input18
[ 2.399044] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
[ 2.399180] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
[ 2.704632] r8169 0000:03:00.0 enp3s0: link down
[ 2.704667] r8169 0000:03:00.0 enp3s0: link down
[ 2.704684] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 2.889853] nvidia 0000:01:00.0: irq 46 for MSI/MSI-X
[ 3.436679] NVRM: Your system is not currently configured to drive a VGA console
[ 3.436683] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[ 3.436686] NVRM: requires the use of a text-mode VGA console. Use of other console
[ 3.436688] NVRM: drivers including, but not limited to, vesafb, may result in
[ 3.436690] NVRM: corruption and stability problems, and is not supported.
[ 4.318649] fuse init (API version 7.22)
[ 5.160446] r8169 0000:03:00.0 enp3s0: link up
[ 5.160458] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[ 18.971615] NVRM: GPU at 0000:01:00: GPU-3840b413-5a51-9da2-923a-a4cbb4a5005e
[ 18.971628] NVRM: Xid (0000:01:00): 13, 0003 00000000 0000a097 00002410 00000030 00000000

ondoho wrote:
archlinux comes as a barebones system - i guess you installed some sort of desktop environment on top of it.
if you installed the same (unity or gnome shell) that will probably not solve your problem.
if you managed to set up an arch system with a gui, you should be able to provide us with more relevant information, so we can start troubleshooting.
off the top of my head (or hat?) i'd say your hardware can't keep up with a full-fledged desktop environment and you should choose something more lightweight. but that's just guessing.
I tried both gnome and unity. My GPU is Nvidia GT640 2GB DDR3, Motherboard Asus p8b75m, Cpu i3-2100. Ram 8 GB. 64GB SSD (Root is on it), 1 TB HDD (Home is on it). I don'tthink my system can't handle a full DE.

RMI server causes the system to slow down and crash with socketException

Hi,
My RMI server application is a simple rmi server which invokes a JNI method once when I invoke through my client application. Server is left as it is after invoking the JNI method. After around 12 hours, server stops running with the following exception
ZoneInfo: C:\Program Files\Java\jre1.6.0\lib\zi\ZoneInfoMappi
ngs (Insufficient system resources exist to complete the requested service)
ZoneInfo: C:\Program Files\Java\jre1.6.0\lib\zi\ZoneInfoMappings (Insufficient s
ystem resources exist to complete the requested service)
Dec 29, 2008 10:09:34 AM sun.rmi.transport.tcp.TCPTransport$AcceptLoop executeAc
ceptLoop
WARNING: RMI TCP Accept-0: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,por
t=0,localport=2161] throws
java.net.SocketException: socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(Unknown Source)
at java.net.ServerSocket.implAccept(Unknown Source)
at java.net.ServerSocket.accept(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(Unkno
wn Source)
at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Dec 29, 2008 10:10:35 AM sun.rmi.transport.tcp.TCPTransport$AcceptLoop executeAc
ceptLoop
WARNING: RMI TCP Accept-0: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,por
t=0,localport=2161] throws
java.net.SocketException: socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(Unknown Source)
at java.net.ServerSocket.implAccept(Unknown Source)
at java.net.ServerSocket.accept(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(Unkno
wn Source)
at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Dec 29, 2008 10:12:36 AM sun.rmi.transport.tcp.TCPTransport$AcceptLoop executeAc
ceptLoop
WARNING: RMI TCP Accept-0: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,por
t=0,localport=2161] throws
java.net.SocketException: socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(Unknown Source)
at java.net.ServerSocket.implAccept(Unknown Source)
at java.net.ServerSocket.accept(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(Unkno
wn Source)
at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Dec 29, 2008 10:15:37 AM sun.rmi.transport.tcp.TCPTransport$AcceptLoop executeAc
ceptLoop
WARNING: RMI TCP Accept-0: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,por
t=0,localport=2161] throws
java.net.SocketException: socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(Unknown Source)
at java.net.ServerSocket.implAccept(Unknown Source)
at java.net.ServerSocket.accept(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(Unkno
wn Source)
at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Dec 29, 2008 10:20:40 AM sun.rmi.transport.tcp.TCPTransport$AcceptLoop executeAc
ceptLoop
WARNING: RMI TCP Accept-0: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,por
t=0,localport=2161] throws
java.net.SocketException: socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(Unknown Source)
at java.net.ServerSocket.implAccept(Unknown Source)
at java.net.ServerSocket.accept(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(Unkno
wn Source)
at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
# An unexpected error has been detected by Java Runtime Environment:
# Internal Error (4D555445583F57494E13120E4350500075), pid=1352, tid=1828
# Java VM: Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode, sharing)
# Can not save log file, dump to screen..
# An unexpected error has been detected by Java Runtime Environment:
# Internal Error (4D555445583F57494E13120E4350500075), pid=1352, tid=1828
# Java VM: Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode, sharing)
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
Does anyone has any idea?
Regards
Nidhin

Your RMI server invokes a JNI method as you mentioned. It seems your system resource is become very low as from the exception from "ZoneInfoMappi"
(Insufficient system resources exist to complete the requested service...I would suggest the following
1- remove the JNI method invocation and replace by a simple method which does nothing special ( counting etc..)
2- Run the RMI sever and stress test it again
If you see the RMI server is working well after 12 hours, then your native method is leaking i.e consuming the system resources ( RAM etc..)
You should profile the running RMI server using jconsole
Regards,
Alan Mehio

Does having too many apps cause the constant freezing?

Hi!
I deleted a number of apps and the freezing doesn't seem as bad.
Would the apps also apply to having the iPod turn itself off?

Never mind...
Before replacing my iPod Touch, I was told that it was most likely the cause.
*Ignore this topic*

I am using Photoshop Elements 12 and when I am importing pictures the system freezes and needs to be forced quit. When I restart it it continues to bring the pictures in eventually. What is the solution to this?

I am using MAC os version of elements 12 with OS 10.9.4 (the latest). When I am importing pictures from a card elements freezes consistently and needs to be voce closed. When I then restart elements it continues to bring the pictures in but this is very tedious and I need to get the matter resolved,

TomWolves
I would do another rename to disable or just delete all the OldFilm.AEX and OldFilm.AEXOLD in that NewBlue Folder.
If you do, please let me know if that OldFilm.AEX regenerates itself the next time you open Premiere Elements 13.
Here is the strange story...at least from my Premiere Elements 13 Windows perspective...never had the No Disc error issue
Here are some details to sort through trying to figure out why you have 2 OldFilm.AEX file in the NewBlue Folder.
1. The original OldFilm.AEX file of Premiere Elements 13 has the date of 9/4/2014 (just before the version was released on 9/24/2014).
After the 13.1 update is done (whenever date), that OldFilm.AEX file has the date of 1/31/2015. I first saw notification of the 13.1 Update
release early in February 2015.
2. Now in Premiere Elements 13.1, if I take my OldFilm.AEX (date 1/31/2015) and disable it by renaming it to OldFilm.AEXOLD, close out of there, and reopen
the program, the OldFilm.AEX is not seen to regenerate. The OldFilm.AEXOLD remains there as its lone self.
3. So, I am thinking that your OldFilm.AEXOLD in the screenshoot is "original equipment" that you disabled to get rid of No disc error.
Why the OldFilm.AEX is there also is not clear, but the dating on it suggests that it came along with the 13.1 Update.
Bottom line: let us try the deletion or disabling one more time and see what happens.
Looking forward to further reports on your findings, as your time permits.
Thanks.
ATR

[SOLVED]Help! bootchard caused the system to stop booting

Hello,
I've installed bootchard and followed the instructions in the archwiki specifically where it says
Open up /boot/grub/menu.lst, and copy/paste the entry you want to log. Append "init=/sbin/bootchartd"
I did that and now the computer wont boot correctly. I get an error that sbin/bootchard was not found and that i'm on my own now? What am I'm supposed to do? I'm now using the Ubuntu LiveCD to post this.
EDIT: I've copied the actual error down and this is what it says.
Error: root revice mounted successfully, but sbin/bootchard does not exist. Bailing out, you are on your own, good luck .
Last edited by aluser (2011-02-12 19:05:21)

Do as Varg said and you should be fine.
Your boot kernel entry should look something like this:
kernel /boot/vmlinuz26 root=/dev/sdb1 ro init=/sbin/bootchartd
Since bootchartd is not something you don't normally want to run on every boot, you might want to create a separate entry for it like so:
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/sdb1 ro fastboot logo.nologo quiet ipv6.disable=1
initrd /boot/kernel26.img
# (1) Bootchart
title Arch Linux Bootchart
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/sdb1 ro fastboot logo.nologo quiet ipv6.disable=1 init=/sbin/bootchartd
initrd /boot/kernel26.img
Lose "fastboot logo.nologo quiet ipv6.disable=1" if you don't want these options and make sure that "root" is set correctly for your system.

OS LION hanged and froze!!! I could not use my iMac at all, the system freezes so frequently and i have to forced quite restart.

Operating on OS SNOW LEOPARD, IMAC, upgraded to OS LION and system froze and hanged several times indefinitely! Did a Harddisk erase and reformat and Re-installed OS LION 4 times already problem still occurred! What happen? The tips from Imac graphics firmware update 1.0 didn't help either, same problem occurred! Stuck with current situation, please help! Is this the end of my 3 year old iMac? I am afraid about the life span and durability of my iMac. Please help.
OS LION pride!

Hi,
Check the logs (using the Console application) for a "GPU Debug Info Start" message followed by a long memory dump. If you find it then you might have been the victim of a very buggy video driver. Lots of people are having this issue but Apple doesn't seem to care.
See this thread: https://discussions.apple.com/message/15676049

Printing A Report Causes The System To Reboot / Crash

Post Author: rhavlick
CA Forum: Crystal Reports
Hello,
I'm not even sure where to start on this one - I built a few reports in CR XI, and deployed them to the customer's machines. So far 2 out of the 10 at 2 seperate locations will have no problems displaying the report on the screen in the screen in the print preview control for .NET. However, when the user presses Print, and selects just their normal HP Laserjet 4240n printer, it actually goes to the blue screen of death, and then reboots. I upgraded to Crystal Reports 2008, and it's doing the same thing after installing the runtime on the user's machine. Next I tested on another computer at the same office, with the same results to the same printer. Next I tried to print to the Microsoft Office XPS Document Writer and that works from Crystal and then printing to the printer from that. I also tried exporting from Crystal to PDF, and then printing from that which works too. I updated drivers with the latest drivers, one is a HP and one is a Lexmark at 2 different not related locations. It appears to be report dependent since some other reports work.
Is there any way anyone knows how to trouble shoot this issue?
Thanks.

Post Author: rhavlick
CA Forum: Crystal Reports
It's taken me about a month and $600 to purchase printers and return them, etc. to finally get this figured out. What is happening is if you have color on a report, and then print to a printer that doesn't support color printing it actually crashes the O.S. I can't recreate this on all B&W printers, it only appears to happen on some, even though they have the same drivers, etc.
I can strip out colors, and just leave it black white and grey and everything works on the one that was crashing. What I am wondering is if anyone knows of a way I can force CR to print in B&W on a printer that only supports B&W either when it's printing or when it's rendering the report? I do need the reports to be in color for the users with a color printer and it renders fine in color even if you don't have a color printer, but it blows up when you print. Does anyone know if this is possible or have any suggestions regarding this? Thanks.

Why is it when I try to install Additional Content the system freezes?!

I am installing Logic Studio for the first time on a new iMac. All was well with the installation until it asked for the Additional Content DVD. It now froze completely! I don't know what to do...

contact iTunes by:
https://expresslane.apple.com/Issues.action

System freezes/crashes

I've only had my new iMac for a couple of weeks but I have already experencied numerous kernal panics (which I think has been corrected by removing 3rd party memory) but also at least 6 system freezes/crashes. There is no regularity to the problem. I will simply go to use the machine any everything will be locked. The mouse will not more nor do the keys on the keyboard work. My only option has been a hard restart. I've spoken to tech support and gone to the apple store and am getting different answers to the possible problem. Any ideas as to what might cause the system freeze? I have since removed all usb devices (had an external hard drive and ipad connected) to see if this corrects the problem. The Apple store told me the next option woudl be a complete software reinstall which I would prefer to avoid as I do not have access to install programs for a purchased version of office.

If you have Snow Leopard 10.6.8 installed, try installing the 10.6.8 combo update from http://support.apple.com/kb/DL1399 . Sometimes the operating system can develop some kinks, especially if Software Update has been used. Repair permissions first, apply the update, then repair permissions again. Then run Software Update to sweep up any other needed updates. A combo update includes all prior updates for that version of the operating system.
If you have Lion, there isn't a combo update for it yet, as there is only one release at 10.7.1. You can manually reapply that release from http://support.apple.com/kb/DL1437

Airport causes the system freeze.

Similar Messages

Maybe you are looking for