Vojtech Pavlik wrote:
> On Tue, Mar 06, 2001 at 09:32:46PM +, Paul Bristow wrote:
> > On Tuesday 06 March 2001 19:13, Konrad Stopsack wrote:
> > > Hello guys,
> > >
> > > I hope you've read my posting "DMA problem with ZIP drive and VIA
> > > VT82C598MVP / VT82C586B chip" (why does anybody
I'm 99.9% certain that those patches referred to have been merged with the
latest 2.4.2-acX, but just to make it 100% certain I'm asking this question.
At www.namesys.com, the reiserfs website, I read:
"Latest patch for linux-2.4.2 contains fixes for tail conversion bug,
preallocated block
Alan Cox wrote:
> 2.4.2-ac14
> o Updated i810_audio.c(Doug Ledford)
I wanted to let people know that there is a lot of new code in this particular
update that needs testing. The nice thing is that quake3 should now play with
this sound driver so the testing can
On Wed, 7 Mar 2001, Tom Sightler wrote:
> 2. Does linux have any problems with large (500GB+) NFS exports, how about
> large files over NFS?
>
> 3. What filesystem would be best for such large volumes? We currently use
> reirserfs on our internal system, but they generally have filesystems
"Richard B. Johnson" <[EMAIL PROTECTED]> writes:
> Attempts to run linux-2.4.3-pre2 on chaos.analogic.com results
> in **MASSIVE** file-system destruction. I have (had) all SCSI
> disks, using the BusLogic controller.
>
> There is something **MAJOR** going on BAD, BAD, BAD, even disks
> that
Hi Linus,
This patch fixes the /dev/fb* entries in devices.txt to conform to the actual
code (which has been there since at least one year).
PLEASE apply this patch! MANY thanks!
--- linux-2.4.3-pre3/Documentation/devices.txt Sat Dec 30 20:26:10 2000
+++
On Wed, 7 Mar 2001, Ben Greear wrote:
> I see it differently: If it's possible for the driver to protect the
> user, and it does not, then it strikes me as irresponsible programming. If
> there is a reason other than 'only elite users are cool enough to tune
> their system, and they never
Alexander Viro wrote:
>
> On Wed, 7 Mar 2001, Ben Greear wrote:
>
> > However, messing with the hdparms options can do random things, at
> > least from my perspective as a user: It may bring exciting new performance
> > to your system, and it may subtly, or not so, corrupt your file system.
>
Tom Sightler wrote:
> ...
> For example if we purchase a NetApp Filer, or EMC Celerra with 1TB of
> storage, and elect to export that entire amount as a single NFS mount, and
> then use that storage to allow several Linux boxes to share 100GB
> (admittedly temporary) files, will Linux handle
On Mar 07 2001, Vojtech Pavlik wrote:
> Also, the vt82c686 will work just fine with Linux, but will be limited
> to UDMA33, because UDMA66 on this chip does reliably fail.
How do I know which one I have? Using the revision of the
chip?
lspci only shows that I have a
On Wed, 7 Mar 2001, Ben Greear wrote:
> However, messing with the hdparms options can do random things, at
> least from my perspective as a user: It may bring exciting new performance
> to your system, and it may subtly, or not so, corrupt your file system.
It's root-only. If you run
Hi. alan.
>2.4.2-ac14
at patching.
>The next patch would create the file `include/linux/hdlc.h',
>which already exists! Assume -R? [n] n
>Apply anyway? [n] y
>patching file `include/linux/hdlc.h'
>Patch attempted to create file `include/linux/hdlc.h', which already exists.
>Hunk #1 FAILED at
On Wed, 7 Mar 2001, Tom Sightler wrote:
> The questions that have been asked are as follows (assume 2.4.x kernels):
>
> 1. What is the largest block device that linux currently supports? i.e.
> Can I create a single 1TB volume on my storage device and expect linux to
> see it and be able to
Alan Cox wrote:
>
> > I'm not arguing it was a smart thing to do, but I would think that the
> > fs/kernel/driver writers could keep really nasty and un-expected things
> > from happenning. For instance, the driver could dis-allow any new (non-hdparm)
>
> Like stopping root from using rm -r ?
>(scsi1:A:0:0): data overrun detected in Data-out phase. Tag == 0x36.
>(scsi1:A:0:0): Have seen Data Phase. Length = 0. NumSGs = 0.
As I mentioned to you the last time you brought up this problem, I
don't believe that this is caused by the aic7xxx driver, but the
aic7xxx driver may be the
It appears that use of CONFIG_PCMCIA_SERIAL_CB was removed in
2.4.2-ac12. The two files affected were Config.in and the Makefile
in drivers/char/pcmcia.
If in fact this option is now history, the reference in Configure.help should also
be history. I noticed this when the number of
Hey There Kernel-people!
I have a disk accessing question you may be able to help me with,
if I may be so bold
I have a notebook computer, and in the interests of saving power
I am trying to get its disk to go into suspend mode (hdparm -S 6 /dev/hda,
say...) However, something seems to
> >1. What is the largest block device that linux currently supports? i.e.
> >Can I create a single 1TB volume on my storage device and expect linux to
> >see it and be able to format it?
>
> Checkout the GFS project for really large filesystems with a high
capability
> of "fail safe"
> Gregory Maxwell wrote:
>
> >
> > There are no threads in Linux.
> > All tasks are processes.
> > Processes can share any or none of a vast set of resources.
> >
> Is there a way a user program can find out what resources
> are shared among which processes?
>
> That would allow enhancing ps,
On Wed, 7 Mar 2001, Jesse Pollard wrote:
> On Wed, 07 Mar 2001, Tom Sightler wrote:
> >Hi All,
> >
> >I'm seeking information in regards to a large Linux implementation we are
> >planning. We have been evaluating many storage options and I've come up
> >with some questions that I have been
Applies against the 2.4.2 kernel and supports i386 and ia64 systems.
This patch provides the ability to register support for generic
process groups. It does this by adding and entry in the task_struct
to maintain a list of pagg (process aggregate) group attachments (or
memberships). In
Applies against the 2.4.2 kernel, supports i386 and ia64, and depends
upon the Linux Process Aggregates (PAGG) patch (linux-2.4.2-pagg.patch).
The PAGG patch was delivered in a previous post with the subject: "[PATCH]
2.4.2 - Process Aggregates". At the bottom of this description will be
a web
On Wed, 07 Mar 2001, Tom Sightler wrote:
>Hi All,
>
>I'm seeking information in regards to a large Linux implementation we are
>planning. We have been evaluating many storage options and I've come up
>with some questions that I have been unable to answer as far as Linux
>capabilities in regards
[Jörn Nettingsmeier, quoting Robert Muller]
> Just create a shell script called yacc with the following content
> ---
> #!/bin/sh
> bison --yacc $*
> ---
> i ran into the same problem with a school proiject here yesterday
Why does nobody learn shell anymore?
I can trigger this every time.
I'm using 2 2gb DEC drives (seagate) wide-scsi. I have an adaptec
aha-2940uw card installed on the primary pci bus.
I'm using reiserfs and LVM (striped), but I can reproduce this w/o these.
All I have to do is:
for dev in /dev/sd[bcd];do cp /dev/zero $dev & ; done
Sorry, I have wasted your time by speaking too early.
Here is a corrected version of my fix; the old one replaced one
typo with another X-<.
You need this to link for Athron/Durons.
--- 2.4.2-ac14/include/asm-i386/processor.h Wed Mar 7 16:59:48 2001
+++
On Wed, Mar 07, 2001 at 05:20:56PM -0600, Erik DeBill wrote:
>
> I went to install some new software on my Visor yesterday and got a
> rude surpise, as my system froze hard (unpingable, no response to
> keyboard or mouse, no oops). A bit of experimenting shows:
>
> It works fine with usb-uhci
Hi All,
I'm seeking information in regards to a large Linux implementation we are
planning. We have been evaluating many storage options and I've come up
with some questions that I have been unable to answer as far as Linux
capabilities in regards to storage.
We are looking at storage systems
You need this to compile for Athron/Durons.
--- 2.4.2-ac14/include/asm-i386/processor.h Wed Mar 7 16:59:48 2001
+++ 2.4.2-ac14/include/asm-i386/processor.h Wed Mar 7 17:25:17 2001
@@ -499,7 +499,7 @@
{
__asm__ __volatile__ ("prefetch (%0)" : : "r"(x));
}
-#define
Ivan Kokshaysky wrote:
...
> Well, it seems that I finally see what is wrong with your code, and
> why it worked in your case. You assume that "window" resources of
> the bridge are already known when we call pbus_assign_resources_sorted().
> This is incorrect.
Oh...do we know the "sizes" of
"J . A . Magallon" wrote:
>
> Try this:
This is the better fix.
I apologise for this stuff-up.
-
-
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
On 03.08 MATSUSHIMA Akihiro wrote:
> Hello,
> I receive the following error with make bzImage:
>
> i386_ksyms.c:170: `do_BUG' undeclared here (not in a function)
> i386_ksyms.c:170: initializer element is not constant
> i386_ksyms.c:170: (near initialization for `__ksymtab_do_BUG.value')
>
On Wed, Mar 07, 2001 at 04:40:52PM -0800, Greg KH wrote:
> On Wed, Mar 07, 2001 at 11:13:37PM +, Alan Cox wrote:
> > o Fix the non build problem with do_BUG (Andrew Morton)
>
> gcc -D__KERNEL__ -I/home/greg/linux/linux-2.4.2-ac14/include -Wall
>-Wstrict-prototypes -O2
>Hi,
>
>Just a note to make gcc 2.96 (and future) happy. The aic7xxx driver is full of
>inline funcs that should return a value and do not do that:
They don't return a value because doing so is meaningless. You aren't
going to get past the panic. The compiler should know that assuming
panic is
> Hello,
> I receive the following error with make bzImage:
>
> i386_ksyms.c:170: `do_BUG' undeclared here (not in a function)
> i386_ksyms.c:170: initializer element is not constant
> i386_ksyms.c:170: (near initialization for `__ksymtab_do_BUG.value')
> make[1]: *** [i386_ksyms.o] Error 1
>
Hello,
2.4.2ac14 compilation fails when CONFIG_DEBUG_BUGVERBOSE is not enabled.
Here is my small patch.
diff -r -u linux-2.4.2-ac14.org/include/asm-i386/page.h
linux-2.4.2-ac14/include/asm-i386/page.h
--- linux-2.4.2-ac14.org/include/asm-i386/page.hThu Mar 8 09:31:45 2001
+++
On Wed, Mar 07, 2001 at 11:13:37PM +, Alan Cox wrote:
> o Fix the non build problem with do_BUG (Andrew Morton)
gcc -D__KERNEL__ -I/home/greg/linux/linux-2.4.2-ac14/include -Wall -Wstrict-prototypes
-O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686
Oswald Buddenhagen wrote:
>
> > The problem with these things it that sometimes such a task may hold
> > a lock, which can prevent higher-priority tasks from running.
> >
> true ... three ideas:
> - a sort of temporary priority elevation (the opposite of SCHED_YIELD)
> as long as the process
On 2001-03-07, "Albert D. Cahalan" <[EMAIL PROTECTED]> wrote:
> Then for proper ps and top output, you need a reasonably efficient
> way to grab all threads as a group. This could be as simple as
> ensuring that /proc directory reads return related tasks together.
> This works too:
Hi,
Just a note to make gcc 2.96 (and future) happy. The aic7xxx driver is full of
inline funcs that should return a value and do not do that:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.2-ac14/include -Wall -Wstrict-prototypes
-O2 -fomit-frame-pointer -fno-strict-aliasing -pipe
Hello,
I receive the following error with make bzImage:
i386_ksyms.c:170: `do_BUG' undeclared here (not in a function)
i386_ksyms.c:170: initializer element is not constant
i386_ksyms.c:170: (near initialization for `__ksymtab_do_BUG.value')
make[1]: *** [i386_ksyms.o] Error 1
make[1]: Leaving
I've been running with just that single visor patch on 2.4.2 for quite
some time now. But I'm building ac13 right now, and I'll let you know
what I find out in a bit.
thanks for letting me know.
greg k-h
--
greg@(kroah|wirex).com
-
To unsubscribe from this list: send the line "unsubscribe
> On ac12 and 13 if the visor driver is compiled into the kernel it wil=
> l
> work poorly for a time (very slow sync, jpilot/pilot-link complains o=
Does 2.4.2ac11 work - I ask this as ac12 has some visro changes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
>hmmm.. Is there a reason why this would be -needed-? It wouldn't be
>hard to implement, but I would rather not have drivers dealing with a
>list whose normal state is defined as "mostly sorted"...
That's the wrong definition. The list is "sorted by probe order".
--
Justin
-
To unsubscribe
I went to install some new software on my Visor yesterday and got a
rude surpise, as my system froze hard (unpingable, no response to
keyboard or mouse, no oops). A bit of experimenting shows:
It works fine with usb-uhci in all versions I tested.
Plain 2.4.2 works fine with either usb-uhci or
Helge Hafting writes:
> Gregory Maxwell wrote:
>> There are no threads in Linux.
>> All tasks are processes.
>> Processes can share any or none of a vast set of resources.
>
> Is there a way a user program can find out what resources
> are shared among which processes?
>
> That would allow
> "AV" == Alexander Viro <[EMAIL PROTECTED]> writes:
AV> Double ugh. Why bother with ioctl() when you can just have a
AV> second channel and do read()/write() on it?
Because you cannot rewrite -- or even re-compile -- every app this
should support. OSS emulation by ALSA is a great example,
On Wed, Mar 07 2001, Pozsar Balazs wrote:
>
> Adding the
> cgc.buflen = 20;
> line into drivers/cdrom/cdrom.c: dvd_read_physical(...)
> solves my problem.
>
> I don't know the difference, but first you mentioned
> cgc.buflen = 16;
> so i tried that also, and it worked the same.
>
> I'll
I was wondering what the difference between wake_up_process and
wake_up_process_synchronous is?
Thanks for your input,
Alberio.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
> It'll only take a few days. Do we want? If not, we can
> extend the dev_probe_lock() thing to cover probes for
> other busses. USB, I guess.
cardbus.. usb.. insmod/rmmod
I'd like it fixed, but you have to convince DaveM
-
To unsubscribe from this list: send the line "unsubscribe
Jeff Garzik wrote:
>
> People from time to time point out a wart in ethernet initialization:
>
They sure do. You were away at the time, but I had a 94 file,
140k patch late last year which fixed all this. It's
at
http://www.uow.edu.au/~andrewm/linux/netdevice.patch
and the design
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
2.4.2-ac14
o Fix the non build problem with do_BUG (Andrew Morton)
o Fix interface autocreation bug in ipx (Arnaldo Carvalho
Also fix pprop routing bugs, tctrl handling de Melo)
Adding the
cgc.buflen = 20;
line into drivers/cdrom/cdrom.c: dvd_read_physical(...)
solves my problem.
I don't know the difference, but first you mentioned
cgc.buflen = 16;
so i tried that also, and it worked the same.
I'll write again if i'm having problems. :)
Thanks for the fast patch.
I
I did an upgrade from kernel-2.2.16 to the latest version-2.4.2.
During the "make bzImage"step, I got bunch of this warning:
"pasting would not give a valid preprocessing token". then I just ignored
it and after all done
rebooted the linux and got into the new kernel successfully. However, when
"Justin T. Gibbs" wrote:
> How often is the list manipulated? My guess is not very often.
Modified very infrequently... at boot, and for each hotplug insertion
or removal. It's not even read very often.
> You can allow people to read the list without taking a spinlock and
> only acquire the
Thank you again for your help. While I do seem to get more errors
with the ide-tape driver, I am also seeing some problems on further
examination which are common to both ide-tape and st over ide-scsi, so
perhaps I have a bad drive or tape.
When trying to mt eom, for example, I get
>I would prefer to sort the list at probe not boot time. That makes it
>easy to reverse the order on the fly, depending on what the driver
>requests at runtime. It's SMP-friendly, because I can grab a private
>copy of the PCI device list, sort it, and scan it. You don't have to
>re-sort at
On Wed, Mar 07, 2001 at 02:35:56PM -0800, Andre Hedrick wrote:
> So basically you are pointing out that there is now a sequencer reject in
> linux? Because this used to effect and wipe drives, but you are showing
> that Linux now does scsi commands check for execution on the /dev/sdxx?
Nope,
> For PCI drivers, you implement the ::suspend and ::remove hooks.
> > I have a race free version of pm_send_all if you want it.
> Is this the same thing that is in 2.4.3-pre3?
Mine is race free for the basics, his is a far far more elegant solution to the
whole problem space. It might be 2.5
So basically you are pointing out that there is now a sequencer reject in
linux? Because this used to effect and wipe drives, but you are showing
that Linux now does scsi commands check for execution on the /dev/sdxx?
On Wed, 7 Mar 2001, Craig Ruff wrote:
> On Wed, Mar 07, 2001 at 01:15:46PM
Hi,
I've taken today to write some documentation for
include/linux/mm.h, as used in 2.4.x
Tonight and tomorrow I'll work on the documentation of other
files. Corrections, improvements and additions to this patch
are requested, lets try to get our stuff documented...
regards,
Rik
--
Linux MM
On Wed, Mar 07 2001, Jens Axboe wrote:
> On Wed, Mar 07 2001, Jens Axboe wrote:
> > Really good question, I sent this patch in the private thread between
> > me and Pozsar just in case the length is what the drive complains about.
>
> Agrh, that's not all. I will fix this properly, sorry about
Jeff Garzik wrote:
> Our API already supports a solution -- setup the device, then call
> register_netdev. The patch below adds a helper, alloc_etherdev, to
> eliminate duplicate code in drivers. Ethernet device initialization,
> after the patch, should now look like
>
> dev =
Andre Hedrick writes:
> That is not the case Joanne is pointing out.
> The SCSI low-level format glue performed by the HOST gets destroyed
> If you write to LBA Zero. ATA only suffers the lose of the partition
> table and that can be recovered, but SCSI needs that information to know
> where
On Tue, Mar 06, 2001 at 10:12:17PM -0500, Jeff Dike wrote:
> [EMAIL PROTECTED] said:
> > If you're a UP system, it never makes sense to spin in userland, since
> > you'll just burn up a timeslice and prevent the lock holder from
> > running. I haven't looked, but assume that their code only uses
On Wed, Mar 07, 2001 at 01:15:46PM -0800, Andre Hedrick wrote:
>
> Then run this and see if you live.
Well, I ran it, the disk lives. The typescript is appended below.
Interestingly, scsikiller didn't cream the partition table like I
expected. However the dd if=/dev/zero of=/dev/sdc certainly
On Wed, 7 Mar 2001, Petr Vandrovec wrote:
> Hi Linus, hi Alan,
> could you apply following patch into 2.4.2-ac14 and 2.4.3-pre4?
> It does:
>
>last three hunks: do not d_add() already hashed dentry.
> It is fix for problem discovered by Urban
>
Linus Torvalds wrote:
> I suspect it's easier to just make the PCI layer call the probe function
> in that order, instead of working around it in your driver.
That seems like a really good idea, especially in light of the fact that
some drivers are doing (have to do?) -reverse- order PCI
On Wednesday March 7, [EMAIL PROTECTED] wrote:
> I run a Dual prozessor SMP system on 2.4.2-ac12 for a while
> in degraded mode. Today I put in a new disk to switch to
> full raid5 mode. Shortly after the command raidhotadd the
> system crashed with the message lost interrupt on cpu1.
Was
On Wed, 7 Mar 2001, Pete Zaitcev wrote:
> Trace; c0127414
> Trace; c0136a2d
> Trace; c012722e
> Trace; c0127290
> Trace; c0127414
> Trace; c014cdec
> Trace; c0143f80
> Trace; c0144aae
> Trace; c014cdec
> Trace; c01392c9
> Trace; c0138130
> Trace; c013805d
> Trace; c0148b97
> Trace;
Hi Alan,
if you are going to apply patch I saw today morning on linux-kernel
to disable redzoning on SLAB_HWCACHE aligned areas, drop this one into
wastebasket.
If not, please apply this. When CONFIG_DEBUG_SLAB is enbled,
dentries do not live on 16bytes boundary, but on x*8 + 4 :-( So I
can
On Wed, Mar 07 2001, Jens Axboe wrote:
> Really good question, I sent this patch in the private thread between
> me and Pozsar just in case the length is what the drive complains about.
Agrh, that's not all. I will fix this properly, sorry about the noise.
--
Jens Axboe
-
To unsubscribe from
Hi Linus, hi Alan,
could you apply following patch into 2.4.2-ac14 and 2.4.3-pre4?
It does:
last three hunks: do not d_add() already hashed dentry.
It is fix for problem discovered by Urban
in his smbfs. Probably it is more utilized
On Wed, Mar 07 2001, Derek Fawcus wrote:
> > > hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
> > > hdd: packet command error: error=0x50
> > > ATAPI device hdd:
> > > Error: Illegal request -- (Sense key=0x05)
> > > Invalid field in command packet -- (asc=0x24,
In article <[EMAIL PROTECTED]> you wrote:
> This bug, which I fix, isn't causing oops AFAIK, just
> exporting ugliness to user space etc.
It CAN and IS causing oopses. init_etherdev() causes /sbin/hotplug to be
invoked, which in turn ifconfig up's the interface.
Several (if not all) drivers have
On Wed, Mar 07, 2001 at 09:36:32PM +0100, Jens Axboe wrote:
> On Wed, Mar 07 2001, Pozsar Balazs wrote:
> > Details: (dmesg)
> >
> > When I run "dvdinfo /dev/hdd" I get:
> > Disc is encrypted.
> > Layer 0[3]
> > Num Layers: 2
> > Start Sector0xd000
> > End Sector 0xd000
> > End
I run a Dual prozessor SMP system on 2.4.2-ac12 for a while
in degraded mode. Today I put in a new disk to switch to
full raid5 mode. Shortly after the command raidhotadd the
system crashed with the message lost interrupt on cpu1.
This continued after reboot. I finaly managed to get it running
On Wed, 7 Mar 2001, Vojtech Pavlik wrote:
> Date: Wed, 7 Mar 2001 20:14:37 +0100
> From: Vojtech Pavlik <[EMAIL PROTECTED]>
> To: George Garvey <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: Linux 2.4.2ac12 (vt82c686 info)
>
> On Tue, Mar 06, 2001 at 05:05:46AM -0800, George Garvey
On Wed, 7 Mar 2001, Andre Hedrick wrote:
>
> Harvey,
>
> That is not the case Joanne is pointing out.
> The SCSI low-level format glue performed by the HOST gets destroyed
> If you write to LBA Zero. ATA only suffers the lose of the partition
> table and that can be recovered, but SCSI needs
People from time to time point out a wart in ethernet initialization:
The net_device is allocated and registered to the system in
init_etherdev, which is usually one of the first things an ethernet
driver probe function does. The net_device's final members are setup at
some time between then
Oh, it should be noted that since this is intended as a stable 2.4
series change. The patch does not change any existing APIs, only adds a
function. Existing 2.4 drivers are free to continue using
init_etherdev... This bug, which I fix, isn't causing oops AFAIK, just
exporting ugliness to user
Then run this and see if you live.
On Wed, 7 Mar 2001, Craig Ruff wrote:
> On Wed, Mar 07, 2001 at 12:32:08PM -0800, Andre Hedrick wrote:
> > The SCSI low-level format glue performed by the HOST gets destroyed
> > If you write to LBA Zero.
>
> This is simply not true. I write to SCSI disk's
Jeff Garzik <[EMAIL PROTECTED]> writes:
> John Fremlin wrote:
> > Why not set up the device driver to handle PM events itself. See
> > Documentation/pm.txt under Driver Interface.
>
> For PCI drivers, you implement the ::suspend and ::remove hooks.
>
> > I have a race free version of
Hello,
I ran 2.4.2 under heavy load since 2 days.
I try to decrypt my /etc/passwd files with the program John
the Ripper on a Pentium133.
This process is very long ;-)
I don't understand the error. Hope it will be useful.
Pierre
you can see the load average and the uptime after crash:
Alexander Viro writes:
>Erm. If ioctls are device-specific - the program is already bound to
>specific driver. If they are for class of devices (and if I guessed
>right that's the case you are interested in - sound, isn't it?) we
>could let the stub driver in kernel open two pipes and redirect
On Wed, Mar 07 2001, Stephen C. Tweedie wrote:
> On Wed, Mar 07, 2001 at 09:15:36PM +0100, Jens Axboe wrote:
> > On Wed, Mar 07 2001, Stephen C. Tweedie wrote:
> > >
> > > For most fs'es, that's not an issue. The fs won't start writeback on
> > > the primary disk at all until the journal commit
Hi,
On Wed, Mar 07, 2001 at 09:15:36PM +0100, Jens Axboe wrote:
> On Wed, Mar 07 2001, Stephen C. Tweedie wrote:
> >
> > For most fs'es, that's not an issue. The fs won't start writeback on
> > the primary disk at all until the journal commit has been acknowledged
> > as firm on disk.
>
> But
On Wed, Mar 07, 2001 at 12:32:08PM -0800, Andre Hedrick wrote:
> The SCSI low-level format glue performed by the HOST gets destroyed
> If you write to LBA Zero.
This is simply not true. I write to SCSI disk's block 0 all of the time
and never loose data. Obviously, you can lose the partition
On Wed, Mar 07 2001, Pozsar Balazs wrote:
> Details: (dmesg)
>
> Linux version 2.4.2-3mdk ([EMAIL PROTECTED]) (gcc version
> egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Tue Feb 27 02:14:17
> CET 2001
> ...
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz system
From: "Jes Sorensen" <[EMAIL PROTECTED]>
> > "Manfred" == Manfred Spraul <[EMAIL PROTECTED]> writes:
>
> Manfred> Mark Hemment wrote:
> >> As no one uses the feature it could well be broken, but is that a
> >> reason to change its meaning?
>
> Manfred> Some hardware drivers use HW_CACHEALIGN
Bill Clark wrote (to the moderated [EMAIL PROTECTED] list):
> Not sure if this is a LVM problem or a ext2fs problem. It is happening
> with the 2.4.2 kernel and the 0.9 release of the LVM user tools.
>
> kernel: Kernel panic: EXT2-fs panic (device lvm(58,0)):
> load_block_bitmap: block_group
Hello:
I was investigating an oops and the trace looked like this:
>>EIP; c01c54a9<=
Trace; c01c3654
Trace; c01c0f0f
Trace; c015e7e2
Trace; c01155a6
Trace; c01272a9
Trace; c0127414
Trace; c0136a2d
Trace; c012722e
Trace; c0127290
Trace; c0127414
Trace; c014cdec
Trace; c0143f80
Harvey,
That is not the case Joanne is pointing out.
The SCSI low-level format glue performed by the HOST gets destroyed
If you write to LBA Zero. ATA only suffers the lose of the partition
table and that can be recovered, but SCSI needs that information to know
where everything else is on the
Details: (dmesg)
Linux version 2.4.2-3mdk ([EMAIL PROTECTED]) (gcc version
egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Tue Feb 27 02:14:17
CET 2001
...
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
VP_IDE:
On Tue, Mar 06, 2001 at 08:10:10PM -0500, Ettore Perazzoli wrote:
> On 06 Mar 2001 17:01:02 -0800, Tim Wright wrote:
[...]
> > The fix for me was to rebuild the kernel and make sure CONFIG_APM_ALLOW_INTS
> > was enabled. So, do you ever use power management and is this similar, or do
> > you have
On Wed, Mar 07 2001, Stephen C. Tweedie wrote:
> On Wed, Mar 07, 2001 at 07:51:52PM +0100, Jens Axboe wrote:
> > On Wed, Mar 07 2001, Stephen C. Tweedie wrote:
> >
> > My bigger concern is when the journalled fs has a log on a different
> > queue.
>
> For most fs'es, that's not an issue. The
John Fremlin wrote:
> Why not set up the device driver to handle PM events itself. See
> Documentation/pm.txt under Driver Interface.
For PCI drivers, you implement the ::suspend and ::remove hooks.
> I have a race free version of pm_send_all if you want it.
Is this the same thing that is in
Hi Tim,
>> Mar 7 11:55:55 debian-f5ibh lpd[567]: lp: filter 'f' terminated
>> (termsig=13)
> Which filter?
Dunno what means 'f', I use magicfilter and the /etc/printcap generated by
magifilterconfig contains :
lp|escp500|Stylus Color 500:\
:lp=/dev/lp0:sd=/var/spool/lpd/escp500:\
On Mon, 5 Mar 2001, Jeff Garzik wrote:
> Is it possible to get addition information, using the vmdump patch?
> http://oss.sgi.com/projects/lkcd/
>
vmdump patch added but system locked up before managing to crash dump. I
have managed to get an OOPS though. :-)
trying a simple:
#
On Wed, Mar 07 2001, Pozsar Balazs wrote:
>
> hi all,
>
> Whatever I tried, I couldn't get my DVDs read. I get:
> sr0: CDROM (ioctl) reports ILLEGAL REQUEST.
> or, I don't use ide-scsi, i get the ATAPI equivalent.
> I have udf support compiled in, i have successfully authenticated the
>
1 - 100 of 428 matches
Mail list logo
