Re: 5.0-RC1: X server crash
On Mon, Dec 16, 2002 at 09:55:09PM +0100, Marc Fonvieille wrote: > On Mon, Dec 16, 2002 at 07:07:01PM +0100, Paolo Pisati wrote: > > Please, try to run the memtest program (it's in the ports tree): > > i had a SERIOUS problem of memory corruption with > > my laptop (PIII, Intel815E, ATI Radeon M6, etcetc) with STABLE > > when i loaded the agp module. > > > > I reported this problem to the drm maintainer but he was unable > > to solve it... =P > > > > Run the memtest for a bit, and then report the result, maybe there's > > a strange bug floating around, or maybe i'm just drunk... =) > > > > We talked about a problem between X and -CURRENT, we had no problem > with -STABLE. > > Btw I don't see how memtest can report memory corruption, I thought it > was to test "hardware" problem. It is. Memtest will not tell you squat about this (unless you have real memory faults .. ). -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-RC1: X server crash
+ Marc Fonvieille <[EMAIL PROTECTED]>: | I use the same machine under 5.0-CURRENT (RC etc.). I used to have | hangs under X, but since I removed | | Load "dri" | | from /etc/X11/XF86Config, it is OK. Didn't make an iota of difference for me. + Paolo Pisati <[EMAIL PROTECTED]>: | Please, try to run the memtest program (it's in the ports tree): | i had a SERIOUS problem of memory corruption with | my laptop (PIII, Intel815E, ATI Radeon M6, etcetc) with STABLE | when i loaded the agp module. It reports no trouble. It only wants to do 32 MB, but no problem there at all. - Harald To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-RC1: X server crash
On Mon, Dec 16, 2002 at 11:25:05PM +0100, Paolo Pisati wrote: > On Mon, Dec 16, 2002 at 09:55:09PM +0100, Marc Fonvieille wrote: > > > > We talked about a problem between X and -CURRENT, we had no problem > > with -STABLE. > > A problem that MAYBE is still present even in CURRENT, don't > you think? > Once again, I was not talking about the same problem as yours. > As i said, i don't have my laptop right now, so i couldn't > test CURRENT on it ( but i'll do it ASAP ), and i was looking > for someone else with the same problem... > > > > Btw I don't see how memtest can report memory corruption, I thought it > > was to test "hardware" problem. > > hardware problem? > > VERY strange, cause IF i load the agp module i got errors > from memtest, system freeze&crash, then if i disable the > agp module, memtest reports 0 errors (even after hours&hours of > test), no crash&freeze, etcetc > As you can it doesn't look like an hardware problem, i think it's a > FreeBSD-related problem, probably toggled by the agp && drm stuff > You missed my point, memtest is a test for hardware. >From memtest site: memtest is a utility for testing the memory subsystem in a computer to determine if it is faulty. It's to test if your ram is "bad", not to see a software problem. The "memtest crash" may come from a totally different reason and could occur in other situation. In fact you should fill a PR with all infos about your problem. Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-RC1: X server crash
On Mon, Dec 16, 2002 at 09:55:09PM +0100, Marc Fonvieille wrote: > > We talked about a problem between X and -CURRENT, we had no problem > with -STABLE. A problem that MAYBE is still present even in CURRENT, don't you think? As i said, i don't have my laptop right now, so i couldn't test CURRENT on it ( but i'll do it ASAP ), and i was looking for someone else with the same problem... > Btw I don't see how memtest can report memory corruption, I thought it > was to test "hardware" problem. hardware problem? VERY strange, cause IF i load the agp module i got errors from memtest, system freeze&crash, then if i disable the agp module, memtest reports 0 errors (even after hours&hours of test), no crash&freeze, etcetc As you can it doesn't look like an hardware problem, i think it's a FreeBSD-related problem, probably toggled by the agp && drm stuff more when i'll get my laptop back... -- Paolo Italian FreeBSD User Group: http://www.gufi.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-RC1: X server crash
On Mon, Dec 16, 2002 at 07:07:01PM +0100, Paolo Pisati wrote: > Please, try to run the memtest program (it's in the ports tree): > i had a SERIOUS problem of memory corruption with > my laptop (PIII, Intel815E, ATI Radeon M6, etcetc) with STABLE > when i loaded the agp module. > > I reported this problem to the drm maintainer but he was unable > to solve it... =P > > Run the memtest for a bit, and then report the result, maybe there's > a strange bug floating around, or maybe i'm just drunk... =) > We talked about a problem between X and -CURRENT, we had no problem with -STABLE. Btw I don't see how memtest can report memory corruption, I thought it was to test "hardware" problem. Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-RC1: X server crash
On Mon, Dec 16, 2002 at 10:08:55AM +0100, Marc Fonvieille wrote: > > I use the same machine under 5.0-CURRENT (RC etc.). I used to have > hangs under X, but since I removed > > Load "dri" > > from /etc/X11/XF86Config, it is OK. Please, try to run the memtest program (it's in the ports tree): i had a SERIOUS problem of memory corruption with my laptop (PIII, Intel815E, ATI Radeon M6, etcetc) with STABLE when i loaded the agp module. I reported this problem to the drm maintainer but he was unable to solve it... =P Run the memtest for a bit, and then report the result, maybe there's a strange bug floating around, or maybe i'm just drunk... =) -- Paolo Italian FreeBSD User Group: http://www.gufi.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-RC1: X server crash
On Mon, Dec 16, 2002 at 03:54:27AM +0100, Harald Hanche-Olsen wrote: > (This is the last of my current batch of 5.0-RC1 problems.) > > Yeah, I know, X server problems ought to be reported to the XFree > maintainers. Is there any interest for details of it here? > > The synopsis: The X server crashes under 5.0-RC1 where it runs fine > with the exact same configuration under 4.7-RELEASE. It says > > Fatal server error: > Caught signal 10. Server aborting > > and then dmesg output says it dies with signal 6 and dumping core. > But I can't find any core dump lying around anywhere. I'll forward > XFree86.0.log and config files if anybody here wants them, but in the > interest of keeping unwanted list traffic down, I'll lay low until > anybody requests this data. > > I'll include this line though: > > (--) PCI:*(1:0:0) ATI Radeon Mobility M7 LW rev 0, Mem @ 0xe000/27, >0xfcff/16, I/O @ 0xc000/8 > > The machine is a Dell Inspiron 4150. > I use the same machine under 5.0-CURRENT (RC etc.). I used to have hangs under X, but since I removed Load "dri" from /etc/X11/XF86Config, it is OK. Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
5.0-RC1: X server crash
(This is the last of my current batch of 5.0-RC1 problems.) Yeah, I know, X server problems ought to be reported to the XFree maintainers. Is there any interest for details of it here? The synopsis: The X server crashes under 5.0-RC1 where it runs fine with the exact same configuration under 4.7-RELEASE. It says Fatal server error: Caught signal 10. Server aborting and then dmesg output says it dies with signal 6 and dumping core. But I can't find any core dump lying around anywhere. I'll forward XFree86.0.log and config files if anybody here wants them, but in the interest of keeping unwanted list traffic down, I'll lay low until anybody requests this data. I'll include this line though: (--) PCI:*(1:0:0) ATI Radeon Mobility M7 LW rev 0, Mem @ 0xe000/27, 0xfcff/16, I/O @ 0xc000/8 The machine is a Dell Inspiron 4150. - Harald To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
