[Bug 221328] New: Starting IRDA causes kernel Oops
https://bugzilla.novell.com/show_bug.cgi?id=221328 Summary: Starting IRDA causes kernel Oops Product: openSUSE 10.2 Version: Beta 2 plus Platform: Other OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: jreuter@novell.com QAContact: qa@suse.de Running /etc/init.d/irda causes all network connections to hang. No IRDA interface is plugged in, the IRDA configuration was created with the YaST2 IRDA module of 10.1. This is the oops from /var/log/messages: Nov 15 16:41:10 lamarr irattach: executing: 'echo lamarr > /proc/sys/net/irda/devname' Nov 15 16:41:10 lamarr irattach: executing: 'echo 1 > /proc/sys/net/irda/discovery' Nov 15 16:41:10 lamarr irattach: Starting device irda0 Nov 15 16:41:10 lamarr kernel: skb_under_panic: text:f998d000 len:3 put:2 head:dfc18800 data:dfc187fe tail:dfc18801 end:dfc18880 dev:<NULL> Nov 15 16:41:10 lamarr kernel: ------------[ cut here ]------------ Nov 15 16:41:10 lamarr kernel: kernel BUG at net/core/skbuff.c:111! Nov 15 16:41:10 lamarr kernel: invalid opcode: 0000 [#1] Nov 15 16:41:10 lamarr kernel: SMP Nov 15 16:41:10 lamarr kernel: last sysfs file: /class/net/irda0/ifindex Nov 15 16:41:10 lamarr kernel: Modules linked in: irtty_sir sir_dev ircomm_tty ircomm irda crc_ccitt deflate zlib_deflate twofish serpent aes blowfish des sha256 sha1 md5 crypto_null af_key ipv6 eeprom lm63 hwmon snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device button battery ac acpi_cpufreq speedstep_lib fre q_table loop dm_mod usbhid ide_cd cdrom e1000 i2c_i801 i2c_core snd_intel8x0 i8xx_tco snd_ac97_codec snd_ac97_bus uhci_hcd ehci_hcd snd_pcm snd_timer snd s oundcore snd_page_alloc intel_agp usbcore shpchp agpgart pci_hotplug parport_pc lp parport reiserfs edd sg fan ata_piix libata piix thermal processor sd_mo d scsi_mod ide_disk ide_core Nov 15 16:41:10 lamarr kernel: CPU: 0 Nov 15 16:41:10 lamarr kernel: EIP: 0060:[<c024f562>] Tainted: G U VLI Nov 15 16:41:10 lamarr kernel: EFLAGS: 00010296 (2.6.18.2-11-default #1) Nov 15 16:41:10 lamarr kernel: EIP is at skb_under_panic+0x5e/0x6c Nov 15 16:41:10 lamarr kernel: eax: 00000070 ebx: f6d8f080 ecx: 00000086 edx: 00000000 Nov 15 16:41:10 lamarr kernel: esi: 00000002 edi: 00000010 ebp: dfc18480 esp: f6eede54 Nov 15 16:41:10 lamarr kernel: ds: 007b es: 007b ss: 0068 Nov 15 16:41:10 lamarr kernel: Process irattach (pid: 4484, ti=f6eec000 task=f74dc2b0 task.ti=f6eec000) Nov 15 16:41:10 lamarr kernel: Stack: c02dec80 f998d000 00000003 00000002 dfc18800 dfc187fe dfc18801 dfc18880 Nov 15 16:41:10 lamarr kernel: c02cd3a6 f6efb9c0 f6d8f080 f998d005 dfc18400 f6d8f080 f9992ed1 00004000 Nov 15 16:41:10 lamarr kernel: f6efc800 f6f2b800 f99066a0 00000000 f9905379 00000246 f6d8f680 00000880 Nov 15 16:41:10 lamarr kernel: Call Trace: Nov 15 16:41:10 lamarr kernel: [<f998d005>] irlmp_data_request+0x30/0x4c [irda] Nov 15 16:41:10 lamarr kernel: [<f9992ed1>] irttp_run_rx_queue+0x1a9/0x1bc [irda] Nov 15 16:41:10 lamarr kernel: [<f9905379>] irtty_start_dev+0x48/0x90 [irtty_sir] Nov 15 16:41:10 lamarr kernel: [<f996f443>] sirdev_open+0x134/0x1e1 [sir_dev] Nov 15 16:41:10 lamarr kernel: [<c0254f17>] dev_open+0x2b/0x62 Nov 15 16:41:10 lamarr kernel: [<c0253900>] dev_change_flags+0x46/0xe3 Nov 15 16:41:10 lamarr kernel: [<c02552e7>] dev_ioctl+0x399/0x462 Nov 15 16:41:10 lamarr kernel: [<c017548f>] do_ioctl+0x1f/0x63 Nov 15 16:41:10 lamarr kernel: [<c017571d>] vfs_ioctl+0x24a/0x25c Nov 15 16:41:10 lamarr kernel: [<c017577b>] sys_ioctl+0x4c/0x65 Nov 15 16:41:10 lamarr kernel: [<c0103d5d>] sysenter_past_esp+0x56/0x79 Nov 15 16:41:10 lamarr kernel: DWARF2 unwinder stuck at sysenter_past_esp+0x56/0x79 Nov 15 16:41:10 lamarr kernel: Leftover inexact backtrace: Nov 15 16:41:10 lamarr kernel: Code: c7 04 24 80 ec 2d c0 89 44 24 18 8b 83 a0 00 00 00 89 44 24 14 8b 83 9c 00 00 00 89 44 24 10 8b 43 60 89 44 24 08 e8 9 2 17 ed ff <0f> 0b 6f 00 19 ec 2d c0 83 c4 24 5b 5e c3 56 89 d6 53 89 c3 83 Nov 15 16:41:10 lamarr kernel: EIP: [<c024f562>] skb_under_panic+0x5e/0x6c SS:ESP 0068:f6eede54 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=221328 ------- Comment #1 from jreuter@novell.com 2006-11-15 09:06 MST ------- Created an attachment (id=105439) --> (https://bugzilla.novell.com/attachment.cgi?id=105439&action=view) IRDA configuration as written by YaST -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=221328 pavel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Normal Status|NEW |ASSIGNED ------- Comment #3 from pavel@novell.com 2006-11-15 17:12 MST ------- Someone is running irattach, why if there's no irda interface? Can you reproduce it on untainted kernel? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=221328 ------- Comment #4 from jreuter@novell.com 2006-11-16 02:37 MST ------- Yes, I can. The taint flag comes with the sensors modules (lm63, hwmon), the oops happens even if I start the system without them. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=221328 ------- Comment #5 from pavel@novell.com 2006-11-16 03:10 MST ------- Can you try to find a command which causes the oops? It looks like you are running irattach -- that is weird given that you should have no irda interfaces. Aha:# Currently the UART (SIR) mode is supported in the normal configuration. The # variable IRDA_PORT sets the used serial port. Have a look at your BIOS-Setup, # to find out which is correct. # # If you have a supported FIR chipset, specify the name of the corresponding # kernel module in IRDA_PORT, e.g. IRDA_PORT="toshoboe". FIR must be enabled in # the BIOS setup first. Sometimes you additionally have to disable the serial # port, which would be used in SIR mode via 'setserial /dev/ttyS<x> uart none' # IRDA_PORT="/dev/ircomm0" But this claims you are running irda on ircomm; no wonder it breaks. Who put ircomm there and why? (Plus error handling should be improved, but as noone maintains irda...) -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=221328 ------- Comment #6 from jreuter@novell.com 2006-11-16 05:24 MST ------- Woops, wrong configuration on my side -- don't remember exactly when I set that, but it has been there on a different machine at least since SL 9.3 without causing any issues. Anyway, it shouldn't oops and destroy network connectivity. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=221328 pavel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Minor ------- Comment #7 from pavel@novell.com 2006-11-16 07:45 MST ------- No, it should not oops. Can you reproduce it on vanilla kernel, then submit it to bugzilla.kernel.org? Perhaps there's someone still working on IrDA. Or you can just use git bisect to find the offending patch. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=221328 pavel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX ------- Comment #8 from pavel@novell.com 2006-11-23 07:28 MST ------- Try reproducing it on vanilla kernel. -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com