Re: [PATCH 5.9 24/74] x86, powerpc: Rename memcpy_mcsafe() to copy_mc_to_{user, kernel}()

Am Dienstag, 3. November 2020, 07:35:29 CET schrieb Greg Kroah-Hartman: > On Mon, Nov 02, 2020 at 10:34:08PM +0100, Hans-Peter Jansen wrote: > > Ah, that kind of makes sense, I saw odd things with these patches that I > couldn't figure out. > > So, is there a symlink that

Re: [PATCH 5.9 24/74] x86, powerpc: Rename memcpy_mcsafe() to copy_mc_to_{user, kernel}()

Hi Greg, hi Dan, Am Samstag, 31. Oktober 2020, 12:36:06 CET schrieb Greg Kroah-Hartman: > From: Dan Williams > > commit ec6347bb43395cb92126788a1a5b25302543f815 upstream. > > In reaction to a proposal to introduce a memcpy_mcsafe_fast() > implementation Linus points out that memcpy_mcsafe() is

Re: AMD PCI Bridge: Hardware error from APEI

Am Samstag, 11. Juli 2020, 18:32:21 CEST schrieben Sie: > Am Dienstag, 7. Juli 2020, 08:56:41 CEST schrieben Sie: > > Am Samstag, 27. Juni 2020, 20:23:35 CEST schrieben Sie: > > > Dear hacker from the order of the penguins, > > > > > > we're facing a disturbing issue here after swapping a

Re: AMD PCI Bridge: Hardware error from APEI

Am Dienstag, 7. Juli 2020, 08:56:41 CEST schrieben Sie: > Am Samstag, 27. Juni 2020, 20:23:35 CEST schrieben Sie: > > Dear hacker from the order of the penguins, > > > > we're facing a disturbing issue here after swapping a motherboard of a > > mission critical system: > > > > Specs: > > ASUS

Re: AMD PCI Bridge: Hardware error from APEI

Am Samstag, 27. Juni 2020, 20:23:35 CEST schrieben Sie: > Dear hacker from the order of the penguins, > > we're facing a disturbing issue here after swapping a motherboard of a > mission critical system: > > Jun 27 20:05:29 server kernel: {10}[Hardware Error]: Hardware error from > APEI Generic

AMD PCI Bridge: Hardware error from APEI

Dear hacker from the order of the penguins, we're facing a disturbing issue here after swapping a motherboard of a mission critical system: Jun 27 20:05:29 server kernel: {10}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 4 Jun 27 20:05:29 server kernel:

Re: 4.14.9 broke nvidia 384.98 kernel module

On Freitag, 29. Dezember 2017 10:23:56 Greg KH wrote: > On Fri, Dec 29, 2017 at 02:08:08AM +0100, Hans-Peter Jansen wrote: > > Hi Greg, > > > > I know, everybody hates NVidia and their proprietary stuff around here. > > > > Anyway, I wanted to let you and fol

Re: 4.14.9 broke nvidia 384.98 kernel module

On Freitag, 29. Dezember 2017 10:23:56 Greg KH wrote: > On Fri, Dec 29, 2017 at 02:08:08AM +0100, Hans-Peter Jansen wrote: > > Hi Greg, > > > > I know, everybody hates NVidia and their proprietary stuff around here. > > > > Anyway, I wanted to let you and fol

4.14.9 broke nvidia 384.98 kernel module

Hi Greg, I know, everybody hates NVidia and their proprietary stuff around here. Anyway, I wanted to let you and followers of 4.14 know, that changes between 4.14.8 and 4.14.9 broke both current nvidia kernel drivers. See:

4.14.9 broke nvidia 384.98 kernel module

Hi Greg, I know, everybody hates NVidia and their proprietary stuff around here. Anyway, I wanted to let you and followers of 4.14 know, that changes between 4.14.8 and 4.14.9 broke both current nvidia kernel drivers. See:

Re: [PATCH 4.2 000/120] 4.2.1-stable review

Dear Greg, FYI, this revision seems to be missing https://lkml.org/lkml/2015/9/3/411 [PATCH 4.2-rc5] workqueue: Make flush_workqueue() available again to non GPL modules which actually defers 4.2 rollout for some cases, hence for 4.2.1 too. Cheers, Pete On Samstag, 19. September 2015

Re: [PATCH 4.2 000/120] 4.2.1-stable review

Dear Greg, FYI, this revision seems to be missing https://lkml.org/lkml/2015/9/3/411 [PATCH 4.2-rc5] workqueue: Make flush_workqueue() available again to non GPL modules which actually defers 4.2 rollout for some cases, hence for 4.2.1 too. Cheers, Pete On Samstag, 19. September 2015

Re: [PATCH 4.2-rc5] workqueue: Make flush_workqueue() available again to non GPL modules

On Dienstag, 4. August 2015 14:05:20 Tejun Heo wrote: > On Tue, Aug 04, 2015 at 11:26:04AM -0600, tim.gard...@canonical.com wrote: > > From: Tim Gardner > > > > Commit 37b1ef31a568fc02e53587620226e5f3c66454c8 ("workqueue: move > > flush_scheduled_work() to workqueue.h") moved the exported non

Re: [PATCH 4.2-rc5] workqueue: Make flush_workqueue() available again to non GPL modules

On Dienstag, 4. August 2015 14:05:20 Tejun Heo wrote: > On Tue, Aug 04, 2015 at 11:26:04AM -0600, tim.gard...@canonical.com wrote: > > From: Tim Gardner > > > > Commit 37b1ef31a568fc02e53587620226e5f3c66454c8 ("workqueue: move > > flush_scheduled_work() to

Re: [GIT PULL] overlay filesystem fixes for 3.18

On Freitag, 21. November 2014 13:41:57 Miklos Szeredi wrote: > On Fri, Nov 21, 2014 at 12:32 PM, Hans-Peter Jansen wrote: > > Dear Miklos, > > > > On Donnerstag, 20. November 2014 17:45:31 Miklos Szeredi wrote: > >> The biggest change is to rename the filesystem fro

Re: [GIT PULL] overlay filesystem fixes for 3.18

Dear Miklos, On Donnerstag, 20. November 2014 17:45:31 Miklos Szeredi wrote: > > The biggest change is to rename the filesystem from "overlayfs" to > "overlay". This will allow legacy overlayfs to be easily carried by distros > alongside the new mainline one. Would you kindly give a firm

Re: [GIT PULL] overlay filesystem fixes for 3.18

Dear Miklos, On Donnerstag, 20. November 2014 17:45:31 Miklos Szeredi wrote: The biggest change is to rename the filesystem from overlayfs to overlay. This will allow legacy overlayfs to be easily carried by distros alongside the new mainline one. Would you kindly give a firm elaboration of

Re: [GIT PULL] overlay filesystem fixes for 3.18

On Freitag, 21. November 2014 13:41:57 Miklos Szeredi wrote: On Fri, Nov 21, 2014 at 12:32 PM, Hans-Peter Jansen h...@urpla.net wrote: Dear Miklos, On Donnerstag, 20. November 2014 17:45:31 Miklos Szeredi wrote: The biggest change is to rename the filesystem from overlayfs to overlay

Re: new mailing list for union/overlay filesystems?

Dear David, sorry for the late chime in. On Mittwoch, 25. Juni 2014 15:54:59 David Miller wrote: > From: Miklos Szeredi > Date: Thu, 19 Jun 2014 14:36:50 +0200 > > > There's interest in having a mailing list specifically for "union > > filesystem" like solutions (currently active projects are

Re: new mailing list for union/overlay filesystems?

Dear David, sorry for the late chime in. On Mittwoch, 25. Juni 2014 15:54:59 David Miller wrote: From: Miklos Szeredi mik...@szeredi.hu Date: Thu, 19 Jun 2014 14:36:50 +0200 There's interest in having a mailing list specifically for union filesystem like solutions (currently active

OT: Re: [PATCH 3/3] x86, vdso32: handle 32 bit vDSO larger one page

On Donnerstag, 13. März 2014 14:00:10 Andi Kleen wrote: > At some point the majority of my nfsroot test image were OpenSUSE 9. Hehe, I had a 9.3 system (2.6.11.4) with an uptime of > 1000 days before power outage, and one 11.1 (2.6.27.56), that has an uptime of 1029 days now. While git

OT: Re: [PATCH 3/3] x86, vdso32: handle 32 bit vDSO larger one page

On Donnerstag, 13. März 2014 14:00:10 Andi Kleen wrote: At some point the majority of my nfsroot test image were OpenSUSE 9. Hehe, I had a 9.3 system (2.6.11.4) with an uptime of 1000 days before power outage, and one 11.1 (2.6.27.56), that has an uptime of 1029 days now. While git brought

Re: strange SysRq problem

Am Donnerstag, 14. Februar 2008 schrieb Arnd Hannemann: > Hans-Peter Jansen wrote: > > I'm suffering from a strange SysRq problem: > > > > syslog shows haphazardly "SysRq : HELP" lines, while I definitely > > didn't triggered them, neither via (PS/2) keyb

Re: IDE cdrom problem with PLEXTOR DVDR PX-608AL

Am Donnerstag, 14. Februar 2008 schrieb Borislav Petkov: > On Thu, Feb 14, 2008 at 12:37:50AM +0100, Hans-Peter Jansen wrote: > > [Added Bart to CC] > > > Am Dienstag, 12. Februar 2008 schrieb Borislav Petkov: > > > On Tue, Feb 12, 2008 at 10:26:17AM +0100, Hans-Pet

Re: IDE cdrom problem with PLEXTOR DVDR PX-608AL

Am Donnerstag, 14. Februar 2008 schrieb Borislav Petkov: On Thu, Feb 14, 2008 at 12:37:50AM +0100, Hans-Peter Jansen wrote: [Added Bart to CC] Am Dienstag, 12. Februar 2008 schrieb Borislav Petkov: On Tue, Feb 12, 2008 at 10:26:17AM +0100, Hans-Peter Jansen wrote: Hi, I suffer

Re: strange SysRq problem

Am Donnerstag, 14. Februar 2008 schrieb Arnd Hannemann: Hans-Peter Jansen wrote: I'm suffering from a strange SysRq problem: syslog shows haphazardly SysRq : HELP lines, while I definitely didn't triggered them, neither via (PS/2) keyboard, nor via /proc/sysrq-trigger

strange SysRq problem

Hi, I'm suffering from a strange SysRq problem: syslog shows haphazardly "SysRq : HELP" lines, while I definitely didn't triggered them, neither via (PS/2) keyboard, nor via /proc/sysrq-trigger. This is accompanied with stalls of about 15-60 secs. Here's an example: Feb 14 00:16:11 xrated

Re: IDE cdrom problem with PLEXTOR DVDR PX-608AL

Am Dienstag, 12. Februar 2008 schrieb Borislav Petkov: > On Tue, Feb 12, 2008 at 10:26:17AM +0100, Hans-Peter Jansen wrote: > > Hi, > > > > I suffer from unreliable cdrom operations (failing DAE and burn > > sessions) with the openSUSE

Re: IDE cdrom problem with PLEXTOR DVDR PX-608AL

Am Dienstag, 12. Februar 2008 schrieb Borislav Petkov: On Tue, Feb 12, 2008 at 10:26:17AM +0100, Hans-Peter Jansen wrote: Hi, I suffer from unreliable cdrom operations (failing DAE and burn sessions) with the openSUSE 2.6.18.8-0.7-bigsmp kernel. Hi, can

strange SysRq problem

Hi, I'm suffering from a strange SysRq problem: syslog shows haphazardly SysRq : HELP lines, while I definitely didn't triggered them, neither via (PS/2) keyboard, nor via /proc/sysrq-trigger. This is accompanied with stalls of about 15-60 secs. Here's an example: Feb 14 00:16:11 xrated

IDE cdrom problem with PLEXTOR DVDR PX-608AL

Hi, I suffer from unreliable cdrom operations (failing DAE and burn sessions) with the openSUSE 2.6.18.8-0.7-bigsmp kernel. Additionally, the syslog is continuesly spammed with: Feb 12 00:03:22 kernel: hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by

IDE cdrom problem with PLEXTOR DVDR PX-608AL

Hi, I suffer from unreliable cdrom operations (failing DAE and burn sessions) with the openSUSE 2.6.18.8-0.7-bigsmp kernel. Additionally, the syslog is continuesly spammed with: Feb 12 00:03:22 kernel: hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by

Re: lockd spams syslog after upgrade from 2.6.18 to 2.6.24-rc8

Am Montag, 21. Januar 2008 schrieb Hans-Peter Jansen: > Hi, > > after installation of 2.6.24-rc8 on a local server, the syslog gets > spammed with "lockd: cannot monitor " > > grep 'lockd: cannot monitor' /var/log/messages | wc -l > 136026 > > in 20 minu

Re: lockd spams syslog after upgrade from 2.6.18 to 2.6.24-rc8

Am Montag, 21. Januar 2008 schrieb Hans-Peter Jansen: Hi, after installation of 2.6.24-rc8 on a local server, the syslog gets spammed with lockd: cannot monitor some client grep 'lockd: cannot monitor' /var/log/messages | wc -l 136026 in 20 minutes! I restarted the offending client

lockd spams syslog after upgrade from 2.6.18 to 2.6.24-rc8

Hi, after installation of 2.6.24-rc8 on a local server, the syslog gets spammed with "lockd: cannot monitor " grep 'lockd: cannot monitor' /var/log/messages | wc -l 136026 in 20 minutes! I restarted the offending client (with 2.6.18.something) for mercy reasons now.. Pete -- To unsubscribe

Re: linux device ordering at boot time

Dear Alan, dear kernel & dvb hackers, Am Sonntag, 20. Januar 2008 schrieb Alan Cox: > > Well, it's a major pain in the a**. I've no idea, what reversed the > > order of PCI devices, but I had to disable the automatic dvb driver > > loading in order > > It depends on the order you load the modules

Re: linux device ordering at boot time

Dear Alan, dear kernel dvb hackers, Am Sonntag, 20. Januar 2008 schrieb Alan Cox: Well, it's a major pain in the a**. I've no idea, what reversed the order of PCI devices, but I had to disable the automatic dvb driver loading in order It depends on the order you load the modules Sure,

lockd spams syslog after upgrade from 2.6.18 to 2.6.24-rc8

Hi, after installation of 2.6.24-rc8 on a local server, the syslog gets spammed with lockd: cannot monitor some client grep 'lockd: cannot monitor' /var/log/messages | wc -l 136026 in 20 minutes! I restarted the offending client (with 2.6.18.something) for mercy reasons now.. Pete -- To

Re: linux device ordering at boot time

Am Samstag, 19. Januar 2008 schrieben Sie: > I have a question concerning the ordering of devices during the boot > process and I hope that the kernel mailing list is the right place for > this question. In my computer are two raid controllers with one raid > array connected to each of them

Re: linux device ordering at boot time

Am Samstag, 19. Januar 2008 schrieben Sie: I have a question concerning the ordering of devices during the boot process and I hope that the kernel mailing list is the right place for this question. In my computer are two raid controllers with one raid array connected to each of them (/dev/sda,

Re: [GIT PATCHES] V4L/DVB fixes

Am Montag, 7. Januar 2008 schrieb Mauro Carvalho Chehab: > > Hans Verkuil (1): > V4L/DVB (6916): ivtv: udelay has to be changed *after* the eeprom > was read, not before boils down to this patch: 89dab3573aa1d95fd222ee4551f964bfa4c16823 drivers/media/video/ivtv/ivtv-driver.c |4

Re: [GIT PATCHES] V4L/DVB fixes

Am Montag, 7. Januar 2008 schrieb Mauro Carvalho Chehab: Hans Verkuil (1): V4L/DVB (6916): ivtv: udelay has to be changed *after* the eeprom was read, not before boils down to this patch: 89dab3573aa1d95fd222ee4551f964bfa4c16823 drivers/media/video/ivtv/ivtv-driver.c |4

Re: [PATCH 00/11] writeback bug fixes and simplifications

Am Freitag, 28. Dezember 2007 schrieb Sascha Warner: > Andrew Morton wrote: > > On Thu, 27 Dec 2007 23:08:40 +0100 Sascha Warner <[EMAIL PROTECTED]> wrote: > >> Hi, > >> > >> I applied your patches to 2.6.24-rc6-mm1, but now I am faced with one > >> pdflush often using 100% CPU for a long time.

Re: [PATCH 00/11] writeback bug fixes and simplifications

Am Freitag, 28. Dezember 2007 schrieb Sascha Warner: Andrew Morton wrote: On Thu, 27 Dec 2007 23:08:40 +0100 Sascha Warner [EMAIL PROTECTED] wrote: Hi, I applied your patches to 2.6.24-rc6-mm1, but now I am faced with one pdflush often using 100% CPU for a long time. There seem to be

Re: arcmsr changelog differs from diffs

Dear Björn, Am Mittwoch, 17. Oktober 2007 02:53 schrieb Björn Steinbrink: > On 2007.10.17 00:07:19 +0200, Hans-Peter Jansen wrote: > > Hi Jeff, > > > > while browsing through Linus' current check ins, I stumbled upon: > > > > [SCSI] arcmsr: irq handler fixes,

Re: arcmsr changelog differs from diffs

Dear Björn, Am Mittwoch, 17. Oktober 2007 02:53 schrieb Björn Steinbrink: On 2007.10.17 00:07:19 +0200, Hans-Peter Jansen wrote: Hi Jeff, while browsing through Linus' current check ins, I stumbled upon: [SCSI] arcmsr: irq handler fixes, cleanups, micro-opts: --8

arcmsr changelog differs from diffs

Hi Jeff, while browsing through Linus' current check ins, I stumbled upon: [SCSI] arcmsr: irq handler fixes, cleanups, micro-opts: --8<-- 488a5c8a9a3b67ae117784cd0d73bef53a73d57d drivers/scsi/arcmsr/arcmsr_hba.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git

arcmsr changelog differs from diffs

Hi Jeff, while browsing through Linus' current check ins, I stumbled upon: [SCSI] arcmsr: irq handler fixes, cleanups, micro-opts: --8-- 488a5c8a9a3b67ae117784cd0d73bef53a73d57d drivers/scsi/arcmsr/arcmsr_hba.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git

Re: [BUG] Linux 2.6.23-rc9 and MAX_ARG_PAGES

Am Samstag, 6. Oktober 2007 10:29 schrieb Hans-Peter Jansen: > Am Donnerstag, 4. Oktober 2007 19:05 schrieb Mathieu Chouquet-Stringer: > > Hey there, > > > > I've seen the changes you made in commit b6a2fea39318 and I guess they > > might be respon

Re: [BUG] Linux 2.6.23-rc9 and MAX_ARG_PAGES

Am Donnerstag, 4. Oktober 2007 19:05 schrieb Mathieu Chouquet-Stringer: > Hey there, > > I've seen the changes you made in commit b6a2fea39318 and I guess they > might be responsible for my xargs breakage... > > In the kernel source tree, if I run a stupid find | xargs ls, I now get >

Re: [BUG] Linux 2.6.23-rc9 and MAX_ARG_PAGES

Am Donnerstag, 4. Oktober 2007 19:05 schrieb Mathieu Chouquet-Stringer: Hey there, I've seen the changes you made in commit b6a2fea39318 and I guess they might be responsible for my xargs breakage... In the kernel source tree, if I run a stupid find | xargs ls, I now get this:

Re: [BUG] Linux 2.6.23-rc9 and MAX_ARG_PAGES

Am Samstag, 6. Oktober 2007 10:29 schrieb Hans-Peter Jansen: Am Donnerstag, 4. Oktober 2007 19:05 schrieb Mathieu Chouquet-Stringer: Hey there, I've seen the changes you made in commit b6a2fea39318 and I guess they might be responsible for my xargs breakage... In the kernel

Re: [RFC 12/26] ext2 white-out support

Am Dienstag, 31. Juli 2007 19:00 schrieb Jan Blunck: > On Tue, Jul 31, Josef Sipek wrote: > > On Mon, Jul 30, 2007 at 06:13:35PM +0200, Jan Blunck wrote: > > > Introduce white-out support to ext2. > > > > I think storing whiteouts on the branches is wrong. It creates all sort > > of nasty cases

Re: [RFC 12/26] ext2 white-out support

Am Dienstag, 31. Juli 2007 19:00 schrieb Jan Blunck: On Tue, Jul 31, Josef Sipek wrote: On Mon, Jul 30, 2007 at 06:13:35PM +0200, Jan Blunck wrote: Introduce white-out support to ext2. I think storing whiteouts on the branches is wrong. It creates all sort of nasty cases when people

Re: Adding subroot information to /proc/mounts, or obtaining that through other means

Am Donnerstag, 21. Juni 2007 00:46 schrieb H. Peter Anvin: > Dr. David Alan Gilbert wrote: > > What happens with the (sick) case of spaces in directory names? > > Also is it really nicely defined that there is no way to put a space > > in an option in any of the filesystems? I suppose someone >

Re: Adding subroot information to /proc/mounts, or obtaining that through other means

Am Donnerstag, 21. Juni 2007 00:46 schrieb H. Peter Anvin: Dr. David Alan Gilbert wrote: What happens with the (sick) case of spaces in directory names? Also is it really nicely defined that there is no way to put a space in an option in any of the filesystems? I suppose someone

Re: [PATCH] XFS: Replace remaining memclear_highpage_flush() with zero_user_page().

Am Montag, 18. Juni 2007 20:43 schrieb Christoph Hellwig: > On Mon, Jun 18, 2007 at 11:59:30AM -0400, Robert P. J. Day wrote: > > Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]> FYI, this patch got attributed to Christoph in Linus' tree with commit 700716c8468d95ec6d03566a4e4fb576c3223cbc..

Re: [PATCH] XFS: Replace remaining memclear_highpage_flush() with zero_user_page().

Am Montag, 18. Juni 2007 20:43 schrieb Christoph Hellwig: On Mon, Jun 18, 2007 at 11:59:30AM -0400, Robert P. J. Day wrote: Signed-off-by: Robert P. J. Day [EMAIL PROTECTED] FYI, this patch got attributed to Christoph in Linus' tree with commit 700716c8468d95ec6d03566a4e4fb576c3223cbc..

Re: irq nobody cared issue on 2.6.2x

Am Mittwoch, 7. März 2007 20:48 schrieb Mws: > hi all, > > i just moved my win tv dvb-s card (PCI) from my old to my actual pc. > > its an ASUS M2N32 WS Professional AMD64 X2 Board equiped with > the nvidia nForce 590 SLI MCP chipset. > > in the past, i had to use the noapic kernel cmdline param

Re: irq nobody cared issue on 2.6.2x

Am Mittwoch, 7. März 2007 20:48 schrieb Mws: hi all, i just moved my win tv dvb-s card (PCI) from my old to my actual pc. its an ASUS M2N32 WS Professional AMD64 X2 Board equiped with the nvidia nForce 590 SLI MCP chipset. in the past, i had to use the noapic kernel cmdline param to get

Re: prioritize PCI traffic ?

Am Montag, 15. Januar 2007 15:53 schrieb Vaidyanathan Srinivasan: > > 33Mhz 32-bit PCI bus on typical PC can do around 100MB/sec... Substract roughly n * 5MB for VIA chipsets, where n is the age (1 <= n <= 4), and even more for SIS, ATI.. Pete - To unsubscribe from this list: send the line

Re: prioritize PCI traffic ?

Am Montag, 15. Januar 2007 15:53 schrieb Vaidyanathan Srinivasan: 33Mhz 32-bit PCI bus on typical PC can do around 100MB/sec... Substract roughly n * 5MB for VIA chipsets, where n is the age (1 = n = 4), and even more for SIS, ATI.. Pete - To unsubscribe from this list: send the line

Re: Mounting NFS root FS

Am Montag, 4. Dezember 2006 12:51 schrieb Janne Karhunen: > On 12/2/06, William Estrada <[EMAIL PROTECTED]> wrote: > > Hi guys, > > > > I have been trying to make FC5's kernel do a boot > > with an NFS root file system. I see the support is in the > > kernel(?). > > Is this really properly

Re: Mounting NFS root FS

Am Montag, 4. Dezember 2006 12:51 schrieb Janne Karhunen: On 12/2/06, William Estrada [EMAIL PROTECTED] wrote: Hi guys, I have been trying to make FC5's kernel do a boot with an NFS root file system. I see the support is in the kernel(?). Is this really properly possible (with

Re: [PATCH] kernel spams syslog every 10 sec with w1 debug

Am Freitag, 12. August 2005 18:00 schrieb Dave Jones: > On Fri, Aug 12, 2005 at 05:38:37PM +0200, Andi Kleen wrote: > > Olaf Hering <[EMAIL PROTECTED]> writes: > > > Bug 104020 - kernel spams syslog every 10 sec with: w1_driver > > > w1_bus_master1: No devices present on the wire. > > > > > >

Re: [PATCH] kernel spams syslog every 10 sec with w1 debug

Am Freitag, 12. August 2005 18:00 schrieb Dave Jones: On Fri, Aug 12, 2005 at 05:38:37PM +0200, Andi Kleen wrote: Olaf Hering [EMAIL PROTECTED] writes: Bug 104020 - kernel spams syslog every 10 sec with: w1_driver w1_bus_master1: No devices present on the wire. After installing

Re: [PATCH] ppc64: Implement a vDSO and use it for signal trampoline #3

Hi Ben, are you copyrighting under a new pseudonym? E.g.: On Thursday 10 February 2005 03:32, Benjamin Herrenschmidt wrote: > === > --- /dev/null 1970-01-01 00:00:00.0 + > +++

Re: [PATCH] ppc64: Implement a vDSO and use it for signal trampoline #3

Hi Ben, are you copyrighting under a new pseudonym? E.g.: On Thursday 10 February 2005 03:32, Benjamin Herrenschmidt wrote: === --- /dev/null 1970-01-01 00:00:00.0 + +++ linux-work/arch/ppc64/kernel/vdso32/sigtramp.S

Re: [PATCH] Configure MTU via kernel DHCP

On Friday 04 February 2005 19:22, Richard A Nelson wrote: > > What will this code do at the (increasingly common) misconfigured > sites - many places (hotels, airports, etc) return a MTU of 64... > to which the DHCP3 client faithfully attempts to set, only to > receive: > SIOCSIFMTU: Invalid

Re: [PATCH] Configure MTU via kernel DHCP

g.c.orig 2005-02-04 15:59:42.430518242 +0100 +++ linux-2.6/net/ipv4/ipconfig.c 2005-02-04 17:07:14.526384702 +0100 @@ -29,6 +29,10 @@ * * Multiple Nameservers in /proc/net/pnp * -- Josef Siemes <[EMAIL PROTECTED]>, Aug 2002 + * + * Support for MTU selection via

Re: [PATCH] Configure MTU via kernel DHCP

/ipconfig.c 2005-02-04 17:07:14.526384702 +0100 @@ -29,6 +29,10 @@ * * Multiple Nameservers in /proc/net/pnp * -- Josef Siemes [EMAIL PROTECTED], Aug 2002 + * + * Support for MTU selection via DHCP + * -- Hans-Peter Jansen [EMAIL PROTECTED], June 2003

Re: [PATCH] Configure MTU via kernel DHCP

On Friday 04 February 2005 19:22, Richard A Nelson wrote: What will this code do at the (increasingly common) misconfigured sites - many places (hotels, airports, etc) return a MTU of 64... to which the DHCP3 client faithfully attempts to set, only to receive: SIOCSIFMTU: Invalid