Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org:
# Wed Jun 29 08:03:27 UTC 2011
# Tagging as pending bugs that are closed by packages in NEW
# http://ftp-master.debian.org/new.html
#
# Source package in NEW: libinternals-perl
tags 631855 + pending
Bug #631855 [wnpp] ITP: libinternals-perl -- Perl module for write-protect
variables, manipulate refcounts
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 631255 + pending
Bug #631255 {Done: maximilian attems m...@debian.org} [linux-2.6]
linux-image-3.0.0-rc3-amd64: aptitude install triggers kerneloops
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 631802 + pending
Bug #631802 {Done: maximilian attems m...@debian.org} [linux-2.6]
linux-image-3.0.0-rc3-686-pae: kernel oops while running 'aptitude install' on
a package
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 631199 + pending
Bug #631199 {Done: maximilian attems m...@debian.org} [linux-2.6]
linux-image-2.6.39-2-amd64: comedi modules are missing
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 631762 + pending
Bug #631762 {Done: maximilian attems m...@debian.org}
[linux-image-2.6.39-2-kirkwood] linux-image-2.6.39-2-kirkwood: please enable
CONFIG_SND_KIRKWOOD_SOC_T5325
Added tag(s) pending.
# Source package in NEW: kst
tags 615738 + pending
Bug #615738 [kst] kst: ftbfs with gold or ld --no-add-needed
Added tag(s) pending.
# Source package in NEW: kst
tags 589685 + pending
Bug #589685 [wnpp] ITA: kst -- application for scientific data displaying
Added tag(s) pending.
# Source package in NEW: kst
tags 553793 + pending
Bug #553793 [kst] replacing libreadline5-dev build dependency with
libreadline-dev
Added tag(s) pending.
# Source package in NEW: kst
tags 604335 + pending
Bug #604335 [src:kst] Please package KDE 4 port
Added tag(s) pending.
# Source package in NEW: s3ql
tags 626651 + pending
Bug #626651 [wnpp] ITP: s3ql -- a full-featured file system for online data
storage
Added tag(s) pending.
End of message, stopping processing here.
Please contact me if you need assistance.
--
626651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626651
589685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589685
553793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553793
604335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604335
615738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615738
631255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631255
631199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631199
631855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631855
631802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631802
631762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631762
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.130933469413520.transcr...@bugs.debian.org
Bug#631942: linux-image-3.0.0-rc4-686-pae: oops and/or hangs when mounting a samba share
Le 29/06/11 06:11, Ben Hutchings a écrit : There have been a lot of fixes to CIFS in 3.0-rc5; please can you test the new package in experimental? hello, tried rc5 this morning, it also oopses thanks, -- Rémi -- 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/4e0af189.8040...@poukram.net
Bug#632044: linux-image-2.6.32-5-amd64: Sandisk Cruzer U3 memory stick not usable
Package: linux-2.6 Version: 2.6.32-35 Severity: normal Hi, i am experiencing problems between Debian 6.0.2 and a Sandisk Cruzer U3 memory stick (4 GB). These sticks appear as USB hub with an emulated CD-ROM drive and a memory stick storage device. So Linux creates /dev/srN as well as /dev/sdX and /dev/sdX1 when such a stick is plugged in. But Debian 6.0.2 drops the devices a few seconds after they appear. /var/log/messages reports a normal installation of the devices, then an unrecoverable error with an SCSI command READ(10), then it resets the USB device multiple times, and finally drops the device files. If i kill the udisks demon, the devices do not vanish and i can read at ~ 900 kB/s from the /dev/sr2 device. But reading from the /dev/sdb device stalls and causes the device files to vanish after some seconds. /var/log/messages lines are similar to those with udisks enabled. The hardware is not to blame alone. I booted RIPLinuX 9.3 (slackware based) on the same machine. No problems with reading the entire memory stick. Speed is 23 MB/s. A SuSE on an older machine could read at 6 MB/s. --- $ uname -a Linux debian2 2.6.32-5-amd64 #1 SMP Tue Jun 14 09:42:28 UTC 2011 x86_64 GNU/Linux $ dpkg -l | grep ^ii | grep linux-image ii linux-image-2.6-amd642.6.32+29 Linux 2.6 for 64-bit PCs (meta-package) ii linux-image-2.6.32-5-amd64 2.6.32-35 Linux 2.6.32 for 64-bit PCs --- With udisks demon still active and trying to automount, i got: --- Jun 26 09:44:22 debian2 kernel: [165443.464304] usb 1-3.2: new high speed USB device using ehci_hcd and address 27 Jun 26 09:44:22 debian2 kernel: [165443.557530] usb 1-3.2: New USB device found, idVendor=0781, idProduct=5406 Jun 26 09:44:22 debian2 kernel: [165443.557539] usb 1-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jun 26 09:44:22 debian2 kernel: [165443.557546] usb 1-3.2: Product: U3 Cruzer Micro Jun 26 09:44:22 debian2 kernel: [165443.557551] usb 1-3.2: Manufacturer: SanDisk Jun 26 09:44:22 debian2 kernel: [165443.557555] usb 1-3.2: SerialNumber: 0164620760128686 Jun 26 09:44:22 debian2 kernel: [165443.557757] usb 1-3.2: configuration #1 chosen from 1 choice Jun 26 09:44:22 debian2 kernel: [165443.558188] scsi15 : SCSI emulation for USB Mass Storage devices Jun 26 09:44:27 debian2 kernel: [165448.557054] scsi 15:0:0:0: Direct-Access SanDisk Cruzer 8.02 PQ: 0 ANSI: 0 CCS Jun 26 09:44:27 debian2 kernel: [165448.557680] scsi 15:0:0:1: CD-ROM SanDisk Cruzer 8.02 PQ: 0 ANSI: 0 Jun 26 09:44:27 debian2 kernel: [165448.558693] sd 15:0:0:0: Attached scsi generic sg4 type 0 Jun 26 09:44:27 debian2 kernel: [165448.561374] sd 15:0:0:0: [sdb] 7864319 512-byte logical blocks: (4.02 GB/3.74 GiB) Jun 26 09:44:27 debian2 kernel: [165448.562519] sd 15:0:0:0: [sdb] Write Protect is off Jun 26 09:44:27 debian2 kernel: [165448.563570] sr3: scsi3-mmc drive: 48x/48x tray Jun 26 09:44:27 debian2 kernel: [165448.563970] sr 15:0:0:1: Attached scsi generic sg5 type 5 Jun 26 09:44:27 debian2 kernel: [165448.565121] sdb: sdb1 Jun 26 09:44:27 debian2 kernel: [165448.567643] sd 15:0:0:0: [sdb] Attached SCSI removable disk Jun 26 09:44:57 debian2 kernel: [165478.853879] usb 1-3.2: reset high speed USB device using ehci_hcd and address 27 Jun 26 09:45:28 debian2 kernel: [165509.880686] usb 1-3.2: reset high speed USB device using ehci_hcd and address 27 Jun 26 09:45:59 debian2 kernel: [165540.365260] usb 1-3.2: reset high speed USB device using ehci_hcd and address 27 Jun 26 09:46:29 debian2 kernel: [165570.829581] usb 1-3.2: reset high speed USB device using ehci_hcd and address 27 Jun 26 09:46:50 debian2 kernel: [165591.417455] sd 15:0:0:0: Device offlined - not ready after error recovery Jun 26 09:46:50 debian2 kernel: [165591.417478] sd 15:0:0:0: [sdb] Unhandled error code Jun 26 09:46:50 debian2 kernel: [165591.417484] sd 15:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK Jun 26 09:46:50 debian2 kernel: [165591.417492] sd 15:0:0:0: [sdb] CDB: Read(10): 28 00 00 77 ff fd 00 00 01 00 Jun 26 09:46:50 debian2 kernel: [165591.417606] usb 1-3.2: USB disconnect, address 27 Jun 26 09:46:50 debian2 kernel: [165591.417989] sr 15:0:0:1: [sr3] Unhandled error code Jun 26 09:46:50 debian2 kernel: [165591.417994] sr 15:0:0:1: [sr3] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK Jun 26 09:46:50 debian2 kernel: [165591.418002] sr 15:0:0:1: [sr3] CDB: Read(10): 28 00 00 00 00 13 00 00 01 00 Jun 26 09:46:50 debian2 kernel: [165591.418078] sr 15:0:0:1: [sr3] Unhandled error code Jun 26 09:46:50 debian2 kernel: [165591.418083] sr 15:0:0:1: [sr3] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK Jun 26 09:46:50 debian2 kernel:
Bug#632064: linux-headers-2.6-amd64: Bluetooth turns off automatically
Package: linux-headers-2.6-amd64 Version: 2.6.32+28 Severity: important After upgrading my kernel to 2.6.39 bluetooth turns off few secondes after I turn it on by keyboard switch. then to turn it on again I should click on the bluetooth icon in the tray and turn it on again. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-headers-2.6-amd64 depends on: ii linux-headers-2.6.32-5-amd64 2.6.32-28 Header files for Linux 2.6.32-5-am linux-headers-2.6-amd64 recommends no packages. linux-headers-2.6-amd64 suggests no packages. -- no debconf information -- 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/20110629115834.2916.59314.reportbug@keivan-laptop
Bug#631997: linux-image-2.6.39-2-486: black screen after grub menu
On Wed, 2011-06-29 at 04:22 +0100, Ben Hutchings wrote: On Tue, 2011-06-28 at 23:12 -0400, Wendy Elmer wrote: [...] I will try the earlier versions when I get a chance. It may not be very soon since that computer is at my church and I will be on vacation for a week. By the way, since I will be using snapshot, is there a config file for APT that I can put something to handle the snapshots being expired? See bug 595801. It is a pain when going to snapshot in synaptic and getting the release file expired message. I drop out to the command line and do apt-get -o 'Acquire::Check-Valid-Until=false' update from the command line to get around it. Sorry, I have no better idea. recovery mode does not work either. Still an endless black screen after grub with no messages from the kernel. What processor and how much RAM does this systeam have? Ben. It is an AMD Athlon 850 MHZ. It is maxed out at a whopping 256 MB ram. It is an old HP computer which has very oddball hardware that I am trying to keep crippling along because the church doesn't have the money to buy a better one. The reason I am running the old custom kernel is because it has an oddball conexant riptide sound card that I have to special handle in the kernel build(3rd party driver and firmware) in order to make it work and it is a pain. Brent -- 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/1309349901.4874.7.camel@belmer
Bug#632074: linux-2.6: NFS4 client sends NULL calls in the TCP session
Package: linux-2.6 Severity: important After kernel upgrade, our debian machines connected through NFSv4 to a NetApp filer cause the log of warning messages by the NAS : Client 1XX.1XX.2XX.73 has an authentication error 2 Client 1XX.1XX.2XX.73 is sending bad rpc requests with error: RPC version mismatch or authentication error(73) This does not prevent the use of the file system, but seems to be a violation of the NFS 4 protocol (see below) This is known to happen with the following version of linux-image : 2.6.32-5-amd64 2.6.32-5-686-bigmem 2.6.29-xs5.5.0.17 and is known not to happen with the follwing versions : 2.6.18.xs4.0.1.900.5799 2.6.26-2-686 Some of the system listed above are virtual machines on XenServer 5.5 or 5.6 hosts, but some are physical machine, so I discard the possibility of a problem on the xen version of the kernel. A ticket has been filed bus us to the NetApp support, and after an analysis of the tcp trace they sent back the problem to the client side. Below see the analysis by NetApp of this issue, and the description of the protocl exchange creating this issue. --- Tue May 24 10:05:59 MEST [vcid@s-jrciprna004p: nfsd.rpc.request.bad:warning]: Client 1XX.1XX.2XX.73 is sending bad rpc requests with error: RPC version mismatch or authentication error(73) We looked in the code and the (73) has no significance here and is simply the error code number for RPC version mismatch or authentication error. What we see is that the following occurs at the time of these errors: - The client has an established TCP session on which it does NFSv4. - The NFSv4 calls uses Kerberos. - On that TCP session, the client occasionally does a NULL call. - The filer rejects it with an authentication error (auth state 2, client must begin new session) - The client does a new NULL call on a separate TCP session without a GSS context. - The filer responds and a new context is established. - The client continues on the original TCP session with the new context. This explains why no side effect is seen: the client simply establishes a new context and continues as if nothing had happened. We have checked through the trace for vlan 240 and the pattern is the same throughout and the error always happens for NULL calls only (occasionally two replies may be sent in the same TCP payload, but the error is always on the NULL reply, then). We know that some Debian kernels do not exhibit this problem at any time, but others do. This (along with the problem being tied to NULL calls only) suggest to us that this is due to client side behaviour. Anyway, we tried to check for the first occurrence of the error, which warrants some chronology. We'll do references per clock second for ease. - The first client call is at 10:04:16 in an established NFS mount. - The initial part of the trace, the client only uses TCP port 1006. - The client uses the same GSS context, with the exception of a SETCLIENTID and a SETCLIENTID_CONFIRM call. - At 10:05:00 the client tears down four GSS sessions (used for Kerberos) using RPCSEC_GSS_DESTROY in an NFSv4 NULL call. This is done from TCP port 1006 but for four different contexts. None of these have been used in the trace at that point. - The client continues with more cals on port 1006 using the the same GSS context. - Still at 10:05:00 (frame 1982792), the client uses an NFSv4 call to do a RPCSEC_GSS_INIT to establish a new GSS context. - The client continues using the new GSS context and does not reuse the old context. - The sequence described above on the NULL calls start. Looking closer at these steps, we notice something important in the NULL calls. Above, the client destroyed four GSS contexts that were not used during the trace. However, it did not destroy the GSS context it was using for a while there. However, we now note the client actually does a RPCSEC_GSS_DESTROY in each of the NFSv4 NULL calls where we respond with an authentication error. As the error indicates that the client has to begin a new session, this seems like a reasonable response to the call. So to summarise: - The filer logs these errors when the client destroys a GSS context. - The error message is a logical response. The decission to tear down the GSS context is with the client. So this would seem to be a client side issue after all, which just happens to get logged on the filer. -- -- System Information: Debian Release: 5.0.8 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) 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 Archive: http://lists.debian.org/20110629114800.2859.34873.report...@s-jrciprcid73v.cidsn.jrc.it
Bug#632074: linux-2.6: NFS4 client sends NULL calls in the TCP session
severity 632074 normal tags 632074 moreinfo thanks On Wed, Jun 29, 2011 at 01:48:00PM +0200, Franck Eyraud wrote: This does not prevent the use of the file system, but seems to be a violation of the NFS 4 protocol (see below) Please cite the appropriate parts of the RFC. It seems to be RFC 3530. | 14.1. Procedure 0: NULL - No Operation |SYNOPSIS | null |ARGUMENT | void; |RESULT | void; |DESCRIPTION | Standard NULL procedure. Void argument, void response. This | procedure has no functionality associated with it. Because of | this it is sometimes used to measure the overhead of processing a | service request. Therefore, the server should ensure that no | unnecessary work is done in servicing this procedure. |ERRORS | None. According to this, a response to a NULL request simply must not return an authentication error. Also no erata exists for this part. This is known to happen with the following version of linux-image : 2.6.32-5-amd64 2.6.32-5-686-bigmem 2.6.29-xs5.5.0.17 and is known not to happen with the follwing versions : 2.6.18.xs4.0.1.900.5799 2.6.26-2-686 You saw that the versions of the ones with the behaviour are strictly higher then the others? Please fix your MUA, it produces too long lines, and ask on linux-...@vger.kernel.org. Bastian -- You! What PLANET is this! -- McCoy, The City on the Edge of Forever, stardate 3134.0 -- 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/20110629133811.ga32...@wavehammer.waldi.eu.org
Processed: Re: Bug#632074: linux-2.6: NFS4 client sends NULL calls in the TCP session
Processing commands for cont...@bugs.debian.org: severity 632074 normal Bug #632074 [linux-2.6] linux-2.6: NFS4 client sends NULL calls in the TCP session Severity set to 'normal' from 'important' tags 632074 moreinfo Bug #632074 [linux-2.6] linux-2.6: NFS4 client sends NULL calls in the TCP session Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 632074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632074 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.13093547025398.transcr...@bugs.debian.org
Processed: reassign 632064 to src:linux-2.6, found 632064 in 2.6.39-2
Processing commands for cont...@bugs.debian.org: reassign 632064 src:linux-2.6 Bug #632064 [linux-headers-2.6-amd64] linux-headers-2.6-amd64: Bluetooth turns off automatically Bug reassigned from package 'linux-headers-2.6-amd64' to 'src:linux-2.6'. Bug No longer marked as found in versions linux-latest-2.6/28. found 632064 2.6.39-2 Bug #632064 [src:linux-2.6] linux-headers-2.6-amd64: Bluetooth turns off automatically Bug Marked as found in versions linux-2.6/2.6.39-2. thanks Stopping processing here. Please contact me if you need assistance. -- 632064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632064 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.13093548035712.transcr...@bugs.debian.org
Bug#632064: linux-headers-2.6-amd64: Bluetooth turns off automatically
On Wed, 2011-06-29 at 16:28 +0430, Keivan Moradi wrote: Package: linux-headers-2.6-amd64 Version: 2.6.32+28 That is a meta-package to supporting building additional kernel modules. The correct package for the kernel you are running is linux-image-2.6.39-2-amd64. Well, never mind, I have reassigned this. Severity: important After upgrading my kernel to 2.6.39 bluetooth turns off few secondes after I turn it on by keyboard switch. then to turn it on again I should click on the bluetooth icon in the tray and turn it on again. Can you send the output of the command: grep . /sys/class/rfkill/*/* under 2.6.39, and under the previous version you were using. Ben. -- Ben Hutchings If at first you don't succeed, you're doing about average. signature.asc Description: This is a digitally signed message part
Bug#632088: dd to a usb drive triggers kernel bug
Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-35 Working on a Tyan 5382 system equipped with Debian 6.0.1 AMD64. After inserting a common USB-based flash drive into a USB port I attempted to raw write a bootable amd64 image generated with live-build: dd if=binary.img of=/dev/sdb where /dev/sdb is the device name assigned to the USB flash drive. The result was a failed write and the trace shown below. I use live-build on i386 on Debian 6 and have not experienced this problem on that architecture. I copied the image over to another Debian 6.0.1 AMD64 system installed on a brand-new Gigabyte GA-P67X-UD3-B3 motherboard and the problem does NOT occur. Thus, it appears to be specific to the Tyan 5382 board. --- USB controllers shown via lspci -v on Tyan 5382: 00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09) (prog-if 00 [UHCI]) Subsystem: Intel Corporation Device 5380 Flags: bus master, medium devsel, latency 0, IRQ 17 I/O ports at 1800 [size=32] Kernel driver in use: uhci_hcd 00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09) (prog-if 00 [UHCI]) Subsystem: Intel Corporation Device 5380 Flags: bus master, medium devsel, latency 0, IRQ 19 I/O ports at 1820 [size=32] Kernel driver in use: uhci_hcd 00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09) (prog-if 00 [UHCI]) Subsystem: Intel Corporation Device 5380 Flags: bus master, medium devsel, latency 0, IRQ 18 I/O ports at 1840 [size=32] Kernel driver in use: uhci_hcd 00:1d.3 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09) (prog-if 00 [UHCI]) Subsystem: Intel Corporation Device 5380 Flags: bus master, medium devsel, latency 0, IRQ 16 I/O ports at 1860 [size=32] Kernel driver in use: uhci_hcd 00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09) (prog-if 20 [EHCI]) Subsystem: Intel Corporation Device 5380 Flags: bus master, medium devsel, latency 0, IRQ 17 Memory at d870 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Kernel driver in use: ehci_hcd --- Kernel trace: [ cut here ] kernel BUG at /build/buildd-linux-2.6_2.6.32-35-amd64-aZSlKL/linux-2.6-2.6.32/debian/build/source_amd64_none/mm/slub.c:2969! invalid opcode: [#1] SMP last sysfs file: /sys/devices/pci:00/:00:1d.7/usb1/1-4/1-4:1.0/host2/target2:0:0/2:0:0:0/block/sdb/removable CPU 1 Modules linked in: usb_storage nls_utf8 nls_cp437 vfat fat ppdev lp sco bridge stp bnep l2cap crc16 bluetooth rfkill cpufreq_stats cpufreq_powersave cpufreq_userspace cpufreq_conservative binfmt_misc fuse loop radeon ttm drm_kms_helper drm i5000_edac i2c_algo_bit parport_pc i2c_i801 edac_core parport i2c_core rng_core pcspkr shpchp i5k_amb ioatdma psmouse dca container pci_hotplug evdev button serio_raw processor ext3 jbd mbcache sg sr_mod cdrom sd_mod crc_t10dif ata_generic uhci_hcd ata_piix libata ehci_hcd floppy e1000 e1000e scsi_mod thermal thermal_sys usbcore nls_base [last unloaded: scsi_wait_scan] Pid: 7400, comm: usb-storage Not tainted 2.6.32-5-amd64 #1 empty RIP: 0010:[810e730b] [810e730b] kfree+0x55/0xcb RSP: 0018:88003d03bcd0 EFLAGS: 00010246 RAX: 0200086c RBX: 88012d753658 RCX: 00150014 RDX: 88012d753658 RSI: ea00041f6f08 RDI: ea000380 RBP: 8801 R08: R09: 81452c20 R10: 880037801180 R11: 814634c0 R12: a000ef01 R13: 88003d03bd5c R14: 1000 R15: c0010280 FS: () GS:88000550() knlGS: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b CR2: 02396000 CR3: 00012d168000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process usb-storage (pid: 7400, threadinfo 88003d03a000, task 88012d018000) Stack: 88012d753658 88012d7535a0 88012d753658 a000ef01 0 88012d7535e0 a035d3d2 0010 0 88003d03bd10 8800b517b000 880072c03000 8800b517b000 Call Trace: [a000ef01] ? sg_clean+0x2f/0x64 [usbcore] [a035d3d2] ? usb_stor_bulk_transfer_sglist+0x7f/0xd1 [usb_storage] [a035d441] ? usb_stor_bulk_srb+0x1d/0x2b [usb_storage] [a035d5cf] ? usb_stor_Bulk_transport+0xf5/0x24c [usb_storage] [a035ce00] ? usb_stor_invoke_transport+0x35/0x32d [usb_storage] [812fb3ff] ? wait_for_common+0xe9/0x15b
Bug#632088: dd to a usb drive triggers kernel bug
On Wed, Jun 29, 2011 at 11:21:55AM -0400, Doug Vetter wrote: Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-35 Working on a Tyan 5382 system equipped with Debian 6.0.1 AMD64. After inserting a common USB-based flash drive into a USB port I attempted to raw write a bootable amd64 image generated with live-build: dd if=binary.img of=/dev/sdb where /dev/sdb is the device name assigned to the USB flash drive. [...] The kernel error messages indicate memory corruption. Could be a hardware or software error. Have you seen other crashes on this system recently? Can you test the RAM using the memtest86+ package? Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/20110629153305.gd29...@decadent.org.uk
Processed: tagging 632088
Processing commands for cont...@bugs.debian.org: tags 632088 + moreinfo Bug #632088 [linux-image-2.6.32-5-amd64] dd to a usb drive triggers kernel bug Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 632088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632088 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.130936159922514.transcr...@bugs.debian.org
Bug#632074: linux-2.6: NFS4 client sends NULL calls in the TCP session
On 29/06/2011 15:38, Bastian Blank wrote: According to this, a response to a NULL request simply must not return an authentication error. Also no erata exists for this part. As I'm not an NFS expert, if someone can prove that the problem is on the server part, despite the analysis from NetApp, then I'll send back the case to them. You saw that the versions of the ones with the behaviour are strictly higher then the others? Yes I did, that's why I inserted this information. I guess some behaviour changed in some version upgrade. Please fix your MUA, it produces too long lines, and ask on linux-...@vger.kernel.org. I will ask them also. Thanks -- 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/4e0b33c6.8040...@jrc.ec.europa.eu
Bug#632088: dd to a usb drive triggers kernel bug
On 06/29/2011 11:33 AM, Ben Hutchings wrote: On Wed, Jun 29, 2011 at 11:21:55AM -0400, Doug Vetter wrote: Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-35 Working on a Tyan 5382 system equipped with Debian 6.0.1 AMD64. After inserting a common USB-based flash drive into a USB port I attempted to raw write a bootable amd64 image generated with live-build: dd if=binary.img of=/dev/sdb where /dev/sdb is the device name assigned to the USB flash drive. [...] The kernel error messages indicate memory corruption. Could be a hardware or software error. Have you seen other crashes on this system recently? No. This is a stable development box I've been using for several years without issue. Until I installed 6.0.1 AMD64 a couple days ago it was most recently running Debian 6.0.0 i386 with no issues, and I was doing the same dd operation on that architecture. The problem only appeared when I attempted that operation under 6.0.1 AMD64. Can you test the RAM using the memtest86+ package? Ran it for an hour or so, no errors noted. Physical memory is ECC, by the way. -Doug -- Doug Vetter Packetstorm Communications, Inc. 732-544-2434 x201 -- 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/4e0b4a76.1030...@packetstorm.com
Bug#631963: linux-image-3.0.0-rc4-686-pae: no sound out the rear plugs
Hi, On Wed, 29.06.2011 at 07:21:33 +0200, Takashi Iwai ti...@suse.de wrote: I'd definitely need alsa-info.sh outputs on both working and non-working kernels, i.e. on 2.6.38 and 3.0-rc4. this first post is for the non-working kernel. The other kernel's information will follow tomorrow. Kind regards, --Toni++ upload=truescript=truecardinfo= !! !!ALSA Information Script v 0.4.60 !! !!Script ran on: Wed Jun 29 18:43:33 UTC 2011 !!Linux Distribution !!-- Debian GNU/Linux 6.0 \n \l !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version !!Kernel Information !!-- Kernel release:3.0.0-rc4-686-pae Operating System: GNU/Linux Architecture: i686 Processor: unknown SMP Enabled: Yes !!ALSA Version !! Driver version: 1.0.24 Library version:1.0.23 Utilities version: 1.0.23 !!Loaded ALSA modules !!--- snd_hda_intel snd_hda_intel !!Sound Servers on this system !! ESound Daemon: Installed - Yes (/usr/bin/esd) Running - No aRts: Installed - Yes (/usr/bin/artsd) Running - No !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe8f irq 16 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xfeaf4000 irq 19 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) 01:05.1 Audio device: ATI Technologies Inc RS880 Audio Device [Radeon HD 4200] !!Advanced information - PCI Vendor/Device/Subsystem ID's !! 00:14.2 0403: 1002:4383 Subsystem: 1043:841b -- 01:05.1 0403: 1002:970f Subsystem: 1043:843e !!Modprobe options (Sound related) !! snd-atiixp-modem: index=-2 snd-intel8x0m: index=-2 snd-via82xx-modem: index=-2 snd-pcsp: index=-2 snd-usb-audio: index=-2 !!Loaded sound module options !!-- !!Module: snd_hda_intel bdl_pos_adj : 32,32,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1 enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 model : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) patch : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) position_fix : 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 power_save : 0 power_save_controller : Y probe_mask : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 probe_only : 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 single_cmd : N !!Module: snd_hda_intel bdl_pos_adj : 32,32,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1 enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 model : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) patch : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
[m68k] Patches for 3.0 (was Re: linux-2.6_2.6.39-1_amd64.changes ACCEPTED into unstable)
Hi Debian Kernel team,
can we please have these for 3.0? They will be in 3.1, and replace
0008-m68k-atari-Reserve-some-ST-RAM-early-on-for-device-b.patch
from 2.6.38-2, addressing the same problem (garbled video output
when the machine has too much FastRAM).
Thanks!
Geert Uytterhoeven dixit:
On Wed, Jun 29, 2011 at 19:38, Thorsten Glaser t...@mirbsd.de wrote:
Geert Uytterhoeven dixit:
I folded it into your previous patch and pushed it out for 3.1.
Can you make a patch (series) on top of 3.0 and mail that to
debian-kernel asking for inclusion in the next 3.0 upload, on
the ground it’s been accepted upstream and fixes UI problems?
The two patches you need are
http://git.kernel.org/?p=linux/kernel/git/geert/linux-m68k.git;a=commitdiff;h=1789c38726c2805563e9049dbc5d5253251761a7
http://git.kernel.org/?p=linux/kernel/git/geert/linux-m68k.git;a=commitdiff;h=10b2495b79eb8c2b6ec92b3ce1e5577f892f7821
which are both on my for-3.1/for-next branch:
http://git.kernel.org/?p=linux/kernel/git/geert/linux-m68k.git;a=shortlog;h=refs/heads/for-3.1
Gr{oetje,eeting}s,
Geert
--
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/pine.bsm.4.64l.1106292002530.32...@herc.mirbsd.org
Bug#632141: rpc.gssd: ERROR: can't open /var/lib/nfs/rpc_pipefs/nfs/clnt[[:xdigit:]]+: No such file or directory
Package: nfs-common Version: 1:1.2.2-4 On a VM where autofs is being kept rather busy mounting and unmounting NFS shares I get a stream of messages like the following: rpc.gssd[513]: ERROR: can't open /var/lib/nfs/rpc_pipefs/nfs/clnt1ac6: No such file or directory rpc.gssd[513]: ERROR: can't open /var/lib/nfs/rpc_pipefs/nfs/clnt1aca: No such file or directory and so on with the client counter incrementing in uneven steps. From eyeballing the logs I'd say that about 1-3% of the clnt* directories give rise to such a message. The message is generated by utils/gssd/gssd_proc.c:process_clnt_dir(), which is called from utils/gssd/gssd_proc.c:process_pipedir(). The latter does a scandir(3) on /var/lib/nfs/rpc_pipefs/nfs, then calls process_clnt_dir() for every entry whose name begins with clnt. process_clnt_dir() tries to open(2) the clnt* directory and sometimes gets ENOENT. My guess is that there is a race condition: something else removes clnt* directories between the scandir() and the open(). If so, maybe the message should be downgraded to a WARNING and not printed at verbosity 0? I haven't been able to discern an actual impact other than the stream of error messages in the logs. Of course that doesn't mean that there is no such impact. -- 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/20110629202823.gb14...@astro.su.se
linux-latest-2.6_37_i386.changes ACCEPTED into experimental
Accepted: linux-doc-2.6_3.0.0~rc5+37_all.deb to main/l/linux-latest-2.6/linux-doc-2.6_3.0.0~rc5+37_all.deb linux-doc_3.0.0~rc5+37_all.deb to main/l/linux-latest-2.6/linux-doc_3.0.0~rc5+37_all.deb linux-headers-2.6-486_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/linux-headers-2.6-486_3.0.0~rc5+37_i386.deb linux-headers-2.6-686-pae_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/linux-headers-2.6-686-pae_3.0.0~rc5+37_i386.deb linux-headers-2.6-amd64_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/linux-headers-2.6-amd64_3.0.0~rc5+37_i386.deb linux-headers-486_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/linux-headers-486_3.0.0~rc5+37_i386.deb linux-headers-686-pae_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/linux-headers-686-pae_3.0.0~rc5+37_i386.deb linux-headers-amd64_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/linux-headers-amd64_3.0.0~rc5+37_i386.deb linux-image-2.6-486_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/linux-image-2.6-486_3.0.0~rc5+37_i386.deb linux-image-2.6-686-bigmem_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/linux-image-2.6-686-bigmem_3.0.0~rc5+37_i386.deb linux-image-2.6-686-pae_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/linux-image-2.6-686-pae_3.0.0~rc5+37_i386.deb linux-image-2.6-686_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/linux-image-2.6-686_3.0.0~rc5+37_i386.deb linux-image-2.6-amd64_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/linux-image-2.6-amd64_3.0.0~rc5+37_i386.deb linux-image-486_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/linux-image-486_3.0.0~rc5+37_i386.deb linux-image-686-bigmem_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/linux-image-686-bigmem_3.0.0~rc5+37_i386.deb linux-image-686-pae_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/linux-image-686-pae_3.0.0~rc5+37_i386.deb linux-image-686_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/linux-image-686_3.0.0~rc5+37_i386.deb linux-image-amd64_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/linux-image-amd64_3.0.0~rc5+37_i386.deb linux-latest-2.6_37.dsc to main/l/linux-latest-2.6/linux-latest-2.6_37.dsc linux-latest-2.6_37.tar.gz to main/l/linux-latest-2.6/linux-latest-2.6_37.tar.gz linux-source-2.6_3.0.0~rc5+37_all.deb to main/l/linux-latest-2.6/linux-source-2.6_3.0.0~rc5+37_all.deb linux-source_3.0.0~rc5+37_all.deb to main/l/linux-latest-2.6/linux-source_3.0.0~rc5+37_all.deb linux-tools-2.6_3.0.0~rc5+37_all.deb to main/l/linux-latest-2.6/linux-tools-2.6_3.0.0~rc5+37_all.deb linux-tools_3.0.0~rc5+37_all.deb to main/l/linux-latest-2.6/linux-tools_3.0.0~rc5+37_all.deb xen-linux-system-2.6-686_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/xen-linux-system-2.6-686_3.0.0~rc5+37_i386.deb xen-linux-system-686-pae_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/xen-linux-system-686-pae_3.0.0~rc5+37_i386.deb xen-linux-system-amd64_3.0.0~rc5+37_i386.deb to main/l/linux-latest-2.6/xen-linux-system-amd64_3.0.0~rc5+37_i386.deb Override entries for your package: linux-doc-2.6_3.0.0~rc5+37_all.deb - optional kernel linux-doc_3.0.0~rc5+37_all.deb - optional kernel linux-headers-2.6-486_3.0.0~rc5+37_i386.deb - optional kernel linux-headers-2.6-686-pae_3.0.0~rc5+37_i386.deb - optional kernel linux-headers-2.6-amd64_3.0.0~rc5+37_i386.deb - optional kernel linux-headers-486_3.0.0~rc5+37_i386.deb - optional kernel linux-headers-686-pae_3.0.0~rc5+37_i386.deb - optional kernel linux-headers-amd64_3.0.0~rc5+37_i386.deb - optional kernel linux-image-2.6-486_3.0.0~rc5+37_i386.deb - optional kernel linux-image-2.6-686-bigmem_3.0.0~rc5+37_i386.deb - optional kernel linux-image-2.6-686-pae_3.0.0~rc5+37_i386.deb - optional kernel linux-image-2.6-686_3.0.0~rc5+37_i386.deb - optional kernel linux-image-2.6-amd64_3.0.0~rc5+37_i386.deb - optional kernel linux-image-486_3.0.0~rc5+37_i386.deb - optional kernel linux-image-686-bigmem_3.0.0~rc5+37_i386.deb - optional kernel linux-image-686-pae_3.0.0~rc5+37_i386.deb - optional kernel linux-image-686_3.0.0~rc5+37_i386.deb - optional kernel linux-image-amd64_3.0.0~rc5+37_i386.deb - optional kernel linux-latest-2.6_37.dsc - source admin linux-source-2.6_3.0.0~rc5+37_all.deb - optional kernel linux-source_3.0.0~rc5+37_all.deb - optional kernel linux-tools-2.6_3.0.0~rc5+37_all.deb - optional kernel linux-tools_3.0.0~rc5+37_all.deb - optional kernel xen-linux-system-2.6-686_3.0.0~rc5+37_i386.deb - optional kernel xen-linux-system-686-pae_3.0.0~rc5+37_i386.deb - optional kernel xen-linux-system-amd64_3.0.0~rc5+37_i386.deb - optional kernel Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- 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/e1qc2nx-0001fx...@franck.debian.org
linux-latest-2.6_38_i386.changes ACCEPTED into experimental
Accepted: linux-doc-2.6_3.0.0~rc5+38_all.deb to main/l/linux-latest-2.6/linux-doc-2.6_3.0.0~rc5+38_all.deb linux-doc_3.0.0~rc5+38_all.deb to main/l/linux-latest-2.6/linux-doc_3.0.0~rc5+38_all.deb linux-headers-2.6-486_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/linux-headers-2.6-486_3.0.0~rc5+38_i386.deb linux-headers-2.6-686-pae_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/linux-headers-2.6-686-pae_3.0.0~rc5+38_i386.deb linux-headers-2.6-amd64_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/linux-headers-2.6-amd64_3.0.0~rc5+38_i386.deb linux-headers-486_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/linux-headers-486_3.0.0~rc5+38_i386.deb linux-headers-686-pae_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/linux-headers-686-pae_3.0.0~rc5+38_i386.deb linux-headers-amd64_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/linux-headers-amd64_3.0.0~rc5+38_i386.deb linux-image-2.6-486_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/linux-image-2.6-486_3.0.0~rc5+38_i386.deb linux-image-2.6-686-bigmem_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/linux-image-2.6-686-bigmem_3.0.0~rc5+38_i386.deb linux-image-2.6-686-pae_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/linux-image-2.6-686-pae_3.0.0~rc5+38_i386.deb linux-image-2.6-686_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/linux-image-2.6-686_3.0.0~rc5+38_i386.deb linux-image-2.6-amd64_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/linux-image-2.6-amd64_3.0.0~rc5+38_i386.deb linux-image-486_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/linux-image-486_3.0.0~rc5+38_i386.deb linux-image-686-bigmem_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/linux-image-686-bigmem_3.0.0~rc5+38_i386.deb linux-image-686-pae_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/linux-image-686-pae_3.0.0~rc5+38_i386.deb linux-image-686_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/linux-image-686_3.0.0~rc5+38_i386.deb linux-image-amd64_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/linux-image-amd64_3.0.0~rc5+38_i386.deb linux-latest-2.6_38.dsc to main/l/linux-latest-2.6/linux-latest-2.6_38.dsc linux-latest-2.6_38.tar.gz to main/l/linux-latest-2.6/linux-latest-2.6_38.tar.gz linux-source-2.6_3.0.0~rc5+38_all.deb to main/l/linux-latest-2.6/linux-source-2.6_3.0.0~rc5+38_all.deb linux-source_3.0.0~rc5+38_all.deb to main/l/linux-latest-2.6/linux-source_3.0.0~rc5+38_all.deb linux-tools-2.6_3.0.0~rc5+38_all.deb to main/l/linux-latest-2.6/linux-tools-2.6_3.0.0~rc5+38_all.deb linux-tools_3.0.0~rc5+38_all.deb to main/l/linux-latest-2.6/linux-tools_3.0.0~rc5+38_all.deb xen-linux-system-2.6-xen-686_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/xen-linux-system-2.6-xen-686_3.0.0~rc5+38_i386.deb xen-linux-system-686-pae_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/xen-linux-system-686-pae_3.0.0~rc5+38_i386.deb xen-linux-system-amd64_3.0.0~rc5+38_i386.deb to main/l/linux-latest-2.6/xen-linux-system-amd64_3.0.0~rc5+38_i386.deb Override entries for your package: linux-doc-2.6_3.0.0~rc5+38_all.deb - optional kernel linux-doc_3.0.0~rc5+38_all.deb - optional kernel linux-headers-2.6-486_3.0.0~rc5+38_i386.deb - optional kernel linux-headers-2.6-686-pae_3.0.0~rc5+38_i386.deb - optional kernel linux-headers-2.6-amd64_3.0.0~rc5+38_i386.deb - optional kernel linux-headers-486_3.0.0~rc5+38_i386.deb - optional kernel linux-headers-686-pae_3.0.0~rc5+38_i386.deb - optional kernel linux-headers-amd64_3.0.0~rc5+38_i386.deb - optional kernel linux-image-2.6-486_3.0.0~rc5+38_i386.deb - optional kernel linux-image-2.6-686-bigmem_3.0.0~rc5+38_i386.deb - optional kernel linux-image-2.6-686-pae_3.0.0~rc5+38_i386.deb - optional kernel linux-image-2.6-686_3.0.0~rc5+38_i386.deb - optional kernel linux-image-2.6-amd64_3.0.0~rc5+38_i386.deb - optional kernel linux-image-486_3.0.0~rc5+38_i386.deb - optional kernel linux-image-686-bigmem_3.0.0~rc5+38_i386.deb - optional kernel linux-image-686-pae_3.0.0~rc5+38_i386.deb - optional kernel linux-image-686_3.0.0~rc5+38_i386.deb - optional kernel linux-image-amd64_3.0.0~rc5+38_i386.deb - optional kernel linux-latest-2.6_38.dsc - source admin linux-source-2.6_3.0.0~rc5+38_all.deb - optional kernel linux-source_3.0.0~rc5+38_all.deb - optional kernel linux-tools-2.6_3.0.0~rc5+38_all.deb - optional kernel linux-tools_3.0.0~rc5+38_all.deb - optional kernel xen-linux-system-2.6-xen-686_3.0.0~rc5+38_i386.deb - optional kernel xen-linux-system-686-pae_3.0.0~rc5+38_i386.deb - optional kernel xen-linux-system-amd64_3.0.0~rc5+38_i386.deb - optional kernel Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- 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/e1qc2nv-0001e5...@franck.debian.org
Re: [m68k] Patches for 3.0 (was Re: linux-2.6_2.6.39-1_amd64.changes ACCEPTED into unstable)
hello,
On Wed, Jun 29, 2011 at 08:05:11PM +, Thorsten Glaser wrote:
Hi Debian Kernel team,
can we please have these for 3.0? They will be in 3.1, and replace
0008-m68k-atari-Reserve-some-ST-RAM-early-on-for-device-b.patch
from 2.6.38-2, addressing the same problem (garbled video output
when the machine has too much FastRAM).
aboves confuses me, I don't see any m68k patches in the trunk branch
heading for the next 3.0-rcX upload?
which are needed?
Thanks!
Geert Uytterhoeven dixit:
On Wed, Jun 29, 2011 at 19:38, Thorsten Glaser t...@mirbsd.de wrote:
Geert Uytterhoeven dixit:
I folded it into your previous patch and pushed it out for 3.1.
Can you make a patch (series) on top of 3.0 and mail that to
debian-kernel asking for inclusion in the next 3.0 upload, on
the ground it’s been accepted upstream and fixes UI problems?
The two patches you need are
http://git.kernel.org/?p=linux/kernel/git/geert/linux-m68k.git;a=commitdiff;h=1789c38726c2805563e9049dbc5d5253251761a7
http://git.kernel.org/?p=linux/kernel/git/geert/linux-m68k.git;a=commitdiff;h=10b2495b79eb8c2b6ec92b3ce1e5577f892f7821
which are both on my for-3.1/for-next branch:
http://git.kernel.org/?p=linux/kernel/git/geert/linux-m68k.git;a=shortlog;h=refs/heads/for-3.1
Gr{oetje,eeting}s,
Geert
ah ok I see, will wait till these 2 materialise in linux-next and
then add them.
thanks.
--
maks
--
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/20110629215316.ga1...@vostochny.stro.at
Re: [m68k] Patches for 3.0
maximilian attems dixit: aboves confuses me, I don't see any m68k patches in the trunk branch heading for the next 3.0-rcX upload? Yes, they were in 2.6.38 but someone removed them before 2.6.39 in Debian. All but this one patch, replaced by (see below), were included in 2.6.39 upstream though, so only this issue popped up again. which are needed? These: The two patches you need are http://git.kernel.org/?p=linux/kernel/git/geert/linux-m68k.git;a=commitdiff;h=1789c38726c2805563e9049dbc5d5253251761a7 http://git.kernel.org/?p=linux/kernel/git/geert/linux-m68k.git;a=commitdiff;h=10b2495b79eb8c2b6ec92b3ce1e5577f892f7821 ah ok I see, will wait till these 2 materialise in linux-next and then add them. OK, thanks! bye, //mirabilos -- 08:05⎜XTaran:#grml mika: Does grml have an tool to read Apple ⎜System Log (asl) files? :) 08:08⎜ft:#grml yeah. /bin/rm. ;) 08:09⎜mrud:#grml hexdump -C 08:31⎜XTaran:#grml ft, mrud: *g* -- 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/pine.bsm.4.64l.1106292158280.32...@herc.mirbsd.org
