On Thu Dec 07 2000 at 00:44, Ben Greear wrote:
> I have a product that is dependent on policy-based (source routing)
> and would like to be able to scream loudly at install and startup if
> policy-based routing is not enabled in the kernel.
>
> Is there some way to determine this? Specifically,
Which ethernet module works with this card? 2.2.17 kernel
--
Mike A. Harris - Linux advocate - Open source advocate
This message is copyright 2000, all rights reserved.
Views expressed are my own, not nec
On Wed, 6 Dec 2000, Rusty Russell wrote:
>Date: Wed, 06 Dec 2000 11:40:12 +1100
>From: Rusty Russell <[EMAIL PROTECTED]>
>To: Mike A. Harris <[EMAIL PROTECTED]>
>Cc: [EMAIL PROTECTED]
>Subject: Re: [PATCH] ipchains log will show all flags
>
>In message <[EMAIL PROTECTED]> you write
>:
>> Personal
On Wed, 6 Dec 2000, Miles Lane wrote:
>
> I have also just tried a test pass with 3c59x built in and
> USB built as modules. I booted with only the 3c575 inserted.
> I got eth0 running and then loaded usb-ohci (with the enable
> bus mastering change added). This resulted in modprobe hanging
>
Alan Cox <[EMAIL PROTECTED]> writes:
> Generic is not always good , thats why we have SIOCDEVPRIVATE. One thing Im
> pondering is if we should make the hardware config ioctl take a hardware type
> ident with each struct. That would help make all the ethernet agree, all the
> wan agree, all the AD
Linus Torvalds wrote:
>
> On Wed, 6 Dec 2000, Miles Lane wrote:
>
>> Here is what goes wrong:
>>
>> Dec 6 04:21:32 agate kernel: eth0: Host error, FIFO diagnostic register .
>
>
> But it continues to work, right?
I'll check. My system only has 80MB RAM, and I run Mozilla, which
pushe
I have a product that is dependent on policy-based (source routing)
and would like to be able to scream loudly at install and startup if
policy-based routing is not enabled in the kernel.
Is there some way to determine this? Specifically, I'd love
a way to find out through the /proc system, but
On Wed, Dec 06, 2000 at 10:07:57PM -0600, Peter Samuelson wrote:
>
> > Don't you think that we will run into problems anyway because soon
> > there will be raid systems with a couple of Terrabytes of space to
> > waste for mp3's ;-)
>
> A couple of terabytes is fine. That's 32 bits of blocks.
I'm not quite clear how the settings under /proc/sys/vm/* would effect the
problem. I neglected to mention in my previous post that all web content
is served directly from the memory of the web server (no file
accesses). The only file accesses that happen are from a MySQL server
which gets
Hallo Mark,
there is one thing, that is some kind of curious:
using 2.4.0-test12pre5 I've many apic errors with CPU1 a n d CPU0:
Dec 7 06:52:04 nmb kernel: APIC error on CPU1: 04(00)
Dec 7 06:52:04 nmb kernel: APIC error on CPU0: 02(00)
Dec 7 06:52:04 nmb kernel: APIC error on CPU0: 04(00)
D
Hi,
At the moment the synchronous flush trigger for bdflush is hardwired to be
double the asynchronous one. This is a pain for people with lots of RAM.
This patch adds a new variable to the bdflush sysctl so both can be
tuned independently. It also sets the defaults to 40% and 80% for async and
Hello,
I've been having a problem with a high volume Linux web server. This
particular web server used to be a FreeBSD machine and I've been trying to
successfully make the switch for some time now. I've been trying the 2.4
development kernels as they come out and I've been tweaking the /pr
On Wed, Dec 06, 2000 at 02:00:12PM -0800, Mike Kravetz wrote:
> Ragnar,
>
> Are you sure that was line 115? Could it have been line 515?
Yes, yes, it was 515. 115 is the result of human cache corruption ;)
> Also, do you have any Oops data?
It just froze there.
--
/| Ragnar Højland
[Reto Baettig]
> Imagine we have a virtual disk which provides a 64bit (sparse)
> address room. Unfortunately we can not use it as a block device
> because in a lot of places (including buffer_head structure), we're
> using a long or even an int for the block number.
Actually it should be 'unsi
On Wed, 6 Dec 2000, Miles Lane wrote:
>
> Here is what goes wrong:
>
> Dec 6 04:21:32 agate kernel: eth0: Host error, FIFO diagnostic register .
But it continues to work, right?
I bet that your ethernet card is just unhappy that it couldn't get DMA in
time, because the bus was so busy.
On Wed, Dec 06, 2000 at 08:10:19PM -0700, Jeff V. Merkey wrote:
>
>
> Alan,
>
> I am still seeing intermittent mouse problems with a PS2 mouse on a
> 4 x PPro box with 2.2.18-24. When the system is first powered up,
> the mouse detection is working great. If I reboot the machine without
> p
Alan,
I am still seeing intermittent mouse problems with a PS2 mouse on a
4 x PPro box with 2.2.18-24. When the system is first powered up,
the mouse detection is working great. If I reboot the machine without
powering it down, about 1 in 3 times I do this, the next kernel load
fails to det
On Wednesday December 6, [EMAIL PROTECTED] wrote:
> Neil Brown wrote:
> >
> > here we have lost the "part" automatic variable in disk_name but
> >
>
> I don't think so. Look again.
Gulp... :-(
Yes, your patch is indeed fine. I heartily recommend it (for whatever
that is worth).
Hi,
I have been having trouble with a server crashing for the last few months. The machine
seems to run fine for a few days and then unexpectedly crashes or locks up. I have
tried numerous things to resolve the problem. At first the issue appeared memory
related so I swapped the memory. Still
I'm glad to say that this is the first 2.4 kernel that works on my noritake
alpha with a pci-pci bridge.
I have a small problem. If I reboot, the srm console can't boot from dka0.
Doing a: show dev
doesn't list any of the hard drives in the machine.
doing an init causes it to reset and find all
Andrew Morton wrote:
> Wakko Warner wrote:
> >
> > > - pre6:
> > > - Andrew Morton: exec_usermodehelper fixes
> >
> > pre4 oopsed all over the place on my alpha with modules and autoloading
> > turned on as soon as it mounted / and freed unused memory. I take it this
> > was seen on i386 a
Hello,
I am doing development work on the 2.4.0 kernel, and can not seem to get
multicasting to work.
I have included two test files which I attempted to run, one as a
sender, and another as the receiver. The
code worked as expected on a stock redhat 6.2 - linux 2.2.14-5.0 kernel.
I have foun
> From: Linus Torvalds [mailto:[EMAIL PROTECTED]]
>
...
> Now, this is with a bog-standard PIIX irq router, so we
> definitely know
> that we have the pirq table parsing right. I even have unofficial
> confirmation from intel engineers on this.
>
> But I see something obviously wrong there: you
The only reason for this pre7 is to resolve some warring patches in the
cs46xx driver.
Linus
---
- test7:
- Kai Germaschewski: ymfpci cleanups and resource leak fixes
- me: UHCI drivers really need to enable bus mastering.
- Trond Myklebust: fix up nfs_writepage_sy
I did not get reply from Linus. Now try my luck with the kernel mailing
list. Please cc your reply to my email account. I stopped watching the
mailing list anymore.
Thanks.
Jun
Jun Sun wrote:
>
> Linus,
>
> A while back I reported the lost need_resched flag bug ( it happens if
> need_resc
Who has one or knows how to kick one to life?
Cheers,
Andre Hedrick
CTO Timpanogas Research Group
EVP Linux Development, TRG
Linux ATA Development
-
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
Florin Andrei wrote:
>
> Anyone tryied to build the drivers from Intel for the e100 (pro/100)
> network card using a 2.2.18pre kernel? I tried, and i'm gettting this
> error:
>
> In file included from e100.c:124:
> e100.h:265: conflicting types for `dma_addr_t'
> /usr/src/linux/includ
Error/bug in the "tulip" network driver from the 2.4.0-test11 kernel, when
detecting media type.
The bug is quite simple. When detecting the media type, it's possible to
access data outside/beyond the array "medianame[]". This leads to an
kernel panic Oops.
I detected the bug, when using th
Erik Mouw wrote:
> On Wed, Dec 06, 2000 at 11:38:30AM -0800, Linus Torvalds wrote:
>
>> But I see something obviously wrong there: you have busmaster disabled.
>>
>> Looking into the UHCI controller code, I notice that neither UHCI driver
>> actually does the (required)
>>
>> pci_set_mast
I saw some time ago some discussion about poll(). This is may question
(if it remembers anyone a known issue):
A driver poll_wait()s hardware and wants to raise an interrupt on hardware
change.
It works on 2.2 SMP but locks in 2.4 SMP. Works on 2.4 UP.
Is any SMP issue with poll ?
Thanks.
--
Okay, here is yet another A20 patch (against test12-pre6) this time
for people to try out. This patch uses the following algorithm for
enabling A20:
1. Try the BIOS call. If it works, we're cool.
2. Try the KBC (using Linus' lowered timeouts.)
3. If the KBC doesn't work, or is very slow, flip p
On Wed, 6 Dec 2000, James Lamanna wrote:
> Here is an excerpt from /proc/pci:
>
> Bus 0, device 11, function 0:
> RAID bus controller: Promise Technology, Inc. 20267 (rev 2).
> IRQ 10.
> Master Capable. Latency=32.
> I/O at 0x9400 [0x9407].
> I/O at 0x9000 [0x9003
On Wed, 6 Dec 2000 17:24:58 -0500 (EST),
"Georg Nikodym" <[EMAIL PROTECTED]> wrote:
>sysklogd 1.3-31 no longer compiles using the latest headers in test11.
>
>Strictly speaking this isn't a kernel bug...
>
>sysklogd's ksym_mod.c includes
Speaking as the modutils maintainer and the person who ad
Jeff Garzik wrote:
> eh? It's self-evident from Erik's patch that pci_enable_device's return
> call is already being tested, thus you only need to add a call to
> pci_set_master.
Sorry. I'll shut up now and go back to doing something
I actually am somewhat knowledgable about -- namely, testi
On 6 Dec 00 at 14:00, Mike Kravetz wrote:
>
> Are you sure that was line 115? Could it have been line 515?
> Also, do you have any Oops data?
>
Yesterday BUG in schedule at 515 happened for me with test12-pre4.
As there were no data, and it was followed by
NMI detected lockup on CPU24 ...
(
Miles Lane wrote:
>
> Hmm. Your patch doesn't test whether pci_enable_device(dev)
> was successful, does it?
eh? It's self-evident from Erik's patch that pci_enable_device's return
call is already being tested, thus you only need to add a call to
pci_set_master.
Jeff
--
Jeff Garzik
> Date: Wed, 6 Dec 2000 15:00:38 -0500 (EST)
> From: Pavel Roskin <[EMAIL PROTECTED]>
> To: Pete Zaitcev <[EMAIL PROTECTED]>
> Subject: Re: YMF PCI - thanks, glitches, patches (fwd)
> > > Date: Wed, 6 Dec 2000 13:12:13 -0500 (EST)
> > > From: Pavel Roskin <[EMAIL PROTECTED]>
> > > cc: Jaroslav Ky
On Wed, Dec 06, 2000, Miles Lane <[EMAIL PROTECTED]> wrote:
> Hmm. Your patch doesn't test whether pci_enable_device(dev)
> was successful, does it?
Umm, it does. If pci_enable_device wasn't successful, it returns -ENODEV.
Your patch below calls pci_set_master if enabling the device fails and
t
Hmm. Your patch doesn't test whether pci_enable_device(dev)
was successful, does it?
I think what you want is:
diff -u --new-file drivers/usb/uhci.c~ drivers/usb/uhci.c
--- drivers/usb/uhci.c~ Tue Dec 5 23:55:38 2000
+++ drivers/usb/uhci.c Wed Dec 6 14:50:00 2000
@@ -2380,8 +2380,10 @@
On Wed, 6 Dec 2000, Linus Torvalds wrote:
>
>
> On Wed, 6 Dec 2000, Tigran Aivazian wrote:
> >
> > This patch combines your previous patch with 2 changes I have just
> > suggested. Both changes are obvious (and correct).
>
> Why remove the EROFS test?
Tigran has a point - permission() does
Hi Linus,
Thanks for the reply.
I agree with your analysis of the information I reported
in this message. However, in previous related bug reports
I mentioned actual functional conflicts between the drivers.
Here is what goes wrong:
Dec 6 04:21:32 agate kernel: eth0: Host error, FIFO diagnos
sysklogd 1.3-31 no longer compiles using the latest headers in test11.
Strictly speaking this isn't a kernel bug...
sysklogd's ksym_mod.c includes
In test11, added struct inter_module_entry. Its
first member is "struct list_head list;". This necessitates the
inclusion of .
The trouble is
Chris Meadors wrote:
>
> On 6 Dec 2000, H. Peter Anvin wrote:
>
> >
> > Please don't use the path /var/shm... it was a really bad precedent
> > set when someone suggested it. Use /dev/shm.
> >
>
> And I'll ask again... If this is now the recommend mount point, can we
> have devfs create thi
Here is an excerpt from /proc/pci:
Bus 0, device 11, function 0:
RAID bus controller: Promise Technology, Inc. 20267 (rev 2).
IRQ 10.
Master Capable. Latency=32.
I/O at 0x9400 [0x9407].
I/O at 0x9000 [0x9003].
I/O at 0x8800 [0x8807].
I/O at 0x8400 [0x84
Ragnar,
Are you sure that was line 115? Could it have been line 515?
Also, do you have any Oops data?
Thanks,
--
Mike Kravetz [EMAIL PROTECTED]
IBM Linux Technology Center
15450 SW Koll Parkway
Beaverton, OR 97006-6063 (503)578-3494
On Wed,
The EXT2-fs errors I recently reported for test11 seem to be gone with
test12-pre5. At least I couldn't reproduce the error, neither with
overcommit_memory turned on nor off; maybe the error was due to
turning on write cache of my hard disk.
The error was a wrong reading of directory lengths and
Neil Brown wrote:
>
> On Wednesday December 6, [EMAIL PROTECTED] wrote:
> > Peter Samuelson wrote:
> > >
> > > [Roberto Ragusa]
> > > > BTW, here is a little patch regarding a silly problem I found
> > > > about RAID partitions naming (/proc/partitions).
> > > > No more "md8" "md9" "md:" "md;" ..
On Wed, 6 Dec 2000, James Lamanna wrote:
> So you are saying that the Promise Fasttrak 100 chipset is
> designed wrong? Because that's exactly what I have.
> and isn't this driver supposed to support it?
> Or are you saying the IDE controller on the MB is wrong?
Clarify things first.
PDC20267 i
So you are saying that the Promise Fasttrak 100 chipset is
designed wrong? Because that's exactly what I have.
and isn't this driver supposed to support it?
Or are you saying the IDE controller on the MB is wrong?
Andre Hedrick wrote:
>
> <4>ide: Assuming 33MHz system bus speed for PIO modes
> <
Erik Mouw wrote:
>
> On Wed, Dec 06, 2000 at 11:38:30AM -0800, Linus Torvalds wrote:
> > But I see something obviously wrong there: you have busmaster disabled.
> >
> > Looking into the UHCI controller code, I notice that neither UHCI driver
> > actually does the (required)
> >
> > pci_set_
> > Ioctl 0x5401 is a mystery. I do not know what it is
> > (looks like SNDCTL_TMR_TIMEBASE without uppper bits).
>
> It is caused by an attempt to play at 5512 Hz. In fact, this time (I've
I was wrong. It happens for all sounds when sox calls
setvbuf (ft->fp,NULL,_IOFBF,sizeof(char)*BUFSIZ)
Io
On Tue, 5 Dec 2000, Igor Yu. Zhbanov wrote:
> Hello!
Hello again
> As I see now in 2.2.18pre24 NCPFS is fixed but VFAT and SMBFS doesn't. (This
> happened because the maintainer of NCPFS resent my patch to Alan Cox but only the
> part of patch related to NCPFS). So I resent you patch for VFAT a
On Wednesday December 6, [EMAIL PROTECTED] wrote:
> Peter Samuelson wrote:
> >
> > [Roberto Ragusa]
> > > BTW, here is a little patch regarding a silly problem I found
> > > about RAID partitions naming (/proc/partitions).
> > > No more "md8" "md9" "md:" "md;" ... but "md8" "md9" "md10" "md11" ..
In article <[EMAIL PROTECTED]>,
Dag Brattli <[EMAIL PROTECTED]> writes:
DB> else. I''ve tried to find it, but I'm still clueless at the prompt.
Fixed by the exec_usermodehelper fixes in 2.4.0test12pre6 (at least here:).
-
To unsubscribe from this list: send the line "unsubscribe l
On Wed, 6 Dec 2000, Andre Hedrick wrote:
> Nope you have a chipset that is designed wrong.
Who makes an on-board chipset (not southbridge) which is designed right?
Highpoint makes HPT370, but after HPT366 fiasco I'm not sure I trust them
anymore...
-Dan
-
To unsubscribe from this list: send th
On 6 Dec 2000, H. Peter Anvin wrote:
>
> Please don't use the path /var/shm... it was a really bad precedent
> set when someone suggested it. Use /dev/shm.
>
And I'll ask again... If this is now the recommend mount point, can we
have devfs create this directory for us?
-Chris
--
Two pengui
On Wed, Dec 06, 2000 at 11:38:30AM -0800, Linus Torvalds wrote:
> But I see something obviously wrong there: you have busmaster disabled.
>
> Looking into the UHCI controller code, I notice that neither UHCI driver
> actually does the (required)
>
> pci_set_master(dev);
>
> Please add tha
Hi,
Steve Hill wrote:
> I'm building boxes with the console set to /dev/ttyS0. However, I can't
> guarantee that there will always be a term plugged into the serial
> port. If there is no term on the port, eventually the buffer fills and
> any processes that write to the console (i.e. init) bl
On Wed, 6 Dec 2000, Miles Lane wrote:
>
> If I insert both my 3c575 and Belkin BusPort Mobile USB host-controller
> and then enable both of them, "modprobe usb-ohci" hangs. If I then
> attempt "modprobe -r 3c59x", that process hangs, too. lsmod shows:
>
> usb-ohci 15072 1 (init
Followup to: <[EMAIL PROTECTED]>
By author:Andre Hedrick <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Did you set and mount a "/var/shm" point?
>
Please don't use the path /var/shm... it was a really bad precedent
set when someone suggested it. Use /dev/shm.
-hpa
--
1) ATAPI DMA hangs and fs corruption, Acer Aspire with 2.4.0-test1x
2) Using the 2.0.4-test1x Ali M15x3 driver in DMA transfer mode on my Acer
Aspire (Running Debian/GNU Linux) with heavy network load I get DMA
timeouts and/or (so far) minor filesystem corruption. Minor just means
that nothing i
On Wed, 6 Dec 2000, Pete Zaitcev wrote:
> > Date: Wed, 6 Dec 2000 13:12:13 -0500 (EST)
> > From: Pavel Roskin <[EMAIL PROTECTED]>
> > cc: Jaroslav Kysela <[EMAIL PROTECTED]>, Pete Zaitcev <[EMAIL PROTECTED]>,
> > <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
>
> > The native YMF PCI driver fro
On Wed, 6 Dec 2000, Udo A. Steinberg wrote:
> What drive are you using? AFAIR, Andre Hedrick once said certain Maxtor
> drives aren't quite safe with DMA.
Depends on the controller. Maxtor drives play badly with Highpoint
controllers, but are OK with Promise.
-Dan
-
To unsubscribe from this lis
Did you set and mount a "/var/shm" point?
On Wed, 6 Dec 2000, Udo A. Steinberg wrote:
> Hi,
>
> Andre Hedrick wrote:
> >
> > No way that this could cause corruption it is a read-only test.
>
> As others pointed out, it's probably something related to shared
> memory, but it's definitely hdp
On Wed, 6 Dec 2000, Udo A. Steinberg wrote:
> I also have an A7V and both of my IBM IDE drives are connected to the
> Promise controller, running in UDMA-5 mode. There hasn't been any
> corruption on either of the drives that had to do with UDMA-5 mode.
> And the ext2 bugs that 2.4 kernels had, h
Hi,
Andre Hedrick wrote:
>
> No way that this could cause corruption it is a read-only test.
As others pointed out, it's probably something related to shared
memory, but it's definitely hdparm that triggers it. I haven't
got the hdparm sources here to look at what exactly it's doing,
but there
I have not tested of checked the nature of the PCD20265 which is the
onboard version.
On Wed, 6 Dec 2000, Skip Collins wrote:
> After running 2.4.0-test11 for a while, my system would occasionally
> hang during heavy disk activity resulting in a corrupt ext2 filesystem.
> Fortunately, none of
This code in fs/fat/file.c::fat_get_block() is getting triggered when I
run wine:
if (iblock<<9 != MSDOS_I(inode)->mmu_private) {
BUG();
return -EIO;
}
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bo
Hi
Imagine we have a virtual disk which provides a 64bit (sparse) address
room. Unfortunately we can not use it as a block device because in a lot
of places (including buffer_head structure), we're using a long or even
an int for the block number.
Is there any way of getting a standardized way
On Wed, Dec 06, 2000 at 11:41:51AM -0800, Andre Hedrick wrote:
> No way that this could cause corruption it is a read-only test.
It definitely does, I saw it, too. It seems to be triggered
by invalidate_buffers().
Jan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Wed, 6 Dec 2000, Tigran Aivazian wrote:
>
> This patch combines your previous patch with 2 changes I have just
> suggested. Both changes are obvious (and correct).
Why remove the EROFS test?
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Wed, 6 Dec 2000, Erik Mouw wrote:
> >
> > Can you tell me what device it is that doesn't work for you?
>
> The USB controller. That's device 00:07.2:
>
> 00:07.2 USB Controller: Intel Corporation 82440MX USB Universal Host Controller
>(prog-if 00 [UHCI])
> Control: I/O+ Mem- BusM
No way that this could cause corruption it is a read-only test.
On Wed, 6 Dec 2000, Udo A. Steinberg wrote:
>
> Hi,
>
> Following the discussion in another thread where someone
> reported fs corruption when enabling DMA with hdparm, I've
> played around with hdparm and found that even the rat
On Wed, 6 Dec 2000, Guennadi Liakhovetski wrote:
> > Re: PCI clock... Something somewhere (can't find now) made me think that
> > my MB is setting the PCI clock synchronously with the CPU clock, i.e. it
> > is 25MHz in my case... Any ideas where I could see it?:-)
>
> I found it - it's in ide.tx
<4>ide: Assuming 33MHz system bus speed for PIO modes
<4>AMD7409: IDE controller on PCI bus 00 dev 39
<4>AMD7409: chipset revision 7
<4>AMD7409: not 100% native mode: will probe irqs later
<4>ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
<4>ide1: BM-DMA at 0xf008-0xf00f,
I have just had a frustrating experience, solely blameable on my
own stupidity.
Basically, I'd been assuming that stopping after "booting kernel" was
due to some corruption, rather than the obvious, of checking that I had
indeed selected the right processor when compiling.
What about "booting the
On Wed, Dec 06, 2000 at 10:38:51AM -0800, Linus Torvalds wrote:
> On Wed, 6 Dec 2000, Erik Mouw wrote:
> > So at first the PCI code can't allocate an IRQ for devices 00:00.1
> > (audio), 00:07.2 (USB), and 00:09.0 (winmodem), but after the audio and
> > USB modules get inserted, IRQ 5 and 11 get a
Peter Samuelson wrote:
>
> [Brian Kress <[EMAIL PROTECTED]>]
> > I got resounding silence to posting the patch last time, so I'm not
> > sure if anyone actually wants this patch,
>
> Well, I like it, but admittedly it's mostly in the "cleanup" category
> (though it does fix the LVM name issue) s
> Date: Wed, 6 Dec 2000 13:12:13 -0500 (EST)
> From: Pavel Roskin <[EMAIL PROTECTED]>
> cc: Jaroslav Kysela <[EMAIL PROTECTED]>, Pete Zaitcev <[EMAIL PROTECTED]>,
> <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
> The native YMF PCI driver from Linux-2.4.0-test12-pre5 works on my card:
I did n
as per subject.. BUG in schedule (sched.c, 115)
--
/| Ragnar Højland Freedom - Linux - OpenGL Fingerprint 94C4B
\ o.O| 2F0D27DE025BE2302C
=(_)= "Thou shalt not follow the NULL pointer for 104B78C56 B72F0822
U chaos and
On Wed, 6 Dec 2000, Udo A. Steinberg wrote:
> Hi,
>
> Following the discussion in another thread where someone
> reported fs corruption when enabling DMA with hdparm, I've
> played around with hdparm and found that even the rather
> harmless hdparm operations are capable of trashing an ext2
> fi
On Wed, 06 Dec 2000, Steven Cole wrote:
> On Tuesday 05 December 2000 18:00, Alan Cox wrote:
> > > I did confirm that 2.4.0-test11(final) works properly with sound and KDE
> > > 2.0.
> > Ok. That sounds even more like its PCI changes
> I copied the cs46xx.c driver from 2.4.0-test11 to 2.4.0-test11
On Wed, 6 Dec 2000, Erik Mouw wrote:
>
> So at first the PCI code can't allocate an IRQ for devices 00:00.1
> (audio), 00:07.2 (USB), and 00:09.0 (winmodem), but after the audio and
> USB modules get inserted, IRQ 5 and 11 get allocated.
No, the irq stuff is a two-stage process: at first it on
"Richard B. Johnson" wrote:
>
> The protected-mode switch in INT 15 is probably the least tested BIOS
> function ever. I wouldn't trust it, and relying on it will put further
> burden on embedded Linux developers, many of whom don't even have a
> BIOS. It is 'least tested' because there is no way
Hi,
On Wed, Dec 06, 2000 at 12:28:54PM -0500, Peng Dai wrote:
>
> This patch fixes a subtle corruption when doing raw IO on the 2.2.x
> kernel
> with bigmem enabled. The problem was first reported by Markus Döhr while
That patch is already part of the full bugfixed raw IO patchset I
posted out
Hello!
The Linux-sound list appears to be dead (I don't see my message in
http://www.kernelnotes.org/lnxlists/linux-sound/), so I'm sending to the
authors and the people discussing the problem on the linux-kernel mailing
list.
An additional problem is that opl3 cannot find the device unless I lo
On Tue, Dec 05, 2000 at 11:25:55PM -0800, Linus Torvalds wrote:
> Concering the PCI irq routing fixes in particular, I'd ask people with
> laptops to start testing their kernels with PnP OS set to "yes" in the
> BIOS setup. We shoul dbe at a stage where it should basically work all the
> time, and
On Wed, 6 Dec 2000, Martin Diehl wrote:
>
> problems with recent 2.4.0-test1* on my HP OmniBook 800 are probably
> combined PCMCIA(CB) / PCI / APM issues. The point is my 16bit cards
> (modem+ne2k) are working perfectly fine with yenta sockets until the first
> suspend/resume. Afterwards the PC
On Wed, 6 Dec 2000, Giacomo Catenazzi wrote:
> On my box, with heavy load I saw:
> spurious 8259A interrupt: IRQ7.
> Newer seen this message before.
>
> Linux (2.4.0.11.4) or my old slow box ?
>
>
> giacomo
>
This is really "normal" occasionally, and probably should not be logged.
This
On Wed, Dec 06, 2000 at 06:25:15PM +0100, Udo A. Steinberg wrote:
> hdparm -tT /dev/hdb1 does the trick here.
>
> After that, several files are corrupted, such as /etc/mtab.
> Reboot+fsck fixes the problem, however e2fsck never finds
> any errors in the fs on disk.
I'm currently trying to isolat
Alan Cox wrote:
>
> > INT 15-2401 disable A20
> > INT 15-2402 query status A20
> > INT 15-2403 query A20 support (kdb or port 92)
> >
> > IBM classifies these functions as optional, but it is enabled on a lot
> > of
> > new BIOS, no know conflicts, thus we can call this function to enable
> > A20
[Timothy A. DeWees]
> Could someone be so kind to point me to a page where I can find a
> list of parameters I can pass to a kernel on boot.
Documentation/kernel-parameters.txt
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PRO
Hi,
Following the discussion in another thread where someone
reported fs corruption when enabling DMA with hdparm, I've
played around with hdparm and found that even the rather
harmless hdparm operations are capable of trashing an ext2
filesystem quite nicely.
hdparm version is 3.9
hdparm -tT
> Aiee, killing interrupt handler
> invalid operand:
> CPU:0
> EIP:0010:[]
> EFLAGS: 00010292
>...
> Aiee, killing interrupt handler
> invalid operand:
> CPU:0
> EIP:0010:[]
> EFLAGS: 00010286
You are not the only one to find this. On the ARM kernels, I have had to
chan
Hi,
This patch fixes a subtle corruption when doing raw IO on the 2.2.x
kernel
with bigmem enabled. The problem was first reported by Markus Döhr while
running SAP DB on a variation of the 2.2.16 kernel with among others the
following patches installed,
> linux-2.2.16-rawio.patch
> linux-2.2.1
In article <[EMAIL PROTECTED]>,
Juri Haberland <[EMAIL PROTECTED]> wrote:
>Rik van Riel wrote:
>>
>> Could you make it a one-way list this time?
>> These two-way lists always give horrible problems
>> and I would hate to killfile all of innominate ;)
>
>Allright, I think we have choice :-/
>Sorr
Hi
I just received another reply from WD (after my repeated enquiry) - now
they say my disk DOES support DMA... So, either - something is wrong with
my kernel configuration / hdparm usage / kernel boot parameters / whatever
else... OR BIOS... Which I don't know how to bypass...
Regards
Guennadi
On my box, with heavy load I saw:
spurious 8259A interrupt: IRQ7.
Newer seen this message before.
Linux (2.4.0.11.4) or my old slow box ?
giacomo
My dmesg
BIOS-provided physical RAM map:
BIOS-e820: 0009fc00 @ (usable)
BIOS-e820: 0400 @ 0
[Brian Kress <[EMAIL PROTECTED]>]
> I got resounding silence to posting the patch last time, so I'm not
> sure if anyone actually wants this patch,
Well, I like it, but admittedly it's mostly in the "cleanup" category
(though it does fix the LVM name issue) so at this point in 2.4 I guess
Linus
"Udo A. Steinberg" wrote:
> What drive are you using? AFAIR, Andre Hedrick once said certain Maxtor
> drives aren't quite safe with DMA.
Using an IBM 45GB udma5 capable drive. The problems only occur under
_heavy_ disk activity. I have -d 1 -c 3 -m 16 set.
Have you tried thrashing your drive f
1 - 100 of 162 matches
Mail list logo
