New kernels won't boot
Hi, I'm currently having the problem that newer kernels won't boot anymore on a HP Proliant DL380G3. The latest kernel I can boot is from Sun Aug 31 15:22:44 CEST 2003. Every attempt to boot a newer one (regardless whether UP or SMP) hangs at: vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 2387622296 Hz quality 800 Timecounters tick every 10.000 msec And then... silence. Any ideas? regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New kernels won't boot
On Fri, 5 Sep 2003, Lukas Ertl wrote: I'm currently having the problem that newer kernels won't boot anymore on a HP Proliant DL380G3. The latest kernel I can boot is from Sun Aug 31 15:22:44 CEST 2003. Every attempt to boot a newer one (regardless whether UP or SMP) hangs at: vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 2387622296 Hz quality 800 Timecounters tick every 10.000 msec Ok, I've found out that if I boot -v I get further than this and see the following messages: (probe9:ciss0:0:9:0): Request completed with CAM_REQ_CMP_ERR (probe9:ciss0:0:9:0): error 5 (probe9:ciss0:0:9:0): Retries Exausted (probe10:ciss0:0:10:0): Request completed with CAM_REQ_CMP_ERR (probe10:ciss0:0:10:0): error 5 (probe10:ciss0:0:10:0): Retries Exausted (probe11:ciss0:0:11:0): Request completed with CAM_REQ_CMP_ERR (probe11:ciss0:0:11:0): error 5 (probe11:ciss0:0:11:0): Retries Exausted (probe12:ciss0:0:12:0): Request completed with CAM_REQ_CMP_ERR (probe12:ciss0:0:12:0): error 5 (probe12:ciss0:0:12:0): Retries Exausted (probe13:ciss0:0:13:0): Request completed with CAM_REQ_CMP_ERR (probe13:ciss0:0:13:0): error 5 (probe13:ciss0:0:13:0): Retries Exausted (probe14:ciss0:0:14:0): Request completed with CAM_REQ_CMP_ERR (probe14:ciss0:0:14:0): error 5 (probe14:ciss0:0:14:0): Retries Exausted ciss0: command status 0x1 (target status) scsi status 0x2 (probe0:ciss0:0:0:0): error 22 (probe0:ciss0:0:0:0): Unretryable Error ciss0: command status 0x1 (target status) scsi status 0x2 (probe1:ciss0:0:1:0): error 22 Anything CAM/SCSI-related? regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New kernels won't boot
On Fri, 5 Sep 2003, Lukas Ertl wrote: vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 2387622296 Hz quality 800 Timecounters tick every 10.000 msec And then... silence. Any ideas? My sources indicate that you should try upgrading the system BIOS. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New ATA drivers problem? (Was: New kernels won't boot)
It seems Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: Soren, I did a bit of experimenting with my CVS archive and found that version 1.8 of ata-all.c was the last one that worked on my problem box. 1.9 spewed out errors about unexpected interrupts whilst probing and eventually hung, and 1.10 gave the unable to mount wd0s2a errors we all love. Hmm, since the only changes are those to support newbus, thats probably where we should find the problem. There has been a fair number of other reports of sound not working etc etc, it might be that we have a problem here with certain HW. COuld you mail me a verbose dmesg when you have the 1.8 and when the 1.10 version ?? -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New ATA drivers problem? (Was: New kernels won't boot)
Soren, I did a bit of experimenting with my CVS archive and found that version 1.8 of ata-all.c was the last one that worked on my problem box. 1.9 spewed out errors about unexpected interrupts whilst probing and eventually hung, and 1.10 gave the unable to mount wd0s2a errors we all love. Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New ATA drivers problem? (Was: New kernels won't boot)
On Thu, 29 Apr 1999, Soren Schmidt wrote: It seems Brian Feldman wrote: Ever going to help with my atapi-fd problems? I found examples of the corruptions, including lots of NULLs... Well, so long as I cannot get my hands on the problem, its real hard to solve it. I'm trying to get ahold of the same LS120 drive here but so far I havn't found any, in fact LS120 drives are extremely rare over here... As I said before, I can make some tests, but unfortunately my machine doesn't want to mount disks at all with the new ATA code... Please take a look at the message I sent about a week ago. Andrzej Bialecki // ab...@webgiro.com WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New ATA drivers problem? (Was: New kernels won't boot)
It seems Andrzej Bialecki wrote: Ever going to help with my atapi-fd problems? I found examples of the corruptions, including lots of NULLs... Well, so long as I cannot get my hands on the problem, its real hard to solve it. I'm trying to get ahold of the same LS120 drive here but so far I havn't found any, in fact LS120 drives are extremely rare over here... As I said before, I can make some tests, but unfortunately my machine doesn't want to mount disks at all with the new ATA code... Please take a look at the message I sent about a week ago. Unfortunately they dont tell me much :( I'll have to rearrange some disks here and try to make some new installs see if I can get the problem to appear then.. -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New ATA drivers problem? (Was: New kernels won't boot)
It seems Soren Schmidt wrote: As I said before, I can make some tests, but unfortunately my machine doesn't want to mount disks at all with the new ATA code... Please take a look at the message I sent about a week ago. Unfortunately they dont tell me much :( I'll have to rearrange some disks here and try to make some new installs see if I can get the problem to appear then.. Meanwhile, could you try this patch to boot2.c and ata-disk.c and install the new bootblocks created by this and see if it works with a genuine ad device set. You should then use ad?? in fstab of cause. Boot directly ie like 0:ad(0,a)/kernel from the boot promt, as the /boot/loader doesn't know about ad devices... Another thing to try is to dump down ata-disk.c so it doesn't use either multi-sector mode or DMA, as that might confuse some disks, notably WD but also Quantum has had some marginal disks... -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New ATA drivers problem? (Was: New kernels won't boot)
(trimmed spaghetti CC: list...) On Fri, 30 Apr 1999, Soren Schmidt wrote: Unfortunately they dont tell me much :( I'll have to rearrange some disks here and try to make some new installs see if I can get the problem to appear then.. Is there any info I can dig out for you? Some useful printfs here and there? Andrzej Bialecki // ab...@webgiro.com WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New ATA drivers problem? (Was: New kernels won't boot)
It seems Brian Feldman wrote: Ever going to help with my atapi-fd problems? I found examples of the corruptions, including lots of NULLs... Well, so long as I cannot get my hands on the problem, its real hard to solve it. I'm trying to get ahold of the same LS120 drive here but so far I havn't found any, in fact LS120 drives are extremely rare over here... -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New ATA drivers problem? (Was: New kernels won't boot)
On Thu, 29 Apr 1999, Soren Schmidt wrote: It seems Brian Feldman wrote: Ever going to help with my atapi-fd problems? I found examples of the corruptions, including lots of NULLs... Well, so long as I cannot get my hands on the problem, its real hard to solve it. I'm trying to get ahold of the same LS120 drive here but so far I havn't found any, in fact LS120 drives are extremely rare over here... Basically, this drive is a Digital Research brand; it (its firmware?) is made by Motorola, and supposedly this is all the same as an off-the-shelf Imation drive. -S?ren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
New ATA drivers problem? (Was: New kernels won't boot)
Hi, In the great new ATA device driver framework (thanks Soren) there seems to be a problem reported before by Stephen: Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: On my machine, a kernel newer than one built on the 22nd will not complete booting, panicing about not being able to mount root. Another machine with a very similar config is fine. The main difference is that the faulty machine has its FreeBSD partition in an odd spot on the disk. Below is the dmesg output, the fdisk output and the config file. [stuff deleted] I have three hosts with -current, all with the new ATA in function. Booting the same kernel produces different results on all of them wrt root file system mounting: - one reports 'changing root device to wd0s3a' - one reports 'changing root device to wd0s3a' followed by 'changing root device to wd0a' and continues flawlessly - one reports 'changing root device to wd0s3a' followed by 'changing root device to wd0a' and panics with 'cannot mount root file system (2), err 22' All motherboards are equipped with the PIIX4 IDE controller. If I need to supply the dmesg output and/or configuration, please let me know. All three hosts have FreeBSD on the first disk (on different disk locations, though). Regards, Thomas To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New ATA drivers problem? (Was: New kernels won't boot)
Hi, I have three hosts with -current, all with the new ATA in function. Booting the same kernel produces different results on all of them wrt root file system mounting: - one reports 'changing root device to wd0s3a' - one reports 'changing root device to wd0s3a' followed by 'changing root device to wd0a' and continues flawlessly - one reports 'changing root device to wd0s3a' followed by 'changing root device to wd0a' and panics with 'cannot mount root file system (2), err 22' All motherboards are equipped with the PIIX4 IDE controller. If I need to supply the dmesg output and/or configuration, please let me know. All three hosts have FreeBSD on the first disk (on different disk locations, though). Hmm, could you mail me the output of fdisk disklabel from those tree machines, with indication of how they behave ?? I'm unable to reproduce those errors here, but this might bring the details I need to figure it out... -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New ATA drivers problem? (Was: New kernels won't boot)
Soren Schmidt wrote: Hmm, could you mail me the output of fdisk disklabel from those tree machines, with indication of how they behave ?? I'm unable to reproduce those errors here, but this might bring the details I need to figure it out... Certainly. First the working machine (reports solely 'changing root device to wd0s3a' and continues): *** Working on device /dev/rwd0 *** parameters extracted from in-core disklabel are: cylinders=970 heads=128 sectors/track=63 (8064 blks/cyl) parameters to be used for BIOS calculations are: cylinders=970 heads=128 sectors/track=63 (8064 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 6,(Primary 'big' DOS ( 32MB)) start 63, size 1048257 (511 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 129/ sector 63/ head 127 The data for partition 2 is: sysid 7,(OS/2 HPFS, NTFS, QNX or Advanced UNIX) start 1048320, size 3386880 (1653 Meg), flag 0 beg: cyl 130/ sector 1/ head 0; end: cyl 549/ sector 63/ head 127 The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 4435200, size 3386880 (1653 Meg), flag 0 beg: cyl 550/ sector 1/ head 0; end: cyl 969/ sector 63/ head 127 The data for partition 4 is: UNUSED # /dev/rwd0s3c: type: ESDI disk: Maxtor 84000A6 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 128 sectors/cylinder: 8064 cylinders: 420 sectors/unit: 3386880 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a:6451204.2BSD0 0 0 # (Cyl.0 - 7) b: 26611264512 swap# (Cyl.8 - 40) c: 33868800unused0 0 # (Cyl.0 - 419) e:64512 3306244.2BSD0 0 0 # (Cyl. 41 - 48) f: 2991744 3951364.2BSD0 0 0 # (Cyl. 49 - 419) Now the one which panics: *** Working on device /dev/rwd0 *** parameters extracted from in-core disklabel are: cylinders=790 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calculations are: cylinders=790 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 6,(Primary 'big' DOS ( 32MB)) start 63, size 208782 (101 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 12/ sector 63/ head 254 The data for partition 2 is: sysid 5,(Extended DOS) start 208845, size 8193150 (4000 Meg), flag 0 beg: cyl 13/ sector 1/ head 0; end: cyl 522/ sector 63/ head 254 The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 8401995, size 4289355 (2094 Meg), flag 0 beg: cyl 523/ sector 1/ head 0; end: cyl 789/ sector 63/ head 254 The data for partition 4 is: UNUSED # /dev/rwd0s3a: type: ESDI disk: wd0s3 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 267 sectors/unit: 4289355 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a:6426004.2BSD0 0 0 # (Cyl.0 - 3) b: 54621064260 swap# (Cyl.4 - 37) c: 42893550unused0 0 # (Cyl.0 - 266) e:64260 6104704.2BSD0 0 0 # (Cyl. 38 - 41) f: 3614625 6747304.2BSD0 0 0 # (Cyl. 42 - 266) The third one is unfortunately at home, I'll have access to it after approx 6.00PM CEST. Thank you, Thomas To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New ATA drivers problem? (Was: New kernels won't boot)
On Wed, 28 Apr 1999, Soren Schmidt wrote: Hi, I have three hosts with -current, all with the new ATA in function. Booting the same kernel produces different results on all of them wrt root file system mounting: - one reports 'changing root device to wd0s3a' - one reports 'changing root device to wd0s3a' followed by 'changing root device to wd0a' and continues flawlessly - one reports 'changing root device to wd0s3a' followed by 'changing root device to wd0a' and panics with 'cannot mount root file system (2), err 22' All motherboards are equipped with the PIIX4 IDE controller. If I need to supply the dmesg output and/or configuration, please let me know. All three hosts have FreeBSD on the first disk (on different disk locations, though). Hmm, could you mail me the output of fdisk disklabel from those tree machines, with indication of how they behave ?? I'm unable to reproduce those errors here, but this might bring the details I need to figure it out... -S?ren Ever going to help with my atapi-fd problems? I found examples of the corruptions, including lots of NULLs... To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
New kernels won't boot
On my machine, a kernel newer than one built on the 22nd will not complete booting, panicing about not being able to mount root. Another machine with a very similar config is fine. The main difference is that the faulty machine has its FreeBSD partition in an odd spot on the disk. Below is the dmesg output, the fdisk output and the config file. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Thu Apr 22 00:37:32 WST 1999 t...@bloop.craftncomp.com:/usr/src/sys/compile/bleep Timecounter i8254 frequency 1193182 Hz CPU: AMD Enhanced Am486DX4 Write-Through (486-class CPU) Origin = AuthenticAMD Id = 0x484 Stepping=4 Features=0x1FPU real memory = 16777216 (16384K bytes) avail memory = 13750272 (13428K bytes) Preloaded elf kernel kernel.good at 0xc02c4000. Probing for PnP devices: npx0: math processor on motherboard npx0: INT 16 interface pcib0: PCI host bus adapter on motherboard pci0: PCI bus on pcib0 chip0: Host to PCI bridge (vendor=10b9 device=1445) at device 0.0 on pci0 de0: Digital 21140 Fast Ethernet at device 4.0 on pci0 de0: interrupting at irq 11 de0: SMC 9332DST 21140 [10-100Mb/s] pass 1.2 de0: address 00:00:c0:a6:59:dc de0: enabling 10baseT port isa0: ISA bus on motherboard atkbdc0: keyboard controller (i8042) at port 0x60 on isa0 atkbd0: AT Keyboard on atkbdc0 atkbd0: interrupting at irq 1 vga0: Generic ISA VGA on isa0 sc0: System console on isa0 sc0: VGA color 16 virtual consoles, flags=0x0 ata1 at irq 14 on isa0 ata1: interrupting at irq 14 fdc0: interrupting at irq 6 fdc0: NEC 765 or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fd0: 1440-KB 3.5 drive at fdc0 drive 0 mse0 at port 0x23c irq 5 on isa0 mse0: interrupting at irq 5 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff irq 10 on isa0 ed0: address 00:00:c0:d2:b2:72, type SMC8216T (16 bit) ed0: interrupting at irq 10 ppc0 at port 0x378 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 lppps0: Pulse per second Timing Interface on ppbus 0 ppc0: interrupting at irq 7 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging disabled ds0 XXX: driver didn't set ifq_maxlen ad0: ST34321A/3.11 ATA-4 disk at ata0 as master ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, PIO mode changing root device to wd0s4a ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates *** Working on device /dev/rwd0 *** parameters extracted from in-core disklabel are: cylinders=1042 heads=128 sectors/track=63 (8064 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1042 heads=128 sectors/track=63 (8064 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: UNUSED The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 201600, size 7999488 (3906 Meg), flag 80 (active) beg: cyl 25/ sector 1/ head 0; end: cyl 1016/ sector 63/ head 127 machine i386 ident BLEEP maxusers10 options INCLUDE_CONFIG_FILE # Include this file in kernel config kernel root on ad0 dumps on ad0 cpu I486_CPU cpu I586_CPU # aka Pentium(tm) cpu I686_CPU # aka Pentium Pro(tm) options COMPAT_43 options USER_LDT#allow user-level control of i386 ldt options SYSVSHM options SYSVSEM options SYSVMSG options VM86 options DDB options KTRACE #kernel tracing options UCONSOLE options USERCONFIG #boot -c editor options INET#Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop#Network loopback device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device disc#Discard device pseudo-device tun 2 #Tunnel driver (ppp(8), nos-tun(8)) options TCP_COMPAT_42 #emulate 4.2BSD TCP bugs options MROUTING# Multicast routing
