On Wed, 28 Mar 2001, Paul Cassella wrote:
> Hangs under 2.4.2-ac{18,19,24} that do not happen under -ac12.
I've been running -ac27 for over 5 days, and it's been fine, so this seems
to have been fixed.
--
Paul Cassella
-
To unsubscribe from this list: send the line "unsubs
Hello Paul Cassella,
Once you wrote about "Hangs under 2.4.2-ac{18,19,24} that do not happen under -ac12.":
PC> [1.] One line summary of the problem:
PC> Hangs under 2.4.2-ac{18,19,24} that do not happen under -ac12.
I have similar problem with 2.4.0, 2.4.1, 2.4.2.
On Thu, 29 Mar 2001, Alan Cox wrote:
> Was anything between 12 and 18 stable ?
I didn't actually try them; I jumped right from 12 to 18, and when that
and 19 died, I went back to 12.
But a quick look suggests that the entire patch I'd applied to 12 and got
a hang with was in 13, including the
> I have had hangs under 2.4.2-ac18, -ac19, and -ac24, after uptimes of
> 36 hours, 12 hours, and 10 hours, respectively. -ac12 has twice run
> for a week without crashing. I didn't see anything in the later -ac
> changelogs that looks responsible, but I haven't actually tried them.
Was anythin
Earlier today, I wrote
> and no sysrq keys other than B worked; I didn't hear disk activity
> after S, and the disks weren't unmounted. Nothing made it to the
Of course, when I rebooted this time (after SysRQ S,U,B), all the
filesystems were clean.
Nothing in the logs this time either though.
[1.] One line summary of the problem:
Hangs under 2.4.2-ac{18,19,24} that do not happen under -ac12.
[2.] Full description of the problem/report:
I have had hangs under 2.4.2-ac18, -ac19, and -ac24, after uptimes of
36 hours, 12 hours, and 10 hours, respectively. -ac12 has twice run
for a
6 matches
Mail list logo
