unable to handle kernel NULL pointer dereference...
Hi! After managing to make NM playing nicely with my Option Icon 225 usb-stick, I experienced few crashes yesterday and one of those are captured in this log snippet: -- BUG: unable to handle kernel NULL pointer dereference at 0020 IP: [] debug_mutex_wake_waiter+0x44/0x160 PGD 4626a067 PUD 4626b067 PMD 0 Oops: [#1] PREEMPT SMP last sysfs file: /sys/devices/pci:00/:00:13.0/usb2/2-3/2-3:1.0/net/hso0/statistics/collisions CPU 0 Modules linked in: radeon drm ipv6 sco bridge stp llc bnep l2cap bluetooth adm1021 hso rfkill usb_storage joydev serio_raw pcspkr psmouse ohci1394 ssb pcmcia yenta_socket rsrc_nonstatic ieee1394 pcmcia_core wmi container video output k8temp sg i2c_piix4 i2c_core shpchp pci_hotplug evdev thermal fan snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device button battery ac vboxdrv snd_atiixp snd_ac97_codec snd_pcm_oss snd_pcm snd_timer snd_page_alloc snd_mixer_oss snd soundcore ac97_bus md_mod cpufreq_ondemand powernow_k8 freq_table processor tg3 libphy rtc_cmos rtc_core rtc_lib ext3 jbd mbcache dm_mod sr_mod cdrom ohci_hcd sd_mod ehci_hcd usbcore ata_generic pata_atiixp libata scsi_mod Pid: 5808, comm: NetworkManager Tainted: G M 2.6.29-ARCH #1 HP Compaq nx6125 (PY417EA#AKN) RIP: 0010:[] [] debug_mutex_wake_waiter+0x44/0x160 RSP: 0018:88004620ddc8 EFLAGS: 00010017 RAX: 880043e6fc78 RBX: RCX: RDX: 0100 RSI: RDI: 880043e6fc74 RBP: 880043e6fc70 R08: R09: R10: R11: R12: 0246 R13: R14: 0008 R15: FS: 7f9926236740() GS:8067a000() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0020 CR3: 46ba7000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process NetworkManager (pid: 5808, threadinfo 88004620c000, task 880046155200) Stack: 880043e6f09c 880043e6fc70 880043e6fc74 804b2896 804b4775 880046052800 88002cca6300 88002bebac08 803c4812 0001 Call Trace: [] ? __mutex_unlock_slowpath+0x96/0x180 [] ? _spin_lock+0x15/0x20 [] ? tty_release_dev+0x162/0x5a0 [] ? sys_sendto+0x11d/0x180 [] ? vfs_ioctl+0x1d/0xb0 [] ? tty_release+0x11/0x20 [] ? __fput+0xc2/0x210 [] ? filp_close+0x5b/0x90 [] ? sys_close+0xb4/0x120 [] ? system_call_fastpath+0x16/0x1b Code: 89 fd 45 85 c9 75 36 48 8d 7f 04 e8 07 04 fc ff 90 85 c0 74 7c 44 8b 05 4b 97 42 00 45 85 c0 75 1c 48 8d 45 08 48 39 45 08 74 42 <48> 3b 5b 20 75 1b 48 3b 1b 0f 1f 00 0f 84 8f 00 00 00 48 8b 5c RIP [] debug_mutex_wake_waiter+0x44/0x160 RSP CR2: 0020 ---[ end trace 80249a4d042672e9 ]--- Is it of any help to NM-devs? Sincerely, Gour pgp2A7fvxTv3k.pgp Description: PGP signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm 0.7.1 3g regression
>>>>> "Gour" == Gour writes: >>>>> "Dan" == Dan Williams writes: Dan> HAL property. You have two options: Dan> 2) Or, install the attached file to Dan> /usr/share/hal/fdi/information/10freedesktop/01-deprecated-keys.fdi Gour> For now, I went with the 2nd one... Dan> That should make things work again. Gour> It seems there is some progress, but I'm still writing this post Gour> using hsoconnect :-/ Just to inform the list that I solved my problem... Browsing the forums at http://pharscape.org/ led me to the following link: https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/368325/ where the workaround for my 3g modem is mentioned, i.e. since there is no use of username and password (only PIN & APN) with my mobile ISP, after putting some dummy values in, NM is connecting nicely now - I'm writing this reply via NM-manged connection :-D However, it would be nice if NM could manage it without dummy values as well. ;) Sincerely, Gour -- Gour | Zagreb, Croatia | GPG key: C6E7162D pgpT6aXb377dP.pgp Description: PGP signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm 0.7.1 3g regression
>>>>> "Dan" == Dan Williams writes: Dan> HAL property. You have two options: Dan> 2) Or, install the attached file to Dan> /usr/share/hal/fdi/information/10freedesktop/01-deprecated-keys.fdi For now, I went with the 2nd one... Dan> That should make things work again. It seems there is some progress, but I'm still writing this post using hsoconnect :-/ Here is the log snippet: May 14 07:23:14 nitai NetworkManager: (ttyHS0): device state change: 3 -> 4 May 14 07:23:14 nitai NetworkManager: Activation (ttyHS0) Stage 1 of 5 (Device Prepare) scheduled... May 14 07:23:14 nitai NetworkManager: Activation (ttyHS0) Stage 1 of 5 (Device Prepare) started... May 14 07:23:14 nitai NetworkManager: [1242278594.688179] nm_serial_device_open(): (ttyHS0) opening device... May 14 07:23:14 nitai NetworkManager: Activation (ttyHS0) Stage 1 of 5 (Device Prepare) complete. May 14 07:23:15 nitai NetworkManager: (ttyHS0): powering up... May 14 07:23:17 nitai NetworkManager: Searching for a network... May 14 07:23:18 nitai NetworkManager: Registered on Home network May 14 07:23:18 nitai NetworkManager: Associated with network: +COPS: 0,0,"T-Mobile HR",2 May 14 07:23:18 nitai NetworkManager: Activation (ttyHS0) Stage 2 of 5 (Device Configure) scheduled... May 14 07:23:18 nitai NetworkManager: Activation (ttyHS0) Stage 2 of 5 (Device Configure) starting... May 14 07:23:18 nitai NetworkManager: (ttyHS0): device state change: 4 -> 5 May 14 07:23:18 nitai NetworkManager: Activation (ttyHS0) Stage 2 of 5 (Device Configure) complete. May 14 07:23:18 nitai NetworkManager: hso_auth_done(): Authentication failed May 14 07:23:18 nitai NetworkManager: (ttyHS0): device state change: 5 -> 9 May 14 07:23:18 nitai NetworkManager: [1242278598.235438] nm_serial_device_close(): Closing device 'ttyHS0' May 14 07:23:18 nitai NetworkManager: Marking connection 'T-mobile' invalid. May 14 07:23:18 nitai NetworkManager: Activation (ttyHS0) failed. May 14 07:23:18 nitai NetworkManager: (ttyHS0): device state change: 9 -> 3 May 14 07:23:18 nitai NetworkManager: (ttyHS0): deactivating device (reason: 0). May 14 07:23:18 nitai NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed May 14 07:23:18 nitai NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed I've entered the same login details (APN only, 'cause user/password is not used) in NM's dialog, but no luck. :( Any idea? Sincerely, Gour -- Gour (Gmail) | Zagreb, Croatia | GPG key: 9AA2B054 --- pgps3LqUBn9IL.pgp Description: PGP signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm 0.7.1 3g regression
>>>>> "Dan" == Dan Williams writes: Dan> You'll probably want to use NM 0.7.1, not 0.7.0. I've tried with 0.7.1, but with it I get: May 12 11:13:58 nitai NetworkManager: (ttyHS2): ignoring due to lack of mobile broadband capabilties May 12 11:13:58 nitai NetworkManager: (ttyHS1): found serial port (udev:GSM hal:GSM) May 12 11:13:58 nitai NetworkManager: (ttyHS0): found serial port (udev:GSM hal:GSM) May 12 11:13:58 nitai NetworkManager: new_modem_device(): couldn't find HSO modem network device. Sincerely, Gour -- Gour | Zagreb, Croatia | GPG key: C6E7162D pgprFLn7eB3FI.pgp Description: PGP signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm 0.7.1 3g regression
>>>>> "Sipos" == Sipos Ferenc writes: Sipos> Hi! I'm using arch linux, kernel 2.6.29, option icon 225 3g Sipos> modem, I've compiled 0.7.0.99, 0.7.0.100, 0.7.1 from sources , Sipos> but with the later, nm can't find the modem, attached is nm Sipos> daemon log: Hi, I've the same problem (on Archlinux x86_64) with my Icon 225 - hsoconnect works nicely but since 3g modem is my only internet option at the moment, I'd like to replace it with NM. Any workaround for the above problem? I also cannot make it work with 0.7.0, here is the snippet from the log: [...] May 12 18:15:46 nitai NetworkManager: ttyHS0: driver is 'hso'. May 12 18:15:46 nitai NetworkManager: [1242144946.246867] setup_monitor_device(): No monitoring udi provided May 12 18:15:46 nitai NetworkManager: Found new Modem device 'ttyHS0'. May 12 18:15:46 nitai NetworkManager: (ttyHS0): exported as /org/freedesktop/Hal/devices/usb_device_af0_6971_Serial_Number_if0_serial_unknown_0 May 12 18:15:46 nitai NetworkManager: ttyHS1: driver is 'hso'. May 12 18:15:46 nitai NetworkManager: [1242144946.456811] setup_monitor_device(): No monitoring udi provided May 12 18:15:46 nitai NetworkManager: Found new Modem device 'ttyHS1'. May 12 18:15:46 nitai NetworkManager: (ttyHS1): exported as /org/freedesktop/Hal/devices/usb_device_af0_6971_Serial_Number_if0_serial_unknown_1 May 12 18:15:50 nitai NetworkManager: (ttyHS0): device state change: 1 -> 2 May 12 18:15:50 nitai NetworkManager: (ttyHS0): deactivating device (reason: 2). May 12 18:15:50 nitai NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed May 12 18:15:50 nitai NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed May 12 18:15:50 nitai NetworkManager: (ttyHS0): device state change: 2 -> 3 May 12 18:15:50 nitai NetworkManager: (ttyHS1): device state change: 1 -> 2 May 12 18:15:50 nitai NetworkManager: (ttyHS1): deactivating device (reason: 2). May 12 18:15:50 nitai NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed May 12 18:15:50 nitai NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed May 12 18:15:50 nitai NetworkManager: (ttyHS1): device state change: 2 -> 3 [...] Any hint? Sincerely, Gour Sipos> Apr 22 22:50:26 leonidas NetworkManager: (ttyHS0): found Sipos> serial port (udev:GSM hal:GSM) Apr 22 22:50:26 leonidas Sipos> NetworkManager: new_modem_device(): couldn't find HSO Sipos> modem network device. Apr 22 22:50:26 leonidas NetworkManager: Sipos> (ttyHS1): found serial port (udev:GSM hal:GSM) Apr 22 Sipos> 22:50:32 leonidas NetworkManager: (ttyHS2): ignoring due Sipos> to lack of mobile broadband capabilties Sipos> The hso driver is the same, hal, udev is the same, nothing is Sipos> changed except nm, with nm 0.7.0.100 and above the modem is Sipos> recognised and connects fine with nm-applet. Sipos> Any help appreciated. Sipos> Thx Sipos> Ferenc ___ Sipos> NetworkManager-list mailing list NetworkManager-list@gnome.org Sipos> http://mail.gnome.org/mailman/listinfo/networkmanager-list -- Gour | Zagreb, Croatia | GPG key: C6E7162D pgptI7HFjDxGI.pgp Description: PGP signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: timeout when connecting
On Thu, 2006-03-23 at 02:15 -0600, Steev Klimaszewski wrote: > You could also try > > http://madwifi.org/attachment/ticket/462/wext19_060322.patch I tried the patch and have few issues: a) the patch is missing WPA2 capabilities and NM reported that my hardware do not support WPA2. I added IW_ENC_CAPA_WPA2 to the patch (madwifi-r1482) but then NM could not connect to the wpa_supplicant :-( > Maybe the patch will work for you and your needs, and you will be able > to travel in comfort :) So, atm, not-so-perfect is better than nothing and I'm downgrading back to r1475 & enc_capa patch :-) Sincerely, Gour ps. I'm sorry for not having enough time to do more testing & proividing better debug reports (logs). signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: timeout when connecting
On Thu, 2006-03-23 at 02:15 -0600, Steev Klimaszewski wrote: Hi Steev! > You could also try > > http://madwifi.org/attachment/ticket/462/wext19_060322.patch Thanks a lot. > this is a stab at attempting to fix this (I saw it on the > madwifi-devel mailing list, I haven't tested it myself, as I haven't > seen my tester (trying to convince him to come over tomorrow) :-) > Maybe the patch will work for you and your needs, and you will be able > to travel in comfort :) Well, if it does not break anything...in any case I'll give it a try. Sincerely, Gour signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: timeout when connecting
On Wed, 2006-03-22 at 21:57 +0100, Luka Renko wrote: > I think this is know issue with madwifi drivers: NM does scans also > when conected and madwifi driver cannot perform such scan in > background, therefore it disconnects current connection to perform > scan. Huh...this is certainly explaining the issue. Thank you. > Not sure if such scans can be turned off. > Well, considering I'm going to travel in a few days, it looks it is something one has to learn to live with :-) Sincerely, Gour signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: timeout when connecting
On Wed, 2006-03-22 at 11:02 -0300, Cesar Cardoso wrote: > Hm, that's a difference here. I went back to wpa_supplicant 0.4.8. I'm with wpa_supplicant-0.5.2 and now everything works except that NM drops connection from time to time although plain wpa was very stable & robust. Sincerely, Gour signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: timeout when connecting
On Wed, 2006-03-22 at 09:50 +0100, Gour wrote: > Any idea? On #networkmanager I got a help and applied the following patch: http://cvs.fedora.redhat.com/viewcvs/*checkout*/devel/NetworkManager/special-case-madwifi.patch?rev=1.1 Now it works :-) but NM quickly drops connection :-( > Sincerely, > Gour signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: timeout when connecting
:wpa_supplicant(14495): EAPOL: External notification - portControl=Auto NetworkManager:wpa_supplicant(14495): Wireless event: cmd=0x8b06 len=12 ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 6 value 0x1 - ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 5 value 0x1 - ioctl[SIOCSIWENCODE]: Invalid argument ioctl[SIOCSIWGENIE]: Operation not supported ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 0 value 0x4 - ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 1 value 0x8 - ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 2 value 0x8 - ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 3 value 0x2 - ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 10 value 0x1 - ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 8 value 0x0 - NetworkManager: Activation (ath0/wireless): association took too long (>20s), failing activation. NetworkManager:Activation (ath0) failure scheduled... NetworkManager:Activation (ath0) failed for access point (gaura) NetworkManager:Activation (ath0) failed. NetworkManager:Deactivating device ath0. sendmsg(CTRL_IFACE monitor): No such file or directory sendmsg(CTRL_IFACE monitor): No such file or directory ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 7 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 5 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 4 value 0x0 - Any idea? Sincerely, Gour signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
timeout when connecting
(13840): EAPOL: External notification - EAP fail=0 NetworkManager:wpa_supplicant(13840): EAPOL: External notification - portControl=Auto ioctl[SIOCSIWSCAN]: Invalid argument ioctl[SIOCSIWSCAN]: Invalid argument NetworkManager:Activation (ath0/wireless): association took too long (>20s), failing activation. NetworkManager:Activation (ath0) failure scheduled... NetworkManager:Activation (ath0) failed for access point (gaura) NetworkManager:Activation (ath0) failed. NetworkManager:Deactivating device ath0. sendmsg(CTRL_IFACE monitor): No such file or directory NetworkManager:SWITCH: no current connection, found better connection 'eth0'. NetworkManager:Will activate connection 'eth0'. On #madwifi I got info that, depending on the setup, madwifi-ng can take up to 30s to associate which is more then the present limit. Any idea how to solve it? (I saw a timeout-patch for 0.5.1) but it is too complicated to apply it on 0.6.0 for myself considering other patches already applied.) NM handles wired eth0 without any problem. I'd really like to have NM working for my next travelling. Please, help... Sincerely, Gour ps. Any IRC #channel where one can get more help (besides #networkmanager which is not very populated? signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
