Temporary work around solution to no black print Photosmart 6515

After exhaustive research I am passing on a work around that actually got the black back:  change your 6515 driver to a Photosmart 3300 driver. No color, but it prints black now.  If anyone has a driver that works better please let me know!

The black ink used in the Photosmart 6515 is pigmented and not compatible with photo paper.  Do you have photo paper selected in the Photosmart 3300 driver settings?  In this case it would appear black is printing but the printer will actually use the dye based color inks to mix and make "black".
I see from your other thread that you have gone through the standard troubleshooting steps and black is not printing properly on your test pages.  I will ask to have one of the HP Support folks step into this thread, they may have other alternatives.
Bob Headrick,  HP Expert
I am not an employee of HP, I am a volunteer posting here on my own time.
If your problem is solved please click the "Accept as Solution" button ------------V
If my answer was helpful please click the "Thumbs Up" to say "Thank You"--V

Similar Messages

  • Work around solutions

    dear gurus,
        what is meant by work around solutions?can anyone please explain with few examples..
                                    -guna

    In SAP there is no method to capture the idle time of a machine.This is very important to calcualate the utilisation of a mahchine - on which we can see where we are loosing the time .
    So what we can do is do a operation confirmaiton without a zero confirmation quantity.
    have a separte production order created without material and do confirmation against this.
    So theese are few methods or workarounds on which we can capture the idle time and then using some z develoopments we willbe able to make a report
    kindly let me know if you still have doubts.

  • Printing Problem Solved (Temporary Work-around)

    I've posted before, and others have posted here and elsewhere, about problems printing with Aperture since upgrading to Leopard. In my case, it's been with an Epson R1800.
    Well, believe it or not, with the help of Epson support on the phone, I've figured this out. First of all, there is definitely a problem with Aperture's (or Leopard's) color management. What used to work (setting a color profile in the Aperture print dialog, and selecting "no color management" in the printer dialog) definitely does not work correctly at this point.
    If you want color management, what you have to do is select "System Managed" in the Aperture print dialog, and select (for Epson) "Color Controls - Epson Standard" in the Epson dialog. What this does is select the standard Epson profile for the paper you have selected. For example, if you've chosen Epson Premium Glossy Photo Paper, the printer driver will use the "SPR1800 Premium Glossy" profile (Epson's standard profile for that paper, assuming you've downloaded it). Of course, that gives you Epson's version of what you want to print. If you have created your own profiles, using a spectrophotometer for example, you need to get the printer driver to apply YOUR profile instead of Epson's.
    Here's how to apply your profile: Open Colorsync (in the Utilities folder), and select "Printers" in the Devices menu. Under the printer model, Stylus Photo R1800, in my case, select the profile for the paper you're interested in, say "SPR1800 Premium Glossy", and look on the right side of the window at "Current Profile:". Click the down arrow, and select "Other". Navigate to the profile you've created, and click "Open". This will set the profile you've created as what the printer driver will use when it thinks it's applying the SPR1800 Premium Glossy profile. Set other paper profiles (e.g., "SPR1800 Enhanced Matte") to whatever profile you've created for those papers.
    Now, when you select "System Managed" in the Aperture dialog, and "Color Controls - Epson Standard" in the Epson dialog, it will apply your own profile.
    Hopefully, Apple will fix the problem with color management, and we'll be able to go back to color management as it was before. In the meantime, this is the only work-around I've found.

    I was/am totally a Mac guy, meaning my roots were System 7 based, and my knowledge of all things UNIX is being built slowly as needed in the OS X world. While I can make Photoshop & Aperture (and the GUI portions of OS X) stand on their heads and do backflips for treats I can't, with much conviction, speak on the roots of UNIX drivers. I think, and someone please correct me if I'm wrong, that Gutenprint drivers are CUPS 'compatible' drivers, but not necessarily "CUPS" drivers in that they work with other printing platforms as well. Here are some sources of info:
    http://gimp-print.sourceforge.net/
    http://www.cups.org/
    The Gutenprint drivers may be the CUPS drivers for the Epson printer, I don't know for sure. On the Canon site, there are two drivers available for download for the Pro9000. One labeled standard, the other labeled CUPS. By default, when adding the printer, my system uses the CUPS driver. I can actually have the Pro9000 added twice, once with the CUPS driver, once with the standard driver. I spoke with an Canon engineer the other day, and contrary to the advice you get from the standard phone support reps, he told me to definitely use the CUPS driver when printing RAW or 16-bit images from Photoshop or Aperture, as it's the only way to do 16-bit printing.
    Message was edited by: KBeat

  • 6D battery drain temporary 'Work Around'

    6D battery drain - "Work Around"
    Install the Canon Battery Grip. 
    Step 1.  Turn the battery lock to 'Open'.and leave it unlocked
          (Batteries are now disconnected from camera)
    Step 2    Use a rubber band to hold battery tray in.
    ====================================
    NOTE:: If Canon will not make a fix, possibly the after-market suppliers of the 'Grip' will make a three position latch.
    A 'Modified' grip could easily be manufactured by modifying the tray and latch assembly.
    Position 1.  Power disconnected and tray locked in (6:00 clock position)
    Position 2.  Tray unlocked (Similar position as present)
    Position 3.  Tray is locked and power is connect. (Same position as present and battery drain will continue as it does now..)
    GET WITH IT CANON....   Or let the after-market fix it with their 'Grip'
    Bill

    6D Battery drain "Fast Stop" using the Canon '6D Grip'
    I am enjoying using only one switch movement  to turn my 6D ON/OFF and not having any battery drain.
    1.   Leave camera switch in the ON position
    2.   Place a sturdy rubber band around the Canon Battery Grip to stop battery tray from coming out
    3.   Turn the Grip battery tray 'Latch' to OPEN/CLOSE (Effectively ON/OFF)
    4.    Making my Grip latch as my on and off switch for the camera and stopping the battery drain by the GPS operation
    5.    My 6D camera is now always ready for that one of a kind picture

  • Getting a "sticky" for all LP8 problems and work arounds/solutions?

    Any chance we could get a sticky on this? It would be a lot faster than going thru the "Search Forum" option.
    List the known issues
    List the fix/work around for the issue
    Rob

    We asked for that in the L7 forum for years and got little in terms of a response (see below). And definitely no sticky!
    Sure, there are a few knowledge base documents that describe issues with L8, but in general, acknowledging known problems is not something Apple does, unfortunately. How do I know this? Well, experience. And also, from what they have to say about their software in the Getting Started guide:
    "Experience has shown that such system _problems are rarely caused by a defect in Apple programs or hardware products_. All Apple hardware and software is _rigorously tested_ by a diverse range of musicians and studio users, from a variety of fields and uses, who look for any faults or problems.
    This doesn’t mean that the possibility of errors can be completely ruled out; problems can crop up periodically. This is not unexpected—as the various applications, operating system versions, and drivers—are all developed, and improved in parallel by unrelated programming teams. This can lead to occasional compatibility problems. _Apple provides fixes in the form of software updates, as soon as such problems are identified._ Apple is always grateful to users who report any problems."
    (emphasis added by iSchwartz)
    If that isn't a profound mixture of truths, half-truths, and flat-out lies.
    Now... there is some kind of "tips" board somewhere amongst Apple's Discussion Forums. When the subject of having a sticky came up once on the L7 board a while ago, a mod suggested that I submit tips/workarounds for inclusion on that board. I checked it out and it's a freekin' nightmare to find anything. And "submitting" tips means that someone has to approve it, and who knows if that person would be Logic-savvy or not. So there it is...

  • No black on Photosmart 6515

    ser no CN1B5437GB
    purchased in Dec 2011
    HP computer running Vista
    problem:  no black suddenly.  all other colors OK. MIght have had some earlier black spottiness issues, but this failure was sudden.  changed the cartridge with HP new black cartridge.  have reset printer.  went to factory defaults. clean printhead several times. when I run alignment test, it says cartidge alignment is not "optimal" but OK to proceed.  I did not waste the ink.  ideas?

    The solution I linked to is the page specific to the Photosmart 6515.   Those are the steps most likely to solve the problem for you.  It includes steps for ensuring the vent is clear.   That's covered in the document in the link.  Did you already try that step?  The last solution would be to check to see if your printer is still in warranty and service or replace the printer.   
    I am an HP employee.

  • ITunes Stream Stuttering and Crackling Noises (Temporary Work Around Option

    Note: If you don’t take the time from your busy schedule to address these suggestions being provided in this and future upcoming series, then by all mean continue with what you were doing before and continue to experience the frustrations and problems. The series is not meant to be a cure-all for the problems you are having. But the information will go a long way toward correcting and improving a lot of issues that you may be having with your system. Think About It !!!!!!!!!!
    I listen to the radio a lot using the iTunes player as well as listen to music that I have transferred to the player. When a problem occurs it aggravates me to no end especially if it is occurring when I am try to relax to my music. At times I am also experiencing the stuttering and crackling issues in the 7.0 update that has been recently released. The following information can be useful in temporarily correcting this problem until Apple comes up with a patch to resolve this issue. If you choose to proceed with implementing this information then you assume any liability that may occur during your attempts at using and applying this information. This information has so far suited any needs that I may or am currently having to date personally.
    1)Quick Time Preferences – In the Quick Time Preferences\Audio tab check to make sure that the settings are at the default level. Your platform may reflect a different khz Rate. On my platform my default level will be the following:
    Rate: 44.1 khz
    Size: 16 bit
    Channels: Stereo (L R)
    When I listen to my music I like a good quality stereo sound so I have my audio sound routed from my laptop to my CD or Video jacks in the back of my stereo. Stereo System: Pioneer SX 251R Receiver. External Speakers: 2 - 8 ohm Yamaha.
    Make sure the Safe Mode box is unchecked. Close the Quick Time player. Now, when you begin experiencing the stutter problem there are two immediate steps that you can try to correct the problem:
    1)Stop the stream or the music that you are listening too and restart the service each time that the event occurs, (In my case the events that have been occurring has not been consistent when they do occur. Close monitoring in place on all connection ports. Running Snap In’s deployed: IPSec Monitor/MMC Console– Currently monitoring IKE and IPSec Statistics for any changes. To run this snap in properly the Event Monitor must be in the running state and actively logging events in the Administrative\Event Viewer Folder) I will also be configuring Dr Watson to generate a Stack and Dump file log to the desk top in the event of an unexpected occurrence. or,
    2)If that does not correct the problem then try the following: Go to the My Computer folder and open it up. When you have done so, Right click the Local Disk and enter the Properties section. When the Local Disk Properties box comes up, enter the Tools tab, in the Error Checking section, place a check mark in the “Automatically Fix System Errors” and click start\yes. Back out of that and close all running programs including firewall in the tray next to your clock and reboot the system.
    Once you have rebooted run the Disk Cleanup utility and the Disk Defragmenter utility. While we are using the Disk Defragmenter lets take an extra step to insure that we defragging the hard drive volumes as much as possible. Click on the analyze button a second time. If there are any entries in the box highlight the first entry and run the Defrag utility a second time.
    Tip! If you would get in the habit of running defrag process regularly on a daily basis it will help improve the overall baseline performance of your machine.
    Last Step: Open your player and try again.
    If you are still experiencing the problem and it hasn’t leveled out to your satisfaction then there are two additional steps that I have personally used or am currently using that may help with your issues. The steps will involve installing a small batch file program and a hot fix patch.
    User Profile Hive Cleanup Service– (Batch Program) Open your Browser and type in the following address: www.microsft.com once the page has loaded look for the search bar in the upper right hand corner of the page. In the search bar type in the following: “User Profile Hive Cleanup Service”. Once the search result page comes up click on the first result to bring up the proper download page. Before you can use this batch program you will be required to go through a short validation process before you can download the program. The validation process is to ensure that you are running a genuine windows platform.
    Overview
    The User Profile Hive Cleanup service helps to ensure user sessions are completely terminated when a user logs off. System processes and applications occasionally maintain connections to registry keys in the user profile after a user logs off. In those cases the user session is prevented from completely ending. This can result in problems when using Roaming User Profiles in a server environment or when using locked profiles as implemented through the Shared Computer Toolkit for Windows XP.
    On Windows 2000 you can benefit from this service if the application event log shows event id 1000 where the message text indicates that the profile is not unloading and that the error is "Access is denied". On Windows XP and Windows Server 2003 either event ids 1517 and 1524 indicate the same profile unload problem.
    To accomplish this the service monitors for logged off users that still have registry hives loaded. When that happens the service determines which application have handles opened to the hives and releases them. It logs the application name and what registry keys were left open. After this the system finishes unloading the profile.
    Once you have downloaded and installed the batch file close all running programs and reboot. Now, ‘This is important”, lets determine if the batch file is properly running after installation. Go to Start\Help and Support. Once the Help and Support Center comes up click on the following link: “Use tools to view your computer information and diagnose problems” under the “Pick a task” section. Once the page has been loaded in the left hand pane click on the “Advanced System Information” link. Once that page has been loaded click on the following link: View detailed system information (Msinfo32.exe).
    Once the System Information box is loaded look in the left pane and open the Software Environment Tree and click on the following link: Windows Error Reporting. If the batch program is properly running you should see the following entry: “User profile hive cleanup service version 1.6.30.0 started successfully
    &#x00a”. The ending symbols may be different on your platform.
    Now, we want to go to another location in your system to verify this entry and that this service is properly working again. Pull up your “Control Panel” and enter the “Administrative Tools” folder. Once there enter the “Event Viewer” folder. Then enter the “Application Folder”. If the service is properly working the following entry will be logged: User profile hive cleanup service version 1.6.30.0 started successfully, Event ID 1001. If for some reason this program is not functioning properly a different error code other then the Event Id 1001 will be generated and logged in this folder. Also if one is generated you will want to verify if it’s a genuine error. To do this you need to go back into the help and support center Advanced System Information link and click on the following link: “View the error log”. If anything goes wrong a corresponding general entry that was logged in the Event Viewer will be logged in this link verifying that a problem had occurred. All of the information in the logs will be useful in your trouble shooting efforts. To date I have not had any measurable conflicts to occur while using this batch program to date. Closing Overview: when this program engages it will target itself at the Kernel System only at shutdown and startup. A corresponding entry will be made in the folders that I have described above stating that the program had started or failed.
    System Restore Feature and USB Device’s – Event Viewer\System and Application Folders\Event ID SR 1 (Hot Fix Patch) – I have noticed that some folks are loading and unloading iTunes in attempt to correct problems. Also, I see by the forum board that a lot of folks are having a lot of problems with their iPods. Think about this for a moment, iPods will have their own unique set of drivers to operate from. I am going to attempt to explain an experience that occurred with me last year on this issue. When working with USB Devices it is important to keep your eyes on the Event Viewer folders for the following event id being logged: Event ID SR 1. This is especially true if you are using your System Restore Feature. The main folders that you want to keep your eyes on are the “System\Application” folders.
    I have not witnessed any specific Software Applications generating this code in general at this point in time. But when it comes to Software and USB Devices I have personally experienced a situation that did cause a SR 1 entry last year. Example: My wife has Sevier medical problems. When we travel I keep a USB Flash Drive on my key chain with her medical information installed in case of an emergence. The Medic Alert E-Health Key was a new device that came out that had bugs that needed resolved just as with iTunes 7.0. The short of the story is that the flash drive was conflicting with the System Restore Feature, which led to additional problems such as conflicts in the Add/Remove Utility. I could not properly unload the Uninstall .Dll files when trying to uninstall the flash drive itself using the Add/Remove Utility. During a conversation with a Microsoft Support tech I was informed that other unloading issues had also been identified in the Add/Remove Utility. I could be wrong but I think there is a patch available that would help with unloading issues while using the Add/Remove Utility. To keep an eye on any possible loading/unloading issues that I may have while using the Add/Remove Utility, I use the following program to determine if there any issue’s that I need to deal with: (30 Day Trial Program-Fully Functional)
    http://www.mikasalonen.com/remove/?remove40
    Program Name: Remove 4.0. All of the information you need to know about this program will be summarized in the provided link. If anything: USE IT !!!!
    NOTE: This SR 1 patch is only a temporary hot fix. They are suggesting that we wait until the next Windows XP service pack release that contains the hot fix.
    Article Id : 888402
    Last Review : June 01, 2006
    Revision : 1.5
    Also keep this in mind. The only time that you want to become concerned about the SR 1 issue is when you notice an increase in the number of SR 1 entries in Event viewer logs. If you are logging two (2) or more events then I would begin investigating the problem. Again, In my case the System Restore Feature was identified as the initial cause of conflict when the conflict first occurred when loading the USB Flash Drivers. So, if you suddenly notice this entry in the Event Viewer then you can pretty much bet that you are experiencing a USB issue that is conflicting with the System Restore Feature. But there is a Hot Fix available to temporarily resolve this issue as I have stated. Go back to the Microsoft link that was provided. When the page loads, in the search bar in the upper right hand corner of the page type in the following KB 888402. Be Advised – if you have to resort to this measure you will have to contact the Microsoft Support Team directly by phone to receive this patch.
    When you talk to the tech you will need to provide the following information: A brief description if the Event being generated in the Event Viewer as well as a brief description of the problem that you are having. Once the tech has verified the information he/she will e-mail the hot fix to you in a zip folder if I’m not mistaken.
    System and Third Party Drivers
    Drivers can be another source of conflict that can have a direct impact on how your system operates. I have already given you an example of this in the System Restore/USB Devices section. They can also cause unexpected stability issues. In addition to that malicious Root Kits and Trojans can download drivers on your hard drive without your knowledge further complicating matters. So, before I close this information out let me show you how we can quickly gather and display a listing of all drivers that are currently installed on you hard drive by using a very simple program. (This program will be a 15-day Trial program).
    Program Name: My Drivers 3.11
    With this program you will be able filter out all preinstalled drivers that came with the system at the time of purchase, thus exposing the remaining Third Party drivers and as well as the Unknowns. If you know what your doing I would take this time now and disable the drive(s) in question if removal procedures are deemed necessary once you have obtained the driver listing. My overall objective with this program is to immediately determine if there is anything out of the norm with the drivers overall.
    A download link is unavailable at this time. The web site appears to be under construction at this time.
    As a final step on this issue I suggest keeping an eye on the Device Manager for any sudden “Yellow Warning Symbols” appearing within the Device Manager Tree Structure.
    Print this information off and us it as a reference point. Any new helpful hints that I can think of will be posted as soon as I can squeeze the time in.
    Jblittlejohn
    Toshiba Satellite 1135/S155 Laptop
    Windows XP Home SP2
    Build 2600
    DSL Lite – 2Wire

    Oh, also want to add that the PC I'm currently using is:
    Windows Vista Home Premium Service Pack 2
    My other PC was:
    Windows 7 Ultimate
    My MacBook is:
    Max OSX 10.5.something (the last update available for it. .8 maybe? haha)
    Not sure if this stuff is important, but I thought I'd add it.

  • Airport cannot be turned on, after trying all work around solutions

    As with many others in this forum, I have been suffering from this problem since upgrading to 10.6. I have tried all suggestions in this forum, but the only "workable" way I found so far is to reboot my Macbook Pro. Usually it backs to work after one reboot, but does not work again the next time. Here is the log I see:
    ====Log Started====
    Sep 5 23:10:21 wukong kernel[0]: Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 20607: 0 == (RREG(pi->wlchw->osh, &pi->regs->maccontrol) & MCTLENMAC)
    Sep 5 23:10:21: --- last message repeated 1 time ---
    Sep 5 23:10:21 wukong kernel[0]: Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 47090: (readphyreg(pi, NPHY_RfseqStatus) & status_mask) == 0
    Sep 5 23:10:21: --- last message repeated 1 time ---
    Sep 5 23:10:21 wukong kernel[0]: Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 20607: 0 == (RREG(pi->wlchw->osh, &pi->regs->maccontrol) & MCTLENMAC)
    Sep 5 23:10:23: --- last message repeated 1 time ---
    Sep 5 23:10:23 wukong kernel[0]: Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 47090: (readphyreg(pi, NPHY_RfseqStatus) & status_mask) == 0
    Sep 5 23:10:23: --- last message repeated 1 time ---
    Sep 5 23:10:23 wukong kernel[0]: Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 20607: 0 == (RREG(pi->wlchw->osh, &pi->regs->maccontrol) & MCTLENMAC)
    Sep 5 23:10:23: --- last message repeated 1 time ---
    Sep 5 23:10:23 wukong kernel[0]: Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 47090: (readphyreg(pi, NPHY_RfseqStatus) & status_mask) == 0
    Sep 5 23:10:23: --- last message repeated 1 time ---
    Sep 5 23:10:23 wukong kernel[0]: Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 30702: (RREG(pi->wlchw->osh, &pi->regs->maccontrol) & MCTLENMAC) == 0
    Sep 5 23:10:23: --- last message repeated 1 time ---
    Sep 5 23:10:23 wukong kernel[0]: Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 3437: (RREG(wlchw->osh, &wlc_hw->regs->maccontrol) & MCTLENMAC) == 0
    Sep 5 23:10:23: --- last message repeated 1 time ---
    Sep 5 23:10:23 wukong kernel[0]: Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5318: !(mc & MCTLPSM_JMP0)
    Sep 5 23:10:23: --- last message repeated 1 time ---
    Sep 5 23:10:23 wukong kernel[0]: Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5319: !(mc & MCTLENMAC)
    Sep 5 23:10:23: --- last message repeated 1 time ---
    Sep 5 23:10:23 wukong kernel[0]: Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5327: !(mc & MCTLPSM_JMP0)
    Sep 5 23:10:23: --- last message repeated 1 time ---
    Sep 5 23:10:23 wukong kernel[0]: Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5332: !(mi & MI_MACSSPNDD)
    Sep 5 23:10:23: --- last message repeated 1 time ---
    Sep 5 23:10:23 wukong kernel[0]: AirPort: Link Down on en1. Reason 3 (Deauthenticated because station leaving).
    ====Log Ended====
    Hope it helps Apple engineers debug this problem and get it fixed in 10.6.1. It is very very annoying.

    Similar problem here, but for me it started sometime around 2 months ago (with 10.5.7 or 10.5.8).
    And it still happens with cleanly installed 10.6.
    My symptoms are:
    - AirPort is silently turned off mostly after waking up from sleep. (note that 'turned off' is different from 'no signal')
    - It does not always occur, but I cannot figure out the condition.
    - Once it happens, there is no way to turn it back on (adding new location, re-ordering network interfaces, etc. didn't work at all).
    - AirPort is usually back on after rebooting, but sometimes I need to reset SMC or PRAM to make it enabled again.
    And yes, it is very very annoying.
    Here's my log, FYI.
    09/09/10 23:43:22 kernel wl0: PSM microcode watchdog fired at 281 (seconds)
    09/09/10 23:43:22 kernel psmdebug 0x00ed80bb, phydebug 0x00000000, psm_brc 0x00000001
    09/09/10 23:43:22 kernel wepctl 0x00000300, pcmctl 0x00000300, pcmstat 0x00004000
    09/09/10 23:43:22 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 839: "PSM Watchdog" && 0
    09/09/10 23:43:22 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 839: "PSM Watchdog" && 0
    09/09/10 23:43:22 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:22 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:22 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:22 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:23 kernel s/wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:23 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:23 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:23 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:23 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:23 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:24 kernel s/wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:24 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:24 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:24 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:24 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:24 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:24 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:24 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:24 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:24 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:24 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:24 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:24 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:24 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:25 kernel /wl/sys/wlc.c", line 11750: wlcpscheck(wlc)
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 11750: wlcpscheck(wlc)
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:25 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:26 kernel rtDriverBrcm4311-410.91.20/src/wl/sys/wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:26 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:27 kernel s/wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:27 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:27 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:27 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:27 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:27 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:27 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:27 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:27 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:27 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:27 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:27 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:27 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:27 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:28 kernel s/wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:28 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:28 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:28 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:28 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:28 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:28 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:28 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:28 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:28 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:28 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:28 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:28 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:28 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:29 kernel s/wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:29 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:29 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:29 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:29 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:29 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:30 kernel s/wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:30 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:30 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:30 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:30 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:30 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:30 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:30 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:30 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:30 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:30 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:30 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:30 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:30 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:31 kernel s/wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:31 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:31 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:31 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:31 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:31 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:31 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:31 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:31 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:31 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:31 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:31 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:31 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:31 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:32 kernel s/wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:32 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:32 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:32 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:32 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:32 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:32 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:32 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:32 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:32 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:32 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:32 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:32 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:32 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:33 kernel s/wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:33 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:33 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:33 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:33 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:33 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:33 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:33 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:33 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:33 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:33 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:33 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:33 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:33 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:34 kernel d: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:34 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:35 kernel s/wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:35 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:36 kernel s/wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:36 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:37 kernel s/wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:37 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:37 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:37 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:37 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:37 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:37 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:37 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:37 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:37 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:37 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:37 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc.c", line 3301: res
    09/09/10 23:43:37 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:37 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 897: wlcpscheck(wlc)
    09/09/10 23:43:39 kernel line 15560: sicore_sflags(pi->wlchw->sih, 0, 0) & SISF_FCLKA
    09/09/10 23:43:39 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 15560: sicore_sflags(pi->wlchw->sih, 0, 0) & SISF_FCLKA
    09/09/10 23:43:39 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 47090: (readphyreg(pi, NPHY_RfseqStatus) & status_mask) == 0
    09/09/10 23:43:39 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 47090: (readphyreg(pi, NPHY_RfseqStatus) & status_mask) == 0
    09/09/10 23:43:39 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 47090: (readphyreg(pi, NPHY_RfseqStatus) & status_mask) == 0
    09/09/10 23:43:39 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 47090: (readphyreg(pi, NPHY_RfseqStatus) & status_mask) == 0
    09/09/10 23:43:39 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 20607: 0 == (RREG(pi->wlchw->osh, &pi->regs->maccontrol) & MCTLENMAC)
    09/09/10 23:43:39 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 20607: 0 == (RREG(pi->wlchw->osh, &pi->regs->maccontrol) & MCTLENMAC)
    09/09/10 23:43:40 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 47090: (readphyreg(pi, NPHY_RfseqStatus) & status_mask) == 0
    09/09/10 23:43:40 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 47090: (readphyreg(pi, NPHY_RfseqStatus) & status_mask) == 0
    09/09/10 23:43:40 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 20607: 0 == (RREG(pi->wlchw->osh, &pi->regs->maccontrol) & MCTLENMAC)
    09/09/10 23:43:40 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 20607: 0 == (RREG(pi->wlchw->osh, &pi->regs->maccontrol) & MCTLENMAC)
    09/09/10 23:43:40 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 47090: (readphyreg(pi, NPHY_RfseqStatus) & status_mask) == 0
    09/09/10 23:43:40 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 47090: (readphyreg(pi, NPHY_RfseqStatus) & status_mask) == 0
    09/09/10 23:43:40 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 20607: 0 == (RREG(pi->wlchw->osh, &pi->regs->maccontrol) & MCTLENMAC)
    09/09/10 23:43:40 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 20607: 0 == (RREG(pi->wlchw->osh, &pi->regs->maccontrol) & MCTLENMAC)
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 47090: (readphyreg(pi, NPHY_RfseqStatus) & status_mask) == 0
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 47090: (readphyreg(pi, NPHY_RfseqStatus) & status_mask) == 0
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 30702: (RREG(pi->wlchw->osh, &pi->regs->maccontrol) & MCTLENMAC) == 0
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_phy.c", line 30702: (RREG(pi->wlchw->osh, &pi->regs->maccontrol) & MCTLENMAC) == 0
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5318: !(mc & MCTLPSM_JMP0)
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5318: !(mc & MCTLPSM_JMP0)
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5319: !(mc & MCTLENMAC)
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5319: !(mc & MCTLENMAC)
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5327: !(mc & MCTLPSM_JMP0)
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5327: !(mc & MCTLPSM_JMP0)
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5332: !(mi & MI_MACSSPNDD)
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5332: !(mi & MI_MACSSPNDD)
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5318: !(mc & MCTLPSM_JMP0)
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5318: !(mc & MCTLPSM_JMP0)
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5319: !(mc & MCTLENMAC)
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5319: !(mc & MCTLENMAC)
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5327: !(mc & MCTLPSM_JMP0)
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5327: !(mc & MCTLPSM_JMP0)
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5332: !(mi & MI_MACSSPNDD)
    09/09/10 23:43:41 kernel Assertion failed: file "/SourceCache/AirPortDriverBrcm4311/AirPortDriverBrcm4311-410.91.20/src/wl/sys/ wlc_bmac.c", line 5332: !(mi & MI_MACSSPNDD)
    09/09/10 23:43:49 Apple80211 framework[91] Scan() error 82 (Device power is off)
    09/09/10 23:43:49 Apple80211 framework[91] __performScan() failed (82)
    09/09/10 23:44:01 Apple80211 framework[91] Scan() error 82 (Device power is off)
    09/09/10 23:44:01 Apple80211 framework[91] __performScan() failed (82)

  • Temporary work around app store problem

    Until apple fixes the problem you can still d/l apps if you can at least get into the app store. If you can, enter whatever app your looking for in the "search" box,,,if that then gives you a drop down menu click on something in that menu and it should take you to the apps,,,this is a round about way of doing it but it will work until apple figures out that many of us here can't access the apps the normal way.

    Some users report it's working now.
     Cheers, Tom

  • IOS 8.1.1 Spotlight not working (temporary work around)

    Spotlight for me is an important way to get to contacts and applications on my iPhone and iPad. With the latest iOS 8.1.1 release, the spotlight feature on my iPhone stopped working completely and the only way to get it to work was rebooting the phone. Even after that it only worked for half an hour (tops)!! My iPad on the other hand had no issues at all.
    After going through a lot of forums, I limited my spotlight search to contacts and applications and reboote my phone. The problem seems to have gone away and I can finally work my phone with ease.
    Give this a try until Apple get their act together and roll out iOS 8.1.2.
    P.S - Restarting your iPhone or your iPad is NECESSARY after you've limited your options in the spotlight menu.
    P.S.S - I'm not sure if this will work for those with the same issue on their iPads but it's worth a try

    Same issue, Spotlight not working as it did, on my iPhone 5S and iPad 3 after 8.1.1. Very frustrating, I'm beginning to think I should do as a Windows user and avoid updates because Apple's QA has really become terrible. Every release is full of bugs, way more so than in the past. I used to look forward to updates, not any more. Wow, sad. I've done a restore but the problem comes back, Apple needs to fix this issue and maybe take some of it's billions and invest back in quality. Please.

  • Shortly after loading,the latest version,downloaded and installed here 5/22/13, reports an error with ntdll.dll forcing a shutdown.  Apple's temporary work around works for me; launch  Itunes while first pressing  and holding CtrlShift keys ...

    This  startsitunes in it's own  "safe mode", allowing normal functions.

    By running in safe mode the plug-ins are not running. The issue may be caused by a plug-in.
    http://support.apple.com/kb/TS3430  gives instructions on how to manage/troubleshoot 3rd part plug-ins.
    Try the knowledge base and let us know.

  • New Q-10 User - Complaints -- Looking for Work-Arounds

    BB OS 10 has a business path (through enterprise activation) and a personal path – so if you are using enterprise activation for business, you need to make sure your employer has the BES10 feature or it will not work.  And without this feature, I sense it impacts use of the device in many ways.
    Q10 does not have a deactivation feature to prevent deleting email from Outlook when one deletes email from the BB.  Very inefficient – I have to go thru email twice – once on Outlook and once on BB.
    Upon set-up, all Outlook contacts did not interface to the BB.
    When I accept calendar invites on the BB show up on the BB calendar, it reads it as "personal path" (see #1 above) and does not show up on the business path to register on my Outlook calendar.  This causes false availability highlighted on Outlook.
    Replying to email and accepting calendar invites on the BB do not show an indication of response/acceptance on Outlook.  This is very confusing, as I have to personally recall what I’ve replied to on the BB before filing on Outlook.
    I'm guessing I will have more difficulties...but these are major inefficient issues for me. If anyone has "work around solutions" here, please let me know.

    Hello scottjones92660;
    Welcome to the forums and thank you for your question.
    In response to your inquiries I have included the following response for your perusal;
    “BB OS 10 has a business path (through enterprise activation) and a personal path – so if you are using enterprise activation for business, you need to make sure your employer has the BES10 feature or it will not work.  And without this feature, I sense it impacts use of the device in many ways.”
    The BlackBerry 10 devices utilize ActiveSync to communicate\sync with end user mailboxes. Although the BlackBerry Enterprise Service 10 does provide security to devices and will setup and separate a Work Perimeter in addition to the Personal Perimeter, devices can also be activated strictly to ActiveSync only.
    “Q10 does not have a deactivation feature to prevent deleting email from Outlook when one deletes email from the BB.  Very inefficient – I have to go thru email twice – once on Outlook and once on BB.
    Upon set-up, all Outlook contacts did not interface to the BB.”
    I am unsure as to your question as it seems contradictory to your above statement. You state the Q-10 does not have a feature to prevent two-way synchronization of mail, which is typical of ActiveSync activated devices. You go on to say that this is inefficient as you have to go through mail on the mail client and on the device.
    The device is utilizing ActiveSync synchronization, as such what is deleted on device or mail client, will sync with the other. If this is not the case and what is deleted on the device or mail client is not syncing, it is possible you may have an incomplete activation. This may also allude to the issue that all contacts from the mailbox Contact Parent Folder did not sync to the device.
    “When I accept calendar invites on the BB show up on the BB calendar, it reads it as "personal path" (see #1 above) and does not show up on the business path to register on my Outlook calendar.  This causes false availability highlighted on Outlook.”
    When a device is activated on the BlackBerry Enterprise Service 10, the device calendar can be accessed from the Personal Perimeter as well as the Work Perimeter.
    The Free\Busy feature with ActiveSync is availability starts in version 14.0 With Microsoft Exchange Server 2010.
    If calendar invites are sent to and accepted by the corporate email account on a device that is activated on a BlackBerry Enterprise Service 10, they will be visible on both Perimeters.
    The following is a link to the BlackBerry Enterprise Service 10 guides and documentation and Microsoft ActiveSync;
    BlackBerry Enterprise Server 10
    Microsoft ActiveSync FAQ;
    Let us know if you have any further questions regarding this specific request.
    MAD-VIKING

  • Work around for request scope for Listitems-working

    Hi finally I got some work around solution for Listitems working with request scope, if any suggesion welcome, below is the small code of jsp and bean.
    <h:selectOneMenu id="ownerListMenu" value="#{pc_trackingSearchPage.trackingSearchPageBean.selectedOwner}">
                                            <f:selectItems value="#{pc_trackingSearchPage.trackingSearchPageBean.ownerList}" />
                                       </h:selectOneMenu>
    I used onPageLoadBegin() and onPagePost(),
    first on PageLoad - I am loading the List from DB, its displaying perfect.,
    than on pagePost -> I am setting the value ->ownerList.add(new SelectItem(getOwnerListMenu().getSubmittedValue().toString(),getOwnerListMenu().getSubmittedValue().toString()));
    ------->here is the getOwnerListMenu method.
         public HtmlSelectOneMenu getOwnerListMenu() {
              if (ownerListMenu == null) {
                   ownerListMenu =
                        (HtmlSelectOneMenu) findComponentInRoot("ownerListMenu");
              return ownerListMenu;
    so this way the List will not be empty what ever the user selectes it will be their, as i am setting key and values as same, so in submit method,
    i am getting the selected keys and going back to backend getting results displaying on other page,
    --->this will work only if they don't need the list , if they want to display the list again, they have to load freshelly.
    I hope it will give some solution for request scope, if the data is huge and not to save on the session for navigation purpose.
    suggestions welcome.
    Thanks
    srikanth
    Message was edited by:
    srikanthg

    Apperently iTunes 11 is not affected (Apple stil makes iTunes11 for the 14 yr old Microsoft XP OS, but not for anything PPCs can run. Go figure)
    "Next door" to Steve was metaphoric, he lived in Los Altos, about 15 miles away, but he cast a big shadow!
    On 9.2.1/10.4.11 differences, some time in the past someone selected 'save file' and checked the box 'don't ask again' on your computers dialog box. That's why you're not given a choice wih the file downloads. I would think that selection should be able to be reversed.
    iTunes 9.2.1/OS10.4.11 puts those downloaded URLs into the Music Libary of iTunes, no matter if it's opened directly, or you click on the file on your desktop. You can create a new playlist, highlight the selection in the Music Libary, and drag it to your new playlist to keep alll the steaming URLs together. NOTE, this only creates an alias, the URL copied by iTunes must remain in the Music Libary. You can then delete the the files on the desktop, if you want. I did multiple stations this way in 9.2.1, they all show in either the new playlist created, or in the Music Libary, and remain after the desktop files are deleted and trash emptied.
    You can switch sations by double clicking them. Another note, all the URLs were all from vtune.
    I hope this helps.
    PS, I forgot how clunky Tiger is compared to Leopard...

  • Question mark not working, as well as others- can I work around by programming another key for this symbol

    The question mark-slash key, the semi-colon key, the eject key, don't work at all as a result of getting wet. Can I do a temporary work-around by assigning another key (like the f11 or f12) to use until I get a "proper" fix>(that's a q-mark...)

    Get the keyboard replaced is best, it's going to go eventually.

  • How do I work around incorrect capture scratch disk use estimates in FCP?

    Hi Everyone,
    I am trying to find a work around solution for FCP incorrectly estimating the space required on my capture scratch disk. I am using a Panasonic AJHD1400 to play back some DVCAM footage. I want to capture it 720x480 Anamorphic H264, via the firewire output on the deck. I am able to "free" capture the clip by hitting play on the deck and crash recording ("capture now") on the log and capture tool. From this process, I know the final captured file will be somewhere in the 3GB range, give or take. The clip is a little less than an hour long. I have 343 GB available on my scratch drive according to the information in the "Capture Settings" tab of the log and capture tool but according to the same info FCP thinks only 36.9 minutes of footage will fit on the disk. Consequently I can't log and capture the clip properly due to "insufficient disk space". What gives?
    Any suggestions and responses will be appreciated.
    Thanks in advance

    It isn't an Easy Setup per se. I modified the "generic capture" template in the capture preset editor to use DV video from the AJHD1400 as the "Digitizer" and set the "Compressor" to be h.264 at 100% quality.
    The whole point of the strange capture is for our sound editorial staff to edit to in pro tools. We don't have networked video storage for our audio department. If i capture in DV, the files are still like 20GB. using my "custom" settings I get a reasonably sized file that looks decent enough for the editors in a file that is small enough to fit on a data dvd if need be. I save rendering time as well.

Maybe you are looking for

  • Remedial rman question - how to connect to db

    Hi. I need to start making some tests with rman, with the hope of maybe next year presenting it as an option for our data managment here. First, I need to connect to my test database, but Im already having some problems: I am following the documentat

  • BAPI or Conversion Program for Head Office/Branch functionality

    We are shifting our Vendors to Head Office/Branch functionality.  Our ordering vendor now becomes a Branch.  We need to transfer any open items left in the Ordering vendor account, and move them to the new Head Office account. Has somebody done this

  • Error Bookmark not defined?

    Hi, How do I remove "ERROR! Bookmark not defined" from the Table of Contents after converting a Word document to PDF? Also the page number are being corrected with updates. Thanks 

  • E 90 - office, skype & downlowad support

    I have been using the Compact IPAQ PDA. It communicates seamlessly with independent service provider, "IPocket nformant" and office suite (word, excel spreadsheet). I can easily read off the downloaded bible (Olive tree bible software). The service c

  • Mail application opens to default inbox

    When I open the mail applicaiton, ratehr than opening up to the main screen where all my inboxes and accounts reside, the app opens to my default account inbox.  If it does open up to the main mail screen, the mail app crashes right away. I was hopin