On Wed, 7 Feb 2007, Andrew Morton wrote:
On Thu, 8 Feb 2007 00:02:10 +0100 (CET) Lukasz Trabinski <[EMAIL PROTECTED]>
wrote:
Hello
On 2.6.19 I had about 60 days uptime, on 2.6.20 2 days :(
Did the machine actually fail? Or did it just print these messages and
keep going?
Was m
On Wed, 7 Feb 2007, Andrew Morton wrote:
On Thu, 8 Feb 2007 00:02:10 +0100 (CET) Lukasz Trabinski [EMAIL PROTECTED]
wrote:
Hello
On 2.6.19 I had about 60 days uptime, on 2.6.20 2 days :(
Did the machine actually fail? Or did it just print these messages and
keep going?
Was message
Hello
On 2.6.19 I had about 60 days uptime, on 2.6.20 2 days :(
oceanic:~$ uname -a
Linux oceanic.wsisiz.edu.pl 2.6.20-oceanic #2 SMP Sun Feb 4 21:55:29 CET
2007 x86_64 x86_64 x86_64 GNU/Linux
Feb 7 22:46:00 oceanic kernel: BUG: soft lockup detected on CPU#0!
Feb 7 22:46:00 oceanic
Hello
On 2.6.19 I had about 60 days uptime, on 2.6.20 2 days :(
oceanic:~$ uname -a
Linux oceanic.wsisiz.edu.pl 2.6.20-oceanic #2 SMP Sun Feb 4 21:55:29 CET
2007 x86_64 x86_64 x86_64 GNU/Linux
Feb 7 22:46:00 oceanic kernel: BUG: soft lockup detected on CPU#0!
Feb 7 22:46:00 oceanic
On Sun, 30 Jan 2005, chas williams - CONTRACTOR wrote:
Hello again
good to hear. what does atmdiag say about that interface? does it have
a large percentage of tx drops?
After one month work without oops, we have experienced oops again. It
happen when one or more VC is down (for example on atm
On Sun, 30 Jan 2005, chas williams - CONTRACTOR wrote:
Hello again
good to hear. what does atmdiag say about that interface? does it have
a large percentage of tx drops?
After one month work without oops, we have experienced oops again. It
happen when one or more VC is down (for example on atm
On Sun, 30 Jan 2005, chas williams - CONTRACTOR wrote:
In message <[EMAIL PROTECTED]>,Lukasz Trabinski writes:
OK, I think that dirver works much better with udelay() function.
good to hear. what does atmdiag say about that interface? does it have
a large percentage of tx drops?
After 12
On Tue, 25 Jan 2005, Lukasz Trabinski wrote:
Ok, i have just put udelay() function to the driver. If router will not crash
after 5-6 days, it mean that driver works fine. I will inform about
it. Generally problems has stareted (frequently crashes) when we puted to
them more atm interfaces/VCs
On Mon, 24 Jan 2005, chas williams - CONTRACTOR wrote:
the author sent me the latest version of the driver and i
got it applied. the driver does has some useful changes
along with this broken change. i suggest udelay() since
it preserves the author's original intent.
Ok, i have just put udelay()
On Mon, 24 Jan 2005, chas williams - CONTRACTOR wrote:
the author sent me the latest version of the driver and i
got it applied. the driver does has some useful changes
along with this broken change. i suggest udelay() since
it preserves the author's original intent.
Ok, i have just put udelay()
On Tue, 18 Jan 2005, chas williams - CONTRACTOR wrote:
the system keeps running right? the error is a 'warning' that the
fore200e is driver is sleeping when it should not (probably while holding
interrupts). the schedule() around like 1782 is not a good idea since
the fore200e_send() might not
On Tue, 18 Jan 2005, chas williams - CONTRACTOR wrote:
the system keeps running right? the error is a 'warning' that the
fore200e is driver is sleeping when it should not (probably while holding
interrupts). the schedule() around like 1782 is not a good idea since
the fore200e_send() might not
Hello
Lately we have problem with our router. For me it's look like driver
fore200e problems. We know that's not a hardware problem.
Below is fragment from logs file. Unfortunately I don't know
how to use ksymoops with 2.6.X kernels :/
System is Fedora Core 2, 2 x Pentium 3.00GHz, 1 GB RAM, 0,5
Hello
Lately we have problem with our router. For me it's look like driver
fore200e problems. We know that's not a hardware problem.
Below is fragment from logs file. Unfortunately I don't know
how to use ksymoops with 2.6.X kernels :/
System is Fedora Core 2, 2 x Pentium 3.00GHz, 1 GB RAM, 0,5
In article <87771.991317458@tiny> you wrote:
>> portraits:~# dmesg
>> vs-13042: reiserfs_read_inode2: [2299 593873 0x0 SD] not found
>> vs-13048: reiserfs_iget: bad_inode. Stat data of (2299 593873) not found
>> vs-13042: reiserfs_read_inode2: [2299 593807 0x0 SD] not found
>> vs-13048:
Hello
What it's means?
portraits:~# dmesg
vs-13042: reiserfs_read_inode2: [2299 593873 0x0 SD] not found
vs-13048: reiserfs_iget: bad_inode. Stat data of (2299 593873) not found
vs-13042: reiserfs_read_inode2: [2299 593807 0x0 SD] not found
vs-13048: reiserfs_iget: bad_inode. Stat data of (2299
Hello
What it's means?
portraits:~# dmesg
vs-13042: reiserfs_read_inode2: [2299 593873 0x0 SD] not found
vs-13048: reiserfs_iget: bad_inode. Stat data of (2299 593873) not found
vs-13042: reiserfs_read_inode2: [2299 593807 0x0 SD] not found
vs-13048: reiserfs_iget: bad_inode. Stat data of (2299
In article 87771.991317458@tiny you wrote:
portraits:~# dmesg
vs-13042: reiserfs_read_inode2: [2299 593873 0x0 SD] not found
vs-13048: reiserfs_iget: bad_inode. Stat data of (2299 593873) not found
vs-13042: reiserfs_read_inode2: [2299 593807 0x0 SD] not found
vs-13048: reiserfs_iget:
Hello
There is two "Oops" from user's space (pine,epic) programs. On 2.2.x
kernels, on this machine, it had never happened.
(2.4.5 #1 SMP Pentium III (Coppermine), 800MHz, RH 7.1, gcc 2.96)
ksymoops 2.4.0 on i686 2.4.5. Options used
-V (default)
-k /proc/ksyms (default)
-l
In article <[EMAIL PROTECTED]> you wrote:
> Okay, so Jeff Garzik already knows about this - I told him last week -
> but seeing as how the code has made it to a Linus pre-release without
> a fix I thought I'd better post the breakage description to l-k!
Try drivers from
In article [EMAIL PROTECTED] you wrote:
Okay, so Jeff Garzik already knows about this - I told him last week -
but seeing as how the code has made it to a Linus pre-release without
a fix I thought I'd better post the breakage description to l-k!
Try drivers from
In article <[EMAIL PROTECTED]> you wrote:
> This is only with kernel 2.4.4; 2.4.2, 2.4.3 and NetBSD boxes are not
> affected. It is independent of platform; I've reproduced it at will on a
> lowly p75, an athlon, a p3-800 and on a powerbook/PPC.
I have just reproduced that on 2.4.5pre-1. It was
In article [EMAIL PROTECTED] you wrote:
This is only with kernel 2.4.4; 2.4.2, 2.4.3 and NetBSD boxes are not
affected. It is independent of platform; I've reproduced it at will on a
lowly p75, an athlon, a p3-800 and on a powerbook/PPC.
I have just reproduced that on 2.4.5pre-1. It was only
In article <[EMAIL PROTECTED]> you wrote:
> Kernel 2.4.4-pre6, 2.2.2-10, 0.74-22 - RedHat 7.1
Little update to my last mail: glibc 2.2.2-10, PAM 0.74-22 - RedHat 7.1.
--
*[ ukasz Trbiski ]*
SysAdmin @wsisiz.edu.pl
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
In article <[EMAIL PROTECTED]> you wrote:
> I'm having a problem with "su -" on ac11/ac12. ac5 doesn't show the
> problem.
> The problem is easy to reproduce - go to a console, log in as root, do an
> "su -" (this will succeed) and then another "su -". The second "su -"
> should hang - ps shows
In article [EMAIL PROTECTED] you wrote:
I'm having a problem with "su -" on ac11/ac12. ac5 doesn't show the
problem.
The problem is easy to reproduce - go to a console, log in as root, do an
"su -" (this will succeed) and then another "su -". The second "su -"
should hang - ps shows it
Hello
I'm using 2.4.2 and 2.4.3, sometimes after cron jobs like slocate process
or checking md5sum on my file system(heavy load disk), i gets errors from
the kernel:
EXT2-fs error (device sd(8,3)): ext2_free_blocks: bit already cleared for
block
80275
EXT2-fs error (device sd(8,3)):
Hello
I'm using 2.4.2 and 2.4.3, sometimes after cron jobs like slocate process
or checking md5sum on my file system(heavy load disk), i gets errors from
the kernel:
EXT2-fs error (device sd(8,3)): ext2_free_blocks: bit already cleared for
block
80275
EXT2-fs error (device sd(8,3)):
In article <007101c09ce4$39dc7680$[EMAIL PROTECTED]> you wrote:
> Linux-2.4.2 does not have IPv6 support ???
[root@lt /root]# ping6 3ffe:8010:19::2:2
PING 3ffe:8010:19::2:2(3ffe:8010:19::2:2) from ::1 : 56 data bytes
64 bytes from 3ffe:8010:19::2:2: icmp_seq=0 hops=64 time=84 usec
64 bytes from
In article 007101c09ce4$39dc7680$[EMAIL PROTECTED] you wrote:
Linux-2.4.2 does not have IPv6 support ???
[root@lt /root]# ping6 3ffe:8010:19::2:2
PING 3ffe:8010:19::2:2(3ffe:8010:19::2:2) from ::1 : 56 data bytes
64 bytes from 3ffe:8010:19::2:2: icmp_seq=0 hops=64 time=84 usec
64 bytes from
Hello
In linux/drivers/scsi/hosts.c we have line:
#include "aic7xxx.h" and during compilation we gets a error:
hosts.c:139: aic7xxx.h: No such file or directory
hosts.c:500: `AIC7XXX' undeclared here (not in a function)
hosts.c:500: initializer element for `builtin_scsi_hosts[0]' is not
Hello
In linux/drivers/scsi/hosts.c we have line:
#include "aic7xxx.h" and during compilation we gets a error:
hosts.c:139: aic7xxx.h: No such file or directory
hosts.c:500: `AIC7XXX' undeclared here (not in a function)
hosts.c:500: initializer element for `builtin_scsi_hosts[0]' is not
In article <[EMAIL PROTECTED]> you wrote:
> On Tue, Jan 16, 2001 at 07:02:52PM -0800, Kostas Nikoloudakis wrote:
>> The machine is running under heavy CPU + memory + network load.
>> It seems that the card has problems finding the required resources.
>> Is there a way to "guarantee" that the
In article [EMAIL PROTECTED] you wrote:
On Tue, Jan 16, 2001 at 07:02:52PM -0800, Kostas Nikoloudakis wrote:
The machine is running under heavy CPU + memory + network load.
It seems that the card has problems finding the required resources.
Is there a way to "guarantee" that the card will
Hello
Today my important machine has dicsonneted from network with message
like this:
Jan 13 12:24:25 portraits kernel: eth0: can't fill rx buffer (force 0)!
Jan 13 12:24:25 portraits kernel: eth0: can't fill rx buffer (force 1)!
Jan 13 12:24:26 portraits kernel: eth0: can't fill rx buffer
Hello
Today my important machine has dicsonneted from network with message
like this:
Jan 13 12:24:25 portraits kernel: eth0: can't fill rx buffer (force 0)!
Jan 13 12:24:25 portraits kernel: eth0: can't fill rx buffer (force 1)!
Jan 13 12:24:26 portraits kernel: eth0: can't fill rx buffer
In article <[EMAIL PROTECTED]> you wrote:
> When I initiate connection from Solaris machine everything goes OK.
> TCP/SYN,ACK segments are OK.
> Can anyone help me?
> Does:
> bash# echo "0" >/proc/sys/net/ipv4/tcp_ecn
Or maybe it?
echo "1" > /proc/sys/net/ipv4/ip_no_pmtu_disc
--
*[
In article [EMAIL PROTECTED] you wrote:
When I initiate connection from Solaris machine everything goes OK.
TCP/SYN,ACK segments are OK.
Can anyone help me?
Does:
bash# echo "0" /proc/sys/net/ipv4/tcp_ecn
Or maybe it?
echo "1" /proc/sys/net/ipv4/ip_no_pmtu_disc
--
*[ ukasz
On Sat, 16 Dec 2000, Tim Waugh wrote:
> > -#define PCI_DEVICE_ID_OXSEMI_16PCI954PP0x9513
> > +#define PCI_DEVICE_ID_OXSEMI_16PCI954 0x9513
>
> Alan, do not apply, this will break the parport code.
>
> If the OXSEMI_16PCI954 is _missing_, it probably ought to be _added_,
> but it does not
Hello
I'm tring to use serial driver 5.05 with kernel in version
2.2.18. There is a little problem with vendor definition in kernel source.
In serial dirver from Theodore Ts'o we have:
{ PCI_VENDOR_ID_SPECIALIX, PCI_DEVICE_ID_OXSEMI_16PCI954,
Hello
I'm tring to use serial driver 5.05 with kernel in version
2.2.18. There is a little problem with vendor definition in kernel source.
In serial dirver from Theodore Ts'o we have:
{ PCI_VENDOR_ID_SPECIALIX, PCI_DEVICE_ID_OXSEMI_16PCI954,
In article <[EMAIL PROTECTED]> you wrote:
> I can (re)confirm that. I work several hours on console without any
> problem ... then I start X session and after several minutes system
> hangs.
I can confirm that, too.
Todaye, crashed two difference machines
One: AMD-K6 3D, 300 MHz, RH 7.0 +
In article [EMAIL PROTECTED] you wrote:
I can (re)confirm that. I work several hours on console without any
problem ... then I start X session and after several minutes system
hangs.
I can confirm that, too.
Todaye, crashed two difference machines
One: AMD-K6 3D, 300 MHz, RH 7.0 + updates,
In article <[EMAIL PROTECTED]> you wrote:
>
> You can't build a kernel with that compiler. You _must_ use gcc
> 2.91.66 or another compiler that can compile the kernel. Red Hat
> ships gcc 2.91.66 packaged as "kgcc" for kernel builds as do
> other major vendors.
Huh, no way,
In article [EMAIL PROTECTED] you wrote:
You can't build a kernel with that compiler. You _must_ use gcc
2.91.66 or another compiler that can compile the kernel. Red Hat
ships gcc 2.91.66 packaged as "kgcc" for kernel builds as do
other major vendors.
Huh, no way, I have
Hello
There is probably not a kernel bug, but bug in gcc, but... :)
[root@beer linux]# make bzImage
[snip]
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=i686-DEXPORT_SYMTAB -c
Hello
There is probably not a kernel bug, but bug in gcc, but... :)
[root@beer linux]# make bzImage
[snip]
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=i686-DEXPORT_SYMTAB -c
On Tue, 28 Nov 2000, Francois romieu wrote:
> > NETDEV WATCHDOG: eth0: transmit timed out
> > eth0: Transmit timeout using MII device, Tx status 0003.
> > eth0: Restarting the EPIC chip, Rx 4568454/4568454 Tx 6262613/6262623.
> > eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt
In article <20001128042134.A1041@twoey> you wrote:
> Using 2.4-test10 I got a series of timeout errors on my tulip network
> card (Linksys LNE version 4, 00:0d.0 Ethernet controller: Bridgecom,
> Inc: Unknown device 0985 (rev 11)). Networking then completely stopped
> working. Restarting the
In article 20001128042134.A1041@twoey you wrote:
Using 2.4-test10 I got a series of timeout errors on my tulip network
card (Linksys LNE version 4, 00:0d.0 Ethernet controller: Bridgecom,
Inc: Unknown device 0985 (rev 11)). Networking then completely stopped
working. Restarting the interface
On Tue, 28 Nov 2000, Francois romieu wrote:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout using MII device, Tx status 0003.
eth0: Restarting the EPIC chip, Rx 4568454/4568454 Tx 6262613/6262623.
eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt 24.
51 matches
Mail list logo
