RE: >128 MB RAM stability problems (again)
Which filesystem are you using on this machine? []s. -Original Message- From: George Bonser [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 04, 2001 5:06 PM To: Ronald Bultje; Linux Kernel Mailing List Subject: RE: >128 MB RAM stability problems (again) > I'm kind of astounded now, WHY can't linux-2.4.x run on ANY machine in > my house with more than 128 MB RAM?!? Can someone please point out to me > that he's actually running kernel-2.4.x on a machine with more than 128 > MB RAM and that he's NOT having severe stability problems? Running 2.4.6-pre and 2.4.6 proper on several machines. Quite busy and all have 256 to 512MB of RAM. As I type this, I am in the process of converting an entire production server farm over to 2.4.6 from 2.2.19 as the 2.4.6-pre series proved out well on a test machine in that farm. No stability problems at all. The only reboots were for patching up the kernel to the next -pre revision on that test box. - 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/ - 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/
Scsi errors on boot.
I am getting the follwing error messages on the kernel boot. Does anyone have any idea what the problem might be? The kernel is 2.2.19. Thanks. Detected scsi disk sda at scsi0, channel 0, id 0, lun 0 (scsi0:0:0:1) Synchronous at 160.0 Mbyte/sec, offset 63. (scsi0:0:0:1) CHECK_CONDITION on REQUEST_SENSE, returning an error. (scsi0:0:0:1) CHECK_CONDITION on REQUEST_SENSE, returning an error. scsi0 channel 0 : resetting for second half of retries. SCSI bus is being reset for host 0 channel 0. (scsi0:0:0:1) Synchronous at 160.0 Mbyte/sec, offset 63. (scsi0:0:0:1) CHECK_CONDITION on REQUEST_SENSE, returning an error. (scsi0:0:0:1) CHECK_CONDITION on REQUEST_SENSE, returning an error. (scsi0:0:0:1) CHECK_CONDITION on REQUEST_SENSE, returning an error. Vendor: SEAGATE Model: ST39204LW Rev: 0002 Type: Direct-Access ANSI SCSI revision: 03 Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0 (scsi0:0:1:1) Synchronous at 160.0 Mbyte/sec, offset 63. (scsi0:0:1:1) CHECK_CONDITION on REQUEST_SENSE, returning an error. (scsi0:0:1:1) CHECK_CONDITION on REQUEST_SENSE, returning an error. scsi0 channel 0 : resetting for second half of retries. SCSI bus is being reset for host 0 channel 0. (scsi0:0:1:1) Synchronous at 160.0 Mbyte/sec, offset 63. (scsi0:0:1:1) CHECK_CONDITION on REQUEST_SENSE, returning an error. (scsi0:0:1:1) CHECK_CONDITION on REQUEST_SENSE, returning an error. (scsi0:0:1:1) CHECK_CONDITION on REQUEST_SENSE, returning an error. scsi : detected 2 SCSI disks total. (scsi0:0:0:0) Synchronous at 160.0 Mbyte/sec, offset 63. - 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/
Multithreaded issue.
We have this multithreaded app that run fine under the kernel 2.2.x series. Last week, we decided to update our linux and went dor RedHat7.1 to use the new kernel. Some threadsw of our app just hangs in random moments. Is there any issue on the 2.4.x series that must be observed that we are missing? Thanks. - 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/
