Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Fri, Sep 16, 2011 at 01:17:51PM +0200, Bart Hartgers wrote: [Previous messages are logged at http://bugs.debian.org/640391. I have now tested properly with debug=1. Unfortunately, the problem remains, and I can't see anything new in the messages. # rmmod ark3116; modprobe ark3116 debug=1 # uname -a Linux elf 3.0.0-1-686-pae #1 SMP Sat Aug 27 16:41:03 UTC 2011 i686 GNU/Linux - Sep 18 08:55:59 elf kernel: [ 308.938724] usbcore: registered new interface driver usbserial Sep 18 08:55:59 elf kernel: [ 308.938785] USB Serial support registered for generic Sep 18 08:55:59 elf kernel: [ 308.938860] usbcore: registered new interface driver usbserial_generic Sep 18 08:55:59 elf kernel: [ 308.938868] usbserial: USB Serial Driver core Sep 18 08:55:59 elf kernel: [ 308.942683] USB Serial support registered for ark3116 Sep 18 08:55:59 elf kernel: [ 308.942758] usbcore: registered new interface driver ark3116 Sep 18 08:55:59 elf kernel: [ 308.942767] ark3116:v0.6:USB ARK3116 serial/IrDA driver Sep 18 08:56:05 elf kernel: [ 314.953411] usbcore: deregistering interface driver ark3116 Sep 18 08:56:05 elf kernel: [ 314.953540] USB Serial deregistering driver ark3116 Sep 18 08:56:05 elf kernel: [ 314.967004] USB Serial support registered for ark3116 Sep 18 08:56:05 elf kernel: [ 314.967178] usbcore: registered new interface driver ark3116 Sep 18 08:56:05 elf kernel: [ 314.967195] ark3116:v0.6:USB ARK3116 serial/IrDA driver -- The above messages just from loading the module: the ark3116 was not plugged in. On plugging it: --- Sep 18 08:56:47 elf kernel: [ 357.080183] usb 2-1: new full speed USB device number 2 using uhci_hcd Sep 18 08:56:47 elf kernel: [ 357.240209] usb 2-1: New USB device found, idVendor=6547, idProduct=0232 Sep 18 08:56:47 elf kernel: [ 357.240229] usb 2-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0 Sep 18 08:56:47 elf kernel: [ 357.240243] usb 2-1: Product: USB-UART Controller Sep 18 08:56:47 elf kernel: [ 357.240254] usb 2-1: Manufacturer: ArkMicroChips Sep 18 08:56:47 elf kernel: [ 357.242579] ark3116 2-1:1.0: ark3116 converter detected Sep 18 08:56:47 elf mtp-probe: checking bus 2, device 2: /sys/devices/pci:00/:00:1d.0/usb2/2-1 Sep 18 08:56:47 elf kernel: [ 357.253199] usb 2-1: ark3116 using RS232 mode Sep 18 08:56:47 elf kernel: [ 357.253590] usb 2-1: ark3116 converter now attached to ttyUSB0 Sep 18 08:56:47 elf mtp-probe: bus: 2, device: 2 was not an MTP device Sep 18 08:56:47 elf kernel: [ 357.544206] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.557194] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.567194] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.674193] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:57:00 elf kernel: [ 370.017895] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:57:21 elf kernel: [ 391.615318] usb 2-1: ark3116: don't know how to do software flow control -- As far as I can see that is just the same as when debug is not set. Or did I get the parameter wrong? I can't see any acknowledgement that debug is set. ael -- 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/20110918081028.GA2619@elf.conquest
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
la, 2011-09-17 kello 06:10 -0700, Will Set kirjoitti: Saturday, September 17, 2011 6:49 AM Tomi Leppänen wrote: pe, 2011-09-16 kello 15:43 -0500, Jonathan Nieder kirjoitti: Hi Tomi, Tomi Leppänen wrote: [0.073485] PCI: Ignoring host bridge windows from ACPI; if necessary, use pci=use_crs and report a bug I was hoping it would be that. Does adding pci=use_crs to the kernel command line help? Thanks, Jonathan Didn't make any difference. Here is dmesg now: If you turn modesetting off you should be able to get the xserver running again. radeon.modeset=0 didn't seem to affect anything. Xorg.0.log: http://pastebin.com/3JKs85PP dmesg: http://pastebin.com/fZehesaK with radeon.modeset=0 see from your initial Xorg.0.log file http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641176 (II) Primary Device is: PCI 01@00:00:0 (II) [KMS] drm report modesetting isn't supported. [...] (EE) RADEON(0): No valid linear framebuffer address [...] (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found If you have a newer mobo to test with this video card it might be interesting to see if it handles modeswitching with a newer than ( Intel 440BX ) chipset and a pentium 4 processor. I don't. This is the only AGP mobo I have (others are PCI-E or PCI only). And it's running VIA C3 (Nehemiah-core) processor. It doesn't support P4 but only P3 and P2 (Slot 1 or Socket 370 with Slotket as I use it). I wonder why my grub is just some colorful crap on bottom of my screen. I can't really edit anything on fly but I have to always make changes to /etc/default/grub and then issue update-grub. That may have something to do with this bug. I also noticed that all of my memory is LOWMEM. Though graphics card doesn't change that (tried with ATI Rage 128VR that has trouble with DRI on Debian 6). -- 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/1316335136.6369.10.camel@tomppeli-laptop
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
2011/9/18 ael law_ence@ntlworld.com: On Fri, Sep 16, 2011 at 01:17:51PM +0200, Bart Hartgers wrote: [Previous messages are logged at http://bugs.debian.org/640391. I have now tested properly with debug=1. Unfortunately, the problem remains, and I can't see anything new in the messages. # rmmod ark3116; modprobe ark3116 debug=1 # uname -a Linux elf 3.0.0-1-686-pae #1 SMP Sat Aug 27 16:41:03 UTC 2011 i686 GNU/Linux Sep 18 08:56:47 elf kernel: [ 357.253199] usb 2-1: ark3116 using RS232 mode Sep 18 08:56:47 elf kernel: [ 357.253590] usb 2-1: ark3116 converter now attached to ttyUSB0 Sep 18 08:56:47 elf mtp-probe: bus: 2, device: 2 was not an MTP device Sep 18 08:56:47 elf kernel: [ 357.544206] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.557194] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.567194] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.674193] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:57:00 elf kernel: [ 370.017895] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:57:21 elf kernel: [ 391.615318] usb 2-1: ark3116: don't know how to do software flow control Strange. The rmmod and modprobe shoudl set the debug flag, so I would expect some debug messages around the 'software flow control' stuff. Did you check the output of 'dmesg'? (The prefixes suggest these are coming through syslogd.) Perhaps the debug messages end up in a different log or something? By the way, the 'software flow control' warnings are relatively harmless. They appear when software flow control is asked for, because that cannot be done reliably without somekind of support in the hardware. But at 9600 baud that should not be a factor. Groeten, Bart -- Bart Hartgers - New e-mail: bart.hartg...@gmail.com -- 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/CAK7h4yeq-84M2ZF0msuj79Z=VaG25rjDWzwtEq5031Lntyj5=q...@mail.gmail.com
Processed: Re: Bug#642003: (ATL1E): transmit queue 0 timed out
Processing commands for cont...@bugs.debian.org: reassign 642003 src:linux-2.6 Bug #642003 [linux-image-2.6.37-2-amd64] (ATL1E): transmit queue 0 timed out Warning: Unknown package 'linux-image-2.6.37-2-amd64' Bug reassigned from package 'linux-image-2.6.37-2-amd64' to 'src:linux-2.6'. Bug No longer marked as found in versions linux-2.6/2.6.37-2. thanks Stopping processing here. Please contact me if you need assistance. -- 642003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.131635832123586.transcr...@bugs.debian.org
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Sun, Sep 18, 2011 at 01:55:50PM +0200, Bart Hartgers wrote: 2011/9/18 ael law_ence@ntlworld.com: On Fri, Sep 16, 2011 at 01:17:51PM +0200, Bart Hartgers wrote: [Previous messages are logged at http://bugs.debian.org/640391. I have now tested properly with debug=1. Unfortunately, the problem remains, and I can't see anything new in the messages. # rmmod ark3116; modprobe ark3116 debug=1 # uname -a Linux elf 3.0.0-1-686-pae #1 SMP Sat Aug 27 16:41:03 UTC 2011 i686 GNU/Linux Sep 18 08:56:47 elf kernel: [ 357.253199] usb 2-1: ark3116 using RS232 mode Sep 18 08:56:47 elf kernel: [ 357.253590] usb 2-1: ark3116 converter now attached to ttyUSB0 Sep 18 08:56:47 elf mtp-probe: bus: 2, device: 2 was not an MTP device Sep 18 08:56:47 elf kernel: [ 357.544206] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.557194] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.567194] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:56:47 elf kernel: [ 357.674193] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:57:00 elf kernel: [ 370.017895] usb 2-1: ark3116: don't know how to do software flow control Sep 18 08:57:21 elf kernel: [ 391.615318] usb 2-1: ark3116: don't know how to do software flow control Strange. The rmmod and modprobe shoudl set the debug flag, so I would expect some debug messages around the 'software flow control' stuff. Did you check the output of 'dmesg'? (The prefixes suggest these are coming through syslogd.) Perhaps the debug messages end up in a different log or something? Ooops. I think you are right. I didn't check dmesg directly believing that it all appeared in /var/log/messages. But now I see /var/log/debug.. Sep 18 08:56:47 elf kernel: [ 357.542178] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting bps to 9600 Sep 18 08:56:47 elf kernel: [ 357.542195] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting hcr:0x00,lcr:0x13,quot:313 Sep 18 08:56:47 elf kernel: [ 357.550315] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting bps to 57600 Sep 18 08:56:47 elf kernel: [ 357.550339] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting hcr:0x00,lcr:0x13,quot:52 Sep 18 08:56:47 elf kernel: [ 357.557438] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting bps to 0 Sep 18 08:56:47 elf kernel: [ 357.557460] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting hcr:0x00,lcr:0x13,quot:313 Sep 18 08:56:47 elf kernel: [ 357.667612] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting bps to 57600 Sep 18 08:56:47 elf kernel: [ 357.667636] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting hcr:0x00,lcr:0x13,quot:52 Sep 18 08:57:00 elf kernel: [ 370.008846] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_read_int_callback - urb shutting down with status: -2 Sep 18 08:57:00 elf kernel: [ 370.009808] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting bps to 9600 Sep 18 08:57:00 elf kernel: [ 370.009872] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting hcr:0x00,lcr:0x13,quot:313 Sep 18 08:57:00 elf kernel: [ 370.022971] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting bps to 115200 Sep 18 08:57:00 elf kernel: [ 370.022994] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_set_termios - setting hcr:0x00,lcr:0x13,quot:26 Sep 18 08:57:06 elf kernel: [ 376.007693] /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/drivers/usb/serial/ark3116.c: ark3116_read_int_callback - urb shutting down with status: -2 Sep 18 08:57:21 elf kernel: [
Bug#642043: linux-image-3.0.0-1-amd64 frequently kerneloops on unmounting USB drives
Package: linux-2.6 Version: 3.0.0-3 Severity: normal * What led up to the situation? Using 'Safely remove drive' option on USB drives under Nautilus/GNOME frequently causes a kerneloops. * What exactly did you do (or not do) that was effective (or ineffective)? Sometimes you are able to switch virtual console and get back to X OK, other times a power cycle is required. I'd say 80% of the time unmounting works fine. * What was the outcome of this action? Here's a syslog dump after a non-fatal kerneloops after unmounting a USB drive: - Sep 18 15:38:12 annes-pc ntfs-3g[4299]: Unmounting /dev/sde1 (Expansion Drive) Sep 18 15:38:17 annes-pc kernel: [ 9762.593370] scsi 6:0:0:0: [sde] Unhandled error code Sep 18 15:38:17 annes-pc kernel: [ 9762.593386] scsi 6:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_OK Sep 18 15:38:17 annes-pc kernel: [ 9762.593391] scsi 6:0:0:0: [sde] CDB: Read(10): 28 00 00 00 00 3f 00 00 08 00 Sep 18 15:38:17 annes-pc kernel: [ 9762.593402] end_request: I/O error, dev sde, sector 63 Sep 18 15:38:17 annes-pc kernel: [ 9762.593408] Buffer I/O error on device sde1, logical block 0 Sep 18 15:38:17 annes-pc kernel: [ 9762.593437] BUG: unable to handle kernel NULL pointer dereference at 0048 Sep 18 15:38:17 annes-pc kernel: [ 9762.593513] IP: [8118d464] elv_completed_request+0x38/0x4c Sep 18 15:38:17 annes-pc kernel: [ 9762.593575] PGD 0 Sep 18 15:38:17 annes-pc kernel: [ 9762.593596] Oops: [#1] SMP Sep 18 15:38:17 annes-pc kernel: [ 9762.593630] CPU 2 Sep 18 15:38:17 annes-pc kernel: [ 9762.593641] Buffer I/O error on device sde1, logical block 0 Sep 18 15:38:17 annes-pc kernel: [ 9762.593663] Buffer I/O error on device sde1, logical block 1 Sep 18 15:38:17 annes-pc kernel: [ 9762.593668] Buffer I/O error on device sde1, logical block 1 Sep 18 15:38:17 annes-pc kernel: [ 9762.593687] Buffer I/O error on device sde1, logical block 122095976 Sep 18 15:38:17 annes-pc kernel: [ 9762.593691] Buffer I/O error on device sde1, logical block 122095976 Sep 18 15:38:17 annes-pc kernel: [ 9762.593793] Buffer I/O error on device sde1, logical block 1 Sep 18 15:38:17 annes-pc kernel: [ 9762.593799] Buffer I/O error on device sde1, logical block 1 Sep 18 15:38:17 annes-pc kernel: [ 9762.593823] Buffer I/O error on device sde1, logical block 122096007 Sep 18 15:38:17 annes-pc kernel: [ 9762.593828] Buffer I/O error on device sde1, logical block 0 Sep 18 15:38:17 annes-pc kernel: [ 9762.594060] Modules linked in: nls_utf8 nls_cp437 vfat fat cryptd aes_x86_64 aes_generic pci_stub vboxpci(O) acpi_cpufreq mperf vboxnetadp(O) ppdev cpufreq_powersave vboxnetflt(O) lp cpufreq_userspace cpufreq_stats cpufreq_conservative vboxdrv(O) fuse loop firewire_sbp2 firewire_core joydev snd_hda_codec_realtek snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_emu10k1 snd_hda_intel snd_ac97_codec snd_hda_codec ac97_bus snd_util_mem snd_hwdep snd_pcm_oss snd_seq_midi snd_mixer_oss snd_rawmidi i915 pcspkr snd_pcm snd_seq_midi_event i2c_i801 snd_seq snd_timer snd_seq_device snd evdev arc4 drm_kms_helper drm i2c_algo_bit button parport_pc rt61pci emu10k1_gp crc_itu_t rt2x00pci rt2x00lib parport processor mac80211 cfg80211 soundcore rfkill gameport eeprom_93cx6 serio_raw snd_page_alloc video i2c_core thermal_sys ext4 mbcache jbd2 crc16 usbhid hid usb_storage uas sg sr_mod sd_mod cdrom crc_t10dif ata_generic xhci_hcd ata_pii x ehci_hcd atl1c usbcore libata scsi_mo Sep 18 15:38:17 annes-pc kernel: d [last unloaded: scsi_wait_scan] Sep 18 15:38:17 annes-pc kernel: [ 9762.594965] Sep 18 15:38:17 annes-pc kernel: [ 9762.594980] Pid: 4271, comm: scsi_eh_6 Tainted: G O 3.0.0-1-amd64 #1 Gigabyte Technology Co., Ltd. H61M-USB3-B3/H61M-USB3-B3 Sep 18 15:38:17 annes-pc kernel: [ 9762.595072] RIP: 0010:[8118d464] [8118d464] elv_completed_request+0x38/0x4c Sep 18 15:38:17 annes-pc kernel: [ 9762.595139] RSP: 0018:8800941c9d30 EFLAGS: 00010002 Sep 18 15:38:17 annes-pc kernel: [ 9762.595178] RAX: RBX: 88011921c100 RCX: 0155 Sep 18 15:38:17 annes-pc kernel: [ 9762.595229] RDX: 88009067f540 RSI: 880036ff1a38 RDI: 88011921c100 Sep 18 15:38:17 annes-pc kernel: [ 9762.595279] RBP: 880036ff1a38 R08: 0001 R09: Sep 18 15:38:17 annes-pc kernel: [ 9762.595329] R10: 024311bc R11: 817ee068 R12: fffb Sep 18 15:38:17 annes-pc kernel: [ 9762.595379] R13: 0282 R14: R15: Sep 18 15:38:17 annes-pc kernel: [ 9762.595430] FS: () GS:88011fa8() knlGS: Sep 18 15:38:17 annes-pc kernel: [ 9762.595486] CS: 0010 DS: ES: CR0: 8005003b Sep 18 15:38:17 annes-pc kernel: [ 9762.595527] CR2: 0048 CR3: 01603000 CR4:
Uploading linux-2.6 (3.0.0-4)
I intend to upload a new version of linux-2.6 to unstable tomorrow. This will include upstream stable update 3.0.4 and various other bug fixes. It should not involve an ABI bump. Let me know if there is anything this should wait for. Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman, Secretary of the US Navy 1981-1987 signature.asc Description: This is a digitally signed message part
Bug#642043: linux-image-3.0.0-1-amd64 frequently kerneloops on unmounting USB drives
severity 642043 important tags 642043 + upstream forwarded 642043 https://bugzilla.kernel.org/show_bug.cgi?id=38842 forwarded 631187 https://bugzilla.kernel.org/show_bug.cgi?id=38842 merge 642043 631187 quit Hi Dan, Dan MacDonald wrote: Using 'Safely remove drive' option on USB drives under Nautilus/GNOME frequently causes a kerneloops. Sounds like http://bugs.debian.org/631187, aka https://bugzilla.kernel.org/show_bug.cgi?id=38842 [ 9762.593437] BUG: unable to handle kernel NULL pointer dereference at 0048 [ 9762.593513] IP: [8118d464] elv_completed_request+0x38/0x4c [...] [ 9762.593630] CPU 2 [ 9762.593641] Buffer I/O error on device sde1, logical block 0 [...] [ 9762.594980] Pid: 4271, comm: scsi_eh_6 Tainted: G O 3.0.0-1-amd64 #1 Gigabyte Technology Co., Ltd. H61M-USB3-B3/H61M-USB3-B3 (This is not the first oops after booting.) Thanks for writing, Jonathan -- 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/20110918222705.GM2308@elie
Processed: Re: linux-image-3.0.0-1-amd64 frequently kerneloops on unmounting USB drives
Processing commands for cont...@bugs.debian.org: severity 642043 important Bug #642043 [linux-2.6] linux-image-3.0.0-1-amd64 frequently kerneloops on unmounting USB drives Severity set to 'important' from 'normal' tags 642043 + upstream Bug #642043 [linux-2.6] linux-image-3.0.0-1-amd64 frequently kerneloops on unmounting USB drives Added tag(s) upstream. forwarded 642043 https://bugzilla.kernel.org/show_bug.cgi?id=38842 Bug #642043 [linux-2.6] linux-image-3.0.0-1-amd64 frequently kerneloops on unmounting USB drives Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=38842'. forwarded 631187 https://bugzilla.kernel.org/show_bug.cgi?id=38842 Bug #631187 [linux-2.6] Kernel panics when removing external hard drive Bug #633890 [linux-2.6] [linux-2.6] kernel oops while disconnecting usb cdrom Bug #634681 [linux-2.6] linux-image-2.6.39-2-686-pae: Usb oops with 2.6.39 (elv_put_request) Bug #636103 [linux-2.6] linux-image-2.6.39-2-amd64: repeatedly crashes: general protection fault, perhaps connected to ata2? Bug #636263 [linux-2.6] linux-image-2.6.39-2-amd64: kernel panic when unmounting USB drives Changed Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=38842' from 'linux-s...@vger.kernel.org' Changed Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=38842' from 'linux-s...@vger.kernel.org' Changed Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=38842' from 'linux-s...@vger.kernel.org' Changed Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=38842' from 'linux-s...@vger.kernel.org' Changed Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=38842' from 'linux-s...@vger.kernel.org' merge 642043 631187 Bug#631187: Kernel panics when removing external hard drive Bug#642043: linux-image-3.0.0-1-amd64 frequently kerneloops on unmounting USB drives Bug#633890: [linux-2.6] kernel oops while disconnecting usb cdrom Bug#634681: linux-image-2.6.39-2-686-pae: Usb oops with 2.6.39 (elv_put_request) Bug#636103: linux-image-2.6.39-2-amd64: repeatedly crashes: general protection fault, perhaps connected to ata2? Bug#636263: linux-image-2.6.39-2-amd64: kernel panic when unmounting USB drives Merged 631187 633890 634681 636103 636263 642043. quit Stopping processing here. Please contact me if you need assistance. -- 631187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631187 636263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636263 633890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633890 642043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642043 636103: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636103 634681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.131638483527770.transcr...@bugs.debian.org
Bug#642043: linux-image-3.0.0-1-amd64 frequently kerneloops on unmounting USB drives
Dan MacDonald wrote: Using 'Safely remove drive' option on USB drives under Nautilus/GNOME frequently causes a kerneloops. Can you reproduce this with 3.1-rc4 or later from experimental? If so, dmesg output for the first oops using that kernel would be very helpful[*]. Thanks, Jonathan [*] http://thread.gmane.org/gmane.linux.scsi/6 -- 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/20110918225036.GA21908@elie
Bug#641946: FM801 Sound card not detected for linux-image-3.0.0-1-486
On Sun, 2011-09-18 at 11:15 +0800, Hor Jiun Shyong wrote:
Package: linux-image-3.0.0-1-486
Version: 3.0.0-3
Issue: Sound card not detected. Soundcard Chipset: FM801.Soundcard
is working under linux-image-2.6.39-2-486 and older kernels.
[...]
Please can you test whether the attached patch fixes this?
Instructions for building a patched kernel package can be found at
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official.
Ben.
--
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.
commit 63bdc367e9dc1a440a2dabeb27ba9745348ff628
Author: Ben Hutchings b...@decadent.org.uk
Date: Mon Sep 19 01:55:57 2011 +0100
fm801: Gracefully handle failure of tuner auto-detect
commit 9676001559fce06e37c7dc230ab275f605556176
(ALSA: fm801: add error handling if auto-detect fails) seems to
break systems that were previously working without a tuner.
As a bonus, this should fix init and cleanup for the case where the
tuner is explicitly disabled.
Reported-by: Hor Jiun Shyong jiunshy...@gmail.com
References: http://bugs.debian.org/641946
Signed-off-by: Ben Hutchings b...@decadent.org.uk
commit b06a2e531f2801093424f625ec1e54872d71052f
Author: Ben Hutchings b...@decadent.org.uk
Date: Mon Sep 19 01:50:05 2011 +0100
fm801: Fix double free in case of error in tuner detection
commit 9676001559fce06e37c7dc230ab275f605556176
(ALSA: fm801: add error handling if auto-detect fails) added
incorrect error handling.
Once we have successfully called snd_device_new(), the cleanup
function fm801_free() will automatically be called by snd_card_free()
and we must *not* also call fm801_free() directly.
Reported-by: Hor Jiun Shyong jiunshy...@gmail.com
References: http://bugs.debian.org/641946
Signed-off-by: Ben Hutchings b...@decadent.org.uk
diff --git a/sound/pci/fm801.c b/sound/pci/fm801.c
index a7ec703..ecce948 100644
--- a/sound/pci/fm801.c
+++ b/sound/pci/fm801.c
@@ -68,6 +68,7 @@ MODULE_PARM_DESC(enable, Enable FM801 soundcard.);
module_param_array(tea575x_tuner, int, NULL, 0444);
MODULE_PARM_DESC(tea575x_tuner, TEA575x tuner access method (0 = auto, 1 = SF256-PCS, 2=SF256-PCP, 3=SF64-PCR, 8=disable, +16=tuner-only).);
+#define TUNER_DISABLED (13)
#define TUNER_ONLY (14)
#define TUNER_TYPE_MASK (~TUNER_ONLY 0x)
@@ -1150,7 +1151,8 @@ static int snd_fm801_free(struct fm801 *chip)
__end_hw:
#ifdef CONFIG_SND_FM801_TEA575X_BOOL
- snd_tea575x_exit(chip-tea);
+ if (!(chip-tea575x_tuner TUNER_DISABLED))
+ snd_tea575x_exit(chip-tea);
#endif
if (chip-irq = 0)
free_irq(chip-irq, chip);
@@ -1236,7 +1238,6 @@ static int __devinit snd_fm801_create(struct snd_card *card,
(tea575x_tuner TUNER_TYPE_MASK) 4) {
if (snd_tea575x_init(chip-tea)) {
snd_printk(KERN_ERR TEA575x radio not found\n);
- snd_fm801_free(chip);
return -ENODEV;
}
} else if ((tea575x_tuner TUNER_TYPE_MASK) == 0) {
@@ -1251,11 +1252,15 @@ static int __devinit snd_fm801_create(struct snd_card *card,
}
if (tea575x_tuner == 4) {
snd_printk(KERN_ERR TEA575x radio not found\n);
- snd_fm801_free(chip);
- return -ENODEV;
+ chip-tea575x_tuner = TUNER_DISABLED;
}
}
- strlcpy(chip-tea.card, snd_fm801_tea575x_gpios[(tea575x_tuner TUNER_TYPE_MASK) - 1].name, sizeof(chip-tea.card));
+ if (!(chip-tea575x_tuner TUNER_DISABLED)) {
+ strlcpy(chip-tea.card,
+ snd_fm801_tea575x_gpios[(tea575x_tuner
+ TUNER_TYPE_MASK) - 1].name,
+ sizeof(chip-tea.card));
+ }
#endif
*rchip = chip;
signature.asc
Description: This is a digitally signed message part
Processed: tagging 641946
Processing commands for cont...@bugs.debian.org: tags 641946 + upstream patch moreinfo Bug #641946 [linux-image-3.0.0-1-486] FM801 Sound card not detected for linux-image-3.0.0-1-486 Added tag(s) upstream, moreinfo, and patch. thanks Stopping processing here. Please contact me if you need assistance. -- 641946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13163944937605.transcr...@bugs.debian.org
Bug#641919: linux-image-3.0.0-1-amd64: VIA-Rhine II resetting: network connectivity lost
On Sat, 2011-09-17 at 15:59 +0100, Antonio Marcos López Alonso wrote: Package: linux-2.6 Version: 3.0.0-3 Severity: normal Tags: upstream This is the same behavior as bug #549606. Network connection is lost somehow and dmesg outputs lots of: via-rhine :00:12.0: eth0: Transmit timed out, status 0003, PHY status 786d, resetting... via-rhine :00:12.0: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 Resetting the machine fixes the issue. This behavior has been happening now and then since the previous bug was closed. [...] I think bug #549606 was closed in error, as the supposed fix is related to behaviour after a transmit timeout and not the cause of timeouts. Before it was closed, you found that the kernel parameter 'noapic' was a workaround for the problem on your system, which means it probably isn't a bug in the driver). I notice that you are currently *not* using that parameter. I asked you to report this bug at http://bugzilla.kernel.org, including the fact that 'noapic' works around it. The product should be 'Platform Specific/Hardware' and the component 'i386'. You won't be able to do that at the moment because that server is done, but please try to do that in a week or so. Then let us know the bug number so we can keep track of it. Ben. -- Ben Hutchings If more than one person is responsible for a bug, no one is at fault. signature.asc Description: This is a digitally signed message part
Processed: tagging 641919, unarchiving 549606, reopening 549606, notfixed 549606 in linux-2.6/2.6.32-10 ...
Processing commands for cont...@bugs.debian.org:
tags 641919 + moreinfo
Bug #641919 [linux-2.6] linux-image-3.0.0-1-amd64: VIA-Rhine II resetting:
network connectivity lost
Added tag(s) moreinfo.
unarchive 549606
Bug #549606 {Done: maximilian attems m...@debian.org} [linux-2.6]
[linux-image-2.6.30-1-amd64] VIA-Rhine II network interface lost connectivity
Unarchived Bug 549606
reopen 549606
Bug #549606 {Done: maximilian attems m...@debian.org} [linux-2.6]
[linux-image-2.6.30-1-amd64] VIA-Rhine II network interface lost connectivity
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
notfixed 549606 linux-2.6/2.6.32-10
Bug #549606 [linux-2.6] [linux-image-2.6.30-1-amd64] VIA-Rhine II network
interface lost connectivity
Ignoring request to alter fixed versions of bug #549606 to the same values
previously set
forcemerge 641919 549606
Bug#641919: linux-image-3.0.0-1-amd64: VIA-Rhine II resetting: network
connectivity lost
Bug#549606: [linux-image-2.6.30-1-amd64] VIA-Rhine II network interface lost
connectivity
Forcibly Merged 549606 641919.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
641919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641919
549606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
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/handler.s.c.131639499110122.transcr...@bugs.debian.org
Re: Upcoming Point Releases
On Wed, 2011-09-14 at 10:33 +0100, Adam D. Barratt wrote:
On Tue, 13 Sep 2011 20:27:55 +0100, Adam D. Barratt wrote:
On Sun, 2011-09-11 at 23:59 +0100, Ben Hutchings wrote:
I believe we're now ready to do the kernel update, having got most
of
the security fixes done separately. I'm going to start a build now
and
intend to upload tomorrow unless I hear any objection to this (or I
find
a problem myself).
Nobody appears to have objected, and it was uploaded. I've just
marked
the upload for acceptance at the next dinstall; thanks.
Unfortunately the upload FTBFS on several architectures.
The ia64 log contains a few cast from pointer to integer of different
size warnings,
A few such warnings are, regrettably, normal.
and dies with:
/build/buildd-linux-2.6_2.6.32-36-ia64-4ELC7i/linux-2.6-2.6.32/debian/build/source_ia64_none/drivers/net/e1000e/netdev.c:6214:
error: 'e1000_suspend' undeclared here (not in a function)
/build/buildd-linux-2.6_2.6.32-36-ia64-4ELC7i/linux-2.6-2.6.32/debian/build/source_ia64_none/drivers/net/e1000e/netdev.c:6214:
error: 'e1000_resume' undeclared here (not in a function)
make[8]: *** [drivers/net/e1000e/netdev.o] Error 1
make[7]: *** [drivers/net/e1000e] Error 2
make[6]: *** [drivers/net] Error 2
armel, mips{,el} and sparc all failed with:
/build/buildd-linux-2.6_2.6.32-36-armel-fnA8Ad/linux-2.6-2.6.32/debian/build/source_armel_none/drivers/net/e1000e/netdev.c:
In function '__e1000e_disable_aspm':
/build/buildd-linux-2.6_2.6.32-36-armel-fnA8Ad/linux-2.6-2.6.32/debian/build/source_armel_none/drivers/net/e1000e/netdev.c:5323:
error: implicit declaration of function 'pci_pcie_cap'
make[8]: *** [drivers/net/e1000e/netdev.o] Error 1
make[7]: *** [drivers/net/e1000e] Error 2
make[6]: *** [drivers/net] Error 2
I understand and have fixes for both of these failures. Following those
changes I have successfully compiled all the modified drivers on the
ia64 and sparc porter boxes (but not attempted a complete package
rebuild).
Ben.
--
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.
signature.asc
Description: This is a digitally signed message part
Processing of firmware-nonfree_0.28+squeeze1_i386.changes
firmware-nonfree_0.28+squeeze1_i386.changes uploaded successfully to localhost along with the files: firmware-nonfree_0.28+squeeze1.dsc firmware-nonfree_0.28+squeeze1.tar.gz firmware-linux_0.28+squeeze1_all.deb firmware-atheros_0.28+squeeze1_all.deb firmware-bnx2_0.28+squeeze1_all.deb firmware-bnx2x_0.28+squeeze1_all.deb firmware-brcm80211_0.28+squeeze1_all.deb firmware-intelwimax_0.28+squeeze1_all.deb firmware-ipw2x00_0.28+squeeze1_all.deb firmware-ivtv_0.28+squeeze1_all.deb firmware-iwlwifi_0.28+squeeze1_all.deb firmware-linux-nonfree_0.28+squeeze1_all.deb firmware-netxen_0.28+squeeze1_all.deb firmware-qlogic_0.28+squeeze1_all.deb firmware-ralink_0.28+squeeze1_all.deb firmware-realtek_0.28+squeeze1_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1r5uns-000186...@franck.debian.org
Bug#587763: linux-image-2.6.32-5-amd64: scary messages from JBD when manipulating quotas on ext4
Moritz wrote: This might have been fixed in 2.6.32.17 (and thus in Debian revision 2.6.32-19 for Squeeze and 2.6.33 for sid). Can you confirm? This bug still exists in squeeze kernel 2.6.32-35squeeze2 (I'm using linux-image-2.6.32-5-amd64 2.6.32-35squeeze2). The patch wasn't committed to the upstream kernel until 2.6.35 on July 27, 2010: http://git.strongswan.org/?p=linux-dumm.git;a=commitdiff;h=62d2b5f2dcd3707b070efb16bbfdf6947c38c194 -- Robert L Mathews, Tiger Technologies, http://www.tigertech.net/ -- 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/4e76d14c.6040...@tigertech.com
