Re: Bug#604438: nautilus: SD Card images corrupted in gnome
reassign 604438 linux-2.6 thanks Le lundi 22 novembre 2010 à 18:50 +1000, Lachlan a écrit : Recently when taking digital pictures off a camera i found all the pictures were corrupted with the majority of the picture being a dark grey. I thought this was the pictures but the cards work in a windows laptop that i tried. Is there a problem in nautilus (or dependancies) reading SDHC cards? This also affect image previews and retain the corruption even when copying off the SD card to my home folder. This has been a recent issue with multiple SD cards. Nautilus (and the plumbing stack underneath) merely give the filesystem to mount to the kernel, so in the end it probably boils down to a driver issue. Cheers, -- .''`. : :' : “You would need to ask a lawyer if you don't know `. `' that a handshake of course makes a valid contract.” `--- J???rg Schilling -- 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/1290416348.30108.1.ca...@meh
Processed: Re: Bug#604438: nautilus: SD Card images corrupted in gnome
Processing commands for cont...@bugs.debian.org: reassign 604438 linux-2.6 Bug #604438 [nautilus] nautilus: SD Card images corrupted in gnome Bug reassigned from package 'nautilus' to 'linux-2.6'. Bug No longer marked as found in versions nautilus/2.30.1-2. thanks Stopping processing here. Please contact me if you need assistance. -- 604438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604438 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.12904163642741.transcr...@bugs.debian.org
Bug#604416: linux-image-2.6.32-5-sparc64: Kernels 2.6.32 hang on boot at Initializing cgroup subsys blkio
On Sun, Nov 21, 2010 at 10:33:58PM -0500, Jonathan Williams wrote: On Nov 21, 2010, at 10:08 PM, Ben Hutchings wrote: You're claiming that: - This bug breaks every system where the package is installed reportbug only refers to the whole system; not *every* whole system, perhaps that should be clarified? If you consider yourself not a novice (the reportbug default mode, where critical is _not_ announced), you are supposed to know a bit about it. 2 breaks the whole systemrenders the entire system unusable (e.g., unbootable, unable to reach a multiuser runlevel, etc.) Where is this from? The official definition[1] is: | makes unrelated software on the system (or the whole system) break, or | causes serious data loss, or introduces a security hole on systems where | you install the package. Neither is the kernel unrelated to any other package (it is an implicit dependency in any of them) nor does it cause data loss, nor does it introduce a security hole. [0.00] bootconsole [earlyprom0] enabled Okay, it uses earlyprom0. But I don't see the console handover, that should have done before the cgroup init. Bastian -- Those who hate and fight must stop themselves -- otherwise it is not stopped. -- Spock, Day of the Dove, stardate unknown -- 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/20101122100030.ga23...@wavehammer.waldi.eu.org
Bug#604442: linux-image-2.6-686: Kernel Oops after return from hibernation
Package: linux-image-2.6-686 Version: 2.6.32+28 Severity: important Hello, I am getting regular oopses again from the kernel after returning from hibernation - this used to work without issue for some time before. From syslog: --- Nov 22 10:03:19 deli kernel: [12670.808315] firewire_core: rediscovered device fw0 Nov 22 10:03:19 deli kernel: [12671.588255] sd 0:0:0:0: [sda] Starting disk Nov 22 10:03:19 deli kernel: [12671.736239] usb 1-6: reset high speed USB device using ehci_hcd and address 4 Nov 22 10:03:19 deli kernel: [12672.024241] usb 3-1: reset full speed USB device using uhci_hcd and address 2 Nov 22 10:03:19 deli kernel: [12672.500053] usb 5-1: reset full speed USB device using uhci_hcd and address 2 Nov 22 10:03:19 deli kernel: [12672.733289] usb 3-1.1: reset full speed USB device using uhci_hcd and address 3 Nov 22 10:03:19 deli kernel: [12672.921290] usb 3-1.2: reset full speed USB device using uhci_hcd and address 4 Nov 22 10:03:19 deli kernel: [12673.072618] Registered led device: iwl-phy0::radio Nov 22 10:03:19 deli kernel: [12673.072639] Registered led device: iwl-phy0::assoc Nov 22 10:03:19 deli kernel: [12673.072659] Registered led device: iwl-phy0::RX Nov 22 10:03:19 deli kernel: [12673.072681] Registered led device: iwl-phy0::TX Nov 22 10:03:19 deli kernel: [12673.095966] Restarting tasks ... Nov 22 10:03:19 deli kernel: [12673.096037] usb 7-1: USB disconnect, address 2 Nov 22 10:03:19 deli kernel: [12673.096146] BUG: unable to handle kernel NULL pointer dereference at (null) Nov 22 10:03:19 deli kernel: [12673.096190] IP: [c113ab61] strcmp+0x6/0x19 Nov 22 10:03:19 deli kernel: [12673.096225] *pde = Nov 22 10:03:19 deli kernel: [12673.096249] Oops: [#1] SMP Nov 22 10:03:19 deli kernel: [12673.096277] last sysfs file: /sys/devices/virtual/sound/timer/uevent Nov 22 10:03:19 deli kernel: [12673.096315] Modules linked in: vboxnetadp vboxnetflt vboxdrv parport_pc ppdev lp parport i8k fuse ext4 jbd2 crc16 firewire_sbp2 loop btusb bluetooth arc4 joydev ecb snd_hda_codec_intelhdmi iwlagn snd_hda_codec_idt iwlcore i915 uvcvideo snd_hda_intel snd_hda_codec drm_kms_helper videode v mac80211 v4l1_compat snd_hwdep snd_pcm drmdone. Nov 22 10:03:19 deli kernel: [12673.11] pcmcia cfg80211 snd_timer snd i2c_i801 soundcore dell_laptop wmi psmouse snd_page_alloc i2c_algo_bit yenta_socket rsrc_nonstatic button ac dcdbas pcmcia_core serio_raw evdev pcspkr video output rfkill battery processor i2c_core ext3 jbd mbcache sha256_generic aes_i586 aes_ generic cbc dm_crypt dm_mod sg sd_mod crc_t10dif sr_mod cdrom usbhid hid uhci_hcd ata_generic ahci sdhci_pci sdhci thermal libata ricoh_mmc mmc_core led_class firewire_ohci firewire_core crc_itu_t thermal_sys ehci_hcd scsi_mod e1000e usbcore nls_base [last unloaded: scsi_wait_scan] Nov 22 10:03:19 deli kernel: [12673.11] Nov 22 10:03:19 deli kernel: [12673.11] Pid: 293, comm: khubd Not tainted (2.6.32-5-686 #1) Latitude E6400 Nov 22 10:03:19 deli kernel: [12673.11] EIP: 0060:[c113ab61] EFLAGS: 00010286 CPU: 1 Nov 22 10:03:19 deli kernel: [12673.11] EIP is at strcmp+0x6/0x19 Nov 22 10:03:19 deli kernel: [12673.11] EAX: EBX: f6de7000 ECX: f6a36d20 EDX: f6649ded Nov 22 10:03:19 deli kernel: [12673.11] ESI: EDI: f6649ded EBP: f4e2a018 ESP: f6649da4 Nov 22 10:03:19 deli kernel: [12673.11] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Nov 22 10:03:19 deli kernel: [12673.11] Process khubd (pid: 293, ti=f6648000 task=f66c4000 task.ti=f6648000) Nov 22 10:03:19 deli kernel: [12673.102822] Stack: Nov 22 10:03:19 deli kernel: [12673.102822] f6649ded f4e2a79c c10f2f36 f6c08180 f6649ded c10f1e2c f6c08180 f6a36ca8 Nov 22 10:03:19 deli kernel: [12673.102822] 0 f6649ded f6c01800 f4e2a79c c11b083d f6649ded c12de22a Nov 22 10:03:19 deli kernel: [12673.102822] 0 000d 0022 3a3331f9 f5003433 f4d45290 f586ec5c 1e193104 f586ec5c Nov 22 10:03:19 deli kernel: [12673.102822] Call Trace: Nov 22 10:03:19 deli kernel: [12673.102822] [c10f2f36] ? sysfs_find_dirent+0x13/0x23 Nov 22 10:03:19 deli kernel: [12673.102822] [c10f1e2c] ? sysfs_hash_and_remove+0x20/0x48 Nov 22 10:03:19 deli kernel: [12673.102822] [c11b083d] ? device_remove_sys_dev_entry+0x57/0x72 Nov 22 10:03:19 deli kernel: [12673.102822] [c11b0a60] ? device_del+0x56/0x152 Nov 22 10:03:19 deli kernel: [12673.102822] [c11be566] ? mousedev_destroy+0xe/0x2c Nov 22 10:03:19 deli kernel: [12673.102822] [c11bc12b] ? input_unregister_device+0xe5/0x16f Nov 22 10:03:19 deli kernel: [12673.102822] [f81c72dd] ? hidinput_disconnect+0x32/0x45 [hid] Nov 22 10:03:19 deli kernel: [12673.102822] [f81c62ad] ? hid_disconnect+0x11/0x35 [hid] Nov 22 10:03:19 deli kernel: [12673.102822] [f81c62f6] ? hid_device_remove+0x25/0x3e [hid] Nov 22 10:03:19 deli kernel: [12673.102822] [c11b25a8] ? __device_release_driver+0x74/0xb7 Nov 22 10:03:19 deli kernel:
Bug#604442: linux-image-2.6-686: Kernel Oops after return from hibernation
George B. i93.b...@gmail.com writes: Nov 22 10:03:19 deli kernel: [12673.102822] [c11be566] ? mousedev_destroy+0xe/0x2c Just to narrow things down. Does this occur if you 1) login using ssh from another computer 2) stop Xorg 3) sudo rmmod psmouse usbhid hid ? If yes, is just loading one of these modules enough to make it crash or do you need to be running Xorg too? Finally, what laptop is this? And, how do you exactly hibernate? -- 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/844ob9hbqn@sauna.l.org
Bug#604457: linux-image-2.6.26-2-xen-686: Raid10 exporting LV to xen results in error can't convert block across chunks or bigger than 64k
Package: linux-image-2.6.26-2-xen-686 Version: 2.6.26-25lenny1 Severity: critical Justification: causes serious data loss When accessing an lv using configured on a raid10 using xen results in corrupted data as the following syslog indicates: kernel: raid10_make_request bug: can't convert block across chunks or bigger than 64k 309585274 4 Continued attempts to use the disk in the domU results in i/o error and the partition being remounted read-only. see also debian bug 461644 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461644) Since this bug is old and closed without a fix, I want to open a new bug for it. Redhat made a patch for the appropriate driver, but its not included upstream. Can someone please make sure this patch gets into the sources of the debian fork. See this patch: https://bugzilla.redhat.com/attachment.cgi?id=342638action=diff See also this kernel trap related discussion : http://kerneltrap.org/mailarchive/linux-raid/2010/3/8/6837883 This same thread contains an other patch then the redhat one and its that one is also confirmed as working. -- System Information: Debian Release: 5.0.6 APT prefers stable APT policy: (990, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-xen-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-2-xen-686 depends on: ii initramfs-tools 0.92o tools for generating an initramfs ii linux-modules-2.6.26-2-x 2.6.26-25lenny1 Linux 2.6.26 modules on i686 Versions of packages linux-image-2.6.26-2-xen-686 recommends: ii libc6-xen 2.10.2-2 GNU C Library: Shared libraries [X Versions of packages linux-image-2.6.26-2-xen-686 suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 none(no description available) -- 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/20101122104855.7917.71402.report...@xen-6080-01.infra.vasco.com
Bug#497392: maybe a duplicate of bug 601017
This looks like a duplicate of bug 601017, which was marked fixed in version linux-2.6/2.6.32-27: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601017 -- Kenyon Ralph signature.asc Description: Digital signature
Bug#604453: linux-2.6: xen domU hangs with systemtap kernel.function(*...@*/*.c)
On Mon, 2010-11-22 at 12:46 +0200, Timo Juhani Lindfors wrote: Package: linux-2.6 Version: 2.6.32-27 Severity: minor [ Note that I have applied a patch from #602273 so this is not a completely unmodified linux-2.6 package.] [...] Also, SystemTap inserts modules into the kernel, so my first thought is to suspect SystemTap. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: reassign 604453 to systemtap
Processing commands for cont...@bugs.debian.org: reassign 604453 systemtap Bug #604453 [linux-2.6] linux-2.6: xen domU hangs with systemtap kernel.function(*...@*/*.c) Bug reassigned from package 'linux-2.6' to 'systemtap'. Bug No longer marked as found in versions 2.6.32-27. thanks Stopping processing here. Please contact me if you need assistance. -- 604453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604453 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.129042502313101.transcr...@bugs.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org:
found 518182 2.6.32-27
Bug #518182 {Done: dann frazier da...@debian.org} [linux-2.6] linux-2.6:
Error with e1000 e1000_clean_tx_irq: Detected Tx Unit Hang
There is no source info for the package 'linux-2.6' at version '2.6.32-27' with
architecture ''
Unable to make a source version for version '2.6.32-27'
Bug Marked as found in versions 2.6.32-27 and reopened.
--
Stopping processing here.
Please contact me if you need assistance.
--
518182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518182
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.129042564816904.transcr...@bugs.debian.org
Bug#497392: maybe a duplicate of bug 601017
On Mon, 2010-11-22 at 03:18 -0800, Kenyon Ralph wrote: This looks like a duplicate of bug 601017, which was marked fixed in version linux-2.6/2.6.32-27: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601017 Yes, it could be. Bastien, please could you test the new version. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 497392
Processing commands for cont...@bugs.debian.org: tags 497392 + moreinfo Bug #497392 [linux-2.6] e1000e driver does not initialize correctly Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 497392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497392 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.12904294745290.transcr...@bugs.debian.org
Bug#602642: More info needed?
The bug report is still tagged moreinfo, please indicate what (if any) additional information that is needed. /Daniel -- 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/aanlktinrz_nuqrmwttkxr1c_6+1mqxas84b9guhbi...@mail.gmail.com
Bug#604469: linux-image-2.6.26-2-openvz-amd64: openvz - deadlock during RAID rebuild with container backing store on LVM+snapshot
Package: linux-image-2.6.26-2-openvz-amd64 Version: 2.6.26-25lenny1 Severity: normal On Lenny, I have observed the following behaviour: An I/O deadlock occurs under the following conditions: . OpenVZ container data stored on an LVM for which the PV is an md RAID1 . RAID1 md undergoing a rebuild or check . An LVM snapshot is active for the logical volume (in order to take a backup) . I/O occurs within the container The RAID resync then stops, as does all other I/O to the filesystem which is mounted upon the LVM. Adding various debug to the md raid1 driver shows that when the system gets to this state, there are a number of bio requests which are still pending (or at least their callback never gets executed). http://marc.info/?t=12847354111r=1w=2 Adding the debug printks and atomic counters appears to make the deadlock occur more readily (within seconds rather than minutes of starting the openvz container). My guess was that this is some sort of a priority inversion deadlock, I/O in the container is triggering I/O outside of the container (via LVM snapshot) which must complete first (because of the OpenVZ scheduling rules or otherwise), and possibly the md barrier code is enforcing the opposite ordering. .. but when I tried: echo 0 /sys/block/sda/queue/iosched/virt_mode echo 0 /sys/block/sdb/queue/iosched/virt_mode prior to starting the container, didn't seem to change things. So maybe that's not the problem. Simply using the container private directory as a chroot, and placing reasonably heavy I/O load does not seem to cause the same deadlock to occur. I haven't seen the deadlock occur on 2.6.32, but haven't tried to insert the same debugging statements. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-openvz-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.26-2-openvz-amd64 depends on: ii debconf [debconf-2.0] 1.5.36 Debian configuration management sy ii initramfs-tools [linux-initra 0.98.5 tools for generating an initramfs ii module-init-tools 3.12-1 tools for managing Linux kernel mo ii vzctl 3.0.24-10 server virtualization solution - c linux-image-2.6.26-2-openvz-amd64 recommends no packages. Versions of packages linux-image-2.6.26-2-openvz-amd64 suggests: pn grub | lilo none (no description available) pn linux-doc-2.6.26 none (no description available) -- 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/20101122131743.2836.76269.report...@ermintrude.seoss.co.uk
Bug#604470: linux-image-2.6.32-5-openvz-amd64: degraded inbound network bandwidth
Package: linux-2.6 Version: 2.6.32-27 Severity: normal For traffic from Internet to Container the bandwidth cut down in 5-10 times compared to Hardware Nodes. And for connection between two containers on different Hardware Nodes but in the same Local Network inbound speed slow down dramatically to 1 times. At the same time outbound bandwidth is close to Hardware Node one. There are no such problems with kernel I've got from openvz site: http://download.openvz.org/kernel/branches/2.6.32/2.6.32-dzhanibekov.1/kernel-2.6.32-dzhanibekov.1.x86_64.rpm as well as with old Debian kernel linux-image-2.6.26-2-openvz-amd64 thre are no problem too. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: HP product_name: ProLiant DL180 G6 product_version: chassis_vendor: HP chassis_version: bios_vendor: HP bios_version: O20 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 5520 I/O Hub to ESI Port [8086:3406] (rev 13) Subsystem: Hewlett-Packard Company Device [103c:330b] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Capabilities: [60] MSI: Enable- Count=1/2 Maskable+ 64bit- Address: Data: Masking: Pending: Capabilities: [90] Express (v2) Root Port (Slot-), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s 64ns, L1 1us ExtTag+ RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal+ Fatal+ Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x4, ASPM L0s L1, Latency L0 512ns, L1 64us ClockPM- Surprise+ LLActRep+ BwNot+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt- RootCtl: ErrCorrectable- ErrNon-Fatal+ ErrFatal+ PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range BCD, TimeoutDis+ ARIFwd+ DevCtl2: Completion Timeout: 260ms to 900ms, TimeoutDis- ARIFwd- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB Capabilities: [e0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES+ TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt+ RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol- UESvrt: DLP+ SDES+ TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn- Capabilities: [150 v1] Access Control Services ACSCap: SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd+ EgressCtrl- DirectTrans- ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans- Capabilities: [160 v0] Vendor Specific Information: ID=0002 Rev=0 Len=00c ? 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 13) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 256 bytes Bus: primary=00, secondary=07, subordinate=07, sec-latency=0 I/O behind bridge: e000-efff Memory behind bridge: fbe0-fbef Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity+ SERR+ NoISA- VGA- MAbort- Reset- FastB2B-
Bug#497392: maybe a duplicate of bug 601017
Le lundi 22 novembre 2010 à 12:37 +, Ben Hutchings a écrit : On Mon, 2010-11-22 at 03:18 -0800, Kenyon Ralph wrote: This looks like a duplicate of bug 601017, which was marked fixed in version linux-2.6/2.6.32-27: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601017 Yes, it could be. Bastien, please could you test the new version. Ben. Hello, The bug was hardware-dependent (it cannot be reproduced with any switch) and I throw the old one I had problem with. Then I cannot try. The specific bug was followed by intel's guy at https://bugzilla.kernel.org/show_bug.cgi?id=11998 the fix I used was introduction of a mdix parameter, which is not shown on 2.6.32-5-amd64's e1000e modinfo I'm sorry to cannot test that. -- Bastien Durel -- 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/1290432772.3292.15.ca...@sietchtabr.geekwu.org
Re: Processed: reassign 604453 to systemtap
Bug #604453 [linux-2.6] linux-2.6: xen domU hangs with systemtap kernel.function(*...@*/*.c) Bug reassigned from package 'linux-2.6' to 'systemtap'. Bug No longer marked as found in versions 2.6.32-27. This is a known problem, also known as http://sourceware.org/PR2725. They appear to be latent kernel (kprobes layer?) bugs, as indicated by perf probe ... (or git systemtap's -DSTP_ALIBI mode) also causing similar kernel failures when probing large subsets of the kernel. -- 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/20101122132652.ga30...@redhat.com
Re: Bug#604459: libdrm-nouveau1: fresh install with Squeeze Beta 1 netinst-amd64 results in hang on boot on MacBook 5, 3
reassign 604459 linux-2.6 2.6.32-27 tag 604459 moreinfo kthxbye On Mon, Nov 22, 2010 at 04:21:13 -0700, Nicholas Holley wrote: Package: libdrm-nouveau1 Version: 2.4.21-1~squeeze3 Severity: important After installing Squeeze Beta 1 using the netinst-amd64 image, I was unuable to boot past nouveau. My laptop would hang and require a restart. The issue was resolved by specifying nouveau.noaccel=1 in Grub. Please attach your kernel log, lspci -nn and Xorg log. Cheers, Julien signature.asc Description: Digital signature
Processed: Re: Bug#604459: libdrm-nouveau1: fresh install with Squeeze Beta 1 netinst-amd64 results in hang on boot on MacBook 5, 3
Processing commands for cont...@bugs.debian.org: reassign 604459 linux-2.6 2.6.32-27 Bug #604459 [libdrm-nouveau1] libdrm-nouveau1: fresh install with Squeeze Beta 1 netinst-amd64 results in hang on boot on MacBook 5, 3 Bug reassigned from package 'libdrm-nouveau1' to 'linux-2.6'. Bug No longer marked as found in versions libdrm/2.4.21-1~squeeze3. Bug #604459 [linux-2.6] libdrm-nouveau1: fresh install with Squeeze Beta 1 netinst-amd64 results in hang on boot on MacBook 5, 3 There is no source info for the package 'linux-2.6' at version '2.6.32-27' with architecture '' Unable to make a source version for version '2.6.32-27' Bug Marked as found in versions 2.6.32-27. tag 604459 moreinfo Bug #604459 [linux-2.6] libdrm-nouveau1: fresh install with Squeeze Beta 1 netinst-amd64 results in hang on boot on MacBook 5, 3 Added tag(s) moreinfo. kthxbye Stopping processing here. Please contact me if you need assistance. -- 604459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604459 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.12904353209421.transcr...@bugs.debian.org
Bug#604177: mistake
I have sent a bug report, number 604177, about a kernel bug. This bug has really happened and details are encountred in its report. In the same report I mensioned a network delay which could be probably a bug. But today I have discovered that it is some problem with my internet provider or with my router, which one of my roommates usually changes something. My HP dv4-2014br is working good with squeeze at work and I'd like to apologize about have erroneously reported a network delay. -- 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/4cea7dc2.5070...@gmail.com
Bug#497392: marked as done (e1000e driver does not initialize correctly)
Your message dated Mon, 22 Nov 2010 14:30:28 + with message-id 1290436228.6770.328.ca...@localhost and subject line Re: Bug#497392: maybe a duplicate of bug 601017 has caused the Debian Bug report #497392, regarding e1000e driver does not initialize correctly 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.) -- 497392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-3 Severity: important The e1000e kernel module does not initialize correctly, then the network cannot initialize. It does not complain, but packets do not exit correctly. The port's LED on switch blinks quickly all time, IPv6 RA's are recevied by the kernel, but no DHCP packet reaches router, nor any ICMP one after manual configuration. rmmod / modprobe module *sometimes* makes it working correctly, then the network interface is bringed up, DHCP responds, and communication can be established. e1000e worked correctly with linux-image-2.6.25-2-686 kernel. -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-3) (wa...@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Aug 20 12:56:41 UTC 2008 ** Command line: root=/dev/sda6 ro ** Not tainted ** Kernel log: [5.639460] EXT3-fs: mounted filesystem with ordered data mode. [6.838118] udevd version 125 started [7.555905] input: PC Speaker as /class/input/input3 [8.116282] ACPI: PCI Interrupt :00:1f.3[B] - GSI 18 (level, low) - IRQ 18 [8.240908] Linux agpgart interface v0.103 [8.280909] agpgart: Detected an Intel G33 Chipset. [8.280909] agpgart: Detected 7164K stolen memory. [8.294893] agpgart: AGP aperture is 256M @ 0xd000 [8.297597] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) [8.316909] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.03 (30-Apr-2008) [8.316909] iTCO_wdt: Found a ICH9R TCO device (Version=2, TCOBASE=0x0460) [8.316909] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [8.568520] input: Power Button (FF) as /class/input/input4 [8.620819] ACPI: Power Button (FF) [PWRF] [8.620945] input: Power Button (CM) as /class/input/input5 [8.669703] ACPI: Power Button (CM) [PWRB] [9.048402] Error: Driver 'pcspkr' is already registered, aborting... [9.068403] ACPI: PCI Interrupt :00:1b.0[A] - GSI 22 (level, low) - IRQ 22 [9.068403] PCI: Setting latency timer of device :00:1b.0 to 64 [9.104403] hda_codec: Unknown model for ALC883, trying auto-probe from BIOS... [9.888929] Adding 1847432k swap on /dev/sda12. Priority:-1 extents:1 across:1847432k [ 10.222051] EXT3 FS on sda6, internal journal [ 10.641805] it87: Found IT8718F chip at 0x290, revision 3 [ 10.641805] it87: in3 is VCC (+5V) [ 10.641805] it87: in7 is VCCH (+5V Stand-By) [ 10.657357] coretemp coretemp.0: Using relative temperature scale! [ 10.657357] coretemp coretemp.1: Using relative temperature scale! [ 10.745725] device-mapper: uevent: version 1.0.3 [ 10.745725] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-de...@redhat.com [ 26.582047] kjournald starting. Commit interval 5 seconds [ 26.582047] EXT3 FS on sda10, internal journal [ 26.582047] EXT3-fs: mounted filesystem with ordered data mode. [ 26.605941] kjournald starting. Commit interval 5 seconds [ 26.605941] EXT3 FS on sda8, internal journal [ 26.605941] EXT3-fs: mounted filesystem with ordered data mode. [ 26.641371] kjournald starting. Commit interval 5 seconds [ 26.641371] EXT3-fs: mounted filesystem with ordered data mode. [ 26.661274] kjournald starting. Commit interval 5 seconds [ 26.661274] EXT3-fs: mounted filesystem with ordered data mode. [ 26.677206] kjournald starting. Commit interval 5 seconds [ 26.677206] EXT3-fs: mounted filesystem with ordered data mode. [ 29.971694] eth0: Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX [ 29.971758] eth0: 10/100 speed: disabling TSO [ 42.084477] NET: Registered protocol family 10 [ 42.085051] lo: Disabled Privacy Extensions [ 42.899159] lp: driver loaded but no devices found [ 42.955150] ppdev: user-space parallel port driver [ 44.514082] RPC: Registered udp transport module. [ 44.514082] RPC: Registered tcp transport module. [ 44.540877] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 44.588337] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [ 44.603502] NFSD: starting 90-second grace
Processed: tagging 602642
Processing commands for cont...@bugs.debian.org: tags 602642 - moreinfo Bug #602642 [nfs-kernel-server] nfs-kernel-server: Crossmnt stopped working after upgrade from Lenny to Squeeze Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 602642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602642 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.129043650816526.transcr...@bugs.debian.org
Bug#604480: linux-2.6: CVE-2010-4072 ff.
Package: linux-2.6 Severity: normal Hi, there are a number of low urgency security problems (with fixes as far as I can find them). CVE-2010-4072 - http://lkml.org/lkml/2010/10/6/454 CVE-2010-4073 - http://lkml.org/lkml/2010/10/6/492 CVE-2010-4075 - http://lkml.indiana.edu/hypermail//linux/kernel/1009.1/03388.html CVE-2010-4076 - http://lkml.org/lkml/2010/9/15/389 CVE-2010-4077 - http://lkml.indiana.edu/hypermail//linux/kernel/1009.1/03387.html CVE-2010-4079 - http://lkml.org/lkml/2010/9/15/393 CVE-2010-4083 - http://www.spinics.net/lists/mm-commits/msg80234.html I hope this helps. AW -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32 (PREEMPT) Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1) 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/20101122142954.15652.43035.report...@anhrefn.saar.de
Bug#604480: linux-2.6: CVE-2010-4072 ff.
On Mon, 2010-11-22 at 15:29 +0100, Arne Wichmann wrote: Package: linux-2.6 Severity: normal Hi, there are a number of low urgency security problems (with fixes as far as I can find them). CVE-2010-4072 - http://lkml.org/lkml/2010/10/6/454 CVE-2010-4073 - http://lkml.org/lkml/2010/10/6/492 CVE-2010-4075 - http://lkml.indiana.edu/hypermail//linux/kernel/1009.1/03388.html CVE-2010-4076 - http://lkml.org/lkml/2010/9/15/389 CVE-2010-4077 - http://lkml.indiana.edu/hypermail//linux/kernel/1009.1/03387.html CVE-2010-4079 - http://lkml.org/lkml/2010/9/15/393 CVE-2010-4083 - http://www.spinics.net/lists/mm-commits/msg80234.html I hope this helps. Thanks, but we were already aware of these. The current unembargoed kernel security issues for Debian are tracked at svn://svn.debian.org/svn/kernel-sec. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#603432: linux-image-2.6.32-5-amd64 hangs when booted as VM under Xen
Hi. Unfortunately it turned out, that my ISP had to but that respective cluster into production now, and was therefore not longer able to play around very much. Also, the commands you've mentioned seemed to not have been available there. So I guess you might close the bug, at least from my side there's not much more I can to for debugging/tracing :-( Cheers, Chris. -- 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/4096ed83270ee4ea2e58cfdb79913...@imap.dd24.net
Re: Security: auto-loading protocol modules
On Fri, 2010-11-19 at 03:14 +, Ben Hutchings wrote: The AX.25 protocol modules (ax25, netrom, rose) have not had a great security record recently, and are not widely used. What do you think of moving the module aliases into ax25-tools, so systems without that package are not vulnerable to security flaws in the kernel modules? Ben. This seems like a good idea to me. +1 -Kamal signature.asc Description: This is a digitally signed message part
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #602078 (http://bugs.debian.org/602078) # * http://bugzilla.kernel.org/show_bug.cgi?id=23002 # * remote status changed: (?) - NEW usertags 602078 + status-NEW # remote status report for #601110 (http://bugs.debian.org/601110) # * http://bugzilla.openvz.org/show_bug.cgi?id=1701 # * remote status changed: (?) - NEW usertags 601110 + status-NEW 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/20101122163453.17869.75574.btsl...@busoni.debian.org
Bug#603903: Documentation for modules=list in initramfs.conf is unclear
Package: initramfs-tools Version: 0.98.5 Severity: normal How's this? --- initramfs.conf.5.orig 2010-11-18 10:08:00.093469868 + +++ initramfs.conf.52010-11-22 16:47:45.692926195 + @@ -22,16 +22,24 @@ .TP \fB MODULES Specifies the modules for the initramfs image. -The default setting is \fImost\fP. + +Modules listed in \fI/etc/initramfs-tools/modules\fP and +\fI/usr/share/initramfs-tools/modules.d/*\fP are always included in the +initramfs, and are loaded early in the boot process. + + +\fIlist\fP doesn't load any additional modules at boot time, other than those +listed in the above files. \fImost\fP adds most file system, all ide, sata, scsi and usb drivers. -\fIdep\fP tries to guess which modules are necessary for the running box. +\fIdep\fP tries to guess which modules are necessary for the running box and +adds those modules. + +\fInetboot\fP adds the base and network modules, but skips block devices. -\fInetboot\fP adds the base modules, network modules, but skips block devices. -\fIlist\fP includes only modules from the additional modules list to load them -early. +The default setting is \fImost\fP. .TP \fB BUSYBOX -- 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/20101122165505.11412.47176.report...@ermintrude.seoss.co.uk
Bug#593245: linux-image-2.6.32-5-xen-amd64_2.6.32-20_amd64.deb can't start VM's due to udev rule mismatch
On Thu, 2010-11-18 at 10:05 +0200, Timo Juhani Lindfors wrote: With $ dpkg-query -W linux-image-$(uname -r) linux-image-2.6.32-5-xen-amd64 2.6.32-27 The version of xen-utils-common may also have some bearing on this since it is the package which provides /lib/udev/rules.d/xend.rules It's also worth checking for stale entries in /etc/udev/rules.d (or whatever the previous path was) which might be interfering. This bug dates back to August and IIRC there was a bunch of fiddling with this sort stuff around that time, both on the kernel and xen-utils side of things (maybe udev too) so it would be interesting to know if this could be reproduced with up to date Squeeze/Sid or not. Ian. -- Ian Campbell The egg cream is psychologically the opposite of circumcision -- it *pleasurably* reaffirms your Jewishness. -- Mel Brooks -- 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/1290445130.31507.6563.ca...@zakaz.uk.xensource.com
Bug#603229: Further information
Hi ! I just have tried the last 2.6.31-2 an it is working flawlessly. Further i have set up a serial connection to my SB1500 and so got an protocol of the boot process and the crash: === bash-3.00$ tip hardwire connected [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-5-amd64 (Debian 2.6.32-27) (m...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sat Oct 30 14:18:21 UTC 2010 [0.00] Command line: root=LABEL=S_rt ro console=ttyS0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009d400 (usable) [0.00] BIOS-e820: 0009d400 - 000a (reserved) [0.00] BIOS-e820: 000ce000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 7ff6 (usable) [0.00] BIOS-e820: 7ff6 - 7ff72000 (ACPI data) [0.00] BIOS-e820: 7ff72000 - 7ff8 (ACPI NVS) [0.00] BIOS-e820: 7ff8 - 8000 (reserved) [0.00] BIOS-e820: fec0 - fec00400 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: fff8 - 0001 (reserved) [0.00] DMI present. [0.00] last_pfn = 0x7ff60 max_arch_pfn = 0x4 [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [0.00] init_memory_mapping: -7ff6 [0.00] RAMDISK: 375e7000 - 37fef333 [0.00] ACPI: RSDP 000f7200 00024 (v02 PTLTD ) [0.00] ACPI: XSDT 7ff6d424 00044 (v01 PTLTD ? XSDT 0604 LTP ) [0.00] ACPI: FACP 7ff71a2a 000F4 (v03 SUNSUNmetro 0604 PTEC 000F4240) [0.00] ACPI: DSDT 7ff6d468 0454E (v01SUNK85AE 0604 MSFT 010D) [0.00] ACPI: FACS 7ff72fc0 00040 [0.00] ACPI: SRAT 7ff71b1e 000C8 (v01 AMDHAMMER 0604 AMD 0001) [0.00] ACPI: APIC 7ff71be6 000AA (v01 PTLTD ? APIC 0604 LTP ) [0.00] ACPI: SSDT 7ff71c90 00370 (v01 PTLTD POWERNOW 0604 LTP 0001) [0.00] SRAT: PXM 0 - APIC 0 - Node 0 [0.00] SRAT: PXM 1 - APIC 1 - Node 1 [0.00] SRAT: Node 0 PXM 0 0-a [0.00] SRAT: Node 0 PXM 0 10-4000 [0.00] SRAT: Node 1 PXM 1 4000-8000 [0.00] Bootmem setup node 0 -4000 [0.00] NODE_DATA [b040 - 0001303f] [0.00] bootmap [00014000 - 0001bfff] pages 8 [0.00] (8 early reservations) == bootmem [00 - 004000] [0.00] #0 [00 - 001000] BIOS data page == [00 - 001000] [0.00] #1 [006000 - 008000] TRAMPOLINE == [006000 - 008000] [0.00] #2 [000100 - 0001688414]TEXT DATA BSS == [000100 - 0001688414] [0.00] #3 [00375e7000 - 0037fef333] RAMDISK == [00375e7000 - 0037fef333] [0.00] #4 [09d400 - 10]BIOS reserved == [09d400 - 10] [0.00] #5 [0001689000 - 00016890c8] BRK == [0001689000 - 00016890c8] [0.00] #6 [008000 - 00a000] PGTABLE == [008000 - 00a000] [0.00] #7 [00a000 - 00b040] MEMNODEMAP == [00a000 - 00b040] [0.00] Bootmem setup node 1 4000-7ff6 [0.00] NODE_DATA [4000 - 40007fff] [0.00] bootmap [40008000 - 4000ffef] pages 8 [0.00] (8 early reservations) == bootmem [004000 - 007ff6] [0.00] #0 [00 - 001000] BIOS data page [0.00] #1 [006000 - 008000] TRAMPOLINE [0.00] #2 [000100 - 0001688414]TEXT DATA BSS [0.00] #3 [00375e7000 - 0037fef333] RAMDISK [0.00] #4 [09d400 - 10]BIOS reserved [0.00] #5 [0001689000 - 00016890c8] BRK [0.00] #6 [008000 - 00a000] PGTABLE [0.00] #7 [00a000 - 00b040] MEMNODEMAP [0.00] found SMP MP-table at [880f7250] f7250 [0.00] Zone PFN ranges: [0.00] DMA 0x - 0x1000 [0.00] DMA320x1000 - 0x0010 [0.00] Normal 0x0010 - 0x0010 [0.00] Movable zone start PFN for each node [0.00] early_node_map[3] active PFN ranges [0.00] 0: 0x - 0x009d [0.00] 0: 0x0100 - 0x0004 [0.00] 1: 0x0004 -
Bug#604049: linux-image-2.6.32-5-amd64: data corruption with promise stex driver and use of device-mapper layers (lvm/dm-crypt/..)
-Original Message- From: Ben Hutchings [mailto:b...@decadent.org.uk] Sent: 2010年11月19日 21:34 To: Ed Lin - PTU; Jens Axboe; dm-de...@redhat.com Cc: Markus Schulz; 604...@bugs.debian.org Subject: Re: Bug#604049: linux-image-2.6.32-5-amd64: data corruption with promise stex driver and use of device-mapper layers (lvm/dm-crypt/..) On Fri, 2010-11-19 at 20:26 +0100, Markus Schulz wrote: Package: linux-2.6 Version: 2.6.32-27 Severity: critical Tags: d-i upstream Justification: causes serious data loss any use of the stex.ko promise hw-raid controller driver with a device-mapper layer produces data corruption (or filesystem corruption like you can see in my dmesg). [...] i've asked Ed Lin (Maintainer of stex.c from promise) on lkml and got the following answer: We found similar problem during test. The stex driver sets sg_tablesize as 32 (for st_yel it's 38) in the probe entry. It seems that this value was overridden by the system if using dm/lvm, for unknown reason. The driver received requests with more sg items than registered. Sg item number could be as high as 64. This is completely unexpected. The firmware could not handle such requests, and error occurred. [..] I have little idea how this stuff is supposed to work, but it looks like dm_dispatch_request() calls blk_insert_cloned_request() which calls blk_rq_check_limits() which checks the request against the maximum number of segments initialised from sg_tablesize. We can perhaps mitigate the data loss by checking the number of segments again in scsi_dispatch_cmd(), but it won't really solve the problem. I believe the cause of the problem has been found. An explanation and a possible solution was posted at the linux-scsi mail list and dm-de...@redhat.com. The link is http://marc.info/?l=linux-scsim=129021716922966w=2 So far no one responded. Any comment is welcome. Thanks, Ed Lin -- 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/85abfdc4641c4847ba6088f2982efd8f049d5...@nonamew.ptu.promise.com
Bug#601081: does #601081 still occur in linux-image-2.6.32-5-686_2.6.32-27?
Am 20.11.2010 14:04, schrieb Tomáš Pospíšek: In http://bugs.debian.org/601081 you report a resume failure on a i915 system with kernel v2.6.32-25. However v2.6.32-27 contains spefically fixes for i915 systems: * Add drm changes from 2.6.32.24+drm33.11: - i915: return -EFAULT if copy_to_user fails. - drm/i915: Prevent double dpms on - drm: Only decouple the old_fb from the crtc is we call mode_set* - drm/i915: Unset cursor if out-of-bounds upon mode change (v4) - drm/i915,agp/intel: Add second set of PCI-IDs for B43 Does your resume problem still occur with the latest sqeeze kernel? Most of the time, hibernate works again, although I have seen some instances lately where it did not. When I reported the issue, the failure to resume occurred every or nearly every time. Thanks, Johannes -- Johannes Rohr Russia Coordinator / ??? ?? ?? International Work Group for Indigenous Affairs / ? ??? ?? ?? ? ??? (IWGIA) Classensgade 11E, DK-2100 Copenhagen http://www.iwgia.org http://www.iwgia.org/ Tel.: +45 35 27 05 01, Fax: +45 35 27 05 07 Mobile: +45-52 80 33 11 (Denmark); +7-909-907 88 84 (Russia), +49-1570-3322883 (Germany) Skype: johannesrohr, /Please visit IWGIA's webshop at/ shop.iwgia.org http://shop.iwgia.org/
Bug#603903: Documentation for modules=list in initramfs.conf is unclear
On Mon, 22 Nov 2010, Tim Small wrote: Package: initramfs-tools Version: 0.98.5 Severity: normal How's this? Indeed, great. thank you merged for review in: http://git.debian.org/?p=kernel/initramfs-tools.git;a=shortlog;h=refs/heads/maks/modules_doc so concerning the conffile itself how about a pointer to the manpage? It may not be evident that this manpage exists? instead of duplicating content there? what do you think? happy hacking -- 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/2010115052.gb8...@stro.at
Processed: tagging 603903
Processing commands for cont...@bugs.debian.org: tags 603903 + pending Bug #603903 [initramfs-tools] initramfs-tools: Documentation for modules=list in initramfs.conf is unclear Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 603903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603903 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.12904662635727.transcr...@bugs.debian.org
Bug#603229: Further information
On Mon, 2010-11-22 at 19:08 +0100, Tilo Hacke wrote: Hi ! I just have tried the last 2.6.31-2 an it is working flawlessly. Further i have set up a serial connection to my SB1500 and so got an protocol of the boot process and the crash: [...] [0.536565] ERROR: domain-cpu_power not set [0.540002] [0.544002] ERROR: groups don't span domain-span [0.548011] ERROR: parent span is not a superset of domain-span [0.552016] ERROR: domain-cpu_power not set [0.556002] [0.560002] ERROR: groups don't span domain-span [0.564024] ERROR: domain-cpu_power not set [0.568005] [0.572002] ERROR: groups don't span domain-span [0.576023] ERROR: domain-cpu_power not set [0.580002] [0.584002] ERROR: groups don't span domain-span [...] This shows something about what's going wrong. Could you please try adding 'debug' to the kernel parameters? That will show some more context for these errors. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
ARM: OMAP2+ flavour
Hi, I'm currently bringing Debian to Nokia's N900 (see [1]). For this I also want to use a kernel package directly from Debian. The 2.6.36 mainline kernel, which is currently used in the Debian experimental contains the most important drivers, so no patches are needed in the kernel package. (check [2] to see what would be working on the N900 with this kernel) For the new flavour an omap entry in config/armel/defines is needed [3] and a new config.omap file [4]. The config file is not yet optimal, but works. Can you please give me some advice how to proceed? [1] https://elektranox.org/n900/ [2] https://elektranox.org/n900/kernel/status.html [3] http://files.ring0.de/sre/n900-debian-kernel/src/defines [4] http://files.ring0.de/sre/n900-debian-kernel/src/config.omap -- Sebastian signature.asc Description: Digital signature
Bug#604470: linux-image-2.6.32-5-openvz-amd64: degraded inbound network bandwidth
On Mon, 2010-11-22 at 16:06 +0300, Vladimir Stavrinov wrote: Package: linux-2.6 Version: 2.6.32-27 Severity: normal For traffic from Internet to Container the bandwidth cut down in 5-10 times compared to Hardware Nodes. And for connection between two containers on different Hardware Nodes but in the same Local Network inbound speed slow down dramatically to 1 times. At the same time outbound bandwidth is close to Hardware Node one. There are no such problems with kernel I've got from openvz site: http://download.openvz.org/kernel/branches/2.6.32/2.6.32-dzhanibekov.1/kernel-2.6.32-dzhanibekov.1.x86_64.rpm as well as with old Debian kernel linux-image-2.6.26-2-openvz-amd64 thre are no problem too. [...] Please could you send 'netstat -s' output for the containers where this is happening. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#604457: linux-image-2.6.26-2-xen-686: Raid10 exporting LV to xen results in error can't convert block across chunks or bigger than 64k
On Mon, 2010-11-22 at 11:48 +0100, Wouter D'Haeseleer wrote:
Package: linux-image-2.6.26-2-xen-686
Version: 2.6.26-25lenny1
Severity: critical
Justification: causes serious data loss
When accessing an lv using configured on a raid10 using xen results in
corrupted data as the following syslog indicates:
kernel: raid10_make_request bug: can't convert block across chunks or bigger
than 64k 309585274 4
Continued attempts to use the disk in the domU results in i/o error and
the partition being remounted read-only.
see also debian bug 461644
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461644)
Since this bug is old and closed without a fix, I want to open a new bug for
it.
Redhat made a patch for the appropriate driver, but its not included upstream.
Can someone please make sure this patch gets into the sources of the debian
fork.
See this patch:
https://bugzilla.redhat.com/attachment.cgi?id=342638action=diff
We much prefer to use bug fixes that have been accepted upstream.
See also this kernel trap related discussion :
http://kerneltrap.org/mailarchive/linux-raid/2010/3/8/6837883
This same thread contains an other patch then the redhat one and its
that one is also confirmed as working.
Well that was also not accepted upstream. However, I eventually tracked
down the accepted version, which for future reference is:
commit 627a2d3c29427637f4c5d31ccc7fcbd8d312cd71
Author: NeilBrown ne...@suse.de
Date: Mon Mar 8 16:44:38 2010 +1100
md: deal with merge_bvec_fn in component devices better.
I have attempted to adjust this for Debian's stable kernel version
(2.6.26) and the result is attached. Please could you test this,
following the instructions at
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
From ea1cddfe4cad61b43b6551ebc6bef466b25ff128 Mon Sep 17 00:00:00 2001
From: NeilBrown ne...@suse.de
Date: Mon, 8 Mar 2010 16:44:38 +1100
Subject: [PATCH] md: deal with merge_bvec_fn in component devices better.
commit 627a2d3c29427637f4c5d31ccc7fcbd8d312cd71 upstream.
If a component device has a merge_bvec_fn then as we never call it
we must ensure we never need to. Currently this is done by setting
max_sector to 1 PAGE, however this does not stop a bio being created
with several sub-page iovecs that would violate the merge_bvec_fn.
So instead set max_segments to 1 and set the segment boundary to the
same as a page boundary to ensure there is only ever one single-page
segment of IO requested at a time.
This can particularly be an issue when 'xen' is used as it is
known to submit multiple small buffers in a single bio.
Signed-off-by: NeilBrown ne...@suse.de
Cc: sta...@kernel.org
[bwh: Backport to Linux 2.6.26]
---
drivers/md/linear.c| 13 -
drivers/md/multipath.c | 20
drivers/md/raid0.c | 14 --
drivers/md/raid1.c | 30 +++---
drivers/md/raid10.c| 30 +++---
5 files changed, 66 insertions(+), 41 deletions(-)
diff --git a/drivers/md/linear.c b/drivers/md/linear.c
index ec921f5..627cd38 100644
--- a/drivers/md/linear.c
+++ b/drivers/md/linear.c
@@ -136,12 +136,15 @@ static linear_conf_t *linear_conf(mddev_t *mddev, int raid_disks)
blk_queue_stack_limits(mddev-queue,
rdev-bdev-bd_disk-queue);
/* as we don't honour merge_bvec_fn, we must never risk
- * violating it, so limit -max_sector to one PAGE, as
- * a one page request is never in violation.
+ * violating it, so limit max_segments to 1 lying within
+ * a single page.
*/
- if (rdev-bdev-bd_disk-queue-merge_bvec_fn
- mddev-queue-max_sectors (PAGE_SIZE9))
- blk_queue_max_sectors(mddev-queue, PAGE_SIZE9);
+ if (rdev-bdev-bd_disk-queue-merge_bvec_fn) {
+ blk_queue_max_phys_segments(mddev-queue, 1);
+ blk_queue_max_hw_segments(mddev-queue, 1);
+ blk_queue_segment_boundary(mddev-queue,
+ PAGE_CACHE_SIZE - 1);
+ }
disk-size = rdev-size;
conf-array_size += rdev-size;
diff --git a/drivers/md/multipath.c b/drivers/md/multipath.c
index e968116..0e84b4f 100644
--- a/drivers/md/multipath.c
+++ b/drivers/md/multipath.c
@@ -293,14 +293,16 @@ static int multipath_add_disk(mddev_t *mddev, mdk_rdev_t *rdev)
blk_queue_stack_limits(mddev-queue, q);
/* as we don't honour merge_bvec_fn, we must never risk
- * violating it, so limit -max_sector to one PAGE, as
- * a one page request is never in violation.
+ * violating it, so limit -max_segments to one, lying
+ * within a single page.
* (Note: it is very unlikely that a device with
* merge_bvec_fn will be involved in multipath.)
*/
- if (q-merge_bvec_fn
- mddev-queue-max_sectors (PAGE_SIZE9))
-blk_queue_max_sectors(mddev-queue, PAGE_SIZE9);
+ if (q-merge_bvec_fn) {
+blk_queue_max_segments(mddev-queue, 1);
+
Bug#604457: linux-image-2.6.26-2-xen-686: Raid10 exporting LV to xen results in error can't convert block across chunks or bigger than 64k
On Tue, 2010-11-23 at 02:31 +, Ben Hutchings wrote:
I have attempted to adjust this for Debian's stable kernel version
(2.6.26) and the result is attached. Please could you test this,
following the instructions at
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official.
Oops, that version was not quite completely adjusted. Please test this
instead.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
From: NeilBrown ne...@suse.de
Date: Mon, 8 Mar 2010 16:44:38 +1100
Subject: [PATCH] md: deal with merge_bvec_fn in component devices better.
commit 627a2d3c29427637f4c5d31ccc7fcbd8d312cd71 upstream.
If a component device has a merge_bvec_fn then as we never call it
we must ensure we never need to. Currently this is done by setting
max_sector to 1 PAGE, however this does not stop a bio being created
with several sub-page iovecs that would violate the merge_bvec_fn.
So instead set max_segments to 1 and set the segment boundary to the
same as a page boundary to ensure there is only ever one single-page
segment of IO requested at a time.
This can particularly be an issue when 'xen' is used as it is
known to submit multiple small buffers in a single bio.
Signed-off-by: NeilBrown ne...@suse.de
Cc: sta...@kernel.org
---
drivers/md/linear.c| 12 +++-
drivers/md/multipath.c | 20
drivers/md/raid0.c | 13 +++--
drivers/md/raid1.c | 28 +---
drivers/md/raid10.c| 28 +---
5 files changed, 60 insertions(+), 41 deletions(-)
diff --git a/drivers/md/linear.c b/drivers/md/linear.c
index af2d39d..bb2a231 100644
--- a/drivers/md/linear.c
+++ b/drivers/md/linear.c
@@ -172,12 +172,14 @@ static linear_conf_t *linear_conf(mddev_t *mddev, int raid_disks)
disk_stack_limits(mddev-gendisk, rdev-bdev,
rdev-data_offset 9);
/* as we don't honour merge_bvec_fn, we must never risk
- * violating it, so limit -max_sector to one PAGE, as
- * a one page request is never in violation.
+ * violating it, so limit max_segments to 1 lying within
+ * a single page.
*/
- if (rdev-bdev-bd_disk-queue-merge_bvec_fn
- queue_max_sectors(mddev-queue) (PAGE_SIZE9))
- blk_queue_max_hw_sectors(mddev-queue, PAGE_SIZE9);
+ if (rdev-bdev-bd_disk-queue-merge_bvec_fn) {
+ blk_queue_max_segments(mddev-queue, 1);
+ blk_queue_segment_boundary(mddev-queue,
+ PAGE_CACHE_SIZE - 1);
+ }
conf-array_sectors += rdev-sectors;
cnt++;
diff --git a/drivers/md/multipath.c b/drivers/md/multipath.c
index 4b323f4..5558ebc 100644
--- a/drivers/md/multipath.c
+++ b/drivers/md/multipath.c
@@ -301,14 +301,16 @@ static int multipath_add_disk(mddev_t *mddev, mdk_rdev_t *rdev)
rdev-data_offset 9);
/* as we don't honour merge_bvec_fn, we must never risk
- * violating it, so limit -max_sector to one PAGE, as
- * a one page request is never in violation.
+ * violating it, so limit -max_segments to one, lying
+ * within a single page.
* (Note: it is very unlikely that a device with
* merge_bvec_fn will be involved in multipath.)
*/
- if (q-merge_bvec_fn
- queue_max_sectors(q) (PAGE_SIZE9))
-blk_queue_max_hw_sectors(mddev-queue, PAGE_SIZE9);
+ if (q-merge_bvec_fn) {
+blk_queue_max_segments(mddev-queue, 1);
+blk_queue_segment_boundary(mddev-queue,
+ PAGE_CACHE_SIZE - 1);
+ }
conf-working_disks++;
mddev-degraded--;
@@ -476,9 +478,11 @@ static int multipath_run (mddev_t *mddev)
/* as we don't honour merge_bvec_fn, we must never risk
* violating it, not that we ever expect a device with
* a merge_bvec_fn to be involved in multipath */
- if (rdev-bdev-bd_disk-queue-merge_bvec_fn
- queue_max_sectors(mddev-queue) (PAGE_SIZE9))
- blk_queue_max_hw_sectors(mddev-queue, PAGE_SIZE9);
+ if (rdev-bdev-bd_disk-queue-merge_bvec_fn) {
+ blk_queue_max_segments(mddev-queue, 1);
+ blk_queue_segment_boundary(mddev-queue,
+ PAGE_CACHE_SIZE - 1);
+ }
if (!test_bit(Faulty, rdev-flags))
conf-working_disks++;
diff --git a/drivers/md/raid0.c b/drivers/md/raid0.c
index a1f7147..377cf2a 100644
--- a/drivers/md/raid0.c
+++ b/drivers/md/raid0.c
@@ -176,14 +176,15 @@ static int create_strip_zones(mddev_t *mddev)
disk_stack_limits(mddev-gendisk, rdev1-bdev,
rdev1-data_offset 9);
/* as we don't honour merge_bvec_fn, we must never risk
- * violating it, so limit -max_sector to one PAGE, as
- * a one page request is never in violation.
+ * violating it, so limit -max_segments to 1, lying within
+ * a single page.
*/
- if (rdev1-bdev-bd_disk-queue-merge_bvec_fn
- queue_max_sectors(mddev-queue) (PAGE_SIZE9))
- blk_queue_max_hw_sectors(mddev-queue, PAGE_SIZE9);
-
+ if (rdev1-bdev-bd_disk-queue-merge_bvec_fn) {
+ blk_queue_max_segments(mddev-queue, 1);
+ blk_queue_segment_boundary(mddev-queue,
+ PAGE_CACHE_SIZE -
Processed: tagging 604457
Processing commands for cont...@bugs.debian.org: tags 604457 + patch moreinfo Bug #604457 [linux-image-2.6.26-2-xen-686] linux-image-2.6.26-2-xen-686: Raid10 exporting LV to xen results in error can't convert block across chunks or bigger than 64k Added tag(s) moreinfo and patch. thanks Stopping processing here. Please contact me if you need assistance. -- 604457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604457 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.12904797112688.transcr...@bugs.debian.org
Bug#604416: linux-image-2.6.32-5-sparc64: Kernels 2.6.32 hang on boot at Initializing cgroup subsys blkio
Since you can reproduce this on the latest upstream version (Linux 2.6.36), please report it upstream at https://bugzilla.kernel.org under product 'Platform Specific/Hardware', component 'SPARC64'. You should attach our kernel configuration, which you will find installed under /boot/config-2.6.36-trunk-sparc64. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 604416
Processing commands for cont...@bugs.debian.org: tags 604416 + moreinfo Bug #604416 [linux-2.6] linux-image-2.6.32-5-sparc64: Kernels 2.6.32 hang on boot at Initializing cgroup subsys blkio Ignoring request to alter tags of bug #604416 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 604416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604416 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.12904801544304.transcr...@bugs.debian.org
Processed: tagging 604416
Processing commands for cont...@bugs.debian.org: tags 604416 - d-i upstream Bug #604416 [linux-2.6] linux-image-2.6.32-5-sparc64: Kernels 2.6.32 hang on boot at Initializing cgroup subsys blkio Removed tag(s) upstream and d-i. thanks Stopping processing here. Please contact me if you need assistance. -- 604416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604416 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.12904801614346.transcr...@bugs.debian.org
Processed (with 1 errors): reopening 461644, reassign 604457 to linux-2.6, forcibly merging 604457 461644
Processing commands for cont...@bugs.debian.org: # Still present in lenny reopen 461644 Failed to reopen 461644: Not altering archived bugs; see unarchive. reassign 604457 linux-2.6 2.6.26-25lenny1 Bug #604457 [linux-image-2.6.26-2-xen-686] linux-image-2.6.26-2-xen-686: Raid10 exporting LV to xen results in error can't convert block across chunks or bigger than 64k Bug reassigned from package 'linux-image-2.6.26-2-xen-686' to 'linux-2.6'. Bug No longer marked as found in versions linux-2.6/2.6.26-25lenny1. Bug #604457 [linux-2.6] linux-image-2.6.26-2-xen-686: Raid10 exporting LV to xen results in error can't convert block across chunks or bigger than 64k There is no source info for the package 'linux-2.6' at version '2.6.26-25lenny1' with architecture '' Unable to make a source version for version '2.6.26-25lenny1' Bug Marked as found in versions 2.6.26-25lenny1. forcemerge 604457 461644 Bug#604457: linux-image-2.6.26-2-xen-686: Raid10 exporting LV to xen results in error can't convert block across chunks or bigger than 64k Bug number 461644 not found. (Is it archived?) thanks Stopping processing here. Please contact me if you need assistance. -- 461644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461644 604457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604457 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.12904804015802.transcr...@bugs.debian.org
Processed: unarchiving 461644, reopening 461644, reassign 604457 to linux-2.6, forcibly merging 604457 461644
Processing commands for cont...@bugs.debian.org:
unarchive 461644
Bug #461644 {Done: maximilian attems m...@stro.at} [linux-2.6]
linux-image-2.6.18-5-xen-686: Exporting an lvm-on-md LV to Xen as a disk
results in kernel errors and corrupt filesystems
Unarchived Bug 461644
# Still present in lenny
reopen 461644
Bug #461644 {Done: maximilian attems m...@stro.at} [linux-2.6]
linux-image-2.6.18-5-xen-686: Exporting an lvm-on-md LV to Xen as a disk
results in kernel errors and corrupt filesystems
reassign 604457 linux-2.6 2.6.26-25lenny1
Bug #604457 [linux-2.6] linux-image-2.6.26-2-xen-686: Raid10 exporting LV to
xen results in error can't convert block across chunks or bigger than 64k
Ignoring request to reassign bug #604457 to the same package
Bug #604457 [linux-2.6] linux-image-2.6.26-2-xen-686: Raid10 exporting LV to
xen results in error can't convert block across chunks or bigger than 64k
There is no source info for the package 'linux-2.6' at version
'2.6.26-25lenny1' with architecture ''
Unable to make a source version for version '2.6.26-25lenny1'
Ignoring request to alter found versions of bug #604457 to the same values
previously set
forcemerge 604457 461644
Bug#604457: linux-image-2.6.26-2-xen-686: Raid10 exporting LV to xen results in
error can't convert block across chunks or bigger than 64k
Bug#461644: linux-image-2.6.18-5-xen-686: Exporting an lvm-on-md LV to Xen as a
disk results in kernel errors and corrupt filesystems
Forcibly Merged 461644 604457.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
604457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604457
461644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461644
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.12904807388089.transcr...@bugs.debian.org
Re: ARM: OMAP2+ flavour
On Tue, 2010-11-23 at 00:58 +0100, Sebastian Reichel wrote: Hi, I'm currently bringing Debian to Nokia's N900 (see [1]). For this I also want to use a kernel package directly from Debian. The 2.6.36 mainline kernel, which is currently used in the Debian experimental contains the most important drivers, so no patches are needed in the kernel package. (check [2] to see what would be working on the N900 with this kernel) For the new flavour an omap entry in config/armel/defines is needed [3] and a new config.omap file [4]. The config file is not yet optimal, but works. Can you please give me some advice how to proceed? [...] AIUI there are many versions of OMAP; can we build one flavour that would run on all/most of them? I would really like to use the forthcoming support for Device Trees to limit the number of different ARM kernel images we need to build. We would presumably need to rework the definition of 'flavours' so multiple flavours could use the same kernel images and different DTs. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
[PATCH 1/3] decnet: Move to staging
Recent review has revealed several bugs in obscure protocol implementations that can be exploited by local users for denial of service or privilege escalation. The decnet protocol (PF_DECnet) is unmaintained. Since 2.6.12-rc2 the only changes appear to be adjustments for net API changes and fixes for bugs found by inspection. This protocol generally should not be enabled by distributions, since the cost of a security flaw affecting all installed systems presumably outweighs the benefit to the few (if any) legitimate users. Signed-off-by: Ben Hutchings b...@decadent.org.uk --- drivers/staging/Kconfig |2 ++ net/Kconfig |2 -- net/decnet/Kconfig |3 +++ 3 files changed, 5 insertions(+), 2 deletions(-) diff --git a/drivers/staging/Kconfig b/drivers/staging/Kconfig index 5eafdf4..dd94cb2 100644 --- a/drivers/staging/Kconfig +++ b/drivers/staging/Kconfig @@ -175,5 +175,7 @@ source drivers/staging/intel_sst/Kconfig source drivers/staging/speakup/Kconfig +source net/decnet/Kconfig + endif # !STAGING_EXCLUDE_BUILD endif # STAGING diff --git a/net/Kconfig b/net/Kconfig index 55fd82e..9e4fc29 100644 --- a/net/Kconfig +++ b/net/Kconfig @@ -186,7 +186,6 @@ config BRIDGE_NETFILTER source net/netfilter/Kconfig source net/ipv4/netfilter/Kconfig source net/ipv6/netfilter/Kconfig -source net/decnet/netfilter/Kconfig source net/bridge/netfilter/Kconfig endif @@ -201,7 +200,6 @@ source net/802/Kconfig source net/bridge/Kconfig source net/dsa/Kconfig source net/8021q/Kconfig -source net/decnet/Kconfig source net/llc/Kconfig source net/ipx/Kconfig source drivers/net/appletalk/Kconfig diff --git a/net/decnet/Kconfig b/net/decnet/Kconfig index 7914fd6..9d17166 100644 --- a/net/decnet/Kconfig +++ b/net/decnet/Kconfig @@ -41,3 +41,6 @@ config DECNET_ROUTER See file:Documentation/networking/decnet.txt for more information. +if NETFILTER +source net/decnet/netfilter/Kconfig +endif -- 1.7.2.3 -- 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/1290484313.6770.1328.ca...@localhost
[PATCH 2/3] econet: Move to staging
Recent review has revealed several bugs in obscure protocol implementations that can be exploited by local users for denial of service or privilege escalation. The econet protocol (PF_ECONET) is unmaintained. There appear to be no published applications for it, and it has never progressed beyond 'experimental' status. This protocol generally should not be enabled by distributions, since the cost of a security flaw affecting all installed systems presumably outweighs the benefit to the few (if any) legitimate users. Signed-off-by: Ben Hutchings b...@decadent.org.uk --- drivers/staging/Kconfig |2 ++ net/Kconfig |1 - 2 files changed, 2 insertions(+), 1 deletions(-) diff --git a/drivers/staging/Kconfig b/drivers/staging/Kconfig index dd94cb2..a9dd984 100644 --- a/drivers/staging/Kconfig +++ b/drivers/staging/Kconfig @@ -177,5 +177,7 @@ source drivers/staging/speakup/Kconfig source net/decnet/Kconfig +source net/econet/Kconfig + endif # !STAGING_EXCLUDE_BUILD endif # STAGING diff --git a/net/Kconfig b/net/Kconfig index 9e4fc29..059c9f1 100644 --- a/net/Kconfig +++ b/net/Kconfig @@ -205,7 +205,6 @@ source net/ipx/Kconfig source drivers/net/appletalk/Kconfig source net/x25/Kconfig source net/lapb/Kconfig -source net/econet/Kconfig source net/wanrouter/Kconfig source net/phonet/Kconfig source net/ieee802154/Kconfig -- 1.7.2.3 -- 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/1290484348.6770.1329.ca...@localhost
[PATCH 3/3] x25: Move to staging
Recent review has revealed several bugs in obscure protocol implementations that can be exploited by local users for denial of service or privilege escalation. The x25 protocol (PF_X25) receives only 'odd fixes'. There appear to be no published applications for it, and it has never progressed beyond 'experimental' status. This protocol generally should not be enabled by distributions, since the cost of a security flaw affecting all installed systems presumably outweighs the benefit to the few (if any) legitimate users. Signed-off-by: Ben Hutchings b...@decadent.org.uk --- I'm somewhat less sure about this one; maybe it's improving? But there is little enough sign of any usefulness after 10 years. There are several X25 dependencies that presumably should be moved too. Ben. drivers/staging/Kconfig |2 ++ net/Kconfig |1 - 2 files changed, 2 insertions(+), 1 deletions(-) diff --git a/drivers/staging/Kconfig b/drivers/staging/Kconfig index a9dd984..1347242 100644 --- a/drivers/staging/Kconfig +++ b/drivers/staging/Kconfig @@ -179,5 +179,7 @@ source net/decnet/Kconfig source net/econet/Kconfig +source net/x25/Kconfig + endif # !STAGING_EXCLUDE_BUILD endif # STAGING diff --git a/net/Kconfig b/net/Kconfig index 059c9f1..1d396ba 100644 --- a/net/Kconfig +++ b/net/Kconfig @@ -203,7 +203,6 @@ source net/8021q/Kconfig source net/llc/Kconfig source net/ipx/Kconfig source drivers/net/appletalk/Kconfig -source net/x25/Kconfig source net/lapb/Kconfig source net/wanrouter/Kconfig source net/phonet/Kconfig -- 1.7.2.3 -- 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/1290484528.6770.1336.ca...@localhost
Re: [PATCH 2/3] econet: Move to staging
On Tue, 23 Nov 2010 03:52:28 + Ben Hutchings b...@decadent.org.uk wrote: Recent review has revealed several bugs in obscure protocol implementations that can be exploited by local users for denial of service or privilege escalation. The econet protocol (PF_ECONET) is unmaintained. There appear to be no published applications for it, and it has never progressed beyond 'experimental' status. This protocol generally should not be enabled by distributions, since the cost of a security flaw affecting all installed systems presumably outweighs the benefit to the few (if any) legitimate users. Signed-off-by: Ben Hutchings b...@decadent.org.uk This I agree with. Probably the Arcnet devices as well. Most distro's don't enable it anyway. -- 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/20101122203236.029c8...@nehalam
Re: [PATCH 1/3] decnet: Move to staging
On Tue, 23 Nov 2010 03:51:53 + Ben Hutchings b...@decadent.org.uk wrote: Recent review has revealed several bugs in obscure protocol implementations that can be exploited by local users for denial of service or privilege escalation. The decnet protocol (PF_DECnet) is unmaintained. Since 2.6.12-rc2 the only changes appear to be adjustments for net API changes and fixes for bugs found by inspection. This protocol generally should not be enabled by distributions, since the cost of a security flaw affecting all installed systems presumably outweighs the benefit to the few (if any) legitimate users. Signed-off-by: Ben Hutchings b...@decadent.org.uk NAK there are still users and stuff does get fixed. If you don't like it then disable it from config. -- -- 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/20101122203131.7cbd6...@nehalam
Re: [PATCH 3/3] x25: Move to staging
On Tue, 23 Nov 2010 03:55:28 + Ben Hutchings b...@decadent.org.uk wrote: Recent review has revealed several bugs in obscure protocol implementations that can be exploited by local users for denial of service or privilege escalation. The x25 protocol (PF_X25) receives only 'odd fixes'. There appear to be no published applications for it, and it has never progressed beyond 'experimental' status. This protocol generally should not be enabled by distributions, since the cost of a security flaw affecting all installed systems presumably outweighs the benefit to the few (if any) legitimate users. Signed-off-by: Ben Hutchings b...@decadent.org.uk --- I'm somewhat less sure about this one; maybe it's improving? But there is little enough sign of any usefulness after 10 years. There are several X25 dependencies that presumably should be moved too. No. If you don't like it then don't enable it. -- 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/20101122203155.27534...@nehalam
[PATCH] Kbuild: kconfig: Verbose version of --listnewconfig
If the KBUILD_VERBOSE environment variable is set to non-zero, show
the default values of new symbols and not just their names.
Based on work by Bastian Blank wa...@debian.org and
maximilian attems m...@stro.at.
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
scripts/kconfig/conf.c | 90 +++-
scripts/kconfig/confdata.c |1 +
scripts/kconfig/expr.h |2 +
3 files changed, 83 insertions(+), 10 deletions(-)
diff --git a/scripts/kconfig/conf.c b/scripts/kconfig/conf.c
index 5459a38..6d37d5c 100644
--- a/scripts/kconfig/conf.c
+++ b/scripts/kconfig/conf.c
@@ -363,7 +363,6 @@ static void conf(struct menu *menu)
switch (prop-type) {
case P_MENU:
if ((input_mode == silentoldconfig ||
-input_mode == listnewconfig ||
input_mode == oldnoconfig)
rootEntry != menu) {
check_conf(menu);
@@ -423,11 +422,7 @@ static void check_conf(struct menu *menu)
if (sym !sym_has_value(sym)) {
if (sym_is_changable(sym) ||
(sym_is_choice(sym) sym_get_tristate_value(sym) == yes))
{
- if (input_mode == listnewconfig) {
- if (sym-name !sym_is_choice_value(sym)) {
- printf(%s%s\n, CONFIG_, sym-name);
- }
- } else if (input_mode != oldnoconfig) {
+ if (input_mode != oldnoconfig) {
if (!conf_cnt++)
printf(_(*\n* Restart
config...\n*\n));
rootEntry = menu_get_parent_menu(menu);
@@ -440,6 +435,78 @@ static void check_conf(struct menu *menu)
check_conf(child);
}
+static void report_conf(struct menu *menu, bool verbose)
+{
+ struct symbol *sym;
+ struct menu *child;
+ int l;
+ const char *str;
+
+ if (!menu_is_visible(menu))
+ return;
+
+ if (verbose menu == rootmenu) {
+ printf(\n#\n
+ # Changes:\n
+ #\n);
+ }
+
+ sym = menu-sym;
+ if (sym (sym-flags SYMBOL_NEW)
+ sym_is_changable(sym) sym-name !sym_is_choice_value(sym)) {
+ if (verbose) {
+ switch (sym-type) {
+ case S_BOOLEAN:
+ case S_TRISTATE:
+ switch (sym_get_tristate_value(sym)) {
+ case no:
+ printf(# CONFIG_%s is not set\n,
sym-name);
+ break;
+ case mod:
+ printf(CONFIG_%s=m\n, sym-name);
+ break;
+ case yes:
+ printf(CONFIG_%s=y\n, sym-name);
+ break;
+ }
+ break;
+ case S_STRING:
+ str = sym_get_string_value(sym);
+ printf(CONFIG_%s=\, sym-name);
+ while (1) {
+ l = strcspn(str, \\\);
+ if (l) {
+ fwrite(str, l, 1, stdout);
+ str += l;
+ }
+ if (!*str)
+ break;
+ printf(\\%c, *str++);
+ }
+ fputs(\\n, stdout);
+ break;
+ case S_HEX:
+ str = sym_get_string_value(sym);
+ if (str[0] != '0' || (str[1] != 'x' str[1]
!= 'X')) {
+ printf(CONFIG_%s=%s\n, sym-name,
str);
+ break;
+ }
+ case S_INT:
+ str = sym_get_string_value(sym);
+ printf(CONFIG_%s=%s\n, sym-name, str);
+ break;
+ default:
+ break;
+ }
+ } else {
+ printf(CONFIG_%s\n, sym-name);
+ }
+ }
+
+ for (child = menu-list; child; child = child-next)
+ report_conf(child, verbose);
+}
+
static struct option long_opts[] = {
{oldaskconfig,no_argument, NULL,
Re: [PATCH 3/3] x25: Move to staging
There are users of linux X.25 for production environments, please don't.. It works well enough, there have been some X.25 over TCP bits of code floating around the Internet and mailing lists. There is an x25 loopback device on sourceforge using tuntap which I have been using to test slowly removing the bkls. Regards, Andrew. On Tue, Nov 23, 2010 at 3:31 PM, Stephen Hemminger shemmin...@vyatta.com wrote: On Tue, 23 Nov 2010 03:55:28 + Ben Hutchings b...@decadent.org.uk wrote: Recent review has revealed several bugs in obscure protocol implementations that can be exploited by local users for denial of service or privilege escalation. The x25 protocol (PF_X25) receives only 'odd fixes'. There appear to be no published applications for it, and it has never progressed beyond 'experimental' status. This protocol generally should not be enabled by distributions, since the cost of a security flaw affecting all installed systems presumably outweighs the benefit to the few (if any) legitimate users. Signed-off-by: Ben Hutchings b...@decadent.org.uk --- I'm somewhat less sure about this one; maybe it's improving? But there is little enough sign of any usefulness after 10 years. There are several X25 dependencies that presumably should be moved too. No. If you don't like it then don't enable it. -- 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/aanlkti=la7o0o16drqf6af1+mgpapv5sum-hqnc1o...@mail.gmail.com
Bug#604613: ath5k driver refuses to get an IP address from dhclient in squeeze
Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-27 When I use the ath5k driver, it fails to resolve an IP address from using the dhclient command. Here are the commands that I entered: ifconfig eth0 down ifconfig wlan0 up iwlist wlan0 scan iwconfig wlan0 essid default dhclient wlan0 These steps worked with Lenny. The card that I'm using is an SMCWPCI-G based Atheros card, which I believe uses the AR5007G chipset. Output from dmesg | grep ath5k: [5.689292] ath5k :00:09.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [5.689353] ath5k :00:09.0: registered as 'phy0' [6.416794] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) Output from kern | grep ath5k: Nov 22 14:12:05 debian-box kernel: [5.621466] ath5k :00:09.0: PCI INT A - GSI 17 (level, low) - IRQ 17 Nov 22 14:12:05 debian-box kernel: [5.621531] ath5k :00:09.0: registered as 'phy0' Nov 22 14:12:05 debian-box kernel: [6.231139] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) Nov 22 17:19:45 debian-box kernel: [5.766165] ath5k :00:09.0: PCI INT A - GSI 17 (level, low) - IRQ 17 Nov 22 17:19:45 debian-box kernel: [5.766235] ath5k :00:09.0: registered as 'phy0' Nov 22 17:19:45 debian-box kernel: [6.469400] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) Nov 22 19:34:41 debian-box kernel: [5.689279] ath5k :00:09.0: PCI INT A - GSI 17 (level, low) - IRQ 17 Nov 22 19:34:41 debian-box kernel: [5.689345] ath5k :00:09.0: registered as 'phy0' Nov 22 19:34:41 debian-box kernel: [6.299683] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) Nov 22 19:45:10 debian-box kernel: [5.689292] ath5k :00:09.0: PCI INT A - GSI 17 (level, low) - IRQ 17 Nov 22 19:45:10 debian-box kernel: [5.689353] ath5k :00:09.0: registered as 'phy0' Nov 22 19:45:10 debian-box kernel: [6.416794] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) Output from kern | grep wlan0: Nov 22 14:14:52 debian-box kernel: [ 176.720056] ADDRCONF(NETDEV_UP): wlan0: link is not ready Nov 22 14:14:54 debian-box kernel: [ 178.558439] wlan0: direct probe to AP 00:15:e9:65:fb:86 (try 1) Nov 22 14:14:54 debian-box kernel: [ 178.756014] wlan0: direct probe to AP 00:15:e9:65:fb:86 (try 2) Nov 22 14:14:54 debian-box kernel: [ 178.956008] wlan0: direct probe to AP 00:15:e9:65:fb:86 (try 3) Nov 22 14:14:55 debian-box kernel: [ 179.156007] wlan0: direct probe to AP 00:15:e9:65:fb:86 timed out Nov 22 19:35:56 debian-box kernel: [ 84.311427] ADDRCONF(NETDEV_UP): wlan0: link is not ready Nov 22 19:37:32 debian-box kernel: [ 180.328121] wlan0: direct probe to AP 00:15:e9:65:fb:86 (try 1) Nov 22 19:37:32 debian-box kernel: [ 180.528011] wlan0: direct probe to AP 00:15:e9:65:fb:86 (try 2) Nov 22 19:37:32 debian-box kernel: [ 180.602991] wlan0: direct probe responded Nov 22 19:37:32 debian-box kernel: [ 180.602995] wlan0: authenticate with AP 00:15:e9:65:fb:86 (try 1) Nov 22 19:37:32 debian-box kernel: [ 180.86] wlan0: authenticate with AP 00:15:e9:65:fb:86 (try 2) Nov 22 19:37:32 debian-box kernel: [ 181.07] wlan0: authenticate with AP 00:15:e9:65:fb:86 (try 3) Nov 22 19:37:33 debian-box kernel: [ 181.26] wlan0: authentication with AP 00:15:e9:65:fb:86 timed out The only issue I can see is in the last result, which is reporting authentication problems. However, I really don't know of any way of correcting the problem. I did, however, test the ath5k module against two other distros, Fedora 14, and Ubuntu 10.10, which use the 2.6.35 kernel and both were able to connect successfully. So this may be an upstream problem that was corrected, but wasn't ported back to this kernel. I don't know for sure because I'm not a kernel developer. Anyone willing to take a stab at it?
Re: [PATCH 1/3] decnet: Move to staging
From: Stephen Hemminger shemmin...@vyatta.com Date: Mon, 22 Nov 2010 20:31:31 -0800 On Tue, 23 Nov 2010 03:51:53 + Ben Hutchings b...@decadent.org.uk wrote: Recent review has revealed several bugs in obscure protocol implementations that can be exploited by local users for denial of service or privilege escalation. The decnet protocol (PF_DECnet) is unmaintained. Since 2.6.12-rc2 the only changes appear to be adjustments for net API changes and fixes for bugs found by inspection. This protocol generally should not be enabled by distributions, since the cost of a security flaw affecting all installed systems presumably outweighs the benefit to the few (if any) legitimate users. Signed-off-by: Ben Hutchings b...@decadent.org.uk NAK there are still users and stuff does get fixed. If you don't like it then disable it from config. Seriously, I can't even remember a bonifides security flaw in decnet being found recently and in fact the decnet stack is very well written code. -- 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/20101122.211923.193717252.da...@davemloft.net
Bug#604470: linux-image-2.6.32-5-openvz-amd64: degraded inbound network bandwidth
There is some other strange effect: after some idle time the network in the container stop working at all. I see this problem (drop connectivity) only on the new created for testing container may be because it is idle most of time, while other containers are production and are getting activity continuously. Here is what You asking for (netstat -s): Ip: 7298988 total packets received 0 forwarded 0 incoming packets discarded 7262036 incoming packets delivered 4830632 requests sent out Icmp: 13593 ICMP messages received 2 input ICMP message failed. ICMP input histogram: destination unreachable: 357 timeout in transit: 34 redirects: 13106 echo requests: 52 echo replies: 44 949 ICMP messages sent 0 ICMP messages failed ICMP output histogram: destination unreachable: 719 echo request: 178 echo replies: 52 IcmpMsg: InType0: 44 InType3: 357 InType5: 13106 InType8: 52 InType11: 34 OutType0: 52 OutType3: 719 OutType8: 178 Tcp: 85940 active connections openings 91936 passive connection openings 303 failed connection attempts 3309 connection resets received 6 connections established 7227101 segments received 4776345 segments send out 32345 segments retransmited 9 bad segments received. 2180 resets sent Udp: 20616 packets received 726 packets to unknown port received. 0 packet receive errors 20993 packets sent UdpLite: TcpExt: 265 invalid SYN cookies received 69 resets received for embryonic SYN_RECV sockets 163 packets pruned from receive queue because of socket buffer overrun 84541 TCP sockets finished time wait in fast timer 26 time wait sockets recycled by time stamp 5 packets rejects in established connections because of timestamp 27496 delayed acks sent 2 delayed acks further delayed because of locked socket Quick ack mode was activated 8377 times 2255888 packets directly queued to recvmsg prequeue. 1439293771 bytes directly in process context from backlog 3017217537 bytes directly received in process context from prequeue 2255586 packet headers predicted 3511681 packets header predicted and directly queued to user 452075 acknowledgments not containing data payload received 717999 predicted acknowledgments 10 times recovered from packet loss due to fast retransmit 5885 times recovered from packet loss by selective acknowledgements 3 bad SACK blocks received Detected reordering 10 times using FACK Detected reordering 5 times using SACK Detected reordering 3 times using time stamp 4 congestion windows fully recovered without slow start 24 congestion windows partially recovered using Hoe heuristic 181 congestion windows recovered without slow start by DSACK 95 congestion windows recovered without slow start after partial ack 8805 TCP data loss events TCPLostRetransmit: 495 8 timeouts after reno fast retransmit 1603 timeouts after SACK recovery 1006 timeouts in loss state 14585 fast retransmits 503 forward retransmits 8431 retransmits in slow start 3385 other TCP timeouts 5 classic Reno fast retransmits failed 952 SACK retransmits failed 7885 packets collapsed in receive queue due to low socket buffer 8407 DSACKs sent for old packets 115 DSACKs sent for out of order packets 1623 DSACKs received 29 DSACKs for out of order packets received 27 connections reset due to unexpected data 18 connections reset due to early user close 188 connections aborted due to timeout TCPDSACKIgnoredOld: 1238 TCPDSACKIgnoredNoUndo: 213 TCPSpuriousRTOs: 49 TCPSackShiftFallback: 49650 IpExt: InOctets: 495299200 OutOctets: -1995348470 -- *** Vladimir Stavrinov * vstavri...@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/20101123074456.ga3...@magus.playfast.oz
Bug#604627: linux-image-2.6.32-5-amd64: megasas: Failed to alloc kernel SGL buffer for IOCTL
Package: linux-2.6 Version: 2.6.32-27 Severity: important Hi, I am unable to do short and long tests initiated with smartd/smartctl. calling 'smartctl -d megaraid,0 /dev/sda -t short' gives: smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Short offline self test failed [Cannot allocate memory] megasas: Failed to alloc kernel SGL buffer for IOCTL calling 'smartctl -i -d megaraid,0 /dev/sda' gives: smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Device: HITACHI HUS153014VLS300 Version: A5C0 Serial number: Device type: disk Transport protocol: SAS Local Time is: Tue Nov 23 08:29:25 2010 CET Device supports SMART and is Enabled Temperature Warning Enabled dmesg info: --- megasas: 00.00.04.01 Thu July 24 11:41:51 PST 2008 megasas: 0x1000:0x0060:0x1000:0x1013: bus 96:slot 0:func 0 megaraid_sas :60:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 megaraid_sas :60:00.0: setting latency timer to 64 lspci info: --- 60:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 1078 (rev 04) Subsystem: LSI Logic / Symbios Logic Device 1013 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at dfa4 (64-bit, non-prefetchable) [size=256K] I/O ports at 3000 [size=256] Memory at dfa0 (64-bit, non-prefetchable) [size=256K] [virtual] Expansion ROM at 4010 [disabled] [size=64K] Capabilities: [b0] Express Endpoint, MSI 00 Capabilities: [c4] Message Signalled Interrupts: Mask- 64bit+ Queue=0/2 Enable- Capabilities: [d4] MSI-X: Enable- Mask- TabSize=4 Capabilities: [e0] Power Management version 2 Capabilities: [ec] Vital Product Data ? Capabilities: [100] Power Budgeting ? Kernel driver in use: megaraid_sas Kernel modules: megaraid_sas It seems I am not alone with this problem: http://www.mail-archive.com/linux-powere...@dell.com/msg02575.html and lots of hits from 2007 and 2008 from RHEL. -- Package-specific info: ** Kernel log: boot messages should be attached -- System Information: Debian Release: squeeze/sid Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: lang=de...@euro, lc_ctype=de...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.32-5-amd64 depends on: ii debconf [debconf-2.0] 1.5.36 Debian configuration management sy ii initramfs-tools [linux-initra 0.98.5 tools for generating an initramfs ii linux-base2.6.32-27 Linux image base package ii module-init-tools 3.12-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.32-5-amd64 recommends: ii firmware-linux-free 2.6.32-27 Binary firmware for various driver Versions of packages linux-image-2.6.32-5-amd64 suggests: pn grub | lilo none (no description available) pn linux-doc-2.6.32 none (no description available) Versions of packages linux-image-2.6.32-5-amd64 is related to: pn firmware-bnx2 none (no description available) pn firmware-bnx2xnone (no description available) pn firmware-ipw2x00 none (no description available) pn firmware-ivtv none (no description available) pn firmware-iwlwifi none (no description available) pn firmware-linuxnone (no description available) pn firmware-linux-nonfreenone (no description available) pn firmware-qlogic none (no description available) pn firmware-ralink none (no description available) pn xen-hypervisornone (no description available) -- debconf information excluded -- 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/20101123074832.32293.54775.report...@lokalhorst.gotdns.com
