On Mon, 26 Mar 2001 23:16:27 -0600,
Steven Walter <[EMAIL PROTECTED]> wrote:
>This has happened twice, now, though I don't believe its completely
>reproduceable. What happens is an Oops, which drops me into kdb. I've
>been in X both times, however, which makes kdb rather useless.
Documentation
On Mon, Mar 26, 2001 at 07:12:55PM +0200, Manfred Spraul wrote:
> > > That doesn't work, at least the i386 semaphore implementation
> doesn't
> > > support semaphore counts < 0.
> >
> > Does that mean that kernel semaphore can not be used for something
> > else than mutual exclusion ?
> >
> It's
> Linus,
> At present, drivers/video/chipsfb.c can only be used on PPC, and it
> doesn't compile even on PPC. The patch below makes it compile, and
> by changing it to use the generic inb/outb, means that there is at
> least a chance it can be used on other platforms. The patch is
> against 2.
Alan Cox wrote:
>
> > >How do you return an out of memory error to a C program that is out of memory
> > >due to a stack growth fault. There is actually not a language construct for it
> > SIGSEGV.
> > Stack overflow for a language like C using standard implementation techniques
> > is the same a
On 03.27 Thomas Foerster wrote:
>
> But suddenly the box was offline. One technical assistant from our ISP tried
> to reboot
> our server (he couldn't tell me if there had been any messages on the screen),
> but the
> system always hangs on
>
> Freeing unused kernel memory: xxk freed
>
Try b
On Mon, Mar 26, 2001 at 07:10:11PM +0100, Tim Waugh wrote:
> On Sun, Mar 25, 2001 at 09:37:38PM -0800, [EMAIL PROTECTED] wrote:
>
> > do_pd_read_drq: status = 0x10050 = SEEK READY TMO
>
> Please try a recent -ac kernel and let me know if the problem persists
> or goes away.
ac25 appears to have
I spent most of the day today trying to track down why the embedded system I am
working
on would not recognize hdb on boot. It refused to show in the devices list even
though I
specifically told the kernel it existed with the hdb=c,h,s option.
After working on what seemed like a hardware pro
Eric W. Biederman wrote:
> Yes user-mode linux
> could help here (you could stress test the core kernel without worry
> that when it crashes your machine will crash as well).
A similar approach can be used for very detailed tests of specific
subsystems. E.g. that's what we've started doing, kin
Hi,
Can I build the linux kernel 2.4.0 for MIPS(R3000) processor.
I have cross compiler and binutils intstalled on my host m/c (x86).
Will it compile ?
Do I need to do any extra patche for MIPS ?
Does the built image work ?
Any input or suggestion are welcome.
Thanks and regards,
Nazim
-
T
Hi Richard,
in fs/devfs/util.c is
void __init devfs_make_root (const char *name)
which is wrong as pivot_root allows changing the root-device in the runtime.
I think it should be
void __init devfs_make_root (const char *name)
and get called by
fs/super.c:
asmlinkage long
Hello folks,
i have a realy strange and annyoing problem here.
I have a very busy webserver. Around 2 weeks ago i upgraded from 2.2.18 to 2.4.2-ac20
(SCSI-System, 512 MB RAM, 3 SCSI-Disks, P-III-500). Everything worked fine, the 2.4x
Kernel
boosted the box a lot :)
But suddenly the box was off
Amit D Chaudhary wrote:
> To put it in brief, since running sbin/init from /linuxrc as resulting
> in init not having PID 1 and thereby not doing some initialization as
> expected.
Easy solution: don't run linuxrc, run something else instead. E.g.
putting the following into the kernel's command
On 26 Mar 2001, Stuart Lynne wrote:
> In article <[EMAIL PROTECTED]>,
> Amit D Chaudhary <[EMAIL PROTECTED]> wrote:
[snip]
> You can run your linuxrc with:
>
> init=/linuxrc
Yes.
> and then end your /linuxrc with:
>
> exec /sbin/init
No. He's doing a pivot_root to a new root files
2.4.2-ac23 nfsroot on a 386SX/20 with 6Mb RAM
On boot to single user, 'ls' and 'ls -l' work fine.
After mounting /proc, 'ls' still works, but 'ls -l' fails
with SIGILL after reading /etc/timezone (so says strace).
Unmounting /proc fixes the problem. Unmounting /dev doesn't.
I also, just now, h
On Sun, 25 Mar 2001 [EMAIL PROTECTED] wrote:
>
> Now what I wrote is that *I* am strongly in favor of sizeof(dev_t) = 8.
> You think that I want bloat - in reality sizeof(dev_t) = 8 makes life
> simpler.
>
> My system here has for example in super.c:
>
> static dev_t next_unnamed_device = 0x1000
On Mon, 26 Mar 2001, David Konerding wrote:
> It's a bug in Linux 2.4.2, fixed in later versions.
> Regression/quality control testing would have caught this, but the
> developers usually just break things and wait for people to complain
> as their "Regression" testers.
As said before, we're i
This has happened twice, now, though I don't believe its completely
reproduceable. What happens is an Oops, which drops me into kdb. I've
been in X both times, however, which makes kdb rather useless. I
blindly type "go", and interrupts get reenabled, at least (I know
because my mp3 stops loopi
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
Intermediate diffs are available from
http://www.bzimage.org
(Note that the cmsfs port to 2.4 is a work in progress)
2.4.2-ac26
o Fix es1370 build bug(me)
o
> It's a bug in Linux 2.4.2, fixed in later versions. Regression/quality control
> testing would
> have caught this, but the developers usually just break things and wait for people
> to complain
> as their "Regression" testers.
Hardly. We knew it was broken since well before 2.4.0. It just got
On Mon, 26 Mar 2001, Jonathan Morton wrote:
>>These are NOT the only 64 bit systems - Intel, PPC, IBM (in various guises).
>>If you need raw compute power, the Alpha is pretty good (we have over a
>>1000 in a Cray T3..).
>
>Best of all, the PowerPC and the POWER are binary-compatible to a very
>la
Update:
Thanks to some advice and help from Mark Hahn, I downloaded
the DFT utility from IBM that checks and fixes their
drives. A low-level format fixed the problems (the utility
calls it "erase disk". That seems odd to me, since I
thought that IDE drives automatically took care of bad
blocks
In article <[EMAIL PROTECTED]>,
Amit D Chaudhary <[EMAIL PROTECTED]> wrote:
>Hi,
>
>We(my team) had some questions regarding booting from initrd and using
>/linuxrc. It will help someone(David, Werner,...) can give their
>thoughts on this.
>
>To put it in brief, since running sbin/init from /lin
Good day, all,
On Mon, 26 Mar 2001, Jason Madden wrote:
> On Mon, 26 Mar 2001, David E. Weekly wrote:
>
> > On Linux 2.4.2, running a "mount -o loop" on a file properly created with
> > "dd if=/dev/zero of=/path/to/my/file.img count=1024" seems to decide to
> > freeze up my shell (not my system)
It's a bug in Linux 2.4.2, fixed in later versions. Regression/quality control
testing would
have caught this, but the developers usually just break things and wait for people
to complain
as their "Regression" testers.
Jason Madden wrote:
> On Mon, 26 Mar 2001, David E. Weekly wrote:
>
> > On L
Jason Madden wrote:
>
> On Mon, 26 Mar 2001, David E. Weekly wrote:
>
> > On Linux 2.4.2, running a "mount -o loop" on a file properly created with
> > "dd if=/dev/zero of=/path/to/my/file.img count=1024" seems to decide to
> > freeze up my shell (not my system). An strace showed the lockup happ
On Mon, 26 Mar 2001, David E. Weekly wrote:
> On Linux 2.4.2, running a "mount -o loop" on a file properly created with
> "dd if=/dev/zero of=/path/to/my/file.img count=1024" seems to decide to
> freeze up my shell (not my system). An strace showed the lockup happening at
> the actual system "mou
On Mon, 26 Mar 2001, Chris Mason wrote:
> On Monday, March 26, 2001 03:21:29 PM -0800 Christoph Lameter
> > On Mon, 26 Mar 2001, Chris Mason wrote:
> >> On Saturday, March 24, 2001 11:56:08 AM -0800 Christoph Lameter
> >> <[EMAIL PROTECTED]> wrote:
> >> > I got a directory /a/yy that I tried to er
I believe this has more to do with how the author of cdrecord chose to
implement it rather than the kernel. Why don't you speak to him?
-b
Andreas Franck wrote:
> Hello people,
>
> after having "upgraded" (?) my distro from my wonderfully hand-configured
> Debian system (which I unfortunate
Hi,
We(my team) had some questions regarding booting from initrd and using
/linuxrc. It will help someone(David, Werner,...) can give their
thoughts on this.
To put it in brief, since running sbin/init from /linuxrc as resulting
in init not having PID 1 and thereby not doing some initializati
This ooops happened while trying to nfsboot a 386, and restarting nfsd
halfway through the boot process. I bet it's not a common problem...
Server is 2.4.2-ac23, client (the Oopser) is 2.4.2-ac24.
The oops is partial because I had to hand-copy from the console, and
it blanked after a few minutes
Thus spoke Frank Jacobberger:
> Trying to do insmod 8139too.o from the :
> /lib/modules/2.4.3-pre8/kernel/drivers/net directory show these
> unresolved symbols:
>
> 8139too.o: unresolved symbol alloc_etherdev
> 8139too.o: unresolved symbol unregister_netdev
> 8139too.o: unresolved symbol registe
It just adds net_init.o to the definition of export-objs.
--- linux-2.4.3-pre8/drivers/net/Makefile.symbols Tue Mar 27 00:30:58 2001
+++ linux-2.4.3-pre8/drivers/net/Makefile Tue Mar 27 03:00:21 2001
@@ -16,7 +16,7 @@
# This list comes from 'grep -l EXPORT_SYMBOL *.[hc]'.
export-o
Explanation:
The bufp pointer should be indexed rather than incremented because it is used
a few lines above as a base pointer to free successfully allocated items if
kmalloc fails.
Begin Patch
--- fs/iobuf.c.orig Wed Mar 21 10:12:36 2001
+++ fs/iobuf.c Wed Mar 21 10:12:3
On Linux 2.4.2, running a "mount -o loop" on a file properly created with
"dd if=/dev/zero of=/path/to/my/file.img count=1024" seems to decide to
freeze up my shell (not my system). An strace showed the lockup happening at
the actual system "mount()" call, which never returns.
Since mount() is in
Bob_Tracy writes:
> So let's quit covering for 'em. Let's have the name(s) behind that
> idiotic policy letter, because I would not knowingly allow any company
> I work for to hire such people.
>
> ProblemRemedy
> -----
> hangnail amputate
>
Juha Saarinen wrote:
> This is a variant on the Nigerian Scam... avoid at all cost.
This is very funny.
-
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
"Zephaniah E. Hull" wrote:
>
> [-ac24 crash]
Guys, this is related to the tty hangup code calling the
console code in interrupt context. Fixed in -ac25. The
IDE connection is just stack fluff.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Mon, Mar 26, 2001 at 06:07:56PM -0500, Adam Schrotenboer wrote:
> > alpha? mips?
>
> Yes, I just didn't feel like listing all arch's. Plus, (ducks) the MIPS
> is no longer supported by Windoze, and I rarely see any discussion on lk
> about this arch, and I forgot about Alpha for a minute.
Alan;
I got the attached compile error in /drivers/sound/es1370.c.
If any further information might be helpful please e-mail me or
post to LKML.
Art Wagner
[EMAIL PROTECTED]
make[2]: Leaving directory `/usr/src/linux-2.4.2-ac/drivers/scsi'
make[2]: Entering directory `/usr/src/linux-2.4.2-ac/dr
On Mon, 26 Mar 2001, Chris Mason wrote:
> On Saturday, March 24, 2001 11:56:08 AM -0800 Christoph Lameter
> <[EMAIL PROTECTED]> wrote:
>
> > I got a directory /a/yy that I tried to erase with rm -rf /a/yy.
> >
> > rm hangs...
> >
> > ls gives the following output:
> >
> > ls: /a/yy/cache3A0F9
On Mon, Mar 26, 2001 at 01:18:06PM -0800, John Byrne wrote:
> Do you have any interest in doing away with the concept of major and
> minor numbers altogether; turning the dev_t into an opaque unique id?
>
> At the application level, the kinds of information that is derived from
> the major/minor
Mark Hahn wrote:
>> Are there any architectures that are simple (sane) to implement sftw on?
>
>
> sftw? software? yes: portable C/C++ is a fine platform.
Not really the platform, but the architecture, from a C/C++ compiler and
kernel/asm/lowlevel lang development standpoint
>
>> The i38
Hello people,
after having "upgraded" (?) my distro from my wonderfully hand-configured
Debian system (which I unfortunately wrecked up lately) to S*SE 7.1, I'm now
really displeasured about the IDE-SCSI emulation thing for my ATAPI CD
roaster. Not that I was not able to set it up correctly, b
>
> Ok, now its clear that I have a big troubles with hardware.
> I compiled kernel 2.2.18+IDE_patches with support for VIA chipset and still get
> errors of type:
>
> kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> kernel: hda: dma_intr: error=0x84 { DriveStatusError BadC
Release 0.9.7: Mon Mar 26 16:55:48 EST 2001
* Can now configure everything except the CONFIG_-less CRIS symbols.
* Prefix-stripping for backward compatibility with, e.g. CONFIG_3C515.
* Resolve all FIXMES, including Andre Hedrick's IDE vendor stuff.
CML2 can now configure
> Another question is that by inspecting the NULL checker's result, I
> found that *_do_scsi is always used in the following way "SRpnt =
> *_do_scsi(SRPnt, ...)" no matther SRPnt is NULL or not. If SRpnt is not
> NULL, why don't just use
> *_do_scsi(SRPnt, ...);
> The same thing happens to
On Mon, 26 Mar 2001 08:48:09 -0800,
David Hinds <[EMAIL PROTECTED]> wrote:
>On Mon, Mar 26, 2001 at 05:14:13PM +1000, Keith Owens wrote:
>What are the things you're planning that will cause trouble?
Support for building third party drivers and patch sets as separate
source trees. Base kernel in
On Mon, 26 Mar 2001, John Byrne wrote:
> > Re: Larger dev_t
> >
> On Sat Mar 24 2001 Linus Torvalds ([EMAIL PROTECTED]) wrote:
> > There is no way in HELL I will ever accept a 64-bit dev_t.
> >
> > I _will_ accept a 32-bit dev_t, with 12 bits for major numbers, and 20
> > bits for minor numbers
Philip Blundell <[EMAIL PROTECTED]>:
> >if [ "$CONFIG_PRINTER" != "n" ]; then
> >- bool 'Support IEEE1284 status readback' CONFIG_PRINTER_READBACK
> >+ bool 'Support IEEE1284 status readback' CONFIG_PARPORT_1284
> >fi
>
> This isn't really right. Although it's true that
> Are you using Becker's ftp://www.scyld.com/pub/diag/ether-wake.c ?
Yes.
> Did you turn on the enable_wol module option? Note that might be a new
> option in the 2.4.3-preXX series...
Well, it is indeed a 2.4.3-pre feature, as I had looked for it on 2.4.2, it
was not there, but it is at least
Manfred Spraul wrote:
> Which field do you access? bh->b_blocknr instead of bh->r_sector?
---
Yes.
>
> There were plans to split the buffer_head into 2 structures: buffer
> cache data and the block io data.
> b_blocknr is buffer cache only, no driver should access them.
---
My 'de
>> Understood - my Physics courses covered this as well, but not using the
>> word "normalise".
>
>Be that as it may, Martin's comments about normalizing are nonsense.
>Rik's killer (at least in 2.4.3-pre7) produces a badness value that's
>a product of badness factors of various units. It then us
>if [ "$CONFIG_PRINTER" != "n" ]; then
>- bool 'Support IEEE1284 status readback' CONFIG_PRINTER_READBACK
>+ bool 'Support IEEE1284 status readback' CONFIG_PARPORT_1284
>fi
This isn't really right. Although it's true that CONFIG_PARPORT_1284 enables
the stuff that used
>These are NOT the only 64 bit systems - Intel, PPC, IBM (in various guises).
>If you need raw compute power, the Alpha is pretty good (we have over a
>1000 in a Cray T3..).
Best of all, the PowerPC and the POWER are binary-compatible to a very
large degree - just the latter has an extra set of 6
Hi,
I have a question about *_do_scsi(Scsi_Request *SRpnt, ...). If *SRpnt
is not NULL, *_do_scsi will not return NULL. I'm not quite sure about the
precondition in the following three 'errors' flaged by the NULL checker.
In these cases, can
*_do_scsi return NULL?
Another question is that
From: "LA Walsh" <[EMAIL PROTECTED]>
> Manfred Spraul wrote:
> >
> > >4k page size * 2GB = 8TB.
> >
> > Try it.
> > If your drive (array) is larger than 512byte*4G (4TB) linux will eat
> > your data.
> ---
> I have a block device that doesn't use 'sectors'. It
> only uses the logical block size (
Jonathan Morton <[EMAIL PROTECTED]> writes:
>
> Understood - my Physics courses covered this as well, but not using the
> word "normalise".
Be that as it may, Martin's comments about normalizing are nonsense.
Rik's killer (at least in 2.4.3-pre7) produces a badness value that's
a product of badne
Martin Dalecki <[EMAIL PROTECTED]>:
> "Eric W. Biederman" wrote:
> >
> > Matthew Wilcox <[EMAIL PROTECTED]> writes:
> >
> > > On Mon, Mar 26, 2001 at 10:47:13AM -0700, Andreas Dilger wrote:
> > > > What do you mean by problems 5 years down the road? The real issue is that
> > > > this 32-bit bl
> Re: Larger dev_t
>
On Sat Mar 24 2001 Linus Torvalds ([EMAIL PROTECTED]) wrote:
> There is no way in HELL I will ever accept a 64-bit dev_t.
>
> I _will_ accept a 32-bit dev_t, with 12 bits for major numbers, and 20
> bits for minor numbers.
>
Do you have any interest in doing away with the
On Mon, 26 Mar 2001, Theodoor Scholte wrote:
> There are no relevant messsages in that file.
Strange, but I bet that you can compile again, right? (Just remove the
broken compile.h that the dd command created) Must have been an NFS
fluke, and without any more precise error messages, there is n
John Cowan <[EMAIL PROTECTED]>:
> > If CML2 is adopted and I become the config system maimtainer,
>^
> Typo-ROTFL!
Of such errors are linguistic innovations made. I wonder if this one
will propagate enough that I have to put it in the Jargo
Eric S. Raymond wrote:
> If CML2 is adopted and I become the config system maimtainer,
^
Typo-ROTFL!
--
There is / one art || John Cowan <[EMAIL PROTECTED]>
no more / no less || http://www.reutershealth.com
to do /
Please CC back to me, as I am not subscribed to the list (but I soon
will be!)
I am writing a new framebuffer driver for a PCI based Chips and
Technologies 69000 HiQVideo chipset in the 2.4.2 code base on an i386
machine. (They are custom cards, but they use the standard BIOS and
setup provided
On Mon, 26 Mar 2001, Andreas Dilger wrote:
> Matthew Wilcox writes:
> > people who can afford 2TB of disc can afford to buy a 64-bit processor.
> This whole "64-bit" fallacy has got to stop.
Indeed.
> Now it is "anybody who needs > 2TB disk should use a 64-bit CPU", soon
> to be wrong.
It was a
Hello,
The attached program attempts to show what happens when a
server tries to talk to a forked child on a UP machine.
The response time using a UNIX socket is awful.
When the machine uses software compiled for a SMP machine, the
data-rate is about 13 bytes / microsecond. This is not too
bad,
On 26 Mar 2001, James Antill wrote:
> If you want overcommit great, and I think it's a valid default
> ... but it'd be nice if I could say I don't want it for apps that
> aren't written using glib etc.
Agreed. Jonathan Morton seems to be making progress in testing
and debugging the non-overcom
> "Matthew" == Matthew Wilcox <[EMAIL PROTECTED]> writes:
Matthew> On Mon, Mar 26, 2001 at 10:47:13AM -0700, Andreas Dilger
Matthew> wrote:
>> What do you mean by problems 5 years down the road? The real issue
>> is that this 32-bit block count limit affects composite devices
>> like MD RAID
Jeff Garzik <[EMAIL PROTECTED]>:
> Wow, your script was longer than your patch :)
But independent of the version/patchlevel, which was the point of shipping it.
If CML2 is adopted and I become the config system maimtainer,
symbolreplace is one of a number of small tools I'll drop into the script
Wow, your script was longer than your patch :)
Patch looks ok to me...
--
Jeff Garzik | May you have warm words on a cold evening,
Building 1024 | a full moon on a dark night,
MandrakeSoft | and a smooth road all the way to your door.
-
To unsubscribe from this list: send the lin
"Eric W. Biederman" wrote:
>
> Matthew Wilcox <[EMAIL PROTECTED]> writes:
>
> > On Mon, Mar 26, 2001 at 10:47:13AM -0700, Andreas Dilger wrote:
> > > What do you mean by problems 5 years down the road? The real issue is that
> > > this 32-bit block count limit affects composite devices like MD
Manfred Spraul wrote:
>
> >4k page size * 2GB = 8TB.
>
> Try it.
> If your drive (array) is larger than 512byte*4G (4TB) linux will eat
> your data.
---
I have a block device that doesn't use 'sectors'. It
only uses the logical block size (which is currently set for
1K). Seems I could
Tom Rini wrote:
> On Mon, Mar 26, 2001 at 09:50:53AM -0500, Jeff Garzik wrote:
> > PPC guys: this is a gratuitous renaming change that is not required.
> > If you have been following the "CML1 cleanup patch" thread, you see that
> > Eric is blindly dictating policy when he says that CONFIG_[0-9]
Hi,
linux 2.4.2 can be killed with multiple 'mount --bind ' -s.
The problem is reproduceable (at least on my system),
and works with User Mode Linux, too. Example script follows:
#!/bin/sh
OUTER=100
INNER=30
for j in `seq $OUTER`
do
for i in `seq $INNER`
do
echo "$j:$i"
On Mon, 26 Mar 2001, Matthew Wilcox wrote:
> people who can afford 2TB of disc can afford to buy a 64-bit processor.
You realise that this'll double the price of storage? ;)
(at least, in a year or two)
Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly noth
Eric Raymond writes:
> Bjorn Wesen <[EMAIL PROTECTED]> informs me that the CRIS symbol bugs
> will be fixed in the next CRIS port update.
Hey, there's even a spec which says that config symbols have to look
like CONFIG_*:
# Documentation/kbuild/config-language.txt
A /symbol/ is a single unqu
Hello all,
I am trying to use the LAPIC timer to generate interrupt for some kernel
profiling work I am doing...but the timer ISR isnt invoking atallhere is
what I have done
1)Initialized a interrupt gate modifying the trap_init function in traps.c
to use vector 0x32
set_intr_g
- Received message begins Here -
>
> On Mon, Mar 26, 2001 at 08:39:21AM -0800, LA Walsh wrote:
> > I vaguely remember a discussion about this a few months back.
> > If I remember, the reasoning was it would unnecessarily slow
> > down smaller systems that would never have block
Progress is being made. I submitted a cleanup patch in order to get rid
of three headaches before the 2.5 fork. Three good things have since
happened since:
(1) Bjorn Wesen <[EMAIL PROTECTED]> informs me that the CRIS symbol bugs
will be fixed in the next CRIS port update. This will get ri
On Mon, Mar 26, 2001 at 10:35:33AM -0800, Grover, Andrew wrote:
> > > > As i recompiled 2.4.2-ac20 with ACPI support
> > > > the system cannot switch itself off.
> > > > I get a message "Couldn't switch to S5" if
> > > > At load it shows that the mode is supported.
> > >
> > > Same with AMR P6BAP
What company was it that you worked for? I'm sure we could convince
them otherwise . . . .
-b
Gregory Maxwell wrote:
> On Mon, Mar 26, 2001 at 10:07:22AM -0500, Richard B. Johnson wrote:
> [snip]
>
>> I have just received notice that my machines will no longer be
>> provided access to "The
On Mon, Mar 26, 2001 at 10:31:17AM -0800, Andre Hedrick wrote:
> On Mon, 26 Mar 2001, Zephaniah E. Hull wrote:
>
> > On Mon, Mar 26, 2001 at 09:46:54AM -0800, Andre Hedrick wrote:
> > >
> > > Zephaniah,
> > >
> > > Does this happen in a non-ac kernel?
> > > I have not updated code since around
>And you always get exactly this message? What happens if you run
> cat /usr/src/linux/include/linux/compile.h
This is the output of cat /usr/src/linux/include/linux/compile.h :
#define UTS_VERSION "#1 SMP Sun Mar 25 21:51:51 CEST 2001"
#define LINUX_COMPILE_TIME "21:51:51"
#define LINUX_CO
At 10:24 AM 3/26/01 -0500, you wrote:
>It's sad that people like the one who sent out messages like that can stay
>employed. In the last year there have been several Windows love-bug type
>worms each causing damaged estimated in the billions. One or two Linux worms
>that go after a long fixed prob
Matthew Wilcox <[EMAIL PROTECTED]> writes:
> On Mon, Mar 26, 2001 at 10:47:13AM -0700, Andreas Dilger wrote:
> > What do you mean by problems 5 years down the road? The real issue is that
> > this 32-bit block count limit affects composite devices like MD RAID and
> > LVM today, not just individ
> From: Ingo Oeser [mailto:[EMAIL PROTECTED]]
> > > As i recompiled 2.4.2-ac20 with ACPI support
> > > the system cannot switch itself off.
> > > I get a message "Couldn't switch to S5" if
> > > try to call reboot(2).
> > > At load it shows that the mode is supported.
> >
> > Same with AMR P6BAP-
I was sent this after my IDE got trashed using 2.4.2
?> PS for people using a hard disk with a LART: Upgrade to
>> linux-2.4.2-rmk1-np2 as soon as possible. Earlier kernels had a nasty
>> IDE bug that could destroy your filesystem. That happened to me...
>dude, maybe this is what fscked up y
On Mon, 26 Mar 2001, Zephaniah E. Hull wrote:
> On Mon, Mar 26, 2001 at 09:46:54AM -0800, Andre Hedrick wrote:
> >
> > Zephaniah,
> >
> > Does this happen in a non-ac kernel?
> > I have not updated code since around 2.4.0, but other have.
> > You point ot a few times w/ ac18, but is there one b
On Mon, Mar 26, 2001 at 09:46:54AM -0800, Andre Hedrick wrote:
>
> Zephaniah,
>
> Does this happen in a non-ac kernel?
> I have not updated code since around 2.4.0, but other have.
> You point ot a few times w/ ac18, but is there one before that which does
> not cause this to happen?
>
> The qu
I got an error message on bootup and shutdown of 2.4.2-ac25 just after
loading and unloading the cs46xx module. The error was not logged
to /var/log/messages, but I copied it from the screen.
On boot:
Loading sound module (cs46xx)
Loading mixer settings:
error: Malformed setting 'kernel.printk=
The following patch enables the toshiba module to compile correctly on
2.2.19.
thanks,
greg k-h
--
greg@(kroah|wirex).com
http://immunix.org/~greg
diff -Naur -X /home/greg/linux/dontdiff linux-2.2.19/drivers/char/toshiba.c
linux-2.2.19-greg/drivers/char/toshiba.c
--- linux-2.2.19/drivers/c
On Mon, Mar 26, 2001 at 08:01:21PM +0200, Manfred Spraul wrote:
> drivers/block/ll_rw_blk.c, in submit_bh()
> >bh->b_rsector = bh->b_blocknr * (bh->b_size >> 9);
>
> But it shouldn't cause data corruptions:
> It was discussed a few months ago, and iirc LVM refuses to create too
> large volume
At 10.51 26/03/01 -0700, Justin T. Gibbs wrote:
> >Hi all,
> >
> >Does anyone know how to configure this controller (chipset AAA-133U2
> >aka AIC-78xx) with one RAID5 hardware volume ? The kernel 2.2.16 see
> >all the disks (4x18Gb) but don't see the unique volume.
>
>These boards are not current
On Sun, Mar 25, 2001 at 09:37:38PM -0800, [EMAIL PROTECTED] wrote:
> do_pd_read_drq: status = 0x10050 = SEEK READY TMO
Please try a recent -ac kernel and let me know if the problem persists
or goes away.
Tim.
*/
PGP signature
On Mon, Mar 26, 2001 at 10:47:13AM -0700, Andreas Dilger wrote:
> What do you mean by problems 5 years down the road? The real issue is that
> this 32-bit block count limit affects composite devices like MD RAID and
> LVM today, not just individual disks. There have been several postings
> I hav
>> I vaguely remember a discussion about this a few months back.
>> If I remember, the reasoning was it would unnecessarily slow
>> down smaller systems that would never have block devices in
>> the 4-28T range attached.
>
>4k page size * 2GB = 8TB.
Try it.
If your drive (array) is larger than 51
On Thursday, March 22, 2001 01:42:15 PM -0500 Jan Harkes
<[EMAIL PROTECTED]> wrote:
>
> I found some code that seems wrong and didn't even match it's comment.
> Patch is against 2.4.2, but should go cleanly against 2.4.3-pre6 as well.
>
Ok, this looks correct, makes reiserfs faster, and surv
LA Walsh <[EMAIL PROTECTED]> writes:
> I vaguely remember a discussion about this a few months back.
> If I remember, the reasoning was it would unnecessarily slow
> down smaller systems that would never have block devices in
> the 4-28T range attached.
With classic 512 byte sectors the top si
On Sun, 25 Mar 2001, LA Walsh wrote:
> Here is the 'alternate' output when the ncr53c8xx driver is
> compiled in:
>
> SCSI subsystem driver Revision: 1.00
> scsi-ncr53c7,8xx : at PCI bus 0, device 8, function 0
> scsi-ncr53c7,8xx : warning : revision of 35 is greater than 2.
> scsi-ncr53c7,8xx
Rik van Riel <[EMAIL PROTECTED]>:
> What's wrong with using the _file type_ for these things ?
I don't understand that.
> Conversely, why can't CML2 use the CONFIG_ prefix to
> determine if a symbol is a configuration option, like
> we're doing now?
I do understand this. Greg Banks pointed it
>Hi all,
>
>Does anyone know how to configure this controller (chipset AAA-133U2
>aka AIC-78xx) with one RAID5 hardware volume ? The kernel 2.2.16 see
>all the disks (4x18Gb) but don't see the unique volume.
These boards are not currently supported in RAID mode. Your
best bet is Linux MD.
--
Ju
1 - 100 of 192 matches
Mail list logo
