Messages in this thread | | | Date | Wed, 27 Jan 1999 01:22:49 +0100 | From | gandalf <> | Subject | Re: 2.2.0 lock <- same here... |
| |
At 00:51 27.01.99 +0100, you wrote: >On Tue, Jan 26, 1999 at 10:45:02PM +0100, gandalf wrote: >> At 20:59 26.01.99 +0100, you wrote: >> >2.2.0 final locks up on my machine the same way as 2.2.0-pre8-ac1 and >> >2.2.0-pre9 did (I posted the error on the list few days ago). >> > >> >> I'm experiencing the same problem since pre8. I already posted this a few >> days ago. > >Some additional info: > >1) It happened in 2.2.0-pre7-ac5 once, too :(( >2) Although the system cannot be reached by telnet, active connections are >not broken (e.g. masquerading worked even when the system was totally locked >up). >3) All of these lock ups happened under X here with a rather heavy cpu or >disk load (kernel compilation or copying of large directories). >4) After exiting X (alt-ctrl-backspace works) no console can be reached >(alt-sysrq-r doesn't help) -- black screen :(( >5) Nothing strange can be seen in any logs and, what is curious, top doesn't >show anything suspicious (distributed.net client gets the highest cpu time >and other processes have less than 10% of cpu time). >6) My configuration: > * pentium 166mmx, 64mb ram, only ide disks used during lock-ups > * kernel compiled using egcs 1.1.1 (debian packaged) with -mpentium > but no other optimizations options changed > >> All I can do is push the reset button and wait till my raid devices have >> been checked =( > >I advise using sysrq commands (they work even then) -- alt-sysrq-s syncs disks >and alt-sysrq-u umounts them. It doesn't prevent all fs errors, though.
yes, i have already recompiled my kernel with sysrq support, also in order to get some more debugging information in case the 'lock-up of death' should strike again.
it's interesting you're also using a cd changer... i have 24 cd's on 4 nakamichi mbr-7 changers always mounted, probably some sort of an "extreme situation"
actually, before the last lock-up tonight i had some scsi timeout errors in my logs:
Jan 26 20:30:58 mir kernel: scsi : aborting command due to timeout : pid 1619, scsi0, channel 0, id 4, lun 1 0x28 20 00 00 00 26 00 00 01 00 Jan 26 20:30:58 mir kernel: scsi: <fdomain> abort Jan 26 20:30:58 mir kernel: Future Domain 16-bit SCSI Driver Version 5.50 Jan 26 20:30:58 mir kernel: scsi0: <fdomain> No BIOS; using scsi id 7 Jan 26 20:30:58 mir kernel: scsi0: <fdomain> TMC-36C70 (PCI bus) chip at 0xe000 irq 10 Jan 26 20:30:58 mir kernel: other (8), target = 4 cmnd = 0x28 pieces = 1 size = 2048 Jan 26 20:30:58 mir kernel: sent_command = 10, have_data_in = -1, timeout = 0 Jan 26 20:30:58 mir kernel: in_interrupt_flag = 0 Jan 26 20:30:58 mir kernel: IMR = 0x11c0, IRR = 0x0000, ISR = 0x0000 Jan 26 20:30:58 mir kernel: SCSI Status = 0x15 Jan 26 20:30:58 mir kernel: TMC Status = 0xf0 Jan 26 20:30:58 mir kernel: Interrupt Status = 0x98 (enabled) Jan 26 20:30:58 mir kernel: FIFO Status = 0x04 Jan 26 20:30:58 mir kernel: Int. Condition = 0x00 Jan 26 20:30:58 mir kernel: Configuration 1 = 0x85 Jan 26 20:30:58 mir kernel: Configuration 2 = 0x03 Jan 26 21:02:20 mir syslogd 1.3-3: restart.
i have to admit, i used to have those timeout problems under 2.0.x as well every month or so, there might be a problem with my aha-2920 or one of the cd changers, but that has never caused a hard lock-up on any kernel before pre8 since i don't have any scsi disks, i load scsi support as a module (like almost everything else i could modularize):
my scsi .config:
CONFIG_SCSI=y # CONFIG_BLK_DEV_SD is not set # CONFIG_CHR_DEV_ST is not set CONFIG_BLK_DEV_SR=m # CONFIG_BLK_DEV_SR_VENDOR is not set CONFIG_CHR_DEV_SG=m CONFIG_SCSI_MULTI_LUN=y # CONFIG_SCSI_CONSTANTS is not set # CONFIG_SCSI_LOGGING is not set CONFIG_SCSI_FUTURE_DOMAIN=m
lsmod:
nls_iso8859-1 2020 24 (autoclean) fdomain 12332 24 (autoclean) sr_mod 16284 24 (autoclean) cdrom 12600 0 (autoclean) [sr_mod] isofs 17464 24 (autoclean)
output of /proc/scsi/scsi (you asked for it ;):
Attached devices: Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 01 Lun: 01 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 01 Lun: 02 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 01 Lun: 03 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 01 Lun: 04 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 01 Lun: 05 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 01 Lun: 06 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 02 Lun: 00 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 02 Lun: 01 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 02 Lun: 02 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 02 Lun: 03 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 02 Lun: 04 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 02 Lun: 05 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 02 Lun: 06 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 03 Lun: 00 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 03 Lun: 01 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 03 Lun: 02 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 03 Lun: 03 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 03 Lun: 04 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 03 Lun: 05 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 03 Lun: 06 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 01 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 02 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 03 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 04 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 05 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 06 Vendor: NRC Model: MBR-7 Rev: 110 Type: CD-ROM ANSI SCSI revision: 02
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |