Bug#697019: Bug is fixed: at least for stable debian 7 kernel SMP Debian 3.2.51-1 x86_64
Bug is fixed: at least for stable debian 7, kernel SMP Debian 3.2.51-1 x86_64 Ext usb-3.0 HDD is mounted properly and it works as expected. Transfer rate shows usb-3 speed. PS uname -a output: Linux lenovo 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux lsusb output: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 003: ID 5986:0299 Acer, Inc Bus 003 Device 002: ID 0bc2:2332 Seagate RSS LLC dmesg output: [ 74.355092] hub 2-0:1.0: unable to enumerate USB device on port 2 [ 74.595165] usb 3-2: new SuperSpeed USB device number 2 using xhci_hcd [ 74.613295] usb 3-2: New USB device found, idVendor=0bc2, idProduct=2332 [ 74.613306] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 74.613312] usb 3-2: Product: Portable [ 74.613316] usb 3-2: Manufacturer: Seagate [ 74.613320] usb 3-2: SerialNumber: 2GH76WY5 [ 74.750174] Initializing USB Mass Storage driver... [ 74.750443] scsi7 : usb-storage 3-2:1.0 [ 74.750584] usbcore: registered new interface driver usb-storage [ 74.750587] USB Mass Storage support registered. [ 75.747222] scsi 7:0:0:0: Direct-Access Seagate Portable SF04 PQ: 0 ANSI: 4 [ 75.749760] sd 7:0:0:0: [sdc] 976773164 512-byte logical blocks: (500 GB/465 GiB) [ 75.750135] sd 7:0:0:0: [sdc] Write Protect is off [ 75.750143] sd 7:0:0:0: [sdc] Mode Sense: 1c 00 00 00 [ 75.750870] sd 7:0:0:0: Attached scsi generic sg2 type 0 [ 75.752304] sd 7:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 75.806605] sdc: sdc1 [ 75.808055] sd 7:0:0:0: [sdc] Attached SCSI disk [ 76.429555] fuse init (API version 7.17) -- 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/52c46062.8070...@fryazino.net
Bug#733895: kernel 3.12 FTBFS and parisc patches
Package: linux Version: 3.12 Severity: bug Tags: patch In Bug# 721191 we removed the parisc-smp and parisc64 (non-SMP) kernel variants. Sadly I forgot to correct the kernel versions in the debian/installer/hppa/kernel-versions file, so that the final build stage failed because it tried to package the parisc64 variant for the debian-installer, while only the parisc64-smp variant is available. The attached patch fixes this. Furthermore the attached patch changes the kernel to build-in the AGP modules, else we get an AGP-error at boot (Ben Hutchings suggested in bug 721191 this: You might yet need to make them built-in, as nothing else ensures that AGP devices are initialised before DRM devices.). And the attached patch enables the CONFIG_DEBUG_STACKOVERFLOW=y option. With that one, we get enhanced information about stack usage in the /proc/interrupts file and stack overflows was one of the main problems regarding stability of the parisc-kernel in the past. Performance-penalty of this option is minimal. Thanks, Helge Index: linux/debian/config/hppa/config === --- linux/debian/config/hppa/config (revision 20943) +++ linux/debian/config/hppa/config (working copy) @@ -21,6 +21,7 @@ ## file: arch/parisc/Kconfig.debug ## # CONFIG_DEBUG_RODATA is not set +CONFIG_DEBUG_STACKOVERFLOW=y ## ## file: block/partitions/Kconfig Index: linux/debian/config/hppa/config.parisc64-smp === --- linux/debian/config/hppa/config.parisc64-smp (revision 20943) +++ linux/debian/config/hppa/config.parisc64-smp (working copy) @@ -19,8 +19,8 @@ ## file: drivers/char/agp/Kconfig ## #. for ATI FireGL DRM in C8000 workstation -CONFIG_AGP=m -CONFIG_AGP_PARISC=m +CONFIG_AGP=y +CONFIG_AGP_PARISC=y ## ## file: drivers/gpu/drm/Kconfig Index: linux/debian/installer/hppa/kernel-versions === --- linux/debian/installer/hppa/kernel-versions (revision 20943) +++ linux/debian/installer/hppa/kernel-versions (working copy) @@ -1,3 +1,3 @@ -# arch version flavour installedname suffix build-depends -hppa - parisc - y - -hppa - parisc64 - y - +# arch version flavour installedname suffix build-depends +hppa - parisc - y - +hppa - parisc64-smp - y -
Bug#733897: parisc patch for kernel 3.13
Package: linux Version: 3.13 Severity: bug Tags: patch As soon as the debian kernel will start with kernel 3.13, please remove the CONFIG_MLONGCALLS=y option as it's then not any longer needed. The option is still needed in the = 3.12 kernel. (This is a follow-up on Bug# 721191) Index: linux/debian/config/hppa/config.parisc64-smp === --- linux/debian/config/hppa/config.parisc64-smp(revision 20943) +++ linux/debian/config/hppa/config.parisc64-smp(working copy) @@ -8,7 +8,6 @@ CONFIG_64BIT=y CONFIG_SMP=y CONFIG_NR_CPUS=8 -CONFIG_MLONGCALLS=y ## ## file: drivers/ata/Kconfig
Bug#652459: initramfs-tools: [patch] Please support mounting of /usr in the initramfs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, I just stumpled over this one. Am Di den 23. Jul 2013 um 18:48 schrieb Michael Prokop: Does anyone have any objections against the current implementation of #652459 to support mounting of /usr in the initramfs? Yes, I have. Sorry about. This will prevent from using /usr via NFS or having a /usr md device or having /usr on LVM (Not sure about any of this issues, as I use initram only on systems with a NFS /usr.) And there is even more cases where the /usr mount needs to be done later in init stack. And I even fear about what to solve with this patch. I usually use a non-initram-kernel to boot my systems and have /usr on separate device. My fantasy tells me that the patch should solve some issues that was brought to debian by systemd. Just my fantasy. I hope, I am wrong with this. Regards Klaus Ethgen - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen kl...@ethgen.de Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iQGcBAEBCgAGBQJSxJRtAAoJEKZ8CrGAGfaspEQL/R/s+vrCU9fR1KV//6Ufx3zr z26KjnYlvMHpAevb17fqbqBrMYm1nJRFtIW85bCIx/jkVgG5yXj4SViVkuWKK8oS 9ZMIqeOsuAeyEizxUZ6OUwQ9fWlbKtvd85mveZqDwvivoSwR30G2Pu7KWqqZHjli 9rCEgSaLoAGmpIvPN+wpQpYjVbDsI5MmyvKCgTu7OUkAP0xZKZEfVlKsl3l9mitw 8iO89kHjVYTI2f1LN8hzR/TbZYNXA4YRf6SZ6RqRzNHGip2j8D2AlMYVoa3L/RzL m8ql1Ok7VYsqe1aRPvxSIAUSjS9Auf458/wdODoEoZtyGWTG2GLWzmT+KZX1HUZ6 ERvWgg7F3EwC9TklPmti+cvN1rL46KH0pbtg6oIA6m4BKqi+74hdyBeDlnhbNPYc iEodPCf9ohWt9pmA6nLlPhveCT6AqmKh1i3nPlSXU0g88jpdUpVTISvenv4k+SNj Ct7xOLQ/qcPIGhbKsb3FeNNxXJabYhTjMu8qGUQzfw== =nPfm -END PGP SIGNATURE- -- 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/20140101221925.ga6...@ikki.ethgen.ch
Bug#652459: initramfs-tools: [patch] Please support mounting of /usr in the initramfs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 01, Klaus Ethgen kl...@ethgen.de wrote: What is being discussed in this bug is not if /usr should be mounted in the initramfs or not. This is a widely accepted design. The purpose of this bug is to implement it in the best way. This will prevent from using /usr via NFS or having a /usr md device or having /usr on LVM (Not sure about any of this issues, as I use initram only on systems with a NFS /usr.) Yes, you are wrong. And thanks to this patch in the future it will be possibile to mount all static OS data via NFS with an everything-in-/usr setup. And there is even more cases where the /usr mount needs to be done later in init stack. Care to show some of these use cases? And I even fear about what to solve with this patch. I usually use a non-initram-kernel to boot my systems and have /usr on separate device. This will not be a supported configuration anymore. - -- ciao, Marco -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iEYEARECAAYFAlLElo8ACgkQFGfw2OHuP7GD8gCdEw4y2PfU0T+BVKjnVf/PRF/E 8rcAn3A4J2RFFy7ac78otGTuGGi/mDPx =m3uZ -END PGP SIGNATURE- -- 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/20140101222831.ga31...@bongo.bofh.it
Bug#697019: marked as done (linux-image-3.2.0-4-amd64: USB 3.0 ext HDD drive doesnt work and hangs usb 3.0 hub)
Your message dated Thu, 02 Jan 2014 00:17:02 + with message-id 1388621822.22017.1.ca...@deadeye.wl.decadent.org.uk and subject line Re: Bug#697019: Bug is fixed: at least for stable debian 7 kernel SMP Debian 3.2.51-1 x86_64 has caused the Debian Bug report #697019, regarding linux-image-3.2.0-4-amd64: USB 3.0 ext HDD drive doesnt work and hangs usb 3.0 hub to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 697019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:linux Version: 3.2.35-2 Severity: normal Problem take place for portable usb 3.0 HDD (no external power source). There are two USB 3.0 ports at my laptop. There is no problem with USB 2.0 HDD and various USB 1.1 devices (such as mouse) at the usb 3.0 ports. When I plug usb 3.0 HDD device, hdd led goes On, after 5-7 sec hdd led goes Off. Hdd is not mounted. After that fail, both USB 3.0 ports became completely unusable (until reboot). Laptop Lenovo Thinkpad Edge 330G (3354-24G), CPU: Pentium B970, chipset: Intel HM77 Express, IO Controller: Intel Corporation 7 Series/C210 Series Chipset, In BIOS menu, USB 3.0 Support=Enabled problematic device: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub kernel log file comments: I've made the following actions: 1) attach USB 3.0 HDD drive (Seagate 500Gb) to USB 2.0 port, device is mounted properly. Unmount and detach. 2) attach old usb 2.0 HDD drive (Transcend 160Gb) to USB 3.0 port, device is mounted properly. Unmount and detach. 3) attach USB 3.0 HDD drive (Seagate 500Gb) to USB 2.0 port, device is not mounted, both USB 3.0 ports became unusable -- 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-14) ) #1 SMP Debian 3.2.35-2 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 root=UUID=5e0a1d7f-3997-43f1-931f-ce10d19ee440 ro quiet ** Tainted: PCO (5121) * Proprietary module has been loaded. * Module from drivers/staging has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [7.025540] sd 6:0:0:0: [sdb] Attached SCSI removable disk [7.477404] fbcon: inteldrmfb (fb0) is primary device [7.661640] Console: switching to colour frame buffer device 170x48 [7.665231] fb0: inteldrmfb frame buffer device [7.665233] drm: registered panic notifier [7.667136] acpi device:47: registered as cooling_device2 [7.667369] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input10 [7.667418] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [7.667466] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [8.914523] Adding 9764860k swap on /dev/sda5. Priority:-1 extents:1 across:9764860k [8.945570] EXT4-fs (sda2): re-mounted. Opts: (null) [9.514518] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro [9.629825] loop: module loaded [ 11.148729] IBM TrackPoint firmware: 0x0e, buttons: 3/3 [ 11.330414] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input11 [ 13.803327] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null) [ 13.935770] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null) [ 14.035077] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null) [ 14.126082] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) [ 15.511759] RPC: Registered named UNIX socket transport module. [ 15.511764] RPC: Registered udp transport module. [ 15.511767] RPC: Registered tcp transport module. [ 15.511770] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 15.550982] FS-Cache: Loaded [ 15.616493] FS-Cache: Netfs 'nfs' registered for caching [ 15.644544] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 18.138183] vboxdrv: Found 2 processor cores. [ 18.138595] vboxdrv: fAsync=0 offMin=0x8f0 offMax=0x1eae [ 18.138711] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. [ 18.138716] vboxdrv: Successfully loaded version 4.1.18_Debian (interface 0x0019). [ 18.255433] vboxpci: IOMMU not found (not registered) [ 18.787906] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input12 [ 20.497047] Bluetooth: Core ver 2.16 [ 20.497067] NET: Registered protocol family 31 [ 20.497069] Bluetooth: HCI device and connection manager initialized [ 20.497072] Bluetooth: HCI socket layer initialized [ 20.497074] Bluetooth: L2CAP socket layer
Processed: Re: Bug#733826: crazy loop xhci_hcd Too many fragments
Processing control commands: severity -1 normal Bug #733826 [src:linux] crazy loop xhci_hcd Too many fragments Severity set to 'normal' from 'wishlist' notfound -1 3.11.10-1 Bug #733826 [src:linux] crazy loop xhci_hcd Too many fragments No longer marked as found in versions linux/3.11.10-1. found -1 3.12.6-1 Bug #733826 [src:linux] crazy loop xhci_hcd Too many fragments Marked as found in versions linux/3.12.6-1. clone -1 -2 Bug #733826 [src:linux] crazy loop xhci_hcd Too many fragments Bug 733826 cloned as bug 733907 retitle -1 xhci_hcd 'Too many fragments' warning appears Bug #733826 [src:linux] crazy loop xhci_hcd Too many fragments Changed Bug title to 'xhci_hcd 'Too many fragments' warning appears' from 'crazy loop xhci_hcd Too many fragments' retitle -2 xhci_hcd 'Too many fragments' warning should be rate-limited Bug #733907 [src:linux] crazy loop xhci_hcd Too many fragments Changed Bug title to 'xhci_hcd 'Too many fragments' warning should be rate-limited' from 'crazy loop xhci_hcd Too many fragments' -- 733826: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733826 733907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733907 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.b733826.138863345728967.transcr...@bugs.debian.org
Bug#733826: crazy loop xhci_hcd Too many fragments
Control: severity -1 normal Control: notfound -1 3.11.10-1 Control: found -1 3.12.6-1 Control: clone -1 -2 Control: retitle -1 xhci_hcd 'Too many fragments' warning appears Control: retitle -2 xhci_hcd 'Too many fragments' warning should be rate-limited On Wed, 2014-01-01 at 07:33 +0800, jida...@jidanni.org wrote: Package: src:linux Version: 3.11.10-1 No, this message did not exist in that version. Severity: wishlist Whatever you do, please add some break out code. Do not just loop putting # grep -c xhci /var/log/syslog 1052792 lines of xhci_hcd :00:14.0: Too many fragments 79, max 63 swelling # ls -l /var/log/syslog -rw-r- 1 root adm 107977515 01-01 07:17 /var/log/syslog Is any other error message logged? Which USB devices are you using (this is probably disk or network related)? Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong. signature.asc Description: This is a digitally signed message part
