On Fri, Oct 10, 2014 at 9:19 PM, Ken Stephens <k...@cad2cam.com> wrote:
> Denis Heidtmann wrote:
>> "asus_wmi: Error removing rfkill notify handler /_sb.pcio.pop5
>> repeat ...pop6
>> repeat ...pop7
>>
>> could not write bytes: Broken Pipe"
>>
>> I have kernel 3.13.0 Ubuntu 12.04
>>
>> Various function buttons fail to work
>>
>> Googling gave me lots of very technical stuff that was way beyond my pay 
>> grade.
>>
>> Does anybody here have a clue as to what the issue is, and possibly a
>> way that a mortal can resolve it?  It is not urgent, as the machine is
>> still usable.
>>
>> Thanks,
>> -Denis
>>
> Dennis,
>
>  From the driver for the wifi card:
>
> 696  
> <http://lxr.free-electrons.com/source/drivers/platform/x86/asus-wmi.c#L696>  
> static voidasus_unregister_rfkill_notifier  
> <http://lxr.free-electrons.com/ident?i=asus_unregister_rfkill_notifier>(structasus_wmi
>   <http://lxr.free-electrons.com/ident?i=asus_wmi>  *asus, char *node  
> <http://lxr.free-electrons.com/ident?i=node>)
> 697  
> <http://lxr.free-electrons.com/source/drivers/platform/x86/asus-wmi.c#L697>  {
> 698  
> <http://lxr.free-electrons.com/source/drivers/platform/x86/asus-wmi.c#L698>   
>        acpi_status  <http://lxr.free-electrons.com/ident?i=acpi_status>  
> status  <http://lxr.free-electrons.com/ident?i=status>  =AE_OK  
> <http://lxr.free-electrons.com/ident?i=AE_OK>;
> 699  
> <http://lxr.free-electrons.com/source/drivers/platform/x86/asus-wmi.c#L699>   
>        acpi_handle  <http://lxr.free-electrons.com/ident?i=acpi_handle>  
> handle  <http://lxr.free-electrons.com/ident?i=handle>;
> 700  
> <http://lxr.free-electrons.com/source/drivers/platform/x86/asus-wmi.c#L700>
> 701  
> <http://lxr.free-electrons.com/source/drivers/platform/x86/asus-wmi.c#L701>   
>        status  <http://lxr.free-electrons.com/ident?i=status>  
> =acpi_get_handle  
> <http://lxr.free-electrons.com/ident?i=acpi_get_handle>(NULL  
> <http://lxr.free-electrons.com/ident?i=NULL>,node  
> <http://lxr.free-electrons.com/ident?i=node>, &handle  
> <http://lxr.free-electrons.com/ident?i=handle>);
> 702  
> <http://lxr.free-electrons.com/source/drivers/platform/x86/asus-wmi.c#L702>
> 703  
> <http://lxr.free-electrons.com/source/drivers/platform/x86/asus-wmi.c#L703>   
>        if (ACPI_SUCCESS  
> <http://lxr.free-electrons.com/ident?i=ACPI_SUCCESS>(status  
> <http://lxr.free-electrons.com/ident?i=status>)) {
> 704  
> <http://lxr.free-electrons.com/source/drivers/platform/x86/asus-wmi.c#L704>   
>                status  <http://lxr.free-electrons.com/ident?i=status>  
> =acpi_remove_notify_handler  
> <http://lxr.free-electrons.com/ident?i=acpi_remove_notify_handler>(handle  
> <http://lxr.free-electrons.com/ident?i=handle>,
> 705  
> <http://lxr.free-electrons.com/source/drivers/platform/x86/asus-wmi.c#L705>   
>                                                    ACPI_SYSTEM_NOTIFY  
> <http://lxr.free-electrons.com/ident?i=ACPI_SYSTEM_NOTIFY>,
> 706  
> <http://lxr.free-electrons.com/source/drivers/platform/x86/asus-wmi.c#L706>   
>                                                    asus_rfkill_notify  
> <http://lxr.free-electrons.com/ident?i=asus_rfkill_notify>);
> 707  
> <http://lxr.free-electrons.com/source/drivers/platform/x86/asus-wmi.c#L707>   
>                if (ACPI_FAILURE  
> <http://lxr.free-electrons.com/ident?i=ACPI_FAILURE>(status  
> <http://lxr.free-electrons.com/ident?i=status>))
> 708  
> <http://lxr.free-electrons.com/source/drivers/platform/x86/asus-wmi.c#L708>   
>                        pr_err  
> <http://lxr.free-electrons.com/ident?i=pr_err>(/"Error removing rfkill notify 
> handler %s\n"/,
> 709  
> <http://lxr.free-electrons.com/source/drivers/platform/x86/asus-wmi.c#L709>   
>                               node  
> <http://lxr.free-electrons.com/ident?i=node>);
> 710  
> <http://lxr.free-electrons.com/source/drivers/platform/x86/asus-wmi.c#L710>   
>        }
> 711  
> <http://lxr.free-electrons.com/source/drivers/platform/x86/asus-wmi.c#L711>  }
>
> So it looks like it was fine for the 0 through 4 sockets, but fails on the 
> 5th, 6th, and 7th socket.  Which may
> be just chaff and can be ignored.
>
>
> Ken
Thanks for looking into this.  But there are other symptoms which
googling tells me are associated with the error(s): Some of the
function controls no longer work, specifically the screen brightness.
This is true for my machine.

To give you a sense of how far I am away from understanding all this,
what is a socket?

-Denis
_______________________________________________
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Reply via email to