Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#15392 - [kernel26] panic on usb device insert

Attached to Project: Arch Linux
Opened by Jeff Anderson (programmerq) - Sunday, 05 July 2009, 19:47 GMT
Last edited by Roman Kyrylych (Romashka) - Monday, 05 October 2009, 09:24 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Kernel panics when inserting a snapstream firefly RF receiver. If cold plugged, the kernel panics when udev is processing events.

Additional info:
* package version(s):

* Linux radiant 2.6.30-ARCH #1 SMP PREEMPT Fri Jun 19 21:25:17 UTC 2009 i686 AMD Athlon(tm) XP 3200+ AuthenticAMD GNU/Linux
* core/udev 141-3

* Device info:

* ID 0bc7:0008 X10 Wireless Technology, Inc. Wireless Transceiver (ACPI-compliant)
* lirc_atiusb driver

* config and/or log files etc.

* kernel.log shows nothing at the time of the crash.

Steps to reproduce:

insert device after boot

or

insert device, boot, wait for udev to start processing events.

* Additional notes

* This device is known to work on another machine running archlinux. The working machine is running a 2.6.29-ARCH kernel.
* I used a PCI usb controller as a control between both machines. The controller and receiver work on the machine with the .29 kernel, but the same pci controller and rf receiver don't work in the machine with the .30 kernel.

* Additional hardware info (for the machine experiencing the problem):

$ lspci
00:00.0 Host bridge: nVidia Corporation nForce2 IGP2 (rev c1)
00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1)
00:05.0 Multimedia audio controller: nVidia Corporation nForce Audio Processing Unit (rev a2)
00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1)
00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3)
00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
00:0d.0 FireWire (IEEE 1394): nVidia Corporation nForce2 FireWire (IEEE 1394) Controller (rev a3)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
01:04.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
01:07.0 PCI bridge: Pericom Semiconductor PI7C8140A PCI-to-PCI Bridge
01:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
01:09.0 Network controller: AIRONET Wireless Communications PC4800 (rev 01)
01:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
01:0a.1 Input device controller: Creative Labs SB Live! Game Port (rev 07)
01:0b.0 RAID bus controller: Silicon Image, Inc. SiI 3112 [SATALink/SATARaid] Serial ATA Controller (rev 02)
02:08.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
02:09.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
04:00.0 VGA compatible controller: ATI Technologies Inc RV620 LE AGP [Radeon HD 3450]
04:00.1 Audio device: ATI Technologies Inc RV620 Audio device [Radeon HD 34xx Series]

$ lsusb # before inserting, of course
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Monday, 05 October 2009, 09:24 GMT
Reason for closing:  Upstream
Comment by Roman Kyrylych (Romashka) - Sunday, 05 July 2009, 19:53 GMT
is this reported on bugzilla.kernel.org or other way known upstream issue?
Comment by Jan de Groot (JGC) - Sunday, 05 July 2009, 19:56 GMT
Could you photograph the kernel panic? Without traces this is not a useful bugreport.
Comment by Jeff Anderson (programmerq) - Thursday, 09 July 2009, 15:47 GMT
There really isn't much of a traceback. Here is the text of the panic:

Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: d0eb6b3b

I have not reported it upstream. I figured I'd report it here since I'm using a -ARCH kernel.
Comment by Tobias Powalowski (tpowa) - Saturday, 01 August 2009, 08:17 GMT
We are not patching the kernels usb system so please report it upstream, thanks.
Comment by Tobias Powalowski (tpowa) - Saturday, 01 August 2009, 08:19 GMT
Also this seems to be more lirc related then a kernel bug so repoting it to lirc bugzilla makes more sense.
Comment by Thomas Bächler (brain0) - Saturday, 01 August 2009, 08:37 GMT
Yes, there are bugs that are invisible until you enable the stack protector (which we do for security reasons). It is likely to be a problem in lirc.

Loading...