Keith Owens wrote:
>
> On Sun, 11 Mar 2001 08:53:40 +0100 (CET),
> Ingo Molnar <[EMAIL PROTECTED]> wrote:
> >it sure has an alternative. The 'cpus spinning' code calls touch_nmi()
> >within the busy loop, the polling code on the control CPU too. This is
> >sure more robust and catches lockup bugs
Hello All.
Maybe I post at wrong place.sorry
The driver has not to be included in officeal kernel.
And the maintainer has not updated the driver from 2.4.0-test9-pre7.
Maybe he is very busy.The last update is 2000-12-03.
I used some kernels from 2.4.0 to 2.4.2-ac17,and the driver always
On Sun, 11 Mar 2001, Keith Owens wrote:
> Works for me. It even makes kdb simpler.
agreed. Also, touch_nmi_watchdog() is stateless and is thus much less
prone to locking bugs.
i've attached nmi-watchdog-2.4.2-A1 that implements touch_nmi_watchdog(),
ontop of 2.4.2-ac18, and changes show_state
Ingo Molnar wrote:
>
> On Sun, 11 Mar 2001, Keith Owens wrote:
>
> > Works for me. It even makes kdb simpler.
>
> agreed. Also, touch_nmi_watchdog() is stateless and is thus much less
> prone to locking bugs.
>
> i've attached nmi-watchdog-2.4.2-A1 that implements touch_nmi_watchdog(),
> onto
Guys,
I've been taking a look at the cursor flashing code,
from the point of view of how it's affected by the
recent enabling of interrupts across the console code.
Pretty much all of the cursor-blink stuff is racy,
and has always been racy on SMP. Enabling the
interrupts has made it racy on UP
george anzinger wrote:
> > > > At the moment I implemented by own delay loop using a small assembler
> > > > loop similar to the one used in the kernel. This has two disadvantages:
> > > > assembler isn't that portable, and the loop has to be calibrated.
> > >
> > > Why not use C? As long as you
Hi
Please could someone help me id the following host and pci bridges, they
don't appear in kernel 2.4.0.
Host Bridge
PCI_0600_1106__3050__30-0-0
PCI_0600_8086_1043_1130_8028_02-0-0
PCI_0600_8086_1028_2500_0095_03-0-0
PCI Bridge
PCI_0604_1106_1106_8391__00-0-0
PCI_0604_8086__113
I just upgraded from 2.2.16 to 2.2.18 in a production machine. The machine
dies after few minutes with the following error message (it's not complete,
the machine was rebooted by a colleague of mine):
Kernel panic
Exception.
Context corruption at bank 0
The motherboard is a RD440LX DP, with ada
Hi,
had an Oops in __mark_inode_dirty running kernel 2.4.2-pre3 on i386 UP
(actually a PII-300). It did happen during the daily cron job. Currently
on proc, devpts and ext2 filesystems are used no nfs and the like. The
system is still running. So if you need further information mail me or
come on
On 10-Mar-2001 Andi Kleen wrote:
> Davide Libenzi <[EMAIL PROTECTED]> writes:
>
>
>> Probably the rate at which is called sys_sched_yield() is not so high to let
>> the performance improvement to be measurable.
>
> LinuxThreads mutexes call sched_yield() when a lock is locked, so when you
> h
On Sun, Mar 11, 2001 at 01:26:23PM +0200, ivor wrote:
> Hi
>
> Please could someone help me id the following host and pci bridges, they
> don't appear in kernel 2.4.0.
>
Where these strange numbers come from ?
Only guesses after this line:
> Host Bridge
> PCI_0600_1106__3050__30-0-0
1
On Sunday 11 March 2001 00:08, Jeff Garzik wrote:
> Keith Owens wrote:
> > On Sat, 10 Mar 2001 23:03:19 -0700,
> >
> > Steven Cole <[EMAIL PROTECTED]> wrote:
> > >With the 2.4.0 kernel, there were 476 CONFIG options which had
> > >no help entry in Configure.help. With 2.4.2-ac18, this number is n
Hi all,
this patch removes panic() calls and adds MODULE_DEVICE_TABLE to cyclades driver.
Best regards.
--
Andrey Panin| Embedded systems software engineer
[EMAIL PROTECTED]| PGP key: http://www.orbita1.ru/~pazke/AndreyPanin.asc
--- /linux/drivers/char/cyclades.c.orig Sun
> This is the linux thread spinlock acquire :
>
>
> static void __pthread_acquire(int * spinlock)
> {
> int cnt = 0;
> struct timespec tm;
>
> while (testandset(spinlock)) {
> if (cnt < MAX_SPIN_COUNT) {
> sched_yield();
> cnt++;
> } else {
> tm.tv_sec = 0;
>
> So PCI interrupts must always be level triggered? If so, then the kernel
> should never program the IO APIC to use an edge triggered interrupt on a PCI
> device. If that's true, then why not force the interrupt type to level
> triggered for all PCI devices (to work around a potentially broken
> [1.] One line summary of the problem:
> RTL8029 based card stops receiving data after being flood pinged
This is probably the apparent hardware problem in the Intel APIC. There is
a workaround for it in 2.4.2-ac
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> Well, the kernel module is open source..
No the Nvidia kernel module is not. Try reading it, its obfuscated to point
of being binary, it contains no permission to modify or redistribute either.
In fact if you are using patched versions of it to make it work with later
kernels you may well be b
> Intel are being remarkably reluctant on the documentation front. We have
> the AMD speed change docs, but the intel ones (chipset not cpu based
> primarily) don't seem to be publically available. In fact the 815M manual
> looks like someone quite pointedly went through and removed the relevan
> But is there a reason we don't allow the notsc option at all on
> certain chipsets? Who would complain if I removed the CONFIG_X86_TSC
> option from the CONFIG_M686 definition or even got rid of it completely?
I believe someone had performance reasons. I'm sceptical and I'd tend to agree
with y
On Sun, 11 Mar 2001 06:37:10 -0700,
Steven Cole <[EMAIL PROTECTED]> wrote:
>On Sunday 11 March 2001 00:08, Jeff Garzik wrote:
>> Keith Owens wrote:
>> > If any of these CONFIG_ options are always derived (i.e. the user never
>> > sees them on a config menu) then please add the suffix _DERIVED to
On Sun, 11 Mar 2001, Andrew Morton wrote:
> Sorry, this doesn't look right. Are you sure you booted with
> `nmi_watchdog=1'? It was turned off by default in -ac18.
of course i did ...
> Two things:
>
> - CPU A could be doing the SYSRQ printing, while
> CPU B is spinning on a lock which CPU A
> >Make sure you have the following symlinks in your /usr/include
> >directory, assuming you're on an x86 machine:
> >
> >asm -> /usr/src/linux/include/asm-i386/
> >linux -> /usr/src/linux/include/linux/
>
> Note! You only have to have those symlinks on broken systems such
> as Redhat.
>
>
Bug report from Martin Bruchanov ([EMAIL PROTECTED], [EMAIL PROTECTED])
[1.] One line summary of the problem:
USB doesn't work properly with SMP kernel on dual-mainboard or with APIC.
##
On 9 Mar 2001, Kai Henningsen wrote:
[snip]
> And remember that other companies have been doing similar things since
> just about forever. It's not as if MS invented this thing.
>
> Or maybe I have to take that back. The "must not modify" clause certainly
> seems non-standard.
>
> AT&T Unix
I'm not sure exactly what happened to the machine as I was at work at the
time when it died I had just sshed in to read my daily spam box ;)
Here is the decoded captured oops (klogd provided):
Mar 11 09:36:33 tweetie kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00
Hi
If you don't pay attention (yeah, I know) Its easy to write
kernel commond lines like 'console=ttyS0, console=.., etc'
The lack of a baud rate after the comma causes the kernel
to panic. The patch below will cause the kernel in treat the
non-existant baud rate specifier as the default without
>From: Alan Cox <[EMAIL PROTECTED]>
>
> > So PCI interrupts must always be level triggered? If so, then the kernel
> > should never program the IO APIC to use an edge triggered interrupt on a
>PCI
> > device. If that's true, then why not force the interrupt type to level
> > triggered for all PCI
> maintainers about the problem. If this isn't ok, then maybe the sanity check
> in pci-irq.c would be to force level triggering only on shared PCI
> interrupts?
This seems a sensible path to take for such machines
> I'm going down this path because I can't see a good way to check for the
> p
On Mon, 12 Mar 2001, Anton Blanchard wrote:
> Perhaps we need something like sched_yield that takes off some of
> tsk->counter so the task with the spinlock will run earlier.
Personally speaking, I wish sched_yield() API was like so:
int sched_yield(pid_t pid);
The pid argument would be adviso
If do_mount() fails in the wrong place, the filesystem module count
is incremented twice, but decremented only once.
This patch agains 2.4.2 fixes the problem.
Jörgen
--- fs/super.c.orig Sun Mar 11 20:25:26 2001
+++ fs/super.c Sun Mar 11 20:05:27 2001
@@ -1414,6 +1414,8 @@
fail:
On Sun, 11 Mar 2001, John William wrote:
> If shared, edge triggered interrupts are ok then I will talk to the driver
> maintainers about the problem. If this isn't ok, then maybe the sanity check
> in pci-irq.c would be to force level triggering only on shared PCI
> interrupts?
DEFINITELY
Hi,
I wrote brief document describing porting 2.2 device driver to 2.4
It contains changes from 2.2 to 2.4 including devfs, /proc, block device
driver, etc.
I'm not a kernel hacker, so there may be errors due to my
misunderstanding.
I'd be grateful if anyone points out and corrects the errors, a
Hi,
Below is a patch which I think fixes the NBD hangs properly. It works for
me and doesn't need any changes to ll_rw_blk.c like my last patch did. I've
shown it to Pavel Machek who has approved it. The patch is against 2.4.2-ac18.
Pavel: I've made the change you requested and also added a flag
On Fri, 9 Mar 2001, W. Michael Petullo wrote:
> If you have or have access to a Linux box with a Venus-based modem,
> answering any of these questions would be very helpful:
>
Well, I'm not absolutely sure if we are talking about the same thing: what
I have is a re-labeled PC-Card modem which
The Digiboard EPCA driver supplied with Linux 2.4.x didn't work for
me, so I took the latest Digi driver and patched it to make it
work with 2.4 and devfs. I'm sure that I managed to horribly
break some stuff, but hey, it works for me. The patch to their
latest (4001450M) driver is included
On Fri, 9 Mar 2001, Lawrence MacIntyre wrote:
> Uniform MultiPlatform E-IDE driver Revision 6.31
> ide: assuminmg 33 MHz system bus speed for PIO modes: override with
> idebus=xx
> SIS5513: IDE controller on PCI bus 00 dev 09
> PCI: Assigned IRQ 14 for device 00:01.1
> SIS5513: chipset revision 2
Hi,
i wrote:
> EIP:0010:[__mark_inode_dirty+92/112]
> EFLAGS: 00010202
> eax: ebx: cc85b240 ecx: cc85b428 edx: cc85b248
> esi: c15dc200 edi: 0001 ebp: c361dfa4 esp: c361df24
This is a bit-flipper. There is a valid super-block entry at c14dc200.
Mich
On Sun, Mar 11, 2001 at 10:03:48PM +0100, Martin Diehl wrote:
> On Fri, 9 Mar 2001, Lawrence MacIntyre wrote:
>
> > Uniform MultiPlatform E-IDE driver Revision 6.31
> > ide: assuminmg 33 MHz system bus speed for PIO modes: override with
> > idebus=xx
> > SIS5513: IDE controller on PCI bus 00 dev
On 11-Mar-2001 Anton Blanchard wrote:
>
>> This is the linux thread spinlock acquire :
>>
>>
>> static void __pthread_acquire(int * spinlock)
>> {
>> int cnt = 0;
>> struct timespec tm;
>>
>> while (testandset(spinlock)) {
>> if (cnt < MAX_SPIN_COUNT) {
>> sched_yield();
>>
On 11-Mar-2001 Anton Blanchard wrote:
>
>> This is the linux thread spinlock acquire :
>>
>>
>> static void __pthread_acquire(int * spinlock)
>> {
>> int cnt = 0;
>> struct timespec tm;
>>
>> while (testandset(spinlock)) {
>> if (cnt < MAX_SPIN_COUNT) {
>> sched_yield();
>>
On 11-Mar-2001 Dave Zarzycki wrote:
> On Mon, 12 Mar 2001, Anton Blanchard wrote:
>
>> Perhaps we need something like sched_yield that takes off some of
>> tsk->counter so the task with the spinlock will run earlier.
>
> Personally speaking, I wish sched_yield() API was like so:
>
> int sched_
Jochen Dolze writes:
> i found at http://acl.bestbits.at the ACL-linux-project. Now i want to know,
> if there is a plan to integrate posix-ACLs into the fs-part of the kernel,
> e.g. into the VFS-Layer? Is there a general discussion about this anywhere?
> What are the biggest problems? (i know t
Hi,
On Sun, Mar 11, 2001 at 04:37:10PM +0800, ³¯¤ý®i wrote:
> The driver has not to be included in officeal kernel.
Yes, that's what I tell people that ask me to submit the driver from
inclusion. The reason are strange problems, which unfortunately I have not
been able to track down, yet. Fortun
> > when I burn CDRs. Some files burned is different from the origin at HD.
> > I use 2.2.17 with Tekram's driver,and nothing is wrong.
>
> Indeed; people report more problems on 2.4 kernels than on 2.2 kernels. I
> currently have no clue why.
2.4 causes longer continuous I/O requests to be sent
> While compiling the vmnet module, there is a warning
>
> make: Entering directory `/tmp/vmware-config2/vmnet-only'
> bridge.c: In function `VNetBridgeReceiveFromDev':
> bridge.c:788: warning: implicit declaration of function `skb_datarefp'
>
> and while inserting the module
>
> /tmp/vmware-co
In article you wrote:
> What are the biggest problems? (i know that many userland-tools must be
> changed for this).
AFAIK there is no Support in User Land Programs required. You just have
additional tools for managing the ACLs . The main problem
I couldn't trace that down to be 100% sure and it's better to conform to
design than implementation, so I'll ask:
Do the probe and remove functions of a pci_driver have to be able to
work in interrupt context? (i.e. GFP_ATOMIC and stuff)
I expect so, since CardBus handling doesn't start a thre
Geert Uytterhoeven writes:
> - The colors for the 16 color logo are wrong. We used a hack to
> give the logo its own color palette, but this no longer works
> as a side effect of a console color map bug being fixed a while
> ago. The solution is to replace the logo with a new one th
Attached patch is required to make ipx compile in 2.4.2-ac18.
Appologies if this has been fixed already.
Best regards,
Anton
--
Anton Altaparmakov (replace at with @)
Linux NTFS maintainer / WWW: http://sourceforge.net/projects/linux-ntfs/
ICQ: 8561279 / WWW: http://www-stu.christs.ca
Hi,
> 2.4.x has changed the scheduler behaviour so that the task that call
> sched_yield() is not rescheduled by the incoming schedule(). A flag is
> set ( under certain conditions in SMP ) and the goodness() calculation
> assign the lower value to the exiting task ( this flag is cleared in
>
Hello
My work will concern with the internationalization of Linux
So, could anybody tell me what kinds of features should be in the
consideration when linux be localized from english to Japanese or chinese,
say using 2 bytes character set.
Thanks a lot
-
To unsubscribe from this list: send the lin
> My work will concern with the internationalization of Linux
> So, could anybody tell me what kinds of features should be in the
> consideration when linux be localized from english to Japanese or chinese,
> say using 2 bytes character set.
Most of the Linux userspace libraries are set up for ha
On a compile of 2.4.2 I get the following (using make bzImage)
make[2]: Leaving directory `/usr/src/linux-2.4.2/linux/arch/i386/lib'
make[1]: Leaving directory `/usr/src/linux-2.4.2/linux/arch/i386/lib'
ld -m elf_i386 -T /usr/src/linux-2.4.2/linux/arch/i386/vmlinux.lds -e stext
arch/i386/kernel
Andreas Bombe wrote:
>
> I couldn't trace that down to be 100% sure and it's better to conform to
> design than implementation, so I'll ask:
>
> Do the probe and remove functions of a pci_driver have to be able to
> work in interrupt context? (i.e. GFP_ATOMIC and stuff)
No, no interrupt contex
hi all,
In my module the code as below ...syntax code from alasandro rubini
...I hope all arguments are not necessary to be initialised
struct device my_dev =
{
myne_name,
0,0,0,0,
Keith Owens wrote:
>
> On Sun, 11 Mar 2001 08:44:24 +0100 (CET),
> Ingo Molnar <[EMAIL PROTECTED]> wrote:
> >Andrew,
> >
> >your patch looks too complex, and doesnt cover the case of the serial
> >driver deadlocking. Why not add a "touch_nmi_watchdog_counter()" function
> >that just changes last_
On Sun, Mar 11, 2001 at 06:06:24PM +0100, Martin Bruchanov wrote:
>
> Bug report from Martin Bruchanov ([EMAIL PROTECTED], [EMAIL PROTECTED])
>
>
> [1.] One line summary of the problem:
> USB doesn't work properly w
I have not been able to run quotas for several versions of 2.2.x now. I
always get stuff like:
Mar 11 18:56:17 turing kernel: Unable to handle kernel paging request at virtual
address 6c206f8f
Mar 11 18:56:17 turing kernel: current->tss.cr3 = 2b4e1000, %%cr3 = 2b4e1000
Mar 11 18:56:17 turing k
>> My work will concern with the internationalization of Linux
>> So, could anybody tell me what kinds of features should be in the
>> consideration when linux be localized from english to Japanese or
chinese,
>> say using 2 bytes character set.
>
>Most of the Linux userspace libraries are set up
"Albert D. Cahalan" wrote:
>
> Geert Uytterhoeven writes:
>
> > - The colors for the 16 color logo are wrong. We used a hack to
> > give the logo its own color palette, but this no longer works
> > as a side effect of a console color map bug being fixed a while
> > ago. The solutio
On Sun, 11 Mar 2001 20:43:16 -0800,
george anzinger <[EMAIL PROTECTED]> wrote:
>Consider this. Why not use the NMI to sync the cpus. Kdb would have a
>function that is called each NMI.
kdb uses NMI IPI to get the other cpu's attention. One cpu is in
control and may or may not be accepting NMI
Alan Cox wrote:
>
> > My work will concern with the internationalization of Linux
> > So, could anybody tell me what kinds of features should be in the
> > consideration when linux be localized from english to Japanese or chinese,
> > say using 2 bytes character set.
>
> Most of the Linux usersp
In 2.4.2-ac18 there are 130 CONFIG options that are always derived from
other options, the user has no control over them. It is useful for the
kernel build process to know which variables are derived and which
variables the user can control. There are also 6 CONFIG options that
are not used anyw
Odd problem: Guaranteed Oops on my "pathological file system" (a monster ext2)
System: Athlon tbird 1100 MHz
GA 79X motherboard (with the notorious VIA kt133 chipset)
this problem with a very minimal 2.4.2 install except with
Pavlich's v4.3 via82cxxx.c driver (same probl
Keith Owens wrote:
>
> In 2.4.2-ac18 there are 130 CONFIG options that are always derived from
> other options, the user has no control over them. It is useful for the
> kernel build process to know which variables are derived and which
> variables the user can control. There are also 6 CONFIG
On Sun, 11 Mar 2001, Steven Walter wrote:
> > on insmod). This is with SiS5513 rev 208 IDE function from SiS5591
> > chipset with CONFIG_BLK_DEV_SIS5513 and autotune enabled (default).
>
> I have this exact same chip on my board (a PCChips M599-LMR or something
> like that) which works flawless
Hi,
I am not exactly new to linux, but right now I am clueless.
I have been running Kernel 2.4.0ac4 for a while and now I tried to
upgrade to 2.4.2. Everything went well, but after boot, I can not use
the keyboard. I can not type a thing, the only way to reboot is to hit
the reset switch.
The key
The linkage of vmlinux fails with lacking code for bust_spinlocks(),
thus I cloned the i386 one as is -- which apparently is not really
processor specific...
--- arch/alpha/mm/fault.c~ Sun Mar 11 11:49:23 2001
+++ arch/alpha/mm/fault.c Sun Mar 11 14:46:39 2001
@@ -231,3 +231,39 @@
68 matches
Mail list logo