[Bug 650914] New: Backtrace on dial up network via mobile phone (rfcomm via bluetooth) after update to latest kernel
https://bugzilla.novell.com/show_bug.cgi?id=650914 https://bugzilla.novell.com/show_bug.cgi?id=650914#c0 Summary: Backtrace on dial up network via mobile phone (rfcomm via bluetooth) after update to latest kernel Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: hmuelle@novell.com QAContact: qa@suse.de CC: meissner@novell.com Found By: Community User Blocker: --- Created an attachment (id=398343) --> (http://bugzilla.novell.com/attachment.cgi?id=398343) Messages including backtrace I get a backtrace on dial up network via mobile (using DUP, rfcomm via bluetooth) instead of a working connection. Backtrace is triggered by an NULL-Pointer deference as far as I can see, which happens already in wvdial. Connection is handled by script, setting up bluetooth connection and starting wvdial afterwards --------------------------------------------------------------------- # config section BLUEZID="<secret>" # after suspend/resume cycle bluetooth might be off echo enable > /proc/acpi/ibm/bluetooth sleep 2 # Channel for dial up network via bluetooth might change on moble restart, set it each time # release all rfcoom devices (I just use one) rfcomm release all # get current active dialup network channel RFCHANNEL=`sdptool browse $BLUEZID | grep -A4 "Dialup Networking" | awk '$1 == "Channel:" {print $2}'` # informational echo echo Channel is: $RFCHANNEL # bind rfcomm0 to channel and device rfcomm bind rfcomm0 $BLUEZID $RFCHANNEL # check if all gone right - JFI rfcomm # Finally dial in wvdial umts --------------------------------------------------------------------- Find attached the relevant part of /var/log/message including the backtrace -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=650914
https://bugzilla.novell.com/show_bug.cgi?id=650914#c1
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=650914
https://bugzilla.novell.com/show_bug.cgi?id=650914#c2
--- Comment #2 from Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=650914
https://bugzilla.novell.com/show_bug.cgi?id=650914#c3
Harald Mueller-Ney
What was the previous kernel which worked for you?
It worke with the kernel I had installed before: kernel-desktop-2.6.34.7-0.4.1.x86_64.rpm I will now install this kernel again in parallel and run a test to be sure the connection works. Comment follows. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=650914
https://bugzilla.novell.com/show_bug.cgi?id=650914#c4
Harald Mueller-Ney
https://bugzilla.novell.com/show_bug.cgi?id=650914
https://bugzilla.novell.com/show_bug.cgi?id=650914#c5
Jiri Slaby
It works, I sending this via my UMTS connection.
uname say::
... 2.6.34.7-0.4-desktop #1 SMP PREEMPT 2010-10-07 19:07:51 +0200 x86_64 x86_64 x86_64 GNU/Linux
Hmm, this is quite strange, as the main updates between 0.4 and 0.5 are xen changes and one isdn patch. Could you attach lsmod output? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=650914
https://bugzilla.novell.com/show_bug.cgi?id=650914#c6
Harald Mueller-Ney
participants (1)
-
bugzilla_noreply＠novell.com