serial ports in 2.4.x
Hi folks, I don't _exactly_ know if this might be an issue for the kernel. However, I noticed that I used to be able to download pictures of my digicam (nikon 600) via /dev/ttySx to the box using gphoto 0.4.3 all the time. At some point, unfortunately I don't recall if it happened while switching from 2.2.17 to 2.4 at all or within the 2.4.x series, I was unable to get any connection to my cam (both up and smp, even same problem on two different systems, one gigabyte vxd7, the other gigabyte bx). It used to work just fine, so anything changed for support of serial ports (serial.c claims no)? Maybe anything related with devfsd, which I switched at the same time as 2.2 to 2.4? Any other interaction which might have caused this? Another symptom is that after I tried to use the port with the digicam (which failed), the port is unusable. The otherwise working connection to the palm doesn't work anymore, a reboot is required to get it back to work. Speed setting of the port is not the issue right here: 1. it used to work without special settings 2. I tried different speed settings (very slow to 115k) And, of course, it doesn't work with the original software from nikon via wine. The orig soft does work under win . Nonetheless, the UPS connected to one port via wired wiring (no real serial protocol used, just certain lines high/low) does work even after the port was used with the digicam and rendered useless for the palm. If any other info is needed, let me know. Unfortunately, I'm currently unable to boot into 2.2.17 because I'm using devfsd and was not able to apply that patch correctly on a plain vanilla kernel, but that I'm not worried about 'cause 2.4.4 runs pretty decent otherwise on both boxes. -- Tschoe,Get my gpg-public-key here Jens http://gecius.de/gpg-key.txt - 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 read the FAQ at http://www.tux.org/lkml/
serial ports in 2.4.x
Hi folks, I don't _exactly_ know if this might be an issue for the kernel. However, I noticed that I used to be able to download pictures of my digicam (nikon 600) via /dev/ttySx to the box using gphoto 0.4.3 all the time. At some point, unfortunately I don't recall if it happened while switching from 2.2.17 to 2.4 at all or within the 2.4.x series, I was unable to get any connection to my cam (both up and smp, even same problem on two different systems, one gigabyte vxd7, the other gigabyte bx). It used to work just fine, so anything changed for support of serial ports (serial.c claims no)? Maybe anything related with devfsd, which I switched at the same time as 2.2 to 2.4? Any other interaction which might have caused this? Another symptom is that after I tried to use the port with the digicam (which failed), the port is unusable. The otherwise working connection to the palm doesn't work anymore, a reboot is required to get it back to work. Speed setting of the port is not the issue right here: 1. it used to work without special settings 2. I tried different speed settings (very slow to 115k) And, of course, it doesn't work with the original software from nikon via wine. The orig soft does work under win argh. Nonetheless, the UPS connected to one port via wired wiring (no real serial protocol used, just certain lines high/low) does work even after the port was used with the digicam and rendered useless for the palm. If any other info is needed, let me know. Unfortunately, I'm currently unable to boot into 2.2.17 because I'm using devfsd and was not able to apply that patch correctly on a plain vanilla kernel, but that I'm not worried about 'cause 2.4.4 runs pretty decent otherwise on both boxes. -- Tschoe,Get my gpg-public-key here Jens http://gecius.de/gpg-key.txt - 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 read the FAQ at http://www.tux.org/lkml/
Re: Longstanding APIC/NE2K bug
[EMAIL PROTECTED] writes: > There has been a bug in the 2.4.x series of kernels for a long time (at > least -pre9) concerning SMP and ne2k-pci. > > Maciej W. Rozycki posted a patch back during 2.4.0 that fixed this problem > "[patch] 2.4.0, 2.4.0-ac12: APIC lock-ups" in late January. I've been > trying new kernels regularly since, and the patch doesn't seem to have > made it in (tested 2.4.2, .3, .4 and .5). Falling back on my patched > 2.4.0 works fine. > > Symptoms: Network driver locks up. Repeated messages of "ETH0: Transmit > timeout" occurs. Unloading and reloading network drivers does not help, > reboot is required. Usually only triggered by heavy network traffic > (300-400 megs at 700k or so usually does it). This fits exactly my problems I mentioned a couple weeks ago. Same question here. Therefore my question: can we expect to see this patch implemented? If not, any other suggestions? -- Tschoe,Get my gpg-public-key here Jens http://gecius.de/gpg-key.txt - 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 read the FAQ at http://www.tux.org/lkml/
Re: Longstanding APIC/NE2K bug
[EMAIL PROTECTED] writes: There has been a bug in the 2.4.x series of kernels for a long time (at least -pre9) concerning SMP and ne2k-pci. Maciej W. Rozycki posted a patch back during 2.4.0 that fixed this problem [patch] 2.4.0, 2.4.0-ac12: APIC lock-ups in late January. I've been trying new kernels regularly since, and the patch doesn't seem to have made it in (tested 2.4.2, .3, .4 and .5). Falling back on my patched 2.4.0 works fine. Symptoms: Network driver locks up. Repeated messages of ETH0: Transmit timeout occurs. Unloading and reloading network drivers does not help, reboot is required. Usually only triggered by heavy network traffic (300-400 megs at 700k or so usually does it). This fits exactly my problems I mentioned a couple weeks ago. Same question here. Therefore my question: can we expect to see this patch implemented? If not, any other suggestions? -- Tschoe,Get my gpg-public-key here Jens http://gecius.de/gpg-key.txt - 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 read the FAQ at http://www.tux.org/lkml/
Re: 2.4.4 kernel freeze
Stephan Brauss <[EMAIL PROTECTED]> writes: > > Any other hints are welcome (other than the noapic, which didn't help). > My system is always completely dead as soon as I start a larger (interrupt > driven?) data transfer to/from any (? I tested with two different NICs and a Promise > Ultra100) PCI card in slot 4 or 5. And it seems that it really only occurs > in slots 4 and 5... To get rid of it, I switched to 2.2.19. I couldn't. Problems getting devfsd patched in 2.2.19 :-( - and I'm going on vacation in shortly... Now after the last couple of "lost interrupts" I set a debian-stable as my primary firewall/router box in front of my server - this way I got rid of the second nic and freed both slot 4 and 5. Unfortunately, after a couple hours running my box again lost irq :-(. And there's no obvious huge transfer going on. The boxes were just alone. Now I try again noapic (different setup). Hope that works. Otherwise I'm kind of lost... -- Tschoe,Get my gpg-public-key here Jens http://gecius.de/gpg-key.txt - 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 read the FAQ at http://www.tux.org/lkml/
Re: 2.4.4 kernel freeze
Stephan Brauss [EMAIL PROTECTED] writes: Any other hints are welcome (other than the noapic, which didn't help). My system is always completely dead as soon as I start a larger (interrupt driven?) data transfer to/from any (? I tested with two different NICs and a Promise Ultra100) PCI card in slot 4 or 5. And it seems that it really only occurs in slots 4 and 5... To get rid of it, I switched to 2.2.19. I couldn't. Problems getting devfsd patched in 2.2.19 :-( - and I'm going on vacation in shortly... Now after the last couple of lost interrupts I set a debian-stable as my primary firewall/router box in front of my server - this way I got rid of the second nic and freed both slot 4 and 5. Unfortunately, after a couple hours running my box again lost irq :-(. And there's no obvious huge transfer going on. The boxes were just alone. Now I try again noapic (different setup). Hope that works. Otherwise I'm kind of lost... -- Tschoe,Get my gpg-public-key here Jens http://gecius.de/gpg-key.txt - 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 read the FAQ at http://www.tux.org/lkml/
Re: 2.4.4 kernel freeze
Jens Gecius <[EMAIL PROTECTED]> writes: > > > what do you mean by freeze? in theory, the fact that the irq > > I cannot ping the machine anymore, no Ooops, no kernel messages, the > > attached screen is freezed (which implies that no more interrupts > > are handled, right?) > > Excuse me hopping in. > > I have that situation here, too. Screen frozen, no pings from the > local network, sysrq doesn't work (keyboard dead). > > maniac kernel: NETDEV WATCHDOG: eth1: transmit timed out > maniac kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, > t=21. > > All this happened on 2.4.3 and 2.4.4 (don't excactly remember on > earlier 2.4). > > I followed your suggestion regarding PCI-slots. Both my nics used to > use PCI 4 and 5 (on a gigabyte vxd7, dual 1GHz). Only the one in slot > 4 had the problems. I switched the card to slot 1 and will monitor the > situation. I'll mail the list in case it doesn't change my situation. OK - now it even got worse. After just a couple hours slot5 was dead (that was the one working just fine with the other card in slot4). Three minutes later slot1 was dead, too. Both cards share irq12. Fortunately, the box wasn't frozen this time. X was up and running fine and I was able to reboot in a sound manner. I'll try another change in slots, but unfortunately, my nics are the ones with the lowest traffic: one other is SCSI, the other one firewire... (even though the latter one is hardly used). > Any other hints are welcome (other than the noapic, which didn't help). I have to reiterate this one. Any hints are very welcome. -- Tschoe,Get my gpg-public-key here Jens http://gecius.de/gpg-key.txt - 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 read the FAQ at http://www.tux.org/lkml/
Re: 2.4.4 kernel freeze
Jens Gecius [EMAIL PROTECTED] writes: what do you mean by freeze? in theory, the fact that the irq I cannot ping the machine anymore, no Ooops, no kernel messages, the attached screen is freezed (which implies that no more interrupts are handled, right?) Excuse me hopping in. I have that situation here, too. Screen frozen, no pings from the local network, sysrq doesn't work (keyboard dead). maniac kernel: NETDEV WATCHDOG: eth1: transmit timed out maniac kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=21. All this happened on 2.4.3 and 2.4.4 (don't excactly remember on earlier 2.4). I followed your suggestion regarding PCI-slots. Both my nics used to use PCI 4 and 5 (on a gigabyte vxd7, dual 1GHz). Only the one in slot 4 had the problems. I switched the card to slot 1 and will monitor the situation. I'll mail the list in case it doesn't change my situation. OK - now it even got worse. After just a couple hours slot5 was dead (that was the one working just fine with the other card in slot4). Three minutes later slot1 was dead, too. Both cards share irq12. Fortunately, the box wasn't frozen this time. X was up and running fine and I was able to reboot in a sound manner. I'll try another change in slots, but unfortunately, my nics are the ones with the lowest traffic: one other is SCSI, the other one firewire... (even though the latter one is hardly used). Any other hints are welcome (other than the noapic, which didn't help). I have to reiterate this one. Any hints are very welcome. -- Tschoe,Get my gpg-public-key here Jens http://gecius.de/gpg-key.txt - 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 read the FAQ at http://www.tux.org/lkml/
Re: 2.4.4 kernel freeze
Stephan Brauss <[EMAIL PROTECTED]> writes: > > what do you mean by freeze? in theory, the fact that the irq > I cannot ping the machine anymore, no Ooops, no kernel messages, the > attached screen is freezed (which implies that no more interrupts > are handled, right?) Excuse me hopping in. I have that situation here, too. Screen frozen, no pings from the local network, sysrq doesn't work (keyboard dead). BUT: the other interface (internet) works just fine. When I look in the logs afterwards, I find everything worked fine except the following: maniac kernel: NETDEV WATCHDOG: eth1: transmit timed out maniac kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=21. Basically, the nic for my local lan is gone. And due to the fact, that the box is unsuable for me (don't have another internet connection to log in *that* remote), I have to reboot hard. Thank god there's reiserfs ;-). All this happened on 2.4.3 and 2.4.4 (don't excactly remember on earlier 2.4). I followed your suggestion regarding PCI-slots. Both my nics used to use PCI 4 and 5 (on a gigabyte vxd7, dual 1GHz). Only the one in slot 4 had the problems. I switched the card to slot 1 and will monitor the situation. I'll mail the list in case it doesn't change my situation. Any other hints are welcome (other than the noapic, which didn't help). -- Tschoe,Get my gpg-public-key here Jens http://gecius.de/gpg-key.txt - 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 read the FAQ at http://www.tux.org/lkml/
Re: 2.4.4 kernel freeze
Stephan Brauss [EMAIL PROTECTED] writes: what do you mean by freeze? in theory, the fact that the irq I cannot ping the machine anymore, no Ooops, no kernel messages, the attached screen is freezed (which implies that no more interrupts are handled, right?) Excuse me hopping in. I have that situation here, too. Screen frozen, no pings from the local network, sysrq doesn't work (keyboard dead). BUT: the other interface (internet) works just fine. When I look in the logs afterwards, I find everything worked fine except the following: maniac kernel: NETDEV WATCHDOG: eth1: transmit timed out maniac kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=21. Basically, the nic for my local lan is gone. And due to the fact, that the box is unsuable for me (don't have another internet connection to log in *that* remote), I have to reboot hard. Thank god there's reiserfs ;-). All this happened on 2.4.3 and 2.4.4 (don't excactly remember on earlier 2.4). I followed your suggestion regarding PCI-slots. Both my nics used to use PCI 4 and 5 (on a gigabyte vxd7, dual 1GHz). Only the one in slot 4 had the problems. I switched the card to slot 1 and will monitor the situation. I'll mail the list in case it doesn't change my situation. Any other hints are welcome (other than the noapic, which didn't help). -- Tschoe,Get my gpg-public-key here Jens http://gecius.de/gpg-key.txt - 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 read the FAQ at http://www.tux.org/lkml/
ide-scsi / cd-writing 2.4.3
Hi folks, I used to be able to use my cdwriter (Philips CDD3610) on 2.2.17. Now, with 2.4.4 I'm not able to get it to work. It's not a permission problem as far as I can see. I suspect ide-scsi? See the output of cdrecord (I tried to burn 450MB): Cdrecord 1.10a18 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling TOC Type: 1 = CD-ROM Using libscg version 'schily-0.5' atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 1 Vendor_info: 'PHILIPS ' Identifikation : 'CDD3610 CD-R/RW ' Revision : '3.01' Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : SWABAUDIO Drive buf size : 786432 = 768 KB FIFO size : 4194304 = 4096 KB scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 Linux sg driver version: 3.1.17 Track 01: data unknown length padsize: 30 KB Lout start: 0 MB (00:02/00) = 0 sectors Current Secsize: 2048 ATIP start of lead in: -11325 (97:31/00) ATIP start of lead out: 336225 (74:45/00) Disk type:Long strategy type (Cyanine, AZO or similar) Manuf. index: 22 Manufacturer: Ritek Co. Starting to write CD/DVD at speed 2 in write mode for single session. /usr/bin/cdrecord: WARNING: Track size unknown. Data may not fit on disk. Performing OPC... /usr/bin/cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 00 01 74 00 00 1F 00 status: 0x0 (GOOD STATUS) cmd finished after 6.818s timeout 40s Track 01: 0 MB written. write track data: error after 761856 bytes Writing time: 18.023s Sense Bytes: F0 00 00 00 00 00 00 19 00 00 38 13 00 00 00 00 0C DB /usr/bin/cdrecord: Input/output error. close track/session: scsi sendcmd: no error CDB: 5B 00 02 00 00 00 00 00 00 00 status: 0x0 (GOOD STATUS) cmd finished after 0.011s timeout 480s cmd finished after 0.011s timeout 480s /usr/bin/cdrecord: Input/output error. mode select g1: scsi sendcmd: no error CDB: 55 10 00 00 00 00 00 00 10 00 status: 0x0 (GOOD STATUS) cmd finished after 0.005s timeout 40s Any Ideas? -- Tschoe,Get my gpg-public-key here Jens http://gecius.de/gpg-key.txt - 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 read the FAQ at http://www.tux.org/lkml/
ide-scsi / cd-writing 2.4.3
Hi folks, I used to be able to use my cdwriter (Philips CDD3610) on 2.2.17. Now, with 2.4.4 I'm not able to get it to work. It's not a permission problem as far as I can see. I suspect ide-scsi? See the output of cdrecord (I tried to burn 450MB): Cdrecord 1.10a18 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling TOC Type: 1 = CD-ROM Using libscg version 'schily-0.5' atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 1 Vendor_info: 'PHILIPS ' Identifikation : 'CDD3610 CD-R/RW ' Revision : '3.01' Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : SWABAUDIO Drive buf size : 786432 = 768 KB FIFO size : 4194304 = 4096 KB scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 Linux sg driver version: 3.1.17 Track 01: data unknown length padsize: 30 KB Lout start: 0 MB (00:02/00) = 0 sectors Current Secsize: 2048 ATIP start of lead in: -11325 (97:31/00) ATIP start of lead out: 336225 (74:45/00) Disk type:Long strategy type (Cyanine, AZO or similar) Manuf. index: 22 Manufacturer: Ritek Co. Starting to write CD/DVD at speed 2 in write mode for single session. /usr/bin/cdrecord: WARNING: Track size unknown. Data may not fit on disk. Performing OPC... /usr/bin/cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 00 01 74 00 00 1F 00 status: 0x0 (GOOD STATUS) cmd finished after 6.818s timeout 40s Track 01: 0 MB written. write track data: error after 761856 bytes Writing time: 18.023s Sense Bytes: F0 00 00 00 00 00 00 19 00 00 38 13 00 00 00 00 0C DB /usr/bin/cdrecord: Input/output error. close track/session: scsi sendcmd: no error CDB: 5B 00 02 00 00 00 00 00 00 00 status: 0x0 (GOOD STATUS) cmd finished after 0.011s timeout 480s cmd finished after 0.011s timeout 480s /usr/bin/cdrecord: Input/output error. mode select g1: scsi sendcmd: no error CDB: 55 10 00 00 00 00 00 00 10 00 status: 0x0 (GOOD STATUS) cmd finished after 0.005s timeout 40s Any Ideas? -- Tschoe,Get my gpg-public-key here Jens http://gecius.de/gpg-key.txt - 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 read the FAQ at http://www.tux.org/lkml/
Re: 2.4.2 and NETDEV WATCHDOG - different bug?
[EMAIL PROTECTED] writes: > > > NETDEV WATCHDOG: eth0: transmit timed out > > > eth0: Transmit timed out: status f048 0c00 at 0/28 command 001a000 > > > > Same here on 2.4.1 smp with two dirt-cheap ne2pci-clones. System > > unusuable (as stated by clem ealier today) and need for > > reboot. Nothing special happened on the box before. > > > > Other message in that context: > > > > Mar 21 18:28:58 maniac kernel: NETDEV WATCHDOG: eth1: transmit timed out > > Mar 21 18:28:58 maniac kernel: eth1: Tx timed out, lost interrupt? > > TSR=0x3, ISR=0x3, t=27. > > This is a generic message generated by card-specific errors and events. > The same message does not imply that the two problems are at all > related... Then, my question will be, why is the kernel loosing the irq for eth1 and gets unusable? Sorry I didn't know about the generic message. -- Tschoe,Get my gpg-public-key here Jens http://gecius.de/gpg-key.txt - 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 read the FAQ at http://www.tux.org/lkml/
Re: 2.4.2 and NETDEV WATCHDOG
John Madden <[EMAIL PROTECTED]> writes: > I'm receiving the following errors while botting a previously-fine 2.2 > machine (Dell 2450, 2 eepro 100's): > > NETDEV WATCHDOG: eth0: transmit timed out > eth0: Transmit timed out: status f048 0c00 at 0/28 command 001a000 Same here on 2.4.1 smp with two dirt-cheap ne2pci-clones. System unusuable (as stated by clem ealier today) and need for reboot. Nothing special happened on the box before. Other message in that context: Mar 21 18:28:58 maniac kernel: NETDEV WATCHDOG: eth1: transmit timed out Mar 21 18:28:58 maniac kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=27. Fortunately, SysRq-S-U-B works... -- Tschoe,Get my gpg-public-key here Jens http://gecius.de/gpg-key.txt - 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 read the FAQ at http://www.tux.org/lkml/
Re: 2.4.2 and NETDEV WATCHDOG
John Madden [EMAIL PROTECTED] writes: I'm receiving the following errors while botting a previously-fine 2.2 machine (Dell 2450, 2 eepro 100's): NETDEV WATCHDOG: eth0: transmit timed out eth0: Transmit timed out: status f048 0c00 at 0/28 command 001a000 Same here on 2.4.1 smp with two dirt-cheap ne2pci-clones. System unusuable (as stated by clem ealier today) and need for reboot. Nothing special happened on the box before. Other message in that context: Mar 21 18:28:58 maniac kernel: NETDEV WATCHDOG: eth1: transmit timed out Mar 21 18:28:58 maniac kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=27. Fortunately, SysRq-S-U-B works... -- Tschoe,Get my gpg-public-key here Jens http://gecius.de/gpg-key.txt - 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 read the FAQ at http://www.tux.org/lkml/
Re: 2.4.2 and NETDEV WATCHDOG - different bug?
[EMAIL PROTECTED] writes: NETDEV WATCHDOG: eth0: transmit timed out eth0: Transmit timed out: status f048 0c00 at 0/28 command 001a000 Same here on 2.4.1 smp with two dirt-cheap ne2pci-clones. System unusuable (as stated by clem ealier today) and need for reboot. Nothing special happened on the box before. Other message in that context: Mar 21 18:28:58 maniac kernel: NETDEV WATCHDOG: eth1: transmit timed out Mar 21 18:28:58 maniac kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=27. This is a generic message generated by card-specific errors and events. The same message does not imply that the two problems are at all related... Then, my question will be, why is the kernel loosing the irq for eth1 and gets unusable? Sorry I didn't know about the generic message. -- Tschoe,Get my gpg-public-key here Jens http://gecius.de/gpg-key.txt - 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 read the FAQ at http://www.tux.org/lkml/
