Bug#695676: snd_rawmidi: Unknown symbol snd_card_unref (err 0) on loading snd-usb-audio
Package: src:linux Version: 3.2.35-1 Severity: normal loading of snd-usb-audio fails with errormessage snd_rawmidi: Unknown symbol snd_card_unref (err 0) -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-12) ) #1 SMP Debian 3.2.32-1 ** Command line: initrd=/boot/initrd.img-3.2.0-4-amd64 root=/dev/disk/by-uuid/813cbe8d-99ea-488b-bd22-5cb211a6449a ro quiet BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [451487.028885] usb 4-1.4: reset high-speed USB device number 103 using ehci_hcd [451487.112668] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [451487.116077] ata2.00: ACPI cmd e3/00:1f:00:00:00:a0 (IDLE) succeeded [451487.118328] ata2.00: ACPI cmd e3/00:02:00:00:00:a0 (IDLE) succeeded [451487.118338] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [451487.120659] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [451487.120957] usb 4-1.4: device firmware changed [451487.121220] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [451487.121233] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [451487.121235] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [451487.122092] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [451487.122103] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [451487.122111] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [451487.122429] ata1.00: configured for UDMA/133 [451487.128213] ata2.00: ACPI cmd e3/00:1f:00:00:00:a0 (IDLE) succeeded [451487.128656] ata5: SATA link down (SStatus 0 SControl 300) [451487.130461] ata2.00: ACPI cmd e3/00:02:00:00:00:a0 (IDLE) succeeded [451487.130470] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [451487.133650] ata2.00: configured for UDMA/100 [451487.192816] usb 3-1.6: reset high-speed USB device number 5 using ehci_hcd [451487.280825] sdhci-pci :05:00.0: setting latency timer to 64 [451487.294545] PM: resume of devices complete after 520.345 msecs [451487.294611] PM: Finishing wakeup. [451487.294612] Restarting tasks ... [451487.295439] usb 4-1.4: USB disconnect, device number 103 [451487.295803] ehci_hcd :00:1d.0: dma_pool_free buffer-128, 8800a91e9000/a91e9000 (bad dma) [451487.295897] cdc_ncm 4-1.4:1.6: usb0: unregister 'cdc_ncm' usb-:00:1d.0-1.4, CDC NCM [451487.305440] done. [451487.305754] video LNXVIDEO:00: Restoring backlight state [451487.328721] ehci_hcd :00:1d.0: dma_pool_free buffer-128, 8800a91dd000/a91dd000 (bad dma) [451487.400680] usb 4-1.4: new high-speed USB device number 104 using ehci_hcd [451487.493587] usb 4-1.4: New USB device found, idVendor=0bdb, idProduct=1912 [451487.493597] usb 4-1.4: New USB device strings: Mfr=0, Product=2, SerialNumber=5 [451487.493604] usb 4-1.4: Product: \xffe3\xff95\xff86\xffe3\xff88\xffb5\xffe6\xff9c\xffb1w [451487.493609] usb 4-1.4: SerialNumber: 2BB9A781BC172640 [451487.539279] generic-usb: probe of 0003:0BDB:1912.004C failed with error -71 [451487.539567] usb 3-1.5: USB disconnect, device number 13 [451487.539578] usb 3-1.5.5: USB disconnect, device number 14 [451487.577224] usb 3-1.5.6: USB disconnect, device number 20 [451487.692426] usb 1-1: new high-speed USB device number 22 using xhci_hcd [451487.709870] usb 1-1: New USB device found, idVendor=0424, idProduct=2514 [451487.709872] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [451487.710516] hub 1-1:1.0: USB hub found [451487.710713] xhci_hcd :0d:00.0: WARN: short transfer on control ep [451487.710866] hub 1-1:1.0: 4 ports detected [451487.713699] usb 4-1.4: USB disconnect, device number 104 [451487.984513] usb 1-1.2: new low-speed USB device number 23 using xhci_hcd [451488.005496] xhci_hcd :0d:00.0: WARN: short transfer on control ep [451488.007743] xhci_hcd :0d:00.0: WARN: short transfer on control ep [451488.008742] xhci_hcd :0d:00.0: WARN: short transfer on control ep [451488.009001] usb 1-1.2: New USB device found, idVendor=046d, idProduct=c063 [451488.009003] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [451488.009004] usb 1-1.2: Product: DELL USB Laser Mouse [451488.009006] usb 1-1.2: Manufacturer: DELL [451488.009150] usb 1-1.2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes [451488.015224] input: DELL DELL USB Laser Mouse as /devices/pci:00/:00:1c.4/:0d:00.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input58 [451488.015447] generic-usb 0003:046D:C063.004D: input,hidraw0: USB HID v1.10 Mouse [DELL DELL USB Laser Mouse] on usb-:0d:00.0-1.2/input0 [451488.516383] usb 4-1.4: new high-speed USB device number 105 using ehci_hcd [451488.614409] usb 4-1.4: New USB device found, idVendor=0bdb, idProduct=1911 [451488.614412] usb 4-1.4:
Bug#567204: serious filesystem corruption with bigmem kernels
On Thu, Feb 18, 2010 at 01:21:22AM +, Ben Hutchings wrote: On Mon, 2010-02-01 at 15:55 +0100, M. Dietrich wrote: Package: linux-image-686-bigmem Severity: normal i started a reportbug run with the real kernel name. this is the outcome: I can't see any obvious suspect here. Therefore, please file a bug report upstream at http://bugzilla.kernel.org, selecting product 'Platform Specific/Hardware', component 'i386', and providing the same information in your report here. Let us know the bug number so we can track it. close the bug i encountered file system corruption with a non-bigmem kernel today i don't now what's going on will now check the hd best regards sorry for the turbulence, michael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225103038.ga4...@emdete.de
Bug#567204: linux-image-686-bigmem: serious filesystem corruption with bigmem kernels
On Wed, Feb 03, 2010 at 11:22:06AM +0100, Cesare Leonardi wrote: M. Dietrich wrote: my system had serious filesystem corruption with several -bigmem kernel in the past (from 2.6.28 to 2.6.32). Does this mean that with normal 686 or 486 kernel the corruption doesn't happen? yes. However many years ago i've experienced frequent filesystem corruption but i couldn't figure out why. Eventually i discovered was some hdparm settings... Was a lot hard to find, so i hope this could help you. ;-) there are no special settings installed using hdparm: /dev/sda: multcount = 0 (off) IO_support= 1 (32-bit) readonly = 0 (off) readahead = 256 (on) geometry = 30401/255/63, sectors = 488397168, start = 0 for sure i can't guarantee that this isn't related to some hardware fault like broken ram or the like but i checked ram with memtest86+. If i were you, i would also install smartmontools and try something like: smartctl -a /dev/yourdisk I'd put particular attention in the Vendor Specific SMART Attributes with Thresholds table to find something strange. it's already installed, this is the output: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 085 069 034Pre-fail Always - 98867399 3 Spin_Up_Time0x0003 100 100 000Pre-fail Always - 0 4 Start_Stop_Count0x0032 001 001 020Old_age Always FAILING_NOW 248712 5 Reallocated_Sector_Ct 0x0033 100 100 036Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 075 060 030Pre-fail Always - 40211526 9 Power_On_Hours 0x0032 095 095 000Old_age Always - 269350284038985 10 Spin_Retry_Count0x0013 100 100 034Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020Old_age Always - 448 184 End-to-End_Error0x0032 100 253 000Old_age Always - 0 187 Reported_Uncorrect 0x003a 100 100 000Old_age Always - 0 189 High_Fly_Writes 0x0022 100 100 045Old_age Always - 0 190 Airflow_Temperature_Cel 0x0032 071 052 000Old_age Always - 29 (Lifetime Min/Max 10/48) 191 G-Sense_Error_Rate 0x0032 100 100 000Old_age Always - 19 192 Power-Off_Retract_Count 0x0022 062 062 000Old_age Always - 77434 193 Load_Cycle_Count0x001a 001 001 000Old_age Always - 320283 194 Temperature_Celsius 0x0012 029 048 000Old_age Always - 29 (0 10 0 0) 195 Hardware_ECC_Recovered 0x0010 070 061 000Old_age Offline - 98881899 196 Reallocated_Event_Count 0x003e 096 096 000Old_age Always - 3645 (28548, 0) 197 Current_Pending_Sector 0x 100 100 000Old_age Offline - 0 198 Offline_Uncorrectable 0x0032 100 100 000Old_age Always - 0 199 UDMA_CRC_Error_Count0x 200 200 000Old_age Offline - 0 200 Multi_Zone_Error_Rate 0x 100 253 000Old_age Offline - 0 202 Data_Address_Mark_Errs 0x 100 253 000Old_age Offline - 0 i wonder how to interpret that. Start_Stop_Count has FAILING_NOW, maybe because hdaps is stopping the device often? why is that bad? hm. but everything else looks fine, right? And try to hear if the disk make suspicious noise. it doesnt - silent as a sleeping baby. If you have a minimum suspect for the ram, try to temporarly remove some bank, if you have more than one, or replace completely if you can. In the past i've seen at least two cases where memtest run ok for about a day but the system had sporadic system freeze and BSOD (Windows PCs). When i've replaced the ram the problems disapperead. removing would reduce mem size and the need for bigmem kernel obsolete. replacing isn't possible right now. point is: i never had strange behaviour related to mem like kernel-freezes or program core dumps and i use the system quite alot with big (cross-)compiles and everything that uses mem alot... thing is that i discovered fs corruption by accident - git complained about a defect repo. then i forced a fsck run at boot and that failed. maybe all bigmem users should force a fsck and see if they already suffer from a similar corruption. if not this bug should be closed because it seems to be hw related. but i don't know how where to search, especially because this computer is a tool to do my work on. best regards, michael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567204: serious filesystem corruption with bigmem kernels
Package: linux-image-686-bigmem Severity: normal i started a reportbug run with the real kernel name. this is the outcome: Subject: linux-image-2.6.32-trunk-686-bigmem: mockup report for fscorruption Package: linux-2.6 Version: 2.6.32-5 Justification: causes non-serious data loss Severity: grave -- Package-specific info: ** Version: Linux version 2.6.32-trunk-686-bigmem (Debian 2.6.32-5) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 07:12:17 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-686-bigmem root=UUID=fbdfdf29-80a2-47f7-9996-a8be95c9ad59 ro acpi_osi=Linux quiet ** Not tainted ** Kernel log: [6.158433] (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) [6.158435] (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) [6.158438] (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) [6.158668] cfg80211: Calling CRDA for country: US [6.181926] usbcore: registered new interface driver cdc_ether [6.216764] usbcore: registered new interface driver zaurus [6.320600] uvcvideo: Found UVC 1.00 device unnamed (17ef:4807) [6.322069] input: UVC Camera (17ef:4807) as /devices/pci:00/:00:1a.7/usb1/1-6/1-6:1.0/input/input7 [6.322130] usbcore: registered new interface driver uvcvideo [6.322232] USB Video Class driver (v0.1.0) [6.332030] usbcore: registered new interface driver hiddev [6.334766] input: Logitech USB-PS/2 Optical Mouse as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.3/1-5.3:1.0/input/input8 [6.334836] generic-usb 0003:046D:C03E.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1a.7-5.3/input0 [6.334853] usbcore: registered new interface driver usbhid [6.334855] usbhid: v2.6:USB HID core driver [6.396051] usb 4-2: new full speed USB device using uhci_hcd and address 3 [6.549439] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean. [6.551241] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7 [6.551942] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean. [6.552523] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean. [6.553274] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean. [6.569065] usb 4-2: New USB device found, idVendor=0a5c, idProduct=2145 [6.569068] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [6.569072] usb 4-2: Product: ThinkPad Bluetooth with Enhanced Data Rate II [6.569075] usb 4-2: Manufacturer: Lenovo Computer Corp [6.569173] usb 4-2: configuration #1 chosen from 1 choice [6.644184] Bluetooth: Core ver 2.15 [6.644216] NET: Registered protocol family 31 [6.644217] Bluetooth: HCI device and connection manager initialized [6.644219] Bluetooth: HCI socket layer initialized [6.786581] Bluetooth: Generic Bluetooth USB driver ver 0.6 [6.786662] usbcore: registered new interface driver btusb [6.906438] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks [6.906440] iwlagn: Copyright(c) 2003-2009 Intel Corporation [6.906490] iwlagn :03:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [6.906498] iwlagn :03:00.0: setting latency timer to 64 [6.906526] iwlagn :03:00.0: Detected Intel Wireless WiFi Link 5100AGN REV=0x54 [6.945601] iwlagn :03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels [6.945674] iwlagn :03:00.0: irq 30 for MSI/MSI-X [6.993939] phy0: Selected rate control algorithm 'iwl-agn-rs' [7.217236] HDA Intel :00:1b.0: PCI INT B - GSI 17 (level, low) - IRQ 17 [7.217264] HDA Intel :00:1b.0: setting latency timer to 64 [7.285683] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input9 [7.285757] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input10 [7.285802] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input11 [7.285846] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input12 [8.415533] Adding 4939976k swap on /dev/sda2. Priority:-1 extents:1 across:4939976k [8.612920] EXT3 FS on sda1, internal journal [8.755456] loop: module loaded [ 11.284861] input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/serio2/input/input13 [ 11.960043] usb 2-4: new high speed USB device using
Bug#567204: linux-image-686-bigmem: serious filesystem corruption with bigmem kernels
Package: linux-image-686-bigmem Severity: grave Justification: renders package unusable my system had serious filesystem corruption with several -bigmem kernel in the past (from 2.6.28 to 2.6.32). git first discovered the problem because it complained about corruption in the repo. a filesystem check found lots of double allocated blocks and other problems. i use a ext3 filesystem. i first thought its related to suspend/resume so i didn't suspend anymore - file corruption still occured. so i switched from a -bigmem kernel to a normal kernel with same version and even after heavy usage (cross compile openwrt) no corruption was found. for sure i can't guarantee that this isn't related to some hardware fault like broken ram or the like but i checked ram with memtest86+. please adjust Severity and/or Justification if i choosed that wrong. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
