Processed: Re: Bug#453120: mptscsi: Massive workload causes FS to be remounted readonly in VMware guest
Processing commands for [EMAIL PROTECTED]: tags 453120 - moreinfo Bug#453120: mptscsi: Massive workload causes FS to be remounted readonly in VMware guest Tags were: moreinfo Tags removed: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453120: mptscsi: Massive workload causes FS to be remounted readonly in VMware guest
tags 453120 - moreinfo thanks Am Dienstag, den 27.11.2007, 18:40 +0100 schrieb maximilian attems: tags 453120 moreinfo severity 453120 normal stop On Tue, Nov 27, 2007 at 03:34:31PM +0100, Sebastian Dröge wrote: Package: linux-2.6 Severity: important hmm your report is missing important info, you don't tell us which debian version against it is? - http://wiki.debian.org/DebianKernelReportingBugs Hi, this is with the etch Kernel, i.e. 2.6.18.dfsg.1-13. Hi, when running a Debian system as VMware guest system one could get SCSI timeouts when there is massive workload on the host system. Since some kernel version these will get the filesystems remounted read-only, which probably makes sense for real hardware, but doesn't make sense for emulated hardware. Instead it should just wait a bit longer. See http://www.tuxyturvy.com/blog/index.php?/archives/31-VMware-ESX-and-ext3-journal-aborts.html for some details and what needs to be changed in the kernel. Redhat and SuSE seem to have this change in their kernels already it seems and without that change it's impossible to run Debian as VMWare guest reliable. Bye as this page only describes upstream changes, did you try newer linux-2.6 images from backports.org 2.6.22 or 2.6.23 from trunk snapshots see apt lines on http://wiki.debian.org/DebianKernel Thanks, it's fixed at least in 2.6.23-1~experimental.1~snapshot.9819 Would be nice if the relevant change could be backported to etch-updates or similar. :) 2.6.23-1~experimental.1~snapshot.9819 has an equivalent change to the one at the URL above. Bye -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453382: linux-source-2.6.18: UDF filsystem driver report errors
Package: linux-source-2.6.18 Version: 2.6.18.dfsg.1-12etch2 Severity: normal As some errors occurs in UDF filesystem, I recompiled this module to activate log/debug facility. Hereafter I detail first (1) user reported error, and second (2), logd error in syslog. Finally (3), the linux packages installed.. 1/ User level error: 1 rm: ne peut enlever `/mnt/iomega/data/*/*.zip': Aucun fichier ou répertoire de ce type 1 cp: ne peut créer le fichier régulier `/mnt/iomega/data/nfs_corfouc_Dossiers.tgz': Erreur d'entrée/sortie 1 tar: /mnt/iomega/data/smb_islande_bergez.tgz: ne peut open: Erreur d'entrée/sortie 1 split: /mnt/iomega/data/smb_islande_bergez.tgz-aa: Erreur d'entrée/sortie 1 split: /mnt/iomega/data/smb_sicile_douzet_fullsync.tgz-ag: Erreur d'entrée/sortie 1 cp: ne peut créer le fichier régulier `/mnt/iomega/data/smb_synchro_file_dates.c': Erreur d'entrée/sortie 1 cp: ne peut créer le fichier régulier `/mnt/iomega/data/smb_synchro_file_dates.exe': Erreur d'entrée/sortie 1 du: ne peut accéder `/mnt/iomega/atlantis_restauration_windows/Restauration/Rest_1/#Root': Permission non accordée 1 du: ne peut accéder `/mnt/iomega/atlantis_restauration_windows/Restauration/Rest_2/#Root/gay': Permission non accordée 1 du: ne peut accéder `/mnt/iomega/poubelle': Permission non accordée 2/ Syslog errors: 1 Nov 29 00:05:01 comp /USR/SBIN/CRON[4946]: (root) CMD (( . sauvegarde.sh . 2 Nov 29 00:05:02 comp kernel: UDF-fs DEBUG fs/udf/lowlevel.c:46:udf_get_last_session: XA disk: no, vol_desc_start=0 3 Nov 29 00:05:02 comp kernel: UDF-fs DEBUG fs/udf/super.c:1563:udf_fill_super: Multi-session=0 4 Nov 29 00:05:02 comp kernel: UDF-fs DEBUG fs/udf/super.c:554:udf_vrs: Starting at sector 16 (2048 byte sectors) 5 Nov 29 00:05:02 comp kernel: UDF-fs DEBUG fs/udf/super.c:895:udf_load_pvoldesc: recording time 1166730473/924891, 2006/12/21 21:47 (1078) 6 Nov 29 00:05:02 comp kernel: UDF-fs DEBUG fs/udf/super.c:906:udf_load_pvoldesc: volIdent[] = 'Cartouche hebdomadaire D' 7 Nov 29 00:05:02 comp kernel: UDF-fs DEBUG fs/udf/super.c:913:udf_load_pvoldesc: volSetIdent[] = '[EMAIL PROTECTED] hebdomadaire D' 8 Nov 29 00:05:02 comp kernel: UDF-fs DEBUG fs/udf/super.c:1105:udf_load_logicalvol: Partition (0:0) type 1 on volume 1 9 Nov 29 00:05:02 comp kernel: UDF-fs DEBUG fs/udf/super.c:1115:udf_load_logicalvol: FileSet found in LogicalVolDesc at block=1044, partition=0 10 Nov 29 00:05:02 comp kernel: UDF-fs DEBUG fs/udf/super.c:943:udf_load_partdesc: Searching map: (0 == 0) 11 Nov 29 00:05:02 comp kernel: UDF-fs DEBUG fs/udf/super.c:984:udf_load_partdesc: unallocSpaceBitmap (part 0) @ 0 12 Nov 29 00:05:02 comp kernel: UDF-fs DEBUG fs/udf/super.c:1025:udf_load_partdesc: Partition (0:0 type 1511) starts at physical 274, block length 17090349 13 Nov 29 00:05:02 comp kernel: UDF-fs DEBUG fs/udf/super.c:1355:udf_load_partition: Using anchor in block 256 14 Nov 29 00:05:02 comp kernel: UDF-fs DEBUG fs/udf/super.c:1591:udf_fill_super: Lastblock=0 15 Nov 29 00:05:03 comp kernel: UDF-fs DEBUG fs/udf/super.c:867:udf_find_fileset: Fileset at block=1044, partition=0 16 Nov 29 00:05:03 comp kernel: UDF-fs DEBUG fs/udf/super.c:929:udf_load_fileset: Rootdir at block=1046, partition=0 17 Nov 29 00:05:03 comp kernel: UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume 'Cartouche hebdomadaire D', timestamp 2006/12/21 21:47 (1078) 18 Nov 29 00:05:05 comp kernel: UDF-fs DEBUG fs/udf/balloc.c:189:udf_bitmap_free_blocks: bit 13195 already set 19 Nov 29 00:05:05 comp kernel: UDF-fs DEBUG fs/udf/balloc.c:190:udf_bitmap_free_blocks: byte=fffd 20 Nov 29 00:05:05 comp kernel: UDF-fs DEBUG fs/udf/balloc.c:189:udf_bitmap_free_blocks: bit 13196 already set 21 Nov 29 00:05:05 comp kernel: UDF-fs DEBUG fs/udf/balloc.c:190:udf_bitmap_free_blocks: byte=fffd 22 Nov 29 00:05:05 comp kernel: UDF-fs DEBUG fs/udf/balloc.c:189:udf_bitmap_free_blocks: bit 13197 already set 23 Nov 29 00:05:05 comp kernel: UDF-fs DEBUG fs/udf/balloc.c:190:udf_bitmap_free_blocks: byte=fffd 24 Nov 29 00:05:05 comp kernel: UDF-fs DEBUG fs/udf/balloc.c:189:udf_bitmap_free_blocks: bit 13198 already set 25 Nov 29 00:05:05 comp kernel: UDF-fs DEBUG fs/udf/balloc.c:190:udf_bitmap_free_blocks: byte=fffd 26 Nov 29 00:05:05 comp kernel: UDF-fs DEBUG fs/udf/balloc.c:189:udf_bitmap_free_blocks: bit 13199 already set 27 Nov 29 00:05:05 comp kernel: UDF-fs DEBUG fs/udf/balloc.c:190:udf_bitmap_free_blocks: byte=fffd 28 Nov 29 00:05:05 comp kernel: UDF-fs DEBUG fs/udf/balloc.c:189:udf_bitmap_free_blocks: bit 13200 already set 29 Nov 29 00:05:05 comp kernel: UDF-fs DEBUG fs/udf/balloc.c:190:udf_bitmap_free_blocks: byte= 3 30 Nov 29 00:05:05 comp kernel: UDF-fs DEBUG fs/udf/balloc.c:189:udf_bitmap_free_blocks: bit 13201 already set 31 Nov 29 00:05:05 comp kernel: UDF-fs DEBUG fs/udf/balloc.c:190:udf_bitmap_free_blocks: byte= 3 32 Nov 29 00:07:27 comp kernel:
Bug#453120: mptscsi: Massive workload causes FS to be remounted readonly in VMware guest
Am Donnerstag, den 29.11.2007, 09:30 +0100 schrieb Sebastian Dröge: tags 453120 - moreinfo thanks Am Dienstag, den 27.11.2007, 18:40 +0100 schrieb maximilian attems: tags 453120 moreinfo severity 453120 normal stop On Tue, Nov 27, 2007 at 03:34:31PM +0100, Sebastian Dröge wrote: Package: linux-2.6 Severity: important hmm your report is missing important info, you don't tell us which debian version against it is? - http://wiki.debian.org/DebianKernelReportingBugs Hi, this is with the etch Kernel, i.e. 2.6.18.dfsg.1-13. Hi, when running a Debian system as VMware guest system one could get SCSI timeouts when there is massive workload on the host system. Since some kernel version these will get the filesystems remounted read-only, which probably makes sense for real hardware, but doesn't make sense for emulated hardware. Instead it should just wait a bit longer. See http://www.tuxyturvy.com/blog/index.php?/archives/31-VMware-ESX-and-ext3-journal-aborts.html for some details and what needs to be changed in the kernel. Redhat and SuSE seem to have this change in their kernels already it seems and without that change it's impossible to run Debian as VMWare guest reliable. Bye as this page only describes upstream changes, did you try newer linux-2.6 images from backports.org 2.6.22 or 2.6.23 from trunk snapshots see apt lines on http://wiki.debian.org/DebianKernel Thanks, it's fixed at least in 2.6.23-1~experimental.1~snapshot.9819 Would be nice if the relevant change could be backported to etch-updates or similar. :) 2.6.23-1~experimental.1~snapshot.9819 has an equivalent change to the one at the URL above. FYI it's changed in upstream commit ad8c31bb69d60c0c6bc6431bccdf67e5a96c0d31 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=ad8c31bb69d60c0c6bc6431bccdf67e5a96c0d31 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 453120 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.10 severity 453120 important Bug#453120: mptscsi: Massive workload causes FS to be remounted readonly in VMware guest Severity set to `important' from `normal' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453393: linux-image-2.6.18-5-686: kernel bug at lookup.c with unionfs (and squashfs)
Package: linux-image-2.6.18-5-686
Version: 2.6.18.dfsg.1-13
Severity: important
I have added an unionfs branch to an existing one mounted on /
it seems to work, but after a while the following message spontaneously
appears in the opened tty and in dmesg
[ cut here ]
kernel BUG at /build/buildd/linux-modules-extra-2.6-2.6.18/debian/build/build_i3
86_none_686_unionfs/build/lookup.c:108!
invalid opcode: [#1]
SMP
Modules linked in: squashfs loop nls_iso8859_1 nls_cp437 vfat fat dm_snapshot dm
_mirror dm_mod sd_mod snd_hda_intel snd_hda_codec rtc parport_pc parport snd_pcm
snd_timer snd soundcore psmouse pcspkr snd_page_alloc serio_raw shpchp pci_hotp
lug tsdev evdev ext2 mbcache usbhid ide_disk usb_storage scsi_mod ide_generic 81
39too 8139cp mii ehci_hcd uhci_hcd usbcore generic ide_core thermal processor fa
n unionfs
CPU:0
EIP:0060:[de836fbb]Not tainted VLI
EFLAGS: 00010202 (2.6.18-5-686 #1)
EIP is at unionfs_lookup_backend+0x1da/0x735 [unionfs]
eax: 0001 ebx: dd7d2ae0 ecx: 0002 edx: 0002
esi: dd7d2b41 edi: de83a4a8 ebp: dd7d2b40 esp: ddd79d80
ds: 007b es: 007b ss: 0068
Process cron (pid: 2056, ti=ddd78000 task=ddbdeaa0 task.ti=ddd78000)
Stack: 0001 7231 ddcaccf0 0002 0002
0001 0008 000b dcef7e5c 0008 0292
ddb700c0 dd2c0844 ddd79e44 0292 ddcaccf0 c016da85 ddcaccf0
Call Trace:
[c016da85] d_alloc+0x142/0x18f
[c016537c] do_lookup+0xa3/0x135
[c0166f45] __link_path_walk+0x865/0xd1d
[c0116d0a] find_busiest_group+0x177/0x46a
[c0167446] link_path_walk+0x49/0xbd
[c012fbe1] enqueue_hrtimer+0x4b/0x6a
[c012fd27] lock_hrtimer_base+0x19/0x35
[c012fdc9] hrtimer_try_to_cancel+0x3c/0x42
[c012fdd9] hrtimer_cancel+0xa/0x14
[c027fb55] do_nanosleep+0x43/0x6a
[c012fee0] hrtimer_nanosleep+0x3d/0xf0
[c016780f] do_path_lookup+0x20a/0x225
[c0167f46] __user_walk_fd+0x29/0x3f
[c0161e99] vfs_stat_fd+0x15/0x3c
[c012fbe1] enqueue_hrtimer+0x4b/0x6a
[c012fd27] lock_hrtimer_base+0x19/0x35
[c012fdc9] hrtimer_try_to_cancel+0x3c/0x42
[c012fdd9] hrtimer_cancel+0xa/0x14
[c027fb55] do_nanosleep+0x43/0x6a
[c012fee0] hrtimer_nanosleep+0x3d/0xf0
[c0161f4d] sys_stat64+0xf/0x23
[c012fcf6] hrtimer_wakeup+0x0/0x18
[c0124657] do_gettimeofday+0x31/0xce
[c0120f0d] sys_time+0xa/0x2e
[c0102c7b] syscall_call+0x7/0xb
Code: 28 00 00 00 00 e9 d8 02 00 00 8b 43 54 8b 40 28 03 44 24 38 80
7c 24 06 00 8b 00 74 0a 85 c0 0f 85 b4 02 00 00 eb 0c 85 c0 74 08 0f
0b 6c 00 26 a4 83 de 8b 54 24 0c 8b 42 54 8b 40 28 03 44 24
EIP: [de836fbb] unionfs_lookup_backend+0x1da/0x735 [unionfs] SS:ESP
0068:ddd79d80
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.18-5-686 depends on:
ii coreutils 5.97-5.3 The GNU core utilities
ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii initramfs-tools [linux-initra 0.85h tools for generating an initramfs
ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.18-5-686 recommends:
pn libc6-i686none (no description available)
-- debconf information:
linux-image-2.6.18-5-686/preinst/failed-to-move-modules-2.6.18-5-686:
* linux-image-2.6.18-5-686/postinst/create-kimage-link-2.6.18-5-686: true
linux-image-2.6.18-5-686/preinst/initrd-2.6.18-5-686:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.18-5-686/preinst/lilo-has-ramdisk:
linux-image-2.6.18-5-686/preinst/abort-install-2.6.18-5-686:
linux-image-2.6.18-5-686/postinst/old-system-map-link-2.6.18-5-686: true
linux-image-2.6.18-5-686/postinst/kimage-is-a-directory:
linux-image-2.6.18-5-686/preinst/elilo-initrd-2.6.18-5-686: true
linux-image-2.6.18-5-686/postinst/bootloader-test-error-2.6.18-5-686:
linux-image-2.6.18-5-686/preinst/abort-overwrite-2.6.18-5-686:
linux-image-2.6.18-5-686/prerm/would-invalidate-boot-loader-2.6.18-5-686: true
linux-image-2.6.18-5-686/postinst/depmod-error-initrd-2.6.18-5-686: false
linux-image-2.6.18-5-686/prerm/removing-running-kernel-2.6.18-5-686: true
linux-image-2.6.18-5-686/postinst/bootloader-error-2.6.18-5-686:
linux-image-2.6.18-5-686/postinst/depmod-error-2.6.18-5-686: false
linux-image-2.6.18-5-686/preinst/already-running-this-2.6.18-5-686:
* linux-image-2.6.18-5-686/preinst/lilo-initrd-2.6.18-5-686: false
linux-image-2.6.18-5-686/preinst/overwriting-modules-2.6.18-5-686: true
linux-image-2.6.18-5-686/preinst/bootloader-initrd-2.6.18-5-686: true
linux-image-2.6.18-5-686/postinst/old-dir-initrd-link-2.6.18-5-686: true
linux-image-2.6.18-5-686/postinst/old-initrd-link-2.6.18-5-686: true
--
Elena of Valhalla
homepage:
Re: 2.6.23 sid upload
On Thu, Nov 29, 2007 at 11:52:24AM +0100, maximilian attems wrote: On Wed, 28 Nov 2007, maximilian attems wrote: announcing upload of linux-image 2.6.23 to sid on friday it is already on 2.6.23.9. please holler if you have outstanding issues. hmm ominous sparc dpkg fix, got a box ready to test it, will do sparc test build with it now. that is blocker, but should be done in time. Which sparc fix? Bastian -- I'm a soldier, not a diplomat. I can only tell the truth. -- Kirk, Errand of Mercy, stardate 3198.9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
SCTP implementation [Scanned]
Hi all, I'm hoping you can answer a question for me. I'm about to start some comparison research on two transport protocols, SCTP and DCCP, which means some network emulation. Lucky for me the open source community is working on implementations of these protocols! From http://www.linux-foundation.org/en/Net:DCCP I believe DCCP is implemented within the Linux kernel and from http://lksctp.sourceforge.net/INSTALL I know I need a Linux distribution with SCTP support. From a search of the mailing lists I also know that in Apr 2004 within the Debian-Mentors listing Michael Biebl was looking for a sponsor to get the packages for the lksctp project into the main Debian archive http://lists.debian.org/debian-mentors/2004/04/msg00263.html and that, subsequent to the packages entering unstable, in http://lists.debian.org/debian-mentors/2004/05/msg00179.html he further mentions bugs relating to the enabling of SCTP support in a 2.6 kernel. Unfortunately I've lost the thread from there on and am not sure what the current status of DCCP and SCTP support is with Debian Is there anyone who can clarify this situation for me so that I either proceed using Debian and/or any required patches, or (hopefully not) start looking at other distributions if necessary. Additionally if Debian has support for these protocols I would appreciate any advice/comments/tips on anything specific to their operation within Debian i.e. any specific documentation I should read. Now I admit (with great regret) that I have very limited experience of the Linux O/S having only covered a basic installation during my degree course. I use open source where possible (Firefox, Thunderbird, Open Office when I can) and look forward to spending some more time getting more acquainted with an open source O/S. I mention this only so that anyone who answers this appreciates that I have limited technical knowledge (at the moment). Thanks in advance for any assistance. Karena Stannett Software Research Centre Athlone Institute of Technology The information contained in this email is confidential and is designated solely for the attention of the intended recipient(s). If you have received this email in error, please do not use or transmit it for any purpose but rather notify us immediately and delete all copies of this email from your computer system(s). Unless otherwise specifically agreed by our authorised representative, the views expressed in this email are those of the author only and shall not represent the view of or otherwise bind Athlone Institute of Technology. Contact [EMAIL PROTECTED] or telephone 090 6471858. _ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
Re: 2.6.23 sid upload
On Wed, 28 Nov 2007, maximilian attems wrote: announcing upload of linux-image 2.6.23 to sid on friday it is already on 2.6.23.9. please holler if you have outstanding issues. hmm ominous sparc dpkg fix, got a box ready to test it, will do sparc test build with it now. that is blocker, but should be done in time. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.23 sid upload
On Thu, 29 Nov 2007, Bastian Blank wrote: Which sparc fix? the prominent sparc futex fix, but it landed it 23.2 stable. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SCTP implementation [Scanned]
On Thu, Nov 29, 2007 at 11:21:42AM -, Karena Stannett wrote:
Hi all,
I'm hoping you can answer a question for me. I'm about to start some
comparison research on two transport protocols, SCTP and DCCP, which
means some network emulation. Lucky for me the open source community
is working on implementations of these protocols! From
http://www.linux-foundation.org/en/Net:DCCP I believe DCCP is
implemented within the Linux kernel and from
http://lksctp.sourceforge.net/INSTALL I know I need a Linux
distribution with SCTP support.
Both kernel and userspace support for SCTP are available in Debian 4.0
and later. Debian 4.0 is based on a 2.6.18 kernel, but a number of
changesets have been backported from later kernels to increase
stability. This is thanks to my coworker Vlad Yasevich, who is also
the upstream SCTP maintainer for Linux.
That said, I'm not an SCTP expert, so I don't know of a good resource
for documentation. I'd suggest beginning with the documentation in the
lksctp-tools and libsctp-dev packages, and using google from there.
I know even less about DCCP, but there is at least kernel support for
it available in Debian 4.0 ('etch') and later.
--
dann frazier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: SCTP implementation [Scanned]
Dann
Many thanks to yourself and Vlad Yasevich for your prompt answer and advice
about where to get further information. I'll follow up on that. At least I
know I'm heading in the right direction now.
Regards
Karena Stannett
Software Research Centre
Athlone Institute of Technology
-Original Message-
From: dann frazier [mailto:[EMAIL PROTECTED]
Sent: Thu 29/11/2007 16:03
To: Karena Stannett
Cc: debian-kernel@lists.debian.org
Subject: Re: SCTP implementation [Scanned]
On Thu, Nov 29, 2007 at 11:21:42AM -, Karena Stannett wrote:
Hi all,
I'm hoping you can answer a question for me. I'm about to start some
comparison research on two transport protocols, SCTP and DCCP, which
means some network emulation. Lucky for me the open source community
is working on implementations of these protocols! From
http://www.linux-foundation.org/en/Net:DCCP I believe DCCP is
implemented within the Linux kernel and from
http://lksctp.sourceforge.net/INSTALL I know I need a Linux
distribution with SCTP support.
Both kernel and userspace support for SCTP are available in Debian 4.0
and later. Debian 4.0 is based on a 2.6.18 kernel, but a number of
changesets have been backported from later kernels to increase
stability. This is thanks to my coworker Vlad Yasevich, who is also
the upstream SCTP maintainer for Linux.
That said, I'm not an SCTP expert, so I don't know of a good resource
for documentation. I'd suggest beginning with the documentation in the
lksctp-tools and libsctp-dev packages, and using google from there.
I know even less about DCCP, but there is at least kernel support for
it available in Debian 4.0 ('etch') and later.
--
dann frazier
__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
__
The information contained in this email is confidential and is designated
solely for the attention of the intended recipient(s). If you have received
this email in error, please do not use or transmit it for any purpose but
rather notify us immediately and delete all copies of this email from your
computer system(s). Unless otherwise specifically agreed by our authorised
representative, the views expressed in this email are those of the author only
and shall not represent the view of or otherwise bind Athlone Institute of
Technology. Contact [EMAIL PROTECTED] or telephone 090 6471858.
_
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
__
Processed: Re: Bug#11922 closed by maximilian attems [EMAIL PROTECTED] (Re: kernel produces no messages for a blank tape)
Processing commands for [EMAIL PROTECTED]: reopen 11922 Bug#11922: kernel produces no messages for a blank tape Bug reopened, originator not changed. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#370651: closed by maximilian attems [EMAIL PROTECTED] (Re: kernel-headers are missing infrastructure needed to build modules with kernel-package)
Processing commands for [EMAIL PROTECTED]: reopen 370651 Bug#370651: kernel-headers are missing infrastructure needed to build modules with kernel-package Bug reopened, originator not changed. reassign 370651 kernel-package Bug#370651: kernel-headers are missing infrastructure needed to build modules with kernel-package Bug reassigned from package `kernel' to `kernel-package'. # Manoj, feel free to add a wontfix tag, but this *is* a bug in kernel-package # tag 370651 wontfix thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#370651: closed by maximilian attems [EMAIL PROTECTED] (Re: kernel-headers are missing infrastructure needed to build modules with kernel-package)
reopen 370651 reassign 370651 kernel-package # Manoj, feel free to add a wontfix tag, but this *is* a bug in kernel-package # tag 370651 wontfix thanks maximilian attems [EMAIL PROTECTED] wrote: if using the linux-headers and linux-support infrastructure please holler on debian-kernel. Why should I? I was using kernel-package, and its maintainer reassigned the bug to kernel-headers. If you think this package or its successors are not responsible for the fact that kernel-package documentation and kernel-headers behavior do not match, please reassign the bug to the package you think is responsible, instead of closing it. reality check on. if nobody would be able to build external modules, we would have the bts full of strange reports. as a matter of fact it is possible. As a matter of fact, I was following what I understood from the documentation of kernel-package - so obviously the documentation is either wrong, or it is hard to understand it with the kind of background that I have. And I do think that documentation for Debian's (Linux) kernel infrastructure should be written in a way that allows not only an experienced developer, but at least an experienced user to compile external modules. the easy way to do it is module-assisstant. i already told that a year ago and no i'm not keen keeping useless bugs open. If that's the best advice we can get, kernel-package's documentation should mention that it should only be used by experience people - it should do that at the places where one finds it, in particular in the description of the modules_image target in the make-kpkg manpage. irc this is even a dup. In which case you should have merged it, not closed. i might come back even grumpier next time when i'll hit the dup ;) no real please use module-assisant and be happy. kernel-package is even no longer a supported way to build linux-2.6 Ah, that's interesting. I don't see any documentation on this in kernel-package in sid, nor a bug report requesting to add it. I do see that kernel-package has quite a lot of rather old bugs (both in terms of submission, and of last modified), but that doesn't mean one shouldn't use the package... Manoj, don't you think you should indicate in your package if development of Debian kernels and kernel-package has so much diverged that it gets hard for you to keep them working together (it seems you don't get support on this from the kernel-package maintainers...) Regards, Frank -- Frank Küster Debian Developer (teTeX/TeXLive)
Bug#453482: kernel: bcm43xx does not detect wireless network on boot
Package: linux-image-2.6.22-3-686 Version: 2.6.22-6 Severity: important File: kernel *** Please type your report below this line *** after updating from kernel version 2.6.21 2.6.22, bcm43xx is unable to connect to my home wireless network on boot. after the os loads into KDE i use Wireless Assistant to connect to the network, some time it take a few tries for a successful connection although the signal is high (full strength) and the laptop is located in the same physical place it was allways at. on boot, switching to the older kernel version works fine :-) -- Package-specific info: ** Version: Linux version 2.6.22-3-686 (Debian 2.6.22-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20071019 (prerelease) (Debian 4.1.2-17)) #1 SMP Mon Nov 12 08:32:57 UTC 2007 ** Not tainted ** Kernel log: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.01 (21-Jan-2007) irda_init() NET: Registered protocol family 23 Synaptics Touchpad, model: 1, fw: 5.8, id: 0x9d48b1, caps: 0x904713/0x4006 input: SynPS/2 Synaptics TouchPad as /class/input/input3 parport_pc 00:05: reported by Plug and Play ACPI parport0: PC-style at 0x378 (0x778), irq 7, dma 1 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA] iTCO_wdt: Found a ICH3-M TCO device (Version=1, TCOBASE=0x1060) iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) Yenta: CardBus bridge found at :02:06.0 [0e11:004e] Yenta: Enabling burst memory read transactions Yenta: Using CSCINT to route CSC interrupts to PCI Yenta: Routing CardBus interrupts to PCI Yenta TI: socket :02:06.0, mfunc 0x012c1202, devctl 0x64 intel_rng: FWH not detected nsc_ircc_pnp_probe() : From PnP, found firbase 0x3E8 ; irq 3 ; dma 3. nsc-ircc, chip-init nsc-ircc, Found chip at base=0x02e nsc-ircc, driver loaded (Dag Brattli) nsc_ircc_open(), can't get iobase of 0x3e8 nsc-ircc, Found chip at base=0x02e nsc-ircc, driver loaded (Dag Brattli) nsc_ircc_open(), can't get iobase of 0x3e8 pnp: Device 00:04 disabled. Yenta: ISA IRQ mask 0x0038, PCI irq 11 Socket status: 3020 Yenta: Raising subordinate bus# of parent bus (#02) from #03 to #06 pcmcia: parent PCI bridge I/O window: 0x2000 - 0x2fff cs: IO port probe 0x2000-0x2fff: clean. pcmcia: parent PCI bridge Memory window: 0x4000 - 0x403f pcmcia: parent PCI bridge Memory window: 0x3000 - 0x33ff pccard: CardBus card inserted into slot 0 ACPI: PCI Interrupt Link [C0B6] enabled at IRQ 5 PCI: setting IRQ 5 as level-triggered ACPI: PCI Interrupt :00:1f.5[B] - Link [C0B6] - GSI 5 (level, low) - IRQ 5 PCI: Setting latency timer of device :00:1f.5 to 64 ieee80211_crypt: registered algorithm 'NULL' cs: IO port probe 0x100-0x3af: clean. cs: IO port probe 0x3e0-0x4ff: clean. cs: IO port probe 0x820-0x8ff: clean. cs: IO port probe 0xc00-0xcf7: clean. cs: IO port probe 0xa00-0xaff: clean. ieee80211: 802.11 data/management/control stack, git-1.1.13 ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED] bcm43xx driver intel8x0_measure_ac97_clock: measured 54654 usecs intel8x0: clocking to 48000 PCI: Enabling device :03:00.0 ( - 0002) ACPI: PCI Interrupt :03:00.0[A] - Link [C0B8] - GSI 11 (level, low) - IRQ 11 PCI: Setting latency timer of device :03:00.0 to 64 bcm43xx: Chip ID 0x4306, rev 0x3 bcm43xx: Number of cores: 5 bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243 bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243 bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243 bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243 bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243 bcm43xx: PHY connected bcm43xx: Detected PHY: Analog: 2, Type 2, Revision 2 bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) bcm43xx: Radio turned off bcm43xx: Radio turned off udev: renamed network interface eth0 to eth2 EXT3 FS on hda1, internal journal loop: module loaded Adding 1253028k swap on /dev/hda5. Priority:-1 extents:1 across:1253028k ACPI: Battery Slot [C11E] (battery present) ACPI: AC Adapter [C11B] (off-line) input: Power Button (FF) as /class/input/input4 ACPI: Power Button (FF) [PWRF] input: Power Button (CM) as /class/input/input5 ACPI: Power Button (CM) [C17A] input: Sleep Button (CM) as /class/input/input6 ACPI: Sleep Button (CM) [C120] input: Lid Switch as /class/input/input7 ACPI: Lid Switch [C11F] bcm43xx: PHY connected bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18 02:36:27) bcm43xx: Radio turned on bcm43xx: Radio enabled by hardware bcm43xx: Chip initialized bcm43xx: 30-bit DMA initialized bcm43xx: Keys cleared bcm43xx: Selected 802.11 core (phytype 2) ttyS2: LSR safety check engaged! [drm] Initialized drm 1.1.0 20060810 ACPI: PCI Interrupt Link [C0B5] enabled at IRQ 11 ACPI: PCI Interrupt :01:00.0[A] - Link [C0B5] - GSI 11 (level, low) - IRQ 11 [drm] Initialized radeon 1.27.0 20060524 on minor 0 agpgart: Found an AGP 2.0 compliant device at :00:00.0. agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode [drm] Setting GART location based on
Bug#453482: kernel: bcm43xx does not detect wireless network on boot
On Thu, Nov 29, 2007 at 10:15:15PM +0200, Nadav Kavalerchik wrote: Package: linux-image-2.6.22-3-686 Version: 2.6.22-6 Severity: important File: kernel *** Please type your report below this line *** after updating from kernel version 2.6.21 2.6.22, bcm43xx is unable to connect to my home wireless network on boot. after the os loads into KDE i use Wireless Assistant to connect to the network, some time it take a few tries for a successful connection although the signal is high (full strength) and the laptop is located in the same physical place it was allways at. on boot, switching to the older kernel version works fine :-) yeah bcm43xxx is pretty good on the regression front ;) can you try 2.6.23, see trunk snapshot apt lines - http://wiki.debian.org/DebianKernel thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sparc and testing migration
On Sun, Sep 02, 2007 at 07:30:24PM +0200, Andreas Barth wrote: as you all are probably aware, we currently have some quite bad issues with the sparc buildds for some times, especially http://bugs.debian.org/433187 unkillable processes on the buildds. I hope that the mentioned RC bug can be fixed soon - if so, we're happy to stop ignoring issues on sparc (or rather: we probably will find us in the situation that such cases cease to exist). I haven't seen a reply to this mail, so JFTR - that bug was fixed. Though I'm still not sure if packages built on the new buildd are getting uploaded, I haven't been able to contact James about it. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
