On Fri, 24 Nov 2000, Alexander Viro wrote:
> I don't see any attempts to tag you (or ATA subsystem, for that matter)
> in that thread. And thread is hardly bogus... I agree that changes in
We agree that the "thread" is valid, trust that point.
There was a quick pointed question that present, "I
I was busy with other things and did not track 2.2.18pre kernels very
carefuly, but now I tried 2.2.18pre23 on Alpha and got an impression
that a situation with a virtual memory handling is worse than it was,
say, in 2.2.18pre15. I can now see in /var/log/messages entries like
"VM: killing proces
On Thu, Nov 23, 2000 at 06:06:31PM -0500, Jeff Garzik wrote:
> Michael Elkins wrote:
> >
> > On Thu, Nov 23, 2000 at 05:49:52PM +0100, Georg Acher wrote:
> > It hangs in start_uhci():
> >
> > /* disable legacy emulation */
> > pci_write_config_word (dev, USBLEGSUP
On Thu, 23 Nov 2000, Andre Hedrick wrote:
[I wrote]
> > ?
> > If you have a l-k feed from future - please share. I'm not saying that
>
> Date: Thu, 23 Nov 2000 04:37:21 -0500 (EST)
>
> > fs/* is not the source of that stuff, but I sure as hell had not said
> > that it is. I simply don't know
On Fri, 24 Nov 2000, Neil Brown wrote:
> Ditto for gcc-2.95.2-13 from Debian (potato). It exhibits the same
> bug.
> Debian applies a total of 49 patches to gcc and the libraries.
>
> I am tempted to write a little script which discards the patches one
> by one and re-builds and re-tests each
> > usb-uhci.c: interrupt, status 3, frame# 212
> > hub.c: already running port 2 disabled by hub (EMI?), re-enabling...
[Greg KH]
> The messages are harmless debug messages. Anyone want to whip up a
> patch to turn them off (like was recently done for 2.4.0-test)?
Is this what you mean?
Pete
On Fri, 24 Nov 2000, Alexander Viro wrote:
>
>
> On Thu, 23 Nov 2000, Andre Hedrick wrote:
>
> > What the F*** does that have to do with the price of eggs in china, heh?
> > Just maybe if you could follow a thread, you would see that that Alex Viro
> > has pointed out that changes in the FS la
2.2.18pre23 allows lseek to negative offsets in ext2 and has no checks
for proc. Here is a patch.
BTW, ext2 2.4-test10 is ok.
--
H.J. Lu ([EMAIL PROTECTED])
---
--- linux/fs/ext2/file.c.lseek Sat Nov 18 17:18:49 2000
+++ linux/fs/ext2/file.cThu Nov 23 21:54:58 2000
@@ -120,6 +120,8 @@
On Thu, 23 Nov 2000, Andre Hedrick wrote:
> What the F*** does that have to do with the price of eggs in china, heh?
> Just maybe if you could follow a thread, you would see that that Alex Viro
> has pointed out that changes in the FS layer as dorked things.
?
If you have a l-k feed from futur
[Chris Wedgwood]
> taking away -O2 is a 'fix' for now... not a very good one though.
Not if you want function inlining to work. The kernel *won't compile*
without optimization.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PR
On Thu, 23 Nov 2000, Ion Badulescu wrote:
> > Yesterday I had a diff -r showing that the old version
> > was corrupted and the new was OK. Of course a second
> > look showed that the old version also was OK, the corruption
> > must have been in the buffer cache, not on disk.)
>
> Are these disks
On Fri, 24 Nov 2000, Mohammad A. Haque wrote:
> I got the error while I was compiling XFree86 4 CVS and kernel. So
> that's what I've been doing in multiples along witha couple otehr things
> thrown inthe mix to generate lots of disk i/o.
Error messages would be interesting... So far we have _
On Friday November 24, [EMAIL PROTECTED] wrote:
> >> ... RedHat's GCC snapshot "2.96" handles this case just fine.
>
> > Now, if you can isolate the relevant part of the diff between
> > 2.95.2 and RH 2.96...
>
> Maybe I have to be more precise in the statement "gcc 2.95.2 is buggy".
>
> I just
I got the error while I was compiling XFree86 4 CVS and kernel. So
that's what I've been doing in multiples along witha couple otehr things
thrown inthe mix to generate lots of disk i/o.
Nothing yet, but I'm pretty sure my machine hates me for putting it
through this.
Alexander Viro wrote:
> Blo
Yep. Unless of course they are SCSI with an identity crisis =P
Ion Badulescu wrote:
>
> Are these disks IDE disks by any chance?
>
> Ion
>
--
=
Mohammad A. Haque http://www.haque.net/
On Fri, 24 Nov 2000, Neil Brown wrote:
> I ran my test script, which builds a variety of raid5 arrays with
> varying numbers of drives and chunk sizes, and runs mkfs/bonnie/dbench
> on each array, and it got through about 8 file systems but choked on
> the 9th by trying to allocate lots of bloc
On Thu, Nov 23, 2000 at 08:58:39PM -0800, Ion Badulescu wrote:
> > (I am reorganizing my disks, copying large trees from
> > one place to the other. Always doing a diff -r between
> > old and new before removing the old version.
> > Yesterday I had a diff -r showing that the old version
> > was c
>> ... RedHat's GCC snapshot "2.96" handles this case just fine.
> Now, if you can isolate the relevant part of the diff between
> 2.95.2 and RH 2.96...
Maybe I have to be more precise in the statement "gcc 2.95.2 is buggy".
I just installed gcc 2.95.2 freshly ftp'ed from ftp.gnu.org, and
% /u
According to Neil Brown:
> You suggest that d_move (or it's caller) must be able to deal with
> the [second parameter] being an "root" dentry (x->d_parent == x).
> However, I cannot see that this could possibly happen.
Hmph. It seems you're right; my d_move changes [1][2] were apparently
not
On Thu, 23 Nov 2000 13:52:52 +0100, Guest section DW <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 23, 2000 at 05:03:00PM +1100, Neil Brown wrote:
>
>> Oh, good. It's not just me and Tigran then.
>
> You have it all backwards. It would be good if it were
> just you and Tigran. Unfortunately it also
On Thu, 23 Nov 2000, Gregory Maxwell wrote:
> On Fri, Nov 24, 2000 at 02:57:45AM +0100, [EMAIL PROTECTED] wrote:
> > but in the meantime there is good confirmation.
> > This really is a bug in gcc 2.95.2.
>
> ... RedHat's GCC snapshot "2.96" handles this case just fine.
Now, if you can isola
[Adam J. Richter]
> +#define PCI_VENDOR_ID_ELSA 0x1048
> +#define PCI_DEVICE_ID_ELSA_MIRCOLINK 0x1000
> +#define PCI_DEVICE_ID_ELSA_QS30000x3000
Oh, don't propagate the typo. Spell it MICROLINK here and in
hisax/elsa.c.
> #define PCI_VENDOR_ID_PLX0x10b5
> +#define PC
On Fri, Nov 24, 2000 at 02:57:45AM +0100, [EMAIL PROTECTED] wrote:
> but in the meantime there is good confirmation.
> This really is a bug in gcc 2.95.2.
... RedHat's GCC snapshot "2.96" handles this case just fine.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
th
Sorry for the rather lengthy email list. I am not sure exactly
which of you it would be appropriate to put this question to.
I am writing a pci_device_id table for ohci1394.c. This will
allow a userland program to automatically load the module when an
ohci1394 card is present.
I have using the next software:
a) test11 + storage checkout from linux-usb at sourceforge ( without
this checkout fails too).
b) cdrecord 1.10a6
If I start to burn a CD at x4 speed, I have always the next error from
cdrecord:
Track 01: 102 of 109 MB written (fifo 100%)./opt/schily/bin/cdre
For those of you who may want to run ReiserFS
on 2.2.18pre23 using reiserfs-3.5.27,
you may find as I did that the main reiserfs patch,
linux-2.2.17-reiserfs-3.5.27-patch, fails like this:
patching file linux/include/linux/fs.h
Hunk #1 FAILED at 279.
Hunk #2 FAILED at 393.
Hunk #3 FAILED at 516.
[Brian Kress]
> 1) Add a function pointer to struct gendisk called hd_name.
>
> 2) Make disk_name in fs/partitions/check.c use that function
> pointer if its non-null.
>
> 3) Change the following drivers to use this method. (adding the
> driver specific method and removing the old co
On Tue, Nov 07, 2000 at 10:57:49PM -0800, Richard Henderson wrote:
> On Tue, Nov 07, 2000 at 10:09:34AM -0800, Reto Baettig wrote:
> > I have a problem whith Alpha SMP's which seems to be kernel-related. I
> > discussed this on the bug-glibc list but everybody seems to agree that
> > it cannot be
[Jeff Garzik]
> If you mean preferring 'if ()' over 'ifdef'... Linus. :) And I agree
> with him: code looks -much- more clean without ifdefs. And the
> compiler should be smart enough to completely eliminate code inside
> an 'if (0)' code block.
Plus the advantage/disadvantage of making the co
In writing a pci_device_id table for
linux-2.4.0-test11/drivers/video/imsttfb.c, I see that that driver
theoretically attepts to bind to any PCI video display with
a vendor ID set to PCI_VENDOR_ID_IMS, although the code does
mention device ID's 0x9128 and 0x9135. Does anybody know if
the
On Thursday November 23, [EMAIL PROTECTED] wrote:
>
>
> On Thu, 23 Nov 2000, Alexander Viro wrote:
>
> > On Thu, 23 Nov 2000, Neil Brown wrote:
> >
> > > which enabled ext2_notify_change, however ext2_notify_change has a
> > > bug.
> > > It sets attributes from iattr->ia_attr_flags even
> > >
On Tuesday November 21, [EMAIL PROTECTED] wrote:
> This may be 2.2.18 material after all I wrote last night:
> > Making nfsd's d_splice() compensate for d_move's limitations is not
> > only a kludge, but also it harder to keep nfsd correct.
> > someday, nfsd may not be the only creator of thi
The following patch adds some missing PCI_VENDOR_ID's and
PCI_DEVICE_ID's that are scattered throughout a bunch of .c files in
drivers/isdn/hisax/. The definitions in the .c files are protected
by '#ifndef PCI_VENDOR_ID_...', so it is not necessary to remove
those declarations from the .c
Yesterday night I wrote
> Note: this is not yet a confirmed compiler bug
but in the meantime there is good confirmation.
This really is a bug in gcc 2.95.2.
>From [EMAIL PROTECTED] Thu Nov 23 10:45:07 2000
> Please, could you send me ...
>From [EMAIL PROTECTED] Thu Nov 23 18:00:48 2000
> Can w
On Thu, Nov 23, 2000 at 11:23:33PM +0100, Pavel Machek wrote:
> Hi!
>
> You see? Kernel_thread does not check is sys_clone() worked! Aha,
"=&a" (retval)
> caller is responsible for that, but init/main.c does not seem too
> carefull. Maybe kernel_thread should at least print a warning?
If clone
Linus Torvalds wrote:
>
> On Thu, 23 Nov 2000, Tobias Ringstrom wrote:
> > >
> > > - enable DEBUG in arch/i386/kernel/pci-i386.h. This should make the code
> > >print out what the pirq table entries are etc.
> >
> > Done. When adding the call to eisa_set_level_irq, the line
> >
> > IRQ for 0
On Thu, 23 Nov 2000, Jeff Garzik wrote:
> >
> > It hangs in start_uhci():
> >
> > /* disable legacy emulation */
> > pci_write_config_word (dev, USBLEGSUP, USBLEGSUP_DEFAULT);
Try changing the thing around a bit: make the above place say
/* disable leg
Bartlomiej Zolnierkiewicz wrote:
> You may also consider processing firestream.[ch] through indent because
> spacing is inconsistent - sometimes tabs, sometimes 8*space (it would
> be nice too have tabs everywhere).
As far as I know the tabs/spaces are exactly the way I want them.
There are tab
Bernd Eckenfels wrote:
>
> In article <[EMAIL PROTECTED]> you wrote:
> > This is mostly a heads-up to say that in this regard gcc is not ready
> > for prime time, so we really can't get away with using if() as an ifdef
> > yet, at least not without penalty.
>
> Humm.. whats the Advantage of this
Ben Fennema wrote:
> Rogier Wolff wrote:
> >
> > Alan Cox wrote:
> > > > under 1 gig in size. You can exhibit the problem by mounting the dvd movie
> > > > "The World is Not Enough" as it contains a video_ts.vob which is larger than
> > > > 1 gigabyte. You will see that most of the file lengths
In article <[EMAIL PROTECTED]> you wrote:
> This is mostly a heads-up to say that in this regard gcc is not ready
> for prime time, so we really can't get away with using if() as an ifdef
> yet, at least not without penalty.
Humm.. whats the Advantage of this?
Greetings
Bernd
-
To unsubscribe fr
Hello all,
I played around with the 'new' masquerading/network stuff for the first time.
xDSL is coming to me in some days...:-)
I get the following unresolved symbols with pure 2.4.0-test11.
Am I missing something?
depmod: *** Unresolved symbols in
/lib/modules/2.4.0-test11/kernel/net/ipv4/n
> "Tobias" == Tobias Ringstrom <[EMAIL PROTECTED]> writes:
Tobias> Btw, does anyone know of a C function that works like strncpy, but does
Tobias> add a terminating null character, event if the string does not fit, ro
Tobias> does one have to do str[5]=0 first, and then strncpy(st
Pavel Machek wrote:
>
> Hi!
>
> > > I also agree that the ioctl patch is kind of a bandaid over
> > > the problems that you described, and, while Zach Brown can speak
> >
> > The biggest problem is that the current code is gross gross gross.
> > I've been avoiding dealing with it too much in
Michael Elkins wrote:
>
> On Thu, Nov 23, 2000 at 05:49:52PM +0100, Georg Acher wrote:
> > On Thu, Nov 23, 2000 at 04:35:33PM +, Rui Sousa wrote:
> > > On Thu, 23 Nov 2000, Michael Elkins wrote:
> > >
> > > Usb controller is sharing a interrupt with the emu10k1.
> > > For what I know the emu1
Since I started running the 2.4.0-test kernels a couple of months ago
I'm not able to use my scsi cdrom and cdwriter.
Today I installed 2.4.0-test11, still the same problem.
bayes:/dev# ls -l /dev/scd0
brw-rw1 root cdrom 11, 0 Oct 21 04:53 /dev/scd0
bayes:/dev# mount -t iso96
Since I started running the 2.4.0-test kernels a couple of months ago
I'm not able to use my scsi cdrom and cdwriter.
Today I installed 2.4.0-test11, still the same problem.
bayes:/dev# ls -l /dev/scd0
brw-rw1 root cdrom 11, 0 Oct 21 04:53 /dev/scd0
bayes:/dev# mount -t iso96
Hi!
> > Can't I run a i386 kernel on a ia64 machine? I know something like this
> > from HP-UX. You can choose between a 32 and a 64 bit kernel when
> > installing, so knowing that you have a 64 bit capable machine does not
> > say that you have a 64 bit kernel.
> > And I want to have the kernel
Hi!
> > I also agree that the ioctl patch is kind of a bandaid over
> > the problems that you described, and, while Zach Brown can speak
>
> The biggest problem is that the current code is gross gross gross.
> I've been avoiding dealing with it too much in the hopes that moving to
> oss_audi
Hi!
Perhaps yo should consider lowering number of stars in the subject.
> Linux Logical Volume Manager 0.8.1 (this is 0.8final plus patches)
> and 0.9 are available for download at www.sistina.com.
> Please see further information below, test it and help us
> to make an even better LVM for Linu
Hi!
> otherwise valid) I think the access macros are unnecessary. I would be
> *very* glad if someone could confirm this, or shoot me down. :)
>
> For instance, a kernel module I am writing allocates some memory in
> the current process's address space as follows:
>
> down(&mm->mmap_sem);
>
Hi!
> HOW?
> No performance loss, RAM is always fully utilized (except if no swap),
Handheld machines never have any swap, and alwys have little RAM [trust me,
velo1 I'm writing this on is so tuned that 100KB les and machine is useless].
Unless reservation can be turned off, it is not acceptab
Hi!
It happened to me today while debugging x86-64. That code probably
likes to fail this way ;-).
Pavel
--
I'm [EMAIL PROTECTED] "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patent
Hi!
You see? Kernel_thread does not check is sys_clone() worked! Aha,
caller is responsible for that, but init/main.c does not seem too
carefull. Maybe kernel_thread should at least print a warning?
Plus, can someone explain me why it does not need to setup %%ecx with
either zero or address of s
On Thu, Nov 23, 2000 at 05:49:52PM +0100, Georg Acher wrote:
> On Thu, Nov 23, 2000 at 04:35:33PM +, Rui Sousa wrote:
> > On Thu, 23 Nov 2000, Michael Elkins wrote:
> >
> > Usb controller is sharing a interrupt with the emu10k1.
> > For what I know the emu10k1 driver doesn't have any problem
> - static unsigned char init_ID_done = 0, version_printed = 0;
> - int i, irq, irqval, retval;
> + static unsigned char init_ID_done, version_printed;
> + int i, irq, retval;
>
> This is wrong because later we depend on assumption that
> these values are equal to 0 (they aren't a
On Thu, 23 Nov 2000, Andreas Bombe wrote:
> > I may be wrong on this, but I thought that copy_{to,from}_user are
> > only necessary if the address range you are accessing might cause a
> > fault which Linux cannot handle (ie. one which would cause the
> > application to segfault if it accessed tha
Hi
patch-3c503:
@@ -307,11 +307,12 @@
{
ei_status.tx_start_page = EL2_MB1_START_PG;
ei_status.rx_start_page = EL2_MB1_START_PG + TX_PAGES;
- printk("\n%s: %s, %dkB RAM, using programmed I/O (REJUMPER for SHARED
MEMORY).\n",
- dev->name, ei_status.name, (w
Hi!
Just a few hints on __init/__exit stuff...
On Wed, 22 Nov 2000, Patrick van de Lageweg wrote:
> +struct reginit_item PHY_NTC_INIT[] = {
Can be marked __initdata
> +void undocumented_pci_fix (struct pci_dev *pdev)
Can be marked __init
> +void write_phy (struct fs_dev *dev, int regnum, i
> is change to field name temporary, and name will be reverted back
> to flags, even although contents may differ between 2.2.x and 2.4.x,
> or is there features to stay? Currently VMware does
>
> "^\(features\|flags\).* tsc"
>
> but question is - should we leave it here, or revert it back?
I
On Thu, Nov 23, 2000 at 10:32:01PM +0100, f5ibh wrote:
> Hi,
>
> I use an USB mouse, it works perfectly both with 'gpm' and with X-window but
> time to time, I've this kind of message stream :
>
> [root@debian-f5ibh] ~ # usb-uhci.c: interrupt, status 3, frame# 20
> usb-uhci.c: interrupt, status
Hi,
I use an USB mouse, it works perfectly both with 'gpm' and with X-window but
time to time, I've this kind of message stream :
[root@debian-f5ibh] ~ # usb-uhci.c: interrupt, status 3, frame# 20
usb-uhci.c: interrupt, status 3, frame# 44
usb-uhci.c: interrupt, status 3, frame# 68
usb-uhci.c: i
On Thu, 23 Nov 2000, Matti Aarnio wrote:
> On Thu, Nov 23, 2000 at 12:38:55PM -0800, Linus Torvalds wrote:
> ...
> > In fact, almost all filesystems do this at some point. ext2 does it for
> > directories too, for some very similar reasons that isofs does. See
> > fs/ext2/dir.c:
> >
> > b
On 23 Nov 00 at 20:22, Alan Cox wrote:
> > vmware-2.0.3-786 refused to run. Running vmware-config.pl resulted in a
> > the following message:
>
> Run 2.4.0-test11-ac3
Hi Alan,
is change to field name temporary, and name will be reverted back
to flags, even although contents may differ between
With recent ide patches, the ide driver seems to try to use DMA mode even for a drive
which dosen't support it. CONFIG_IDEDMA_PCI_AUTO is enabled but even so with the stock
kernel this dosen't happen. older patches didn't have this behavior either. Is this
change intentional ?
hdc: 333630 sect
I'm still trying to reproduce the darn thing w/o the patch. No luck so
far.
Maybe I'll put some mission critical stuff on my machine. Then it'll pop
up like clock works. Thats the way everythign is supposed to work right?
=)
Tigran Aivazian wrote:
> However, I can't say that _without_ your patch
Hello all,
Using RHL 2.2.16-3 kernel on i686.
Raising MAX_UNITS define from 8 to 16 or 32 in net drivers (tested
tulip.c) causes reproducible oops. The latest Don Becker driver also does
this. Using DFE-570TX quad ethernet cards.
So, why change MAX_UNITS? Interfaces 9-> can't be passed optio
Hi.
Some time ago there was a thread about subject and a patch was posted
(by davej?). It was rejected because of the vmlist_modify_{un}lock
mess (AFAIR) and nothing has been done since. The first patch below
moves mm->rss inside the page_table_lock in mm/.
I noticed that mm->rss is also modif
Hi Alexander,
I am "hammering" an ext2 filesystem with all sorts (bonnies, make -j8
bzImage, cp -a dir1 dir2 + all these over localhost NFSv3) for a while and
so far it survives. The system is 2way SMP with 1G RAM.
However, I can't say that _without_ your patch the above did _not_
survive. The c
On Wed, Nov 22, 2000 at 09:39:51PM +, Keir Fraser wrote:
> > The reason that everyone else uses copy_{to,from}_user is that there
> > is no way to guarantee that the userspace pointer is valid. That
> > memory may have been swapped out. The copy macros are prepared to
> > fault the memory in.
On Thu, Nov 23, 2000 at 12:38:55PM -0800, Linus Torvalds wrote:
...
> In fact, almost all filesystems do this at some point. ext2 does it for
> directories too, for some very similar reasons that isofs does. See
> fs/ext2/dir.c:
>
> blk = (filp->f_pos) >> EXT2_BLOCK_SIZE_BITS(sb);
>
> (an
On Thu, 23 Nov 2000, Andi Kleen wrote:
>
> I am actually not sure if the normal kernel contains even a variable
> width long long shift.
Sure it does. The isofs code contains exctly that:
block = filp->f_pos >> bufbits;
In fact, almost all filesystems do this at some point. ext2 does
On Tue, 21 Nov 2000, Jorge Nerin wrote:
>> How about a working URL?
>>
>> traceroute to skaro.nightcrawler.com (216.186.140.118), 30 hops max, 38 byte packets
>> [...]
>> 11 pos3-0-0-155M.sjc-bb3.cerf.net (134.24.29.26) 66.400 ms 74.860 ms 68.486 ms
>> 12 dslnetworks1.dslnetworks.com (206.19
Albert D. Cahalan writes:
> Also, cross-arch debugging is done by people who don't need tools
> like ksymoops anyway. Most likely they have half the opcodes
> memorized already, and they have the CPU manual open on their desk.
I certainly don't have each of the 4 billion opcode combinations on
th
> vmware-2.0.3-786 refused to run. Running vmware-config.pl resulted in a
> the following message:
Run 2.4.0-test11-ac3
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Thu, Nov 23, 2000 at 12:07:01PM -0800, Phil Stracchino wrote:
> I just compiled and installed kernel 2.4.0-test11. Upon rebooting,
> vmware-2.0.3-786 refused to run. Running vmware-config.pl resulted in a
> the following message:
>
> "Your processor does not have a Time Stamp Counter.
On Thu, 23 Nov 2000, Charles Cazabon wrote:
> [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > > Thats because too many things get put on a line then.
> > > And because we do [] [] not [][] ?
> >
> > In the good old times we had foo bar for a total of 8*(8+1) = 72
> > positions. Now we hav
Tiny patch for vmware-config.pl
Phil Stracchino wrote:
>
> I just compiled and installed kernel 2.4.0-test11. Upon rebooting,
> vmware-2.0.3-786 refused to run. Running vmware-config.pl resulted in a
> the following message:
>
> "Your processor does not have a Time Stamp Counter. VMwa
On Thu, Nov 23, 2000 at 06:54:48PM +, Tigran Aivazian wrote:
> Hi,
>
> The sizeof(struct tty_struct) = 3084. Why don't we have a private slab
> cache for it instead of getting a page and wasting some precious bytes at
> the end? Potentially, we can have thousands of tty_struct allocated
> (as
On Thu, Nov 23, 2000 at 08:59:46AM -0800, Linus Torvalds wrote:
> [ Btw, I noticed that one of my machines _does_ have gcc-2.95.2, so I can
> look at the isofs code generation myself. I don't see anything obvious,
> and the code is hairy. The differences between 2.91.66 and 2.95.2 are
> big
"Heinz J. Mauelshagen" wrote:
>
> On Wed, Nov 22, 2000 at 04:27:51PM -0500, Brian Kress wrote:
> > "Heinz J. Mauelshagen" wrote:
> > >
> > > On Wed, Nov 22, 2000 at 04:05:39PM -0500, Brian Kress wrote:
> > > > Question about /proc/partitions and LVM. LVM devices in
> > > > /proc/partitions
Dans son message du Thu 23 November, Maciej W. Rozycki ecrit :
> Hmm, your BIOS reports the timer IRQ is directly connected...
> > Int: type 0, pol 3, trig 3, bus 2, IRQ 09, APIC ID 2, APIC INT 09
> This is weird for an ISA IRQ.
Remember that I have TWO PCI buses and one ISA Bus.
>
> > ENABLI
Hi,
Since I use kernel 2.4.0(test11) the power-off on halt doesn't work
anymore (I have the same problem with previous 2.4.0 releases).
I use apm to power-off the system (my system doesn't support acpi) and
with kernel 2.2.17 everything works great. But since I've compiled
2.4.0test11 with ex
On Thu, Nov 23, 2000 at 12:01:35PM +, Stephen C. Tweedie wrote:
> Hi,
>
> On Wed, Nov 22, 2000 at 11:54:24AM -0700, Jeff V. Merkey wrote:
> >
> > I have not implemented O_SYNC in NWFS, but it looks like I need to add it
> > before posting the final patches. This patch appears to force writ
On Thu, Nov 23, 2000 at 06:54:48PM +, Tigran Aivazian wrote:
> Hi,
>
> The sizeof(struct tty_struct) = 3084. Why don't we have a private slab
> cache for it instead of getting a page and wasting some precious bytes at
> the end? Potentially, we can have thousands of tty_struct allocated
> (as
Hi,
The sizeof(struct tty_struct) = 3084. Why don't we have a private slab
cache for it instead of getting a page and wasting some precious bytes at
the end? Potentially, we can have thousands of tty_struct allocated
(assuming we have thousands of concurrent users)...
regards,
Tigran
-
To unsub
hot-pluggable devices are turned off in the config (see below).
-test9 had some problems with depmod arguments, make completed
if i used '-' in the Makefile to ignore the status and went back
to run depmod by hand.
make[1]: Leaving directory `/usr/src/linux-2.4.0-test11/arch/i386/lib'
cd /lib/mo
On Thu, 23 Nov 2000, Tobias Ringstrom wrote:
> >
> > - enable DEBUG in arch/i386/kernel/pci-i386.h. This should make the code
> >print out what the pirq table entries are etc.
>
> Done. When adding the call to eisa_set_level_irq, the line
>
> IRQ for 00:0a.0(0) via 00:0a.0 -> PIRQ 03, ma
On Thu, 23 Nov 2000, Linus Torvalds wrote:
> Tobias? Does changing that if-statement that make your bus happier?
I'll try this tomorrow. The sick laptop is at work, and I'm home. The time
difference really slows things down. :-(
/Tobias
-
To unsubscribe from this list: send the line "unsubscri
[Martin Dalecki]
> Just a small trivial obviously correct update...
OK, merged into my pending pci_ids.h patch. (This is bigger than
necessary because I converted almost all spaces to tabs.)
Peter
--- 2.4.0test11/include/linux/pci_ids.h.bak Mon Nov 13 01:43:49 2000
+++ 2.4.0test11/include
Albert D. Cahalan writes:
> > they are not only references to
> > kernel functions, but also kernel data and read only data within
> > the kernel text segment.
>
> 1. this is harmless
> 2. this is useful (you might get a variable's name)
Wrong. Op-codes on this machine are organised such that b
Ragnar Hojland Espinosa writes:
> On Thu, Nov 23, 2000 at 12:26:30AM +, Russell King wrote:
> > Oh, missed this one. Here you're wrong again. The numbers in [< >]
> > should be looked up, and no others. The code can look exactly like
> > a kernel address. In this case you definitely do NOT
On Thu, 23 Nov 2000, Linus Torvalds wrote:
> > > Tobias, can you confirm that calling pci_enable_device before reading
> > > dev->irq fixes the 3c59x.c problem for you?
> >
> > Nope. The interrupts do not seem to get through. Packets are transmitted,
> > but that's it. I've copied the interesting
Rogier Wolff wrote:
>
> Alan Cox wrote:
> > > under 1 gig in size. You can exhibit the problem by mounting the dvd movie
> > > "The World is Not Enough" as it contains a video_ts.vob which is larger than
> > > 1 gigabyte. You will see that most of the file lengths are incorrect due to
> > > the
On Thu, Nov 23, 2000 at 09:20:15AM -0800, Linus Torvalds wrote:
> Can you check whether the single patch of _just_ removing the extra "f_pos
> >= i_size" test in do_isofs_readdir() fixes it? The other changes of
> Andries patch look like they should not affect code generation at all, but
> I'd sti
[ Tobias: thanks for an excellent report, btw ]
On Wed, 22 Nov 2000, Tobias Ringstrom wrote:
> On Wed, 22 Nov 2000, Tobias Ringstrom wrote:
>
> > Not that I like it, but I need to boot Win98, and then warm boot into
> > Linux, or the Cardbus is not working. This is using Linux-2.4.0-test11 on
On Thu, 23 Nov 2000, Linus Torvalds wrote:
> To tie two threads together again: the thread about FS corruption is one
> of my main worries right now. Do people who see this happen to use a gcc
> other than egcs-2.91.66? I know Andries apparently has 2.95.2, and he's
> one of the people who have re
On Thu, 23 Nov 2000, Ragnar Hojland Espinosa wrote:
>
> Yup, indeed it solves the dir/namei problem.
Can you check whether the single patch of _just_ removing the extra "f_pos
>= i_size" test in do_isofs_readdir() fixes it? The other changes of
Andries patch look like they should not affect
On Thu, 23 Nov 2000, Alexander Viro wrote:
> On Thu, 23 Nov 2000, Neil Brown wrote:
>
> > which enabled ext2_notify_change, however ext2_notify_change has a
> > bug.
> > It sets attributes from iattr->ia_attr_flags even
> > if ATTR_ATTR_FLAG is NOT SET in iattr->ia_valid.
>
> Arrrgh. Could yo
On Tue, 21 Nov 2000, Tobias Ringstrom wrote:
> >
> > Tobias, can you confirm that calling pci_enable_device before reading
> > dev->irq fixes the 3c59x.c problem for you?
>
> Nope. The interrupts do not seem to get through. Packets are transmitted,
> but that's it. I've copied the interesting
1 - 100 of 158 matches
Mail list logo
