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
