Date: Tue, 7 Nov 2000 10:27:43 +0100 From: Michel Talon <michel@lpthe.jussieu.fr> To: stable@freebsd.org Subject: panic with 4.2 Message-ID: <20001107102743.A651@lpthe.jussieu.fr>
next in thread | raw e-mail | index | archive | help
Hello, I have tried to upgrade my desktop to 4.2 from FreeBSD 4.1-STABLE #0: Wed Sep 6 15:16:28 CEST 2000 buildworld and buildkernel went out smooth. However, when i rebooted multi user to test my new kernel, i had a lot of troubles (i had disabled any modules loading). First i had a 30s timeout on the ata devices, but i have seen that since 4.0 Then the machine paniced just after having issued mountd. Nov 7 10:02:10 niobe /kernel: ad0: 1222MB <QUANTUM FIREBALL1280A> [2484/16/63] at ata0-master WDMA2 Nov 7 10:02:10 niobe /kernel: acd0: CDROM <CD-56E> at ata1-master using PIO3 Nov 7 10:02:10 niobe /kernel: Waiting 5 seconds for SCSI devices to settle Nov 7 10:02:10 niobe /kernel: (probe5:sym0:0:5:0): phase change 6-7 6@0fc96f8c resid=4. Nov 7 10:02:10 niobe /kernel: Mounting root from ufs:/dev/da0s1a Nov 7 10:02:10 niobe /kernel: da0 at sym0 bus 0 target 0 lun 0 Nov 7 10:02:10 niobe /kernel: da0: <QUANTUM FIREBALL ST3.2S 0F0C> Fixed Direct Access SCSI-2 device Nov 7 10:02:10 niobe /kernel: da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled Nov 7 10:02:10 niobe /kernel: da0: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C) Nov 7 10:02:10 niobe /kernel: da1 at sym0 bus 0 target 5 lun 0 Nov 7 10:02:10 niobe /kernel: da1: <IOMEGA ZIP 100 J.03> Removable Direct Access SCSI-2 device Nov 7 10:02:10 niobe /kernel: da1: 3.300MB/s transfers Nov 7 10:02:10 niobe /kernel: da1: 96MB (196608 512 byte sectors: 64H 32S/T 96C) Nov 7 10:02:11 niobe savecore: reboot after panic: kmem_malloc(134524928): kmem_map too small: 6807552 total allocated Nov 7 10:02:11 niobe savecore: writing core to /var/crash/vmcore.5 Nov 7 10:03:09 niobe /kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting Nov 7 10:03:09 niobe /kernel: ata0: resetting devices .. done Nov 7 10:03:14 niobe savecore: writing kernel to /var/crash/kernel.5 As you can see, when saving the coredump, i had some at0 resetting. I have observed such things previously, but with no adverse effects. I have the coredump, but i don't know how to compile a debugging kernel with make buildkernel. At the moment, i am very reluctant to do a make installworld, and have reverted to kernel.old. Is it possible that the old mountd is able to panic the machine? -- Michel Talon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001107102743.A651>