On Sun, Jan 02, 2005 at 07:22:28PM +, Luke Kenneth Casson Leighton wrote:
> Package: initrd-tools
> Version: 0.1.65
> Severity: normal
>
>
> 2.6.9 and above now have capability as a module.
>
> if this module is not loaded, udev will not operate properly.
and with the module loaded we'll ha
On Sun, Jan 02, 2005 at 07:37:59PM +0100, Stephan Niemz wrote:
> The kernel version 2.4.28 is out for almost seven weeks now.
> Does anybody know about the status of the corresponding Debian
> packages? And is there an estimation for when the kernel-patch-*
> packages will support the new kern
On Wed, Dec 22, 2004 at 09:16:00AM -0500, Lennart Sorensen wrote:
> I have been having trouble with the filesystem apparently locking up on
> a P4 2.8GHz HT machine (1GB ram, dual 120G SATA in raid1 with LVM on
> top).
>
> It locks up when I try and delete a lot of small files at once.
> Yesterday
On Wed, Dec 15, 2004 at 11:04:40AM +, Martin Michlmayr wrote:
> * Horms <[EMAIL PROTECTED]> [2004-12-15 13:28]:
> > I checked 2.6 upstream and the refcount field is present.
> > Curiously upstream 2.4 seems to neither include this field nor
> > a fix for CAN-2004-0814 (N.B not CAN-2004-081 as I
On Mon, Dec 13, 2004 at 06:38:57AM +0100, Harald Dunkel wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Philipp Niemann wrote:
> |
> | In the script /usr/sbin/mkinitrd, Line 497, is a find which seems to
> | search /proc/scsi for modules needed to mount the root device. If one
> | has
On Sun, Dec 05, 2004 at 05:04:14PM -0600, Brad Sims wrote:
> Package: kernel-image-2.4.27-1-k7
> Version: 2.4.27-6
> Severity: important
>
>
> Attempting to insert my modules for sensors after it
> failed I discovered this error message:
>
> /lib/modules/2.4.27-1-k7/i2c/i2c-core.o:
> /lib/module
On Fri, Dec 03, 2004 at 11:10:35PM +, Michael Shields wrote:
> Package: initrd-tools
> Version: 0.1.74
> Severity: normal
>
> mkinitrd contains the lines:
>
> 8 | 11)
> if [ ! -d /proc/scsi ]; then
> echo "$PROG: Cannot determine SCSI module" >&
On Thu, Dec 02, 2004 at 12:41:59PM +0100, Christoffer Sawicki wrote:
> What if the PCI ID associations in the kernel for eepro100 and e100 were
> changed so that a card is only associated with the module it works (best)
> with? The only issue I see with this approach is collecting the necesary
>
On Wed, Dec 01, 2004 at 07:55:59PM +0900, Mike Hommey wrote:
> The problem is the following: is the e100 driver available in all kernel
> flavours/versions ?
> If yes, then it is safe to blacklist it in hotplug directly.
> If not, then it is not safe to do it in hotplug because it would
> blacklist
On Tue, Sep 28, 2004 at 07:17:12PM +0200, Harald Dunkel wrote:
> Christoph Hellwig wrote:
> >
> >See recent discussion on linux-kernel and linux-scsi
> >
>
> I did. Sounds very promissing.
>
> Is this something that could be included in the 2.6.9 kernel?
It's probabaly too late for 2.6.9.
On Sun, Oct 03, 2004 at 07:54:12PM -0400, Joey Hess wrote:
> Steve Langasek wrote:
> > The d-i images really need to be built from kernel-image packages that
> > are in the archive at the time we ship. Optimizing for 486 isn't a very
> > good reason on its own to force another kernel build cycle.
severity 274408 wishlist
tags 274408 upstream
thanks
> This feature is not there in 2.6. (Or else I need to RTFM -- can
> somebody point me to the right FM?)
Yes, it was removed when the filesystem was rewritten to not eat data
for breakfast.
> Thus, running a 2.6.8 kernel, mounting the boot.i
On Wed, Sep 29, 2004 at 10:54:21PM +0100, Luke Kenneth Casson Leighton wrote:
> On Wed, Sep 29, 2004 at 10:33:28PM +0200, Christoph Hellwig wrote:
> > On Wed, Sep 29, 2004 at 09:14:20PM +0100, Luke Kenneth Casson Leighton
> > wrote:
> > > it's not
On Wed, Sep 29, 2004 at 09:14:20PM +0100, Luke Kenneth Casson Leighton wrote:
> it's not a severe performance penalty.
>
> especially when it's disabled by default with "selinux=0".
Yes, all the indirect calls due to CONFIG_SECURITY are a performance
penalty.
On Mon, Sep 20, 2004 at 10:11:13PM +0200, Harald Dunkel wrote:
> Hi Christoph,
>
> What would be your suggestion how get the name of the
> {scsi, sata, ide} driver used to access the partition
> currently mounted on / ?
>
> Of course it would be safe to assume that there is
> no chroot environmen
On Sun, Sep 26, 2004 at 03:37:18PM +0200, Norbert Tretkowski wrote:
> * Jaakko Niemi wrote:
> [...]
> > Has anyone looked at this issue? I could not find anything from list
> > archives or from bts with quick search.
>
> A few days ago, Christoph mention that this has been fixed in svn
> already.
On Thu, Sep 23, 2004 at 03:40:18PM +0200, Joey Hess wrote:
> Package: kernel
> Version: 2.6.8
> Severity: normal
>
> The 2.4 kernel supports parameters passed on the kernel command line of
> the form COUNTRY="United States"; it understands the use of quotes
> around the value with a space in it, a
On Thu, Sep 23, 2004 at 10:26:55AM +0200, Piotr Roszatycki wrote:
> Package: kernel-image-2.6.8-1-686
> Version: 2.6.8-3
> Severity: important
>
> Kernel 2.6.8 sets TCP window scaling to 7. It doesn't work with many broken
> routers including mine. It is possible to set
>
> net.ipv4.tcp_default_w
On Fri, Sep 24, 2004 at 12:22:39PM -0400, Avery Fay wrote:
> I just upgraded to the latest 2.6.8 kernel from an earlier one. I didn't
> change anything in the .config and now my machine no longer recognizes
> my scsi adapter, which is an aic7902. Reverting to and earlier kernel
> fixes the problem.
On Thu, Sep 02, 2004 at 02:55:50PM +0200, Magnus Ekdahl wrote:
> Subject: Problems with some firewalls
> Package: kernel-image-2.6.8-1-k7
> Version: 2.6.8-2
> Severity: normal
>
> Somewhere after the 18th of august I got problems downloading my mail from
> pophost.ludd.luth.se. One of the administ
On Sun, Sep 19, 2004 at 09:21:12AM +0200, Robert Millan wrote:
> On Fri, Sep 17, 2004 at 08:38:56AM +0200, Christoph Hellwig wrote:
> > tags 272029 +upstream
> > thanks
> >
> > Please get feature-patches merged upstream before bugging us, thanks.
>
> Upstream re
Looking over the various cdrom problems I noticed we still have
CONFIG_IDE_TASKFILE_IO enabled in many places, could the port
maintainers turn it off please?
close 272082
thanks
Wonderfull, with a grave bug you _prevent_ -3 from going into testing.
Closing the bug so it can be migrated.
I've backported the tg3 driver from current mainline which wasn't too
easy because of our firmware removal and various interface changes in
the mean time.
I remember some people had problems with the IBM blades, care to test
a kernel with the patch below?
Testers with normal cards are also welcom
tags 272029 +upstream
thanks
Please get feature-patches merged upstream before bugging us, thanks.
On Wed, Sep 15, 2004 at 12:21:58PM +0100, Martin Michlmayr wrote:
> 2) is no longer as important since recent 2.6 kernels have castrated
> /proc/scsi so running mkinitrd from a vanilla upstream kernel won't
> work anyway.
It's not present in ny 2.6.x reason. In fact even the limited
/proc/scsi/*
On Thu, Sep 16, 2004 at 08:18:59PM +0200, Christoph Hellwig wrote:
> On Thu, Sep 16, 2004 at 11:51:31AM +0200, Jens Schmalzing wrote:
> > Hi,
> >
> > I recently encountered a machine (a Thinkpad 860) with a NCR 53C810
> > SCSI controller that would not work proper
On Thu, Sep 16, 2004 at 11:51:31AM +0200, Jens Schmalzing wrote:
> Hi,
>
> I recently encountered a machine (a Thinkpad 860) with a NCR 53C810
> SCSI controller that would not work properly unless the config option
> CONFIG_SCSI_SYM53C8XX_IOMAPPED was set. Under these circumstances,
> installatio
severity 271517 wishlist
tags 271517 +upstream
retitle 271517 swim3 driver should be made SMP-safe
reassign 271517 kernel
thanks
> CC[M]drivers/block/swim3.o
> drivers/block/swim3.c: In function `do_fd_request':
> drivers/block/swim3.c:305: warning: implicit declaration of function `sti'
> drivers
> Attempts to manually configure with mii-tool fail
> also. This module worked perfectly fine in the 2.6.7
> kernel images.
This is a known issue and there have been various attempts to fix this
on the networking mailing lists. I'll try to get one of them into the
next kernel-source release.
On Mon, Sep 13, 2004 at 09:37:23AM +0200, Milan Kuchta wrote:
> Package: kernel-image
> Version: 2.6.8-1-k7
> Severity: critical
>
>
> Installed new kernel image (depending on kernel-image-2.6-k7) and after
> restart I get:
>
> hdc: IRQ probe failed (0xfdf8)
> hdc: IRQ probe failed (0xfd
On Mon, Sep 13, 2004 at 10:29:15AM +0200, Marco d'Itri wrote:
> [Please Cc me, I'm not subscribed.]
>
> I'm not even sure this is a bug... But it almost looks like that old
> pty devices are not reused.
> What can I do to regain access to my screen session? Rebooting this
> this server would be qu
On Mon, Sep 13, 2004 at 01:06:06AM -0400, Andres Salomon wrote:
> On Sun, 12 Sep 2004 18:14:48 -0700, Joshua Kwan wrote:
>
> > Hello,
> >
> > I'm wondering how close kernel-source-2.6.8-6 is to being ready for prime
> > time. Andres is waiting on it for i386 images. I'm waiting on it for sparc
>
On Fri, Sep 10, 2004 at 09:45:55PM -0700, mfedyk wrote:
> Package: kernel-image-2.6.7-1-686
> Version: 2.6.7-2
> Severity: normal
>
> I'm trying to debug a problem with one of the devices on my scsi bus, and I
> saw this[1] post on dumping the bus and it looks like I can reproduce a
> similar oops
On Fri, Sep 10, 2004 at 11:32:14PM -0400, Michel Daenzer wrote:
> Package: kernel-image-2.6.8-powerpc
> Version: 2.6.8-4
> Severity: wishlist
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Please enable the CONFIG_IKCONFIG and CONFIG_IKCONFIG_PROC configuration
> options so one can lo
tags 271090 +wontfix
thanks
On Fri, Sep 10, 2004 at 11:12:56PM -0700, Mike Fedyk wrote:
> reassign 271090 kernel-image-2.4.27-1-686
> thanks
>
> Looks like I was running a 2.4 kernel at the time...
>
> Here's the ksymoops output.
>
> I can re-run it on a 2.4 kernel so /proc/ksyms is available
On Sat, Sep 11, 2004 at 12:21:16PM +0200, Guus Sliepen wrote:
> Hello kernel team,
>
> I'm maintaining packages for the ifenslave utility. This utility is
> distributed with the kernel sources, in the Documentation/networking/
> directory. This utility is necessary to configure bonding devices.
>
On Fri, Sep 10, 2004 at 08:44:31AM -0400, Joey Hess wrote:
> I'm concernd about the status of the 2.6.8 packages, which have been
> held out of testing for the past week by bug #269164, which nobody seems
> to be working on (based on the nil response to the report). Since we
> were told 2.6.8 was t
On Fri, Sep 10, 2004 at 02:08:29PM +0100, Sam Morris wrote:
> Joey Hess wrote:
> >I'm concernd about the status of the 2.6.8 packages, which have been
> >held out of testing for the past week by bug #269164, which nobody seems
> >to be working on (based on the nil response to the report). Since we
On Tue, Sep 07, 2004 at 09:03:08AM -0700, Debian Bug Tracking System wrote:
> Processing commands for [EMAIL PROTECTED]:
>
> > # Automatically generated email from bts, devscripts version 2.8.4
> > reassign 270385 kernel-image-2.6.8-1-386
> Bug#270385: [i386] [20040905] SCSI controller DDRS-39130W
seems we've gained a -$RELEASE in the middle now, e.g.
kernel-source-2.6.8-6-2.6.8-6
and an .orig.tar.gz name of
kernel-source-2.6.8-6_2.6.8-6.orig.tar.gz
was this intentional?
Does the slow network only happen with the nvidia ethernet or also
with e1000? There's a know problem in the 2.6.8 forcedeth driver that
could cause problems like that. If you're willing to test a patched
kernel please drop me a mail.
Is matroxfb enabled in the kernel-image packages? Else I think we
should just close it.
Any updates on this one?
On Mon, Sep 06, 2004 at 01:43:07PM +0100, Russel Winder wrote:
> Package: kernel-image-2.4.26-1-686
> Version: 2.4.26-6
> Severity: normal
>
>
> The sk98lin driver distributed with the kernel is version 6.22 and does not
> work. The module loads fine but does not correctly initialize the
> hardw
close 270299
thanks
On Tue, Sep 07, 2004 at 03:07:11AM +1000, Donovan Baarda wrote:
> Package: kernel-headers-2.6.8-1
> Version: 2.6.8-1
> Severity: normal
>
>
> Several *.h header files are not included in the kernel-headers
> packages. Some of the missing headers are needed when building
> so
On Sat, Sep 04, 2004 at 04:06:35PM +0200, Christoph Hellwig wrote:
> On Thu, Sep 02, 2004 at 09:29:05AM +0200, Sven Luther wrote:
> > On Wed, Sep 01, 2004 at 11:32:19PM +0200, ncrfgs wrote:
> > > On Fri, Aug 20, 2004 at 10:50:42AM +0200, Luca Bigliardi - shammash wrote:
>
On Sun, Aug 29, 2004 at 04:51:08PM -0400, Jerry Quinn wrote:
> Christoph Hellwig writes:
> > does this still happen with 2.6.8?
>
> I've only seen it happen once with 2.6.7 and with 2.6.8 I'm somewhat blocked
> because I've got an atheros wireless chip and th
On Sun, Aug 29, 2004 at 04:27:04PM -0500, Bill Brown wrote:
> Greetings:
>
> It did happen for the 2.6 kernels. I had to add "noapic" to the end of
> the kernel parameters in the GRUB bootloader. I posted this information
> on debianhelp.org /networking.
Hmm, okay. Another apic bug..
On Mon, Aug 30, 2004 at 03:46:10PM -0400, Walter Tautz wrote:
>
>
>
> On Sat, 28 Aug 2004, Christoph Hellwig wrote:
>
> > Adrian, which m-i-t release should have fixed this?
> >
> > Walter, is this still happening for you?
> >
>
> Yes, it is, s
On Wed, Sep 01, 2004 at 03:58:45PM +0300, Shaul Karl wrote:
> On Sun, Aug 29, 2004 at 11:24:09PM +0200, Christoph Hellwig wrote:
> > this looks almost like broken memory. Can you run memtest86 on the box?
> >
>
>
> memtest86 and memtest86+ (what are the differences a
On Sat, Sep 04, 2004 at 07:27:45PM +0200, Domenico Andreoli wrote:
> On Sat, Sep 04, 2004 at 04:05:19PM +0200, Christoph Hellwig wrote:
> > On Sat, Sep 04, 2004 at 03:16:02PM +0200, Domenico Andreoli wrote:
> > >
> > > Reiser4 filesystem has finally been release
On Sat, Sep 04, 2004 at 03:07:35PM +0100, Jonathan Lucas wrote:
> Package: kernel-image-2.6.8-1-k7
> Version: 2.6.8-2
> Severity: important
>
> When booting up, the display goes completely blank about halfway through
> the boot process, only returning when X starts. Even after X starts, the
> cons
tags 269945 +upstream
thanks
On Sat, Sep 04, 2004 at 03:16:02PM +0200, Domenico Andreoli wrote:
> Package: kernel-source-2.6.8
> Version: 2.6.8-5
> Severity: wishlist
>
> hi,
>
> Reiser4 filesystem has finally been released. It would be nice to have
> the support built into the Debian's kernel
On Thu, Sep 02, 2004 at 09:29:05AM +0200, Sven Luther wrote:
> On Wed, Sep 01, 2004 at 11:32:19PM +0200, ncrfgs wrote:
> > On Fri, Aug 20, 2004 at 10:50:42AM +0200, Luca Bigliardi - shammash wrote:
> > > On Tue, Aug 17, 2004 at 02:06 PM, Luca Bigliardi - shammash wrote:
> > > > sensors-detect find
On Thu, Sep 02, 2004 at 09:33:25AM +0100, Alister Winfield wrote:
> On Thu, 2004-09-02 at 01:55, Joshua Kwan wrote:
> > alister.winfield wrote:
> > > LV Size1.95 TB
> >
> > I was under the impression that 2.4 could only handle <= 1TB sanely, not
> > 2. So probably the support he
On Wed, Sep 01, 2004 at 11:33:31PM +0200, Jan-Jaap van der Heijden wrote:
> I don't think placing a strategic printk() qualifies as a fix though :-)
> Maybe GCC is to blame here. I'm using gcc 3.3.4-6sarge1.0.1 (current from
> testing)
This indeed smells like a compiler bug
> Is it safe to use
On Mon, Aug 30, 2004 at 07:22:54PM +0200, Jan-Jaap van der Heijden wrote:
> >http://people.debian.org/~nobse/kernel/kernel-image-2.6.8-alpha/
> >
> >They are currently sitting in incoming, and will be moved into the
> >regular archive in a few hours.
> >
>
> I tried again with 2.6.8-3 from this UR
I think we want a TCP window scaling workaround. Either wevert the default
to the pre-2.6.7 or backport the autoscaling patch. I'd prefer the safe
variant (switch the defaults back)
- Forwarded message from Maciej Soltysiak <[EMAIL PROTECTED]> -
Date: Mon, 30 Aug 2004 13:00:37 +0200
this looks almost like broken memory. Can you run memtest86 on the box?
I just talked to Jens Axboe about all cdrom failures we see, and he
asked the right questions. Except on powerpc, hppa and the alpha
'default' kernel we have CONFIG_IDE_TASKFILE_IO turned on, which is an
alternate, experimental and much less tested codepath through the ide
subsystem. We should tu
On Sun, Aug 29, 2004 at 02:22:45PM +0200, Laszlo 'GCS' Boszormenyi wrote:
> Hi,
>
> I maintain the kernel-patch-grsecurity2 package in Debian. This patch
> is for vanilla kernel, but as some users requested, I would like to make
> it work with Debian kernels as well. I could do it 99%, but
> fs/p
How does 2.6.8 detect the mouse?
reassign 252192 hotplug
thanks
The kernel doesn't load modules. If it's loaded despite the blacklist
that's a hotplug problem.
reassign 250331 xserver-xfree86
thanks
While this bug is due to a kernel change this change was intentionally
and you will need the the new wacom X input driver to get this device
work. Thus reassignning to xserver-xfree86 to track merging that
driver.
The latest 2.6.8-based kernel-image should have a fix for this issue.
Can you verify it's working now?
tags 234889 +moreinfo
thanks
Could you please answer Francesco's question?
We have tons of reports for broken CDs in the BTS, and I noticed that
unlike the commercial distibution vendors we don't have
CONFIG_IDEDMA_ONLYDISK set ibn our install kernels. I'd rather play
safe and slow in this case.
reassign 258979 kernel-package
thanks
kernel-package is generating the file list for kernel-image-i386, so
it's a problem there.
On Sat, Aug 28, 2004 at 11:11:32PM -0700, Joshua Kwan wrote:
> The point of kernel-patch-debian, as far as building our kernels go, is:
>
> Suppose a kernel-image source package build-depends on
> kernel-tree-2.4.27-4. This is provided by kernel-tree-2.4.27, which in
> turn depends on kernel-sou
I don't really see how the kernel could be involved here.
Are you absolutely sure this happens on 2.6 but not 2.4 with an
otherwise identical system? Does it still happen with an uptodate sarge
or sid system?
tags #243441 +moreinfo
thanks
Please rety with 2.4.27 and if not obey Martins requests. Thanks.
tags 244030 +moreinfo
thanks
still waiting for the information Herbert requested.
The report at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=263901
looks to me like this device needs an US_FL_SCM_MULT_TARG entry? Still
wondering why it works in 2.4 then.
Adrian, which m-i-t release should have fixed this?
Walter, is this still happening for you?
Does this still happen with 2.6.8?
severity 248619 normal
tags 248619 +moreinfo
thanks
> Are you loading mousedev manually? If so please don't (unless you're
> using hotplug as well) as that stops the auto-loading mechanisms from
> working.
Could you please answer Herberts question?
This bug (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=256008) looks
like an ALSA issue, any chance someone could look at it?
severity 254910 normal
thanks
Any chance you could reproduce this without this cisco device (btw,
a pointer to this devices' description would be nice, can't find it on
their website)? If not we'll probably close this.
Just download the .diff.gz from kernel-source instead and run the
included prune-non-free script. kernel-patch-debian is a useless
package.
reassign 268392 dvd+rw-tools
tags 268392 +patch
thanks
> growisofs
> ---
> INFO: ISO-8859-15 character encoding detected by locale settings.
> Assuming ISO-8859-15 encoded filenames on source filesystem,
> use -input-charset to override.
> :-( unable to PREVENT MEDIA REMOVAL
On Fri, Aug 27, 2004 at 12:33:41PM -0400, Joey Hess wrote:
> Christoph Hellwig wrote:
> > The FBIOGET_CON2FBMAP is only implemented for builtin framebuffer
> > console and isn't easily implementable for modular framebuffer console.
> >
> > If nessecary and
On Fri, Aug 27, 2004 at 10:47:29AM +0200, Matthias Klose wrote:
> > It will be 2.6.8.
>
> If you write 2.6.8, do you mean 2.6.8.1? Or is the diff to .1 included
> in the Debian packages? I cannot find a hint and the version number is
> misleading.
Given the diff to .1 is tiny and four-digit versi
On Thu, Aug 26, 2004 at 06:13:41PM -0400, Bharath Ramesh wrote:
> I still get the stack overflow error. Some searching suggested that best
> thing would be to use a 16K stack kernel. I found that there is a 16K
> stack kernel available from Linuxant website. I just wanted to know if
> there is a wa
reassign 266564 hotplug
thanks
Both driver actually do support the hardware, but you want to select the
8139cp driver were possible. hotplug needs to be adjuste to make a
manual decision here.
Does this still happen with recent kernels?
> On 2 different systems with the same (sid) Debian distribution the
> connection speed is limited to (more or less) 100 Kbit/s when using
> 100 Mbit/s Ethernet cards.
>
> I have tried 2 different network cards on a machine and another card
> on a different machine (all 100 Mb/s cards) but with th
reassign 268169 initrd-tools
thanks
The kernel already oofers many fbdev drivers, but it's not his job to
select which one goes into the initrd
merge 266912 268085
thanks
severity 268167 normal
thanks
severity 268166 minor
merge 268166 266674
thanks
On Thu, Aug 26, 2004 at 09:02:45AM +0200, Jens Schmalzing wrote:
> Hi,
>
> It seems that the above-mentioned revision of kernel-source, which is
> currently in incoming, won't build at all (see below). Unless I'm
> completely mistaken, the missing values should be 0x8f for VERIFY_16
> and 0x5d fo
On Wed, Aug 25, 2004 at 12:17:46PM -0600, dann frazier wrote:
> I just realized that having this package may add load to the security
> team by increasing the number of packages they need to rebuild. Normally
> a kernel-image update uses the same package name as the current version
> (thus no new
Can you please retest with 2.4.27/2.6.{7,8}, we fixed some alpha pci
handling issue there.
Does this still happen with a recent kernel?
does this still happen with 2.6.8?
what does "cat /proc/modules" and "dmesg" say?
The FBIOGET_CON2FBMAP is only implemented for builtin framebuffer
console and isn't easily implementable for modular framebuffer console.
If nessecary and there's enough space left on the bootdisks we could
ship a builin framebuffer console. Please start a discussion on
debian-kernel on that ASAP
packages must not depend on kernel headers. Use libc headers or private
copies if nessecary.
I'll leave the bug open because there might be other reasons to add
these packages back and the hppa/sparc maintainers should take that
decision.
On Sat, Aug 21, 2004 at 10:40:09PM -0400, Kristine Diana Daniels wrote:
> Package: kernel-image-2.6.8-1-686-smp
> Version: 2.6.8-1
> Followup-For: Bug #267342
>
>
> putting values less than or equal to 6 in
> /proc/sys/net/ipv4/tcp_default_win_scale
> resolves the nntp issue.
> putting values le
101 - 200 of 406 matches
Mail list logo
