Change Compaq Array names to "HP Proliant Array Controllers" in KConfig

Someone may wish to change the description of the Compaq Array Controllers under Block Devices to "HP" based controllers for the HP appliances. It's rather confusing and inaccurate since Compaq has not existed for several years now. The controllers come up and identify themselves as "HP Prol

Preemption Broken: centrino_target busted under SMP on 2.6.20.4

BUG: using smp_processor_id() in preemptible [0001] code: kondemand/0/2473 caller is centrino_target+0xfb/0x600 [<401e3646>] debug_smp_processor_id+0x9e/0xb0 [<40112afb>] centrino_target+0xfb/0x600 [<40112a00>] centrino_target+0x0/0x600 [<40305bd9>] __cpufreq_driver_target+0x5c/0x6b [] do_d

Re: Latest e1000 7.3.20 driver busted with 2.6.20.4

Kok, Auke wrote: Jeff V. Merkey wrote: Kok, Auke wrote: Jeff V. Merkey wrote: CC [M] drivers/net/chelsio/mv88x201x.o CC [M] drivers/net/chelsio/my3126.o LD [M] drivers/net/chelsio/cxgb.o CC drivers/net/e1000/e1000_main.o drivers/net/e1000/e1000_main.c:1185:45: error: macro

Re: Latest e1000 7.3.20 driver busted with 2.6.20.4

Kok, Auke wrote: Jeff V. Merkey wrote: CC [M] drivers/net/chelsio/mv88x201x.o CC [M] drivers/net/chelsio/my3126.o LD [M] drivers/net/chelsio/cxgb.o CC drivers/net/e1000/e1000_main.o drivers/net/e1000/e1000_main.c:1185:45: error: macro "INIT_WORK" passed 3 arguments,

Latest e1000 7.3.20 driver busted with 2.6.20.4

CC [M] drivers/net/chelsio/mv88x201x.o CC [M] drivers/net/chelsio/my3126.o LD [M] drivers/net/chelsio/cxgb.o CC drivers/net/e1000/e1000_main.o drivers/net/e1000/e1000_main.c:1185:45: error: macro "INIT_WORK" passed 3 arguments, but takes just 2 ared (first use in this function) drive

Re: Conclusions from my investigation about ioapic programming

Eric, Please find attached the APIC code I used in Gadugi. It's code for plain vanilla APICs, but does just this. This code not only allows interrupts to be migrated, but processors to be stopped and restarted on the fly without system interruption. You may find some useful ideas in it. Jeff

Re: Conclusions from my investigation about ioapic programming

Here's the include file that goes with it. Jeff #include "types.h" #include "emit.h" #define _82489APIC_MASK 0x00F0 #define APIC_IO_REG 0x #define APIC_IO_DATA 0x0004 // APIC registers are 128 bit aligned. accesses are offset * 4 #define APIC_TASKPRI (4 * 0x0008) #define

Re: Conclusions from my investigation about ioapic programming

Eric W. Biederman wrote: ** Conclusions. *IRQs must be reprogramed in interrupt context. The result of this is investigation is that I am convinced we need to perform the irq migration activities in interrupt context although I am not convinced it is completely safe. I suspect multiple irqs

Re: Free Linux Driver Development!

Jeff Garzik wrote: Great offer to folks for drivers, but it sends a mixed message. OSDL should offer to host a page somewhere to coordinate all of this. :-) Jeff Roland Dreier wrote: Just look at the in-tree drivers: there are tons of them that don't work on big-endian platforms, or hav

Re: SATA/IDE Dual Mode w/Intel 945 Chipset or HOW TO LIQUIFY a flash IDE chip under 2.6.18

Lennart Sorensen wrote: On Wed, Jan 10, 2007 at 06:29:28PM +0100, Prakash Punnoor wrote: You can install the Intel Matrix driver after "adjusting" the inf file... Hmm, I guess a good question is: Why should I have to edit the inf file? Is it an issue of them making it only install if

Re: SATA/IDE Dual Mode w/Intel 945 Chipset or HOW TO LIQUIFY a flash IDE chip under 2.6.18

Jeff Garzik wrote: Jeff V. Merkey wrote: Jeff Garzik wrote: Jeff V. Merkey wrote: I just finished pulling out a melted IDE flash drive out of a Shuttle motherboard with the intel 945 chipset which claims to support SATA and IDE drives concurrently under Linux 2.6.18. The chip worked

Re: SATA/IDE Dual Mode w/Intel 945 Chipset or HOW TO LIQUIFY a flash IDE chip under 2.6.18

Lennart Sorensen wrote: On Tue, Jan 09, 2007 at 01:46:42PM -0700, Jeff V. Merkey wrote: I just finished pulling out a melted IDE flash drive out of a Shuttle motherboard with the intel 945 chipset which claims to support SATA and IDE drives concurrently under Linux 2.6.18. The chip worked

Re: SATA/IDE Dual Mode w/Intel 945 Chipset or HOW TO LIQUIFY a flash IDE chip under 2.6.18

Jeff Garzik wrote: Jeff V. Merkey wrote: I just finished pulling out a melted IDE flash drive out of a Shuttle motherboard with the intel 945 chipset which claims to support SATA and IDE drives concurrently under Linux 2.6.18. The chip worked for about 30 seconds before liquifying in the

Re: SATA/IDE Dual Mode w/Intel 945 Chipset or HOW TO LIQUIFY a flash IDE chip under 2.6.18

Auke Kok wrote: Jeff V. Merkey wrote: Jeff V. Merkey wrote: root=/dev/hda2 is what was passed to the kernel from grub. Jeff I just finished pulling out a melted IDE flash drive out of a Shuttle motherboard with the intel 945 chipset which claims to support SATA and IDE drives

Re: SATA/IDE Dual Mode w/Intel 945 Chipset or HOW TO LIQUIFY a flash IDE chip under 2.6.18

Jeff V. Merkey wrote: root=/dev/hda2 is what was passed to the kernel from grub. Jeff I just finished pulling out a melted IDE flash drive out of a Shuttle motherboard with the intel 945 chipset which claims to support SATA and IDE drives concurrently under Linux 2.6.18. The chip worked

Re: NTFS deadlock on 2.6.18.6

Sergey Vlasov wrote: Yep. Hello! I have encountered a deadlock in the NTFS filesystem on a 2.6.18.6-based kernel (x86_64, CONFIG_SMP set, but the machine has only one CPU (Athlon64 3200+), no PREEMPT). The kswapd0 and mklocatedb processes were apparently involved in the deadlock: kswapd0

SATA/IDE Dual Mode w/Intel 945 Chipset or HOW TO LIQUIFY a flash IDE chip under 2.6.18

I just finished pulling out a melted IDE flash drive out of a Shuttle motherboard with the intel 945 chipset which claims to support SATA and IDE drives concurrently under Linux 2.6.18. The chip worked for about 30 seconds before liquifying in the chassis. I note that the 945 chipset in the

Re: GPL only modules

Linus Torvalds wrote: On Mon, 18 Dec 2006, Alexandre Oliva wrote: In other words, in the GPL, "Program" does NOT mean "binary". Never has. Agreed. So what? How does this relate with the point above? The binary is a Program, as much as the sources are a Program. Both forms are sub

Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19]

Eric W. Biederman wrote: Things we can say without being hypocrites and without getting into legal theory: Kernel modules without source, or that don't have a GPL compatible license are inconsiderate and rude. ?? Please don't be rude. ??? J Eric - To unsubscribe from

Re: [ANNOUNCE] Open Source Protocol Reconstruction Project for Linux

Jeff V. Merkey wrote: Corrected URL. http://sourceforge.net/projects/data-echo Jeff We have open sourced this project for our Linux based appliances and file systems. Anyone from Linux who wants to help port the program from Windows to Linux is welcome. The program supports all native

[ANNOUNCE] Open Source Protocol Reconstruction Project for Linux

We have open sourced this project for our Linux based appliances and file systems. Anyone from Linux who wants to help port the program from Windows to Linux is welcome. The program supports all native Linux forensics applications and formats. The program reconsutructs web session and email,

execv() problems with busybox on 2.6.18

/etc/init.d/rcS script execution fails with busybox on 2.6.18. Seems ldlinux.so related. J - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read

Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19]

This whole effort is pointless. This is the same kind of crap MICROSOFT DOES to create incompatibilities DELIBERATELY. The code is either FREE or its NOT FREE.If the code is FREE then let it be. You can put whatever you want in the code -- I will remove any such constructs, just like I

Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19]

Linus Torvalds wrote: On Thu, 14 Dec 2006, Jeff V. Merkey wrote: Yeah, like that one. WITH THE POLITICAL AGENDA CODE REMOVED. No. That's really a purely technical thing. I'm not certain I understand what you mean here. Nasty messages using the word "taint"

Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19]

Martin J. Bligh wrote: Jeff V. Merkey wrote: Again, I agree with EVERY statement Linus made here. We operate exactly as Linus describes, and legally, NO ONE can take us to task on GPL issues. We post patches of affected kernel code (albiet the code resembles what Linus describes as a

Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19]

Again, I agree with EVERY statement Linus made here. We operate exactly as Linus describes, and legally, NO ONE can take us to task on GPL issues. We post patches of affected kernel code (albiet the code resembles what Linus describes as a "skeleton driver") and our proprietary non derived cod

Re: Need to enable caches in SMP ? (was Kernel 2.6 SMP very slow with ServerWorks LE Chipset)

Alan wrote: As per Alan's suggestion I decompressed the kernel source tree with the processes pegged to one CPU then the other, and as he predicted it took vastly longer on one CPU than the other, but I don't know what that implies, or how to fix it. From the timing it sounds like one

Re: ReiserFS corruption with 2.6.19 (Was 2.6.19 is not stable with SATA and should not be used by any meansis not stable with SATA and should not be used by any means)

Phillip Susi wrote: If your comment here was in reply to my general comment about resierfs stability and not the specific hibernation issue the OP was having, please edit the quote down to just that portion instead of quoting the entire message, including the quotes it was replying to. I won

Re: ReiserFS corruption with 2.6.19 (Was 2.6.19 is not stable with SATA and should not be used by any meansis not stable with SATA and should not be used by any means)

Phillip Susi wrote: Andrew Robinson wrote: Now I am confused on what may be the cause of the corruption. Could it have been just a ReiserFS problem (I will be using Ext3 or JSF on my next rebuild I think after reading some reviews on the ReiserFS and this recent experience). I have been run

[ANNOUNCE] DSFS File System Kernel Patches posted for kernel 2.6.18

the GPL license regarding modifications to the linux kernel core code sections. This patch DOES NOT contain the DSFS file system code, but only contains those portions of the Linux kernel which have been modified and are required to be released under the GPL. Jeff V. Merkey Chief Scientist

Re: scst support for kernels above 2.6.15

Vladislav Bolkhovitin wrote: The code is not at sourceforge on your project site with these updates for 2.6.18. Where is the 2.6.18 version currently hosted? It is there on http://sourceforge.net/projects/scst (http://scst.sourceforge.net/). See 0.9.5 release version as well as developmen

Re: scst support for kernels above 2.6.15

Vladislav Bolkhovitin wrote: Jeff V. Merkey wrote: I have noticed that scsi_do_req has apparently been obsoleted in 2.6.18 and above. Is scst and target support for FC-AL going to remain supported and/or merged at some point? If so, what is planned for scst support for later kernels

scst support for kernels above 2.6.15

I have noticed that scsi_do_req has apparently been obsoleted in 2.6.18 and above. Is scst and target support for FC-AL going to remain supported and/or merged at some point? If so, what is planned for scst support for later kernels? Jeff - To unsubscribe from this list: send the line "uns

2.6.18 X problems with ES4

If the X server is started manually on 2.6.14 and above with "startx &" and if you hit the enter key in the detached session, the desktop will stop responding to keyboard and mouse events. It's easy to reproduce. Set to run level 3 on an ES4, then start the X server manually and hit enter in

Re: [ANNOUNCE] DSFS Network Forensic File System for Linux Patches

NOTE! This copyright does *not* cover user programs that use kernel services by normal system calls - this is merely considered normal use of the kernel, and does *not* fall under the heading of "derived work". Also note that the GPL below is copyrighted by the Free Software Foundation, but the i

Re: [ANNOUNCE] DSFS Network Forensic File System for Linux Patches

[EMAIL PROTECTED] wrote: On Wed, 31 Aug 2005 12:00:45 MDT, "Jeff V. Merkey" said: There's also a more fundamental problem with the GPL language. The GPL stated it confers "RIGHT TO COPY". This is not the same as "RIGHT TO GRANT LICENSES TO DISTRIBUTE.&qu

Re: [ANNOUNCE] DSFS Network Forensic File System for Linux Patches

Arjan van de Ven wrote: The GPL terms that require GPL conversion of any code that runs on Linux is not supported by US Law. Many would disagree, but that's OK. In short, it's just like any other proprietary app running on Linux. If it uses no Linux code (which it does not), then the GPL does

Re: [ANNOUNCE] DSFS Network Forensic File System for Linux Patches

Rik van Riel wrote: On Wed, 31 Aug 2005, Jeff V. Merkey wrote: The Core File System code is a separate proprietary module and is not released under the GPL Are you going to post an analysis on the legality of this on merkeylaw.com ? ;) I am very open to discussions of this

[ANNOUNCE] DSFS Network Forensic File System for Linux Patches

high performance network forensic open source applications on the Linux Operating System. DSFS is fully SMP enabled and supports Hyperthreaded architectures as well as native SMP. Jeff V. Merkey Solera Networks www.soleranetworks.com - To unsubscribe from this list: send the line

Re: [Fwd: United States Patent: 6,862,609]

Trever L. Adams wrote: On Thu, 2005-03-03 at 08:48 -0700, Jeff V. Merkey wrote: Patent law in the US is based on section 113 of the United States Constitution, and patents are not going away. Merkey aren't you supposed to be a lawyer? Unless you do some funky concatenation of art

Re: [Fwd: United States Patent: 6,862,609]

Bernd Petrovitsch wrote: On Wed, 2005-03-02 at 21:28 -0700, Jeff V. Merkey wrote: Gene Heskett wrote: On Wednesday 02 March 2005 21:36, Jeff V. Merkey wrote: Another Linux patent. ... and another - AFAICS obvious - trivial ("prior art") patent (but I'

Re: [Fwd: United States Patent: 6,862,609]

Why the hell would I want to look at the link in kwrite? Talk to the USPTO, they created these links from their website. BTW, if you check the verson of web server run on the uspto.gov server, you will discover it is Apache on IBM servers and IBM Linux. Ask them why IBM's sofware outputs lin

Re: [Fwd: United States Patent: 6,862,609]

Gene Heskett wrote: On Wednesday 02 March 2005 21:36, Jeff V. Merkey wrote: Another Linux patent. And that pretty much says it. Assigned to the Canopy Group. So SCO will have yet another lawsuit to threaten us with. If they survive the thrashing I've Been Moved will give th

[Fwd: United States Patent: 6,862,609]

Another Linux patent. --- Begin Message --- http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=/netahtml/search-bool.html&r=1&f=G&l=50&co1=AND&d=ptxt&s1=merkey.INZZ.&OS=IN/merkey&RS=IN/merkey

Re: RFD: Kernel release numbering

Zwane Mwaikambo wrote: On Wed, 2 Mar 2005, Jeff V. Merkey wrote: __Stable__ would be a good thing. The entire 2.6 development has been a disaster from a stability viewpoint. I have to maintain a huge tree of patches in order to ship appliance builds due to the lack of stability for 2.6. I

Re: RFD: Kernel release numbering

Randy.Dunlap wrote: Jeff V. Merkey wrote: __Stable__ would be a good thing. The entire 2.6 development has been a disaster from a stability viewpoint. I have to maintain a huge tree of patches in order to ship appliance builds due to the lack of stability for 2.6. I think that the even number

Re: RFD: Kernel release numbering

__Stable__ would be a good thing. The entire 2.6 development has been a disaster from a stability viewpoint. I have to maintain a huge tree of patches in order to ship appliance builds due to the lack of stability for 2.6. I think that the even number releases will take longer but it's worth the

Re: Uncle Sam Wants YOU!

On Sun, Jul 01, 2001 at 04:50:44PM -0700, Ben Ford wrote: Microsoft is like a mountain with their installed base. Like it or not, no matter how loud the wind howls, the mountain cannot bow to it. :-) Jeff > Paul Mundt wrote: > > >On Sun, Jul 01, 2001 at 01:35:24PM -0400, Adam Schrotenboer

Re: NWFS Submitted to Alan Cox

On Sun, Jul 01, 2001 at 12:23:17PM -0700, Justin Guyett wrote: > On Mon, 2 Jul 2001, Chris Wedgwood wrote: > > > On Sun, Jul 01, 2001 at 01:50:00PM +0100, Alan Cox wrote: > > > > > I'm not a file sustem hacker, nor since I work for one vendor the > > > appropriate owner for larg chunks of code in

Re: NWFS Submitted to Alan Cox

On Sun, Jul 01, 2001 at 12:16:34AM -0400, Trever L. Adams wrote: > > I am doing very well with my consulting projects, but to be honest, > > my family has sufferred horribly in the past four years fighting with > > Novell every other week, and there's a very strong chance I will be > > moving sh

Re: NWFS Submitted to Alan Cox

On Sun, Jul 01, 2001 at 01:50:00PM +0100, Alan Cox wrote: > > There are several areas that need restructuring and work, and I am > > available to answer questions, and assist with technical consulting, > > I'm not a file sustem hacker, nor since I work for one vendor the > appropriate owner for

Re: NWFS Submitted to Alan Cox

On Sat, Jun 30, 2001 at 10:59:59PM -0500, Paul Fulghum wrote: > > From: "Jeff V. Merkey" <[EMAIL PROTECTED]> > > > Novell has recently threatened to try to take my house and > > assets if I post any more NWFS releases or MANOS. > [snip] > > They

Re: NWFS Submitted to Alan Cox

On Mon, Jul 02, 2001 at 02:54:18AM +1200, Chris Wedgwood wrote: > On Sun, Jul 01, 2001 at 01:50:00PM +0100, Alan Cox wrote: > > > I'm not a file sustem hacker, nor since I work for one vendor the > > appropriate owner for larg chunks of code in some people's eyes. I > > suspect the FSF is a much

Re: NWFS Submitted to Alan Cox

On Sat, Jun 30, 2001 at 05:35:58PM -0700, Jeff V. Merkey wrote: Alan, There is a very current version which I have not released that is in great shape. I have not posted it. This is the version I would be sending you. Jeff > > > Alan, > > I would like for you to take o

NWFS Submitted to Alan Cox

Alan, I would like for you to take over NWFS if you are willing. I have dissolved TRG as a Utah Corporation and I am now focused on a variety of projects for various clients related to Linux development. Novell has recently threatened to try to take my house and assets if I post any more N

Re: aic7xxx oops with 2.4.5-ac13

On Thu, Jun 21, 2001 at 05:08:24PM +0900, Tachino Nobuhiro wrote: Thanks, I'll try this patch. Jeff > > Hello, > > At Thu, 21 Jun 2001 08:15:10, > Trevor Hemsley wrote: > > > > On Thu, 21 Jun 2001 03:05:02, "Jeff V. Merkey" > > <[EM

Re: aic7xxx oops with 2.4.5-ac13

On Thu, Jun 21, 2001 at 02:08:17AM +, Trevor Hemsley wrote: Ditto. I am also seeing this oops calling the sg driver for a robotic tape library, and it also seems to happen on 2.4.4. Jeff > Just upgraded from 2.4.3 to 2.4.5-ac13 and get an aiee, killing interrupt > handler on boot as ai

aic7xxx problems on 2.4.4

On 2.4.4, with the aic7xxx driver loaded, if a test unit ready command (0) is sent to a device which is not loaded via the generic scsi interface, it results in the driver rolling out of memory, even though sg may have open file handles for /dev/sgX, etc. active. Jeff - To unsubscribe fro

Re: IPX to Netware 5.1

On Mon, Jun 11, 2001 at 10:15:50PM +, Petr Vandrovec wrote: > On 11 Jun 01 at 14:56, Matthew G. Marsh wrote: > > On Mon, 11 Jun 2001, Lauri Tischler wrote: > > > > > I've been mounting Netware volumes from Netware 4.1x to linux for > > > a quite a while now, works just fine. > > > We installe

Re: IPX to Netware 5.1

On Mon, Jun 11, 2001 at 12:15:19PM -0300, Arnaldo Carvalho de Melo wrote: The problem is related to the default NLSP (NetWare Link State Routing) stack loaded by default on NetWare versions 5.1 >. NLSP doesn't send RIP/SAP all the time, and if ipx_configure is set to --auto-interface=on --auto

2.4.4 aic7xxx drivers unloads with open sg handles

I am seeing the aic7xxx driver unload itself on 2.4.4 with sg loaded and with a user space app holding active handles. Subsequent closing and reopening of the /dev/sg0, etc. handles is not causing a modprobe autoload of the driver, as normally happens after the code gets into this state. Ple

TRG vger.timpanogas.org hacked

Our master server (vger.timpanogas.org) running 2.2.19 was hacked and completely obliterated by someone using a Novell Proxy Cache via a kernel level exploit in [sys_wait+4]. They somehow created a segmentation fault down inside the kernel, then gained access to the /lib directory and relinke

Re: [Linux-ntfs] Re: [Linux-NTFS-Dev] Re: ANN: NTFS new release available (1.1.15)

On Tue, May 29, 2001 at 10:18:41AM +0200, Martin von Loewis wrote: > > > Anyone know about 3.1? > > > > > > > It's an HPFS variant. > > No. NT was using NTFS right from the start. > > Regards, > Martin No. They were not. Their first cuts of NT used an HPFS variant until NTFS could be compl

Re: [Linux-ntfs] Re: [Linux-NTFS-Dev] Re: ANN: NTFS new release available (1.1.15)

On Mon, May 28, 2001 at 03:49:28PM +0100, Anton Altaparmakov wrote: > At 14:08 28/05/2001, Yuri Per wrote: > >Anton Altaparmakov wrote: > > > >>Does anyone know what NTFS version the NT 3.1 / 3.51 volumes had? If I > >>know I can make sure we don't mount such beasts considering we know the > >>

Re: Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h

On Fri, May 25, 2001 at 07:34:57PM -0700, Adam J. Richter wrote: Copyright infringement would void the GPL, since it would involve conversion (there's that fancy legal word for "steal" again) of someone else's property into another form if you take someone's code and copy it. Some things cann

Re: /dev/sch0 interface

On Tue, May 15, 2001 at 11:44:23PM +, Thorsten Kranzkowski wrote: > On Tue, May 15, 2001 at 03:08:01PM -0600, Jeff V. Merkey wrote: > > > > > > Is anyone actuaslly using the /dev/sch0 interface for SCSI tape changers > > in Linux? I noticed that the device defini

/dev/sch0 interface

Is anyone actuaslly using the /dev/sch0 interface for SCSI tape changers in Linux? I noticed that the device definitions are present, but I do not see any driver shipped in the standard base that actually uses it. Thanks Jeff - To unsubscribe from this list: send the line "unsubscribe linux

Re: more 3ware issues

I am working on them with a project here, and they have a lot of issues. Most of these issues just require some hard work. I am seeing problems on 2.2.19 on all machines if you cram 4 of these 8 IDE disk adapters into a single bus. There are some hardware issues with the cards that seem to sho

Re: Linux support for Microsoft dynamic disks?

On Sun, May 13, 2001 at 12:06:03AM +0100, Anton Altaparmakov wrote: > Hi all, > > Is anyone working on supporting the dynamic disk format introduced with > Windows 2000? If not, does anyone have the specs / any detailed info on the > on disk structures involved? > > Cheers, > > Anton

Re: __alloc_pages: 4-order allocation failed

On Thu, Apr 26, 2001 at 08:00:12PM +0200, Szabolcs Szakacsits wrote: > > On Thu, 26 Apr 2001, Jeff V. Merkey wrote: The request should fail after two or three attempts rather than hang the entire system waiting for memory. Jeff > > > I am seeing this as well on

Re: __alloc_pages: 4-order allocation failed

I am seeing this as well on 2.4.3 with both _get_free_pages() and kmalloc(). In the kmalloc case, the modules hang waiting for memory. Jeff On Wed, Apr 25, 2001 at 09:09:57PM -0400, Feng Xian wrote: > Hi, > > I am running linux-2.4.3 on a Dell dual PIII machine with 128M memory. > After the

Re: filp_open() in 2.2.19 causes memory corruption

On Mon, Apr 23, 2001 at 11:47:27PM +0100, David Woodhouse wrote: David/LKML, I've gotten to the bottom of this problem, and you are correct that klog is trashing the messages file for the oops. As for the oops, it was related to the use of ll_rw_blk() instead of submit_bh() in 2.4.3 which was

Re: NWFS broken on 2.4.3 -- someone removed WRITERAW

On Tue, Apr 24, 2001 at 12:58:09AM +0200, Jens Axboe wrote: > On Mon, Apr 23 2001, Jeff V. Merkey wrote: > > > > > > Hey guys, > > > > Whomever removed WRITERAW has broken NWFS. WRITE requests call > > _refile_buffer() after the I/O request and take m

Re: 3-Ware Raid driver fails to update GenDisk head

On Tue, Apr 24, 2001 at 12:45:35AM +0200, Jens Axboe wrote: > On Mon, Apr 23 2001, Jeff V. Merkey wrote: > > On Mon, Apr 23, 2001 at 11:13:12PM +0200, Guest section DW wrote: > > > On Mon, Apr 23, 2001 at 01:55:00PM -0600, Jeff V. Merkey wrote: > > > > On Mon, Ap

Re: filp_open() in 2.2.19 causes memory corruption

On Mon, Apr 23, 2001 at 11:03:48PM +0100, David Woodhouse wrote: > > [EMAIL PROTECTED] said: > > Are you sure the trace is decoded correctly? > > > > CPU:0 > > > EIP:0010:[sys_mremap+31/884] > > Probably not. It looks like it was munged by klogd. Some distributions are > still shipp

NWFS broken on 2.4.3 -- someone removed WRITERAW

Hey guys, Whomever removed WRITERAW has broken NWFS. WRITE requests call _refile_buffer() after the I/O request and take my locally created buffer heads and munge them back into the linux buffer cache, causing massive memory corruption in the system. These buffers don't belong in Linus' buf

Re: 3-Ware Raid driver fails to update GenDisk head

On Mon, Apr 23, 2001 at 11:13:12PM +0200, Guest section DW wrote: > On Mon, Apr 23, 2001 at 01:55:00PM -0600, Jeff V. Merkey wrote: > > On Mon, Apr 23, 2001 at 09:47:01PM +0200, Guest section DW wrote: > > > On Mon, Apr 23, 2001 at 12:08:52PM -0600, Jeff V. Merkey wrote: >

Re: filp_open() in 2.2.19 causes memory corruption

On Mon, Apr 23, 2001 at 10:24:55PM +0200, Manfred Spraul wrote: > Are you sure the trace is decoded correctly? > > > CPU:0 > > EIP:0010:[sys_mremap+31/884] > > EFLAGS: 00010206 > > > Code: ac ae 75 08 84 c0 75 f8 31 c0 eb 04 19 c0 0c 01 85 c0 75 d9 > ac ae is > lodsb > scasb > > Could

Re: 3-Ware Raid driver fails to update GenDisk head

On Mon, Apr 23, 2001 at 09:47:01PM +0200, Guest section DW wrote: > On Mon, Apr 23, 2001 at 12:08:52PM -0600, Jeff V. Merkey wrote: > > > > I am still working on this, but would appreciate some help from > > whomever owns this driver proper. I have discovered that the >

3-Ware Raid driver fails to update GenDisk head

Andre/LKML, I am still working on this, but would appreciate some help from whomever owns this driver proper. I have discovered that the 3Ware drivers are not updating the gendisk_head with devices reported and exposed to user space as /dev/sda, sdb, etc. The adapter driver does correctly r

filp_open() in 2.2.19 causes memory corruption

I am now using the filp_open() call in kernel to scan for tape devices in lieu of chrdev_open()/blkdev_open(), but I have discovered that calling this api with non-existent devices appears to result in memory corruption and some nasty oops. I have attached the code fragment and oops generate

Re: BUG() at line 804, slab.c, 2.4.3

On Tue, Apr 17, 2001 at 03:29:20PM -0600, Jeff V. Merkey wrote: Added kmem_cache_destroy() to get around the problem. I'm still curious as to why we need to panic at this point rather than return an error. Thanks Jeff > > > I noticed that subsequent calls to kmem_cache_c

BUG() at line 804, slab.c, 2.4.3

I noticed that subsequent calls to kmem_cache_create with the same name does not return an -EEXIST return code, but instead barfs and crashes with a bug at slab.c line 804. This occurs in 2.4.3. Is this the expected behavior for kmem_cache_create? I am using the slab allocator to create and

Re: EXPORT_SYMBOL for chrdev_open 2.4.3

On Fri, Apr 13, 2001 at 09:25:10PM -0400, Alexander Viro wrote: > > > On Fri, 13 Apr 2001, Jeff V. Merkey wrote: > > > Not meaning to offend, but how could you know what everyone > > who uses Linux needs in every instance? NT, NetWare, etc. all > > expose thes

Re: EXPORT_SYMBOL for chrdev_open 2.4.3

On Fri, Apr 13, 2001 at 09:29:43PM -0400, Alexander Viro wrote: > > On Fri, 13 Apr 2001, Jeff V. Merkey wrote: > > > How are folks supposed to open disk and tape devices from kernel modules > > without these? Not everything should be done in user space Al. If you >

Re: EXPORT_SYMBOL for chrdev_open 2.4.3

On Fri, Apr 13, 2001 at 06:38:10PM -0600, Jeff V. Merkey wrote: > On Fri, Apr 13, 2001 at 08:13:41PM -0400, Alexander Viro wrote: > > > > > > On Fri, 13 Apr 2001, Jeff V. Merkey wrote: > > > > > It would be nice if chrdev_open were added to ksyms.c alo

Re: EXPORT_SYMBOL for chrdev_open 2.4.3

On Fri, Apr 13, 2001 at 08:13:41PM -0400, Alexander Viro wrote: > > > On Fri, 13 Apr 2001, Jeff V. Merkey wrote: > > > It would be nice if chrdev_open were added to ksyms.c along with > > blkdev_open since tape devices seem are always registered as character >

EXPORT_SYMBOL for chrdev_open 2.4.3

It would be nice if chrdev_open were added to ksyms.c along with blkdev_open since tape devices seem are always registered as character rather than block devices. I am finding that kernel modules that need to open and close a tape drive have to export chrdev_open manually on 2.4.3. Can this

[Open Source W2K argument fallout][securityalert@sans.org: Large Criminal Hacker Attack on Windows NT E-Banking and E-Commerce Sites]

I am continually amazed at how secure an "open source" OS is in comparison to W2K. Relative to the W2K open source arguments, one good fallout would be that folks would be able to identify holes like this one quickly. Jeff - Forwarded message from The SANS Institute <[EMAIL PROTECTED]> --

Re: Microsoft begining to open source Windows 2000?

On Thu, Mar 08, 2001 at 05:53:08PM +, Anton Altaparmakov wrote: > > > >They do already license the source to a few trusted companies (Executive > >Software used to ship modified NTFS drivers for NT 3.51 as part of > >Diskeeper, IIRC). They are inching ever so slowly towards letting human > >be

[ANNOUNCE] PCI-SCI Drivers 1.2-2 reposted

I have reposted the PCI-SCI files since some folks have reported corruption in one of the files on our server. These drivers support PCI-SCI hardware versions up to the PSB66. These drivers can be downloaded for 2.2 and 2.4 Linux at vger.timpanogas.org:/sci/pci-sci-1.2-2 via ftp or from

Re: partition table: chs question

- Original Message - From: "Guest section DW" <[EMAIL PROTECTED]> To: "Jeff V. Merkey" <[EMAIL PROTECTED]> Cc: "Jeff V. Merkey" <[EMAIL PROTECTED]>; "Andreas Jellinghaus" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; &

Re: partition table: chs question

- Original Message - From: "Andre Hedrick" <[EMAIL PROTECTED]> To: "Jeff V. Merkey" <[EMAIL PROTECTED]> Cc: "Jeff V. Merkey" <[EMAIL PROTECTED]>; "Guest section DW" <[EMAIL PROTECTED]>; "Andreas Jellinghaus" <

Re: partition table: chs question

table has been corrupted. Jeff > > On Sun, 25 Feb 2001, Jeff V. Merkey wrote: > > > > > Please also check vger.timpanogas.org/nwfs/nwfs.tar.gz:disk.c for NetWare > > specific calculations of the CHS values, a different method is used for > > NetWare parti

Re: partition table: chs question

On Mon, Feb 26, 2001 at 04:11:56AM +0100, Guest section DW wrote: > On Sun, Feb 25, 2001 at 05:02:09PM -0700, Jeff V. Merkey wrote: > > > Please also check vger.timpanogas.org/nwfs/nwfs.tar.gz:disk.c for NetWare > > specific calculations of the CHS values, a different

Re: partition table: chs question

Please also check vger.timpanogas.org/nwfs/nwfs.tar.gz:disk.c for NetWare specific calculations of the CHS values, a different method is used for NetWare partitions vs. everything else (Novell just had to be different). If you do not use their methods on NetWare partitions, NetWare will not reco

Re: partition table: chs question

- Original Message - From: "Jeff V. Merkey" <[EMAIL PROTECTED]> To: "Guest section DW" <[EMAIL PROTECTED]>; "Andreas Jellinghaus" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Sunday, February 25, 2001 5:02 PM Subject: Re:

[ANNOUNCE] PCI-SCI Dolphin Drivers 1.2-2 Released

Linux Kernel, The Dolphin PCI-SCI Scalable Coherent Interface drivers v1.2-2 have been posted at vger.timpanogas.org:/sci/pci-sci-1.2-2 and are avaialble for download in tar.gz and .src.rpm (RedHat Package Manager) formats. These drivers are released under the GPL, and are freely redistribu

[ANNOUNCE] PCI-SCI Drivers v1.2-1 Released

Linux Kernel, The PCI-SCI Drivers for the Dolphin Scalable Coherent Interface v1.2-1 has posted at vger.timpanogas.org:/sci/pci-sci-1.2-1. This release corrects several hardware related bugs, and corrects several previously reported build and performance problems related to the RedHat 7.1 F

PCI-SCI Build Problems on RedHat 7.1

On Wed, Feb 07, 2001 at 01:24:26PM -0700, Jeff V. Merkey wrote: Larry, Please provide to Alan Cox the exact versions and revision levels of the RedHat 7.1 build used for the SCI testing. Please provide him any other information he requests concerning the setup of this system. Jeff >

  1   2   3   4   5   6   7   >