It seems Chris Faulhaber wrote:
> I have been seeing the same issue since August with a different,
> but similiar, set of drives:
>
> ad0: 57241MB [116301/16/63] at ata0-master UDMA100
> ad1: 57241MB [116301/16/63] at ata0-slave UDMA100
>
> Under -CURRENT only the first drive is seen; RELENG_4
Could you try this simple patch and see if that helps?
Index: ata-lowlevel.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-lowlevel.c,v
retrieving revision 1.23
diff -u -r1.23 ata-lowlevel.c
--- ata-lowlevel.c 2 Nov 2003 22:04:53
It seems Christoph Sold wrote:
> FreeBSD 5.2-B still does not detect my ATAPI DVD-ROM drive. This used to
> work until Søren's ATAng commits. Other OSes (Win, Linux, Solaris)
> detect the drive appropriately.
Hmm from the bootlogs it seems that your drive does not set the proper
ATAPI signature,
It seems Jun Kuriyama wrote:
>
> I got lockups in recent -current box. This box is my main workstation
> and usually be up to date kernel.
>
> In recent days, I usually locked up. This is not a panic, only locks
> up. My situation is:
>
> o KDE's clock is working.
> o KDE's virtual screen swi
It seems Joe Marcus Clarke wrote:
> I agree. I really needed to be up and running ASAP, so I opted for the
> new controller. Søren, if you're listening, and need an SiI controller
> for testing, you're free to have mine. Else, I can keep it and test it
> as needed (I can put a test drive on it).
It seems Will Andrews wrote:
> Yeah, that's what I figured. When I looked at the change, the
> fix only appears to affect rev 0x00, but my SiI3112A is 0x02. :(
The errata should be fixed in rev 2 silicon.
> Well, I can tell you that people aren't gonna be happy when their
> brand new motherboar
It seems Joe Marcus Clarke wrote:
> > There are some early issues of the SiI3112 chips that has problems that
> > can cause datacorruption etc etc..
> > You can try the following patch (which btw re@ has for approval),
> > otherwise I'd try another controller as there seem to be no end of the
> >
It seems Joe Marcus Clarke wrote:
> atapci1: port
> 0x14b0-0x14bf,0x14c0-0x14c3,0x14c8-0x14cf,0x14c4-0x14c7,0x14d0-0x14d7
> mem 0xe800a000-0xe800a1ff irq 9 at device 16.0 on pci0
> GEOM: create disk ad4 dp=0xc5246460
> ad4: 78167MB [158816/16/63] at ata2-master UDMA133
>
> Nothing else was chang
It seems Bruce M Simpson wrote:
> Hi all,
>
> kimchi# uname -a
> FreeBSD kimchi.dek.spc.org 5.2-BETA FreeBSD 5.2-BETA #4: Sun Nov 23 01:52:10 GMT
> 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/KIMCHI i386
>
> atacontrol doesn't report any devices. Using commands such as cap/info/list
>
It seems Dag-Erling Smørgrav wrote:
> Soren Schmidt <[EMAIL PROTECTED]> writes:
> > Disregard above, some crappy port has installed "cups" which apparently
> > has its own "lpr" command, nice...
>
> Sorry, but *you* are the "crappy port".
It seems Soren Schmidt wrote:
>
> On a fresh current 23/11 1600CET :
>
> normal user cannot print anymore:
>
> >lpr
> lpr: error - scheduler not responding!
>
> but as root things works as expected.
>
> Ideas ? or another item for the "bugs to fix&q
On a fresh current 23/11 1600CET :
normal user cannot print anymore:
>lpr
lpr: error - scheduler not responding!
but as root things works as expected.
Ideas ? or another item for the "bugs to fix" list ?
-Søren
___
[EMAIL PROTECTED] mailing list
htt
It seems Christian Laursen wrote:
> I just upgraded my workstation from 5.1-RELEASE to todays -CURRENT.
>
> When I boot it, I get the following messages about my CD drives:
>
> acd0-5: CDROM with 6 CD changer at ata1-master PIO4
> acd6: DVDROM at ata1-slave PIO4
> acd0-5: FAILURE - LOAD_UNLOAD
It seems Lars Eggert wrote:
> Lars Eggert wrote:
> > Soren Schmidt wrote:
> >
> >>> Is there any other patch I can try? I've just confirmed that this bug
> >>> still exists with today's kernel.
> >>
> >> I cant reproduce the
It seems Andy Farkas wrote:
>
> When messages are sent to console rapidly, console becomes unavailable :(
That is an oold problem, at least its been do for months...
> My previous email complains of messages being spewed to the console. These
> messages stop after a few minutes and the console i
It seems Robert Watson wrote:
> How fast are your systems, speaking of which? I live in the world of
> 300-500 mhz machines at work, and 300-800 mhz boxes at home. If you're
> using multi-ghz boxes, that could well be the distinguishing factor
> between our configurations...
Server is 533MhzVIA
It seems Matt Smith wrote:
> With a current build from november the 9th I am still getting exactly
> the same NFS lockups. I assume soren is as well. NFS has basically been
> pretty unusable now for over a month.
Yes I do, NFS is virtually useless...
> As only a couple of people have complained
It seems Peter Edwards wrote:
> With a -current built after atapi-cd was changed over to GEOM, reads
> from a filesystem mounted on a CD device are being corrupted, with
> junk being inserted into the file from offset 63489 onwards.
>
> I had a quick look around atapi-cd.c, and I think I spotted t
It seems Josef Karthauser wrote:
> p.s. are there any plans to fix power cycling of ide harddrives
> with an acpi suspend? I can get my machine to suspend, but the power
> runs down because the hard drive is still spinning.
Hmm, on the laptops I have thats done automatically, but that seems
not t
It seems Kris Kennaway wrote:
-- Start of PGP signed section.
> Since upgrading the bento package machines to -current I am getting
> a lot of the following errors:
>
> ad0: FAILURE - READ_DMA status=51 error=40
That does look like a valid error condition from the drive...
> 1) All my drives hav
It seems Jeremy Messenger wrote:
> On Fri, 07 Nov 2003 10:10:40 +0100, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote:
>
> > I've been having a variety of problems burning CDs with atang:
> >
> > - burncd consistently failing in exactly the same spot in the ISO,
> >and reporting "only wrote 0
It seems Kirill Ponomarew wrote:
> I got panic during the boot:
>
> ioapic0: Changing APIC ID to 2
> ioapic0 irqs 0-23 on motherboard
> panic: Can't find ExtINT pin to route through!
> cpuid=0;
>
> Is it known problem ?
Dunno, but I get it as well when I set interrupt mode to APIC in
the BIOS,
It seems Josef Karthauser wrote:
-- Start of PGP signed section.
> I've been getting a lot of this kind of error from my cdrom drive on a
> variety of disks recently:
>
> acd0: FAILURE - READ_BIG status=51 sensekey=ILLEGAL REQUEST
> error=1
> acd0: FAILURE - READ_BIG status=51 sensekey=IL
It seems Lars Eggert wrote:
> Bruce Evans wrote:
> > On Thu, 30 Oct 2003, Soren Schmidt wrote:
> >>
> >>Anyhow if you loose the test for error in atapi-cd.c::acd_tray in the
> >>close case, does it work then ? Problem is that the call to read toc
> >>mi
It seems Anshuman Kanwar wrote:
Ehem, this machine is NOT ServerWorks based, its Intel...
> rack2-102.nyc# pciconf -l
> [EMAIL PROTECTED]:0:0: class=0x06 card=0x chip=0x254c8086 rev=0x01
> hdr=0x00
> [EMAIL PROTECTED]:2:0: class=0x060400 card=0x chip=0x25438086 rev=0x01
> hdr=
It seems Matthias Andree wrote:
> Hi,
>
> I received a bug report against BerkeleyDB 4 that may not be BerkeleyDB
> related, but a problem with FreeBSD or specific hardware in general.
>
> Jie Song (CC'd) reported that writing files with BerkeleyDB (no
> threading or something) on his ServerWorks
It seems John Baldwin wrote:
>
> On 01-Nov-2003 Soren Schmidt wrote:
> > It seems Sean Chittenden wrote:
> >> Howdy. I'm not sure if this is a ULE bug or a KSE bug, or both, but,
> >> for those interested (this is using ule 1.67, rebuilding world now),
>
It seems Dag-Erling Smørgrav wrote:
> Soren Schmidt <[EMAIL PROTECTED]> writes:
> > It diapeared some time ago, but setting it in loader.conf still works
> > you just cannot see it. Its on my TODO list, but real bugs has priority
> > over this minor nit...
>
> Th
It seems Harald Schmalzbauer wrote:
>
> I always had it in loader.conf.local but why is this sysctl not listed
> anymore?
> cale:~> sysctl hw.ata
> hw.ata.ata_dma: 1
> hw.ata.wc: 1
>
> I can remember some other sysctl which were not displayed before altered.
> How can I get ALL sysctls? (-a also
Is this available anywhere ?
-Søren
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
It seems Harald Schmalzbauer wrote:
>
> Ha, stop. Today it doesn't work as non-root anymore.
> I'm sure with -current some days ago and the same patch it worked without root
> privileges.
> I can't follow that.
Thats a feature of atapi-cd now being under GEOM..
The device nodes are now mode 640
It seems Sven Esbjerg wrote:
> On my Fujitsu-Siemens S-4572 I get random hangs when doing recursive copying
> to af mfs device. I suspect it has something to do with the fact the I still
> get a lot of spurious interrupst on the ata controller.
Those spurious interrupts are because ata1 share irq1
It seems Sean Chittenden wrote:
> Howdy. I'm not sure if this is a ULE bug or a KSE bug, or both, but,
> for those interested (this is using ule 1.67, rebuilding world now),
> here's my stack. I couldn't figure out where td was being set to
> NULL. :( Oh! Where is TD_SET_LOCK defined? egrep -r
It seems Lars Eggert wrote:
> > I've already committed a solution that works on all the drives I
> > could test on (some of which failed before), if this still
> > fails for you I'd like a more detailed description of what
> > exactly goes wrong...
>
> I must have missed that commit message, sor
It seems Lars Eggert wrote:
> FYI, the issue is still present with yesterday's -current. Will Pav
> Lucistnik's patch be committed soon?
I've already committed a solution that works on all the drives I
could test on (some of which failed before), if this still
fails for you I'd like a more deta
It seems David Gilbert wrote:
> I have tried several times in recent days to burn DVDs with burncd,
> growisofs and cdrecord ... all of which worked before atang.
> Growisofs complains that it can't flush it's buffers. Burncd doesn't
> complain ... but the resulting disk is not mountable.
>
> I t
It seems Matt wrote:
> I'm now running a kernel/world of October 26th on both NFS client and
> server machines. I am still seeing NFS lockups as reported by several
> people in these threads:
>
> http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1296172+0+archive/2003/freebsd-current/20031026.freebsd
It seems Nate Lawson wrote:
> > > * Panic occurs after ATAFD fails to probe. Last event: 2003/10/6
> > > I have no ATAFD device on my system and normally no messages are printed
> > > about it on boot. However, periodically ATAFD will print a bunch of
> > > messages on console about failing to pr
It seems Matt wrote:
> I have a typical NFS setup where I have two boxes both running -CURRENT
> from around 24 hours ago. One box runs nfsd and rpcbind, and the other
> nfsclient and mounts /usr/ports, /usr/src and /usr/obj read/write.
>
> Since this latest cvsup I am finding that something is
Just got this one (using bsd scheduler):
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x24
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc04b8f3b
stack pointer = 0x10:0xcd619bc4
frame pointer = 0x10:0xcd6
I have now found a way to reproduce the DMA problems some setups seems
to be having with the SiI3112A SATA chip.
Now, if I use real SATA drives, (and I mean real SATA drives, the
WD Raptor fx is not a real SATA device but just a PATA device
with a build in PATA->SATA converter chip) it works just
It seems Hiroyuki Aizu wrote:
> Hi.
>
> The original ata_reset() lost ATA-master drive and remove main file system
> after suspend/resume. Of cource it occors panic!
> I think that the ata_reset() in ata-lowlevel.c is bogus and I can not
> understand the code. So I study ATA and rewrite ata_reset(
It seems Balazs Nagy wrote:
> Hi,
>
> I had a -CURRENT setting with an Abit BE7-S and two SATA disks with
> vinum configuration. It worked very well until a power failure, and
> the mainboard died. Yesterday I got a replacement mainboard, the only
> type met the requirements (eg. two SATA por
It seems Christoph P. Kukulies wrote:
> Help! Am I alone with this? I cvsuped again today built world,kernel.
> Still this panic. Soeren, do you get this also? You have the Motherboard
> P4S8X which I donated a couple of months ago.
Nope, I dont see this at all. No problems whatsoever with the P3S
It seems Matteo Riondato wrote:
>
> It works perfectly and solves my problem.
> Thanks.
> Do you plan to commit it?
Already done :)
-Søren
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
It seems Matteo Riondato wrote:
> After having update my -CURRENT box to yesterday afternoon (Central
> Europe Time) sources, I can't get it to boot. It stops probing ata1:
> GEOM: create disk ad0 dp=0xc4536a70
> ad0: 57259MB [116336/16/63] at ata0-master UDMA133
> GEOM: create disk ad1 dp=0xc4915
It seems Johny Mattsson wrote:
> Hi all,
>
> Quick question: Is there an "official" way of changing ATA modes on
> boot/startup? I grepped my /etc/rc.d (5.1-R) for 'atacontrol' and did a
> quick search of the archives, but both came up empty, so I'm guessing
> there isn't.
>
> I'm quite happy
It seems Dan Nelson wrote:
> In the last episode (Oct 08), Robert Ferguson said:
> > I see this problem as well. I'm running on a T40, with a DVD/CDRW in
> > the ultrabay, and -CURRENT as of this morning. At boot, it hangs
> > immediately after
> >
> > ad0: 35174MB [71465/16/63] at ata0-maste
It seems Josef Karthauser wrote:
> I've just built and installed a new kernel, the first since Aug 6th.
> There appears to be a problem with the IP stack. What happens is that
> everything is fine for a few hours, and then the IP stack stops working.
> I can no longer ping anything on the local ne
It seems Antony T Curtis wrote:
> > Does your laptop have an Acer chipset? There are issues with them, I
> > have a similar problem on my fujitsu.
The Acer bug has been resolved, pointy hat to me :)
-Søren
___
[EMAIL PROTECTED] mailing list
http://lis
It seems Radko Keves wrote:
> hi
>
> this verbosed dmesg is from my box maybe it help you
Uhm, and what exactly is the problem ?
-Søren
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send an
It seems Daniel Rock wrote:
> > I recently decided to update my alpha UP1000 to today's current from a
> > mid-July build. However, UDMA33 did not work on a hard disk attached
> > to the built-in Acer Aladdin controller (verbose dmesg appended).
> >
> > I think I have narrowed the problem down to
It seems Vladimir B. Grebenschikov wrote:
> Does not help, another panic in ad_attach:
ARGH, try this instead:
diff -u -r1.191 ata-all.c
--- ata-all.c 7 Oct 2003 13:44:15 - 1.191
+++ ata-all.c 8 Oct 2003 08:03:09 -
@@ -35,6 +35,7 @@
#include
#include
#include
+#include
It seems Vladimir B. Grebenschikov wrote:
> > Any solution or workaround ?
Try this patch please:
diff -u -r1.191 ata-all.c
--- ata-all.c 7 Oct 2003 13:44:15 - 1.191
+++ ata-all.c 7 Oct 2003 19:15:03 -
@@ -35,6 +35,7 @@
#include
#include
#include
+#include
#include
#in
It seems Derek Ragona wrote:
> The SATA seems better, but is still not working. I tried the Oct 5
> snapshot, doing a clean install. I CVSup'd and did
> make buildworld
> make buildkernel KERNCONF=GENERIC
> make installkernel KERNCONF=GENERIC
> reboot to single user
> mount -a
> swapon -a
> merg
It seems Jan Stocker wrote:
> I've updates my -current system from Sep, 14th to todays -current (2
> hours old). Now i cant boot further than detecting cdrom drives. After
> testing my second cdrom (cdrw) for its UDMA capabilities the kernel
> hangs in an endless loop. The output is a repeat from t
It seems Christoph Sold wrote:
> I set up a box
>
>(FreeBSD 5.1-CURRENT #0: Tue Sep 23 00:21:31 CEST 2003
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC,
> compiled from the sources the day before)
>
> showing the erratic behaviour. Verbose boot logs are available at
>
>http://
It seems Steve Ames wrote:
> G'day.
>
> My company is putting together a system with lots of file system on it to do disk
> based backup.
>
> Under 5.1-CURRENT what's the best supported (and performing optimally) SATA RAID
> controller (RAID 0, maybe 5)? What manufacturer/model of SATA disks do
It seems Will Andrews wrote:
> On Tue, Sep 30, 2003 at 10:22:33PM +0200, Soren Schmidt wrote:
> > No what I mean is that the Raptor is a PATA device fitted with a
> > marvell PATA->SATA converter "on board", its not a "pure" SATA
> > design, but j
It seems Will Andrews wrote:
> On Tue, Sep 30, 2003 at 10:06:40PM +0200, Soren Schmidt wrote:
> > I have now found a way to reproduce the DMA problems some setups seems
> > to be having with the SiI3112A SATA chip.
> >
> > Now, if I use real SATA drives, (and I mean r
I have now found a way to reproduce the DMA problems some setups seems
to be having with the SiI3112A SATA chip.
Now, if I use real SATA drives, (and I mean real SATA drives, the
WD Raptor fx is not a real SATA device but just a PATA device
with a build in PATA->SATA converter chip) it works just
It seems Gabriel Ambuehl wrote:
> The drivers in 28.9.JPSNAP of current will allow you to install
> FreeBSD on a SATA disk connected to a Silicon Image 3112 SATA RAID
> controller but not much more. Shortly after booting, the system will
> start getting UDMA timeouts and basically just freezes. Fur
It seems Michael McGoldrick wrote:
> I haven't been able to boot a -current kernel since the ATAng import.
> They all die after (in a boot -v) a message from GEOM about creating ad0.
> If any further info would be helpful, just let me know what you need.
I know there are a problem with *some* Acer
It seems Derek Ragona wrote:
> Søren,
>
> My setup is as follows:
> Maxtor 6Y120MO 120GB SATA drive
> Adaptec Serial ATA RAID 1210SA
> Intel® Desktop Board D845GEBV2
> 1GB RAM
> 1.7 GHz Celeron CPU
Ok, I'll try to get something semialr setup here and try to reproduce.
> If there is some way to g
It seems Peter Wemm wrote:
>
> > Hi, I want to report a regression in ATAng. It's exactly same problem
> > that Richard Nyberg reported on current@ 9 days ago.
> >
> > After updating to today -current, my system no longer see primary slave
> > hard drive. It's one year old Seagate 80 GB hard driv
It seems Robert Ferguson wrote:
> Last week, Nate Lawson reported a panic in 5.1-CURRENT as described
> below. However, despite the apparent resolution, doing a clean install
> on an IBM t40 with the most recent snapshot from
> snapshots.jp.freebsd.org still results in the same panic for me.
>
> I
It seems Putinas wrote:
> Hi all,
> Inspired with all the FreeBSD is free software , windows and buggy hardware
> and blabla I realize what maybe I could do more to help solve this problem.
> I made small research on my computer and I find out what till the cvsup date
> 2003.08.24.00.00.00 till ATA
It seems Daniel Eischen wrote:
> > It seems Daniel Eischen wrote:
> > > On a kernel built just a few hours ago, it hangs on boot
> > > right after:
> > >
> > > acd0: CDROM at ata0-master PIO4
> >
> > Get atapicam out and see if that helps..
>
> No, using latest sources, with or without atapicam
It seems Derek Ragona wrote:
> I have a single SATA drive on an Adaptec 1210SA card.
>
> The drive will give a write error warning a few times, then will repeatedly
> give:
> ad4: timeout sending command=ca
>
> The only recovery is the reset switch, reboot single-user fsck, and then
> come back
It seems Vladimir Kushnir wrote:
>
> > > Together with sys/cdio.h, where both ioc_read_audio and CDIOCREADAUDIO are
> > > declared
> >
> > I'll get rid of those...
> >
> Again, a pity. What benefits do we gain here? Speed? CDDA extraction never
> required all that much of it, and to be honest the
It seems Daniel Eischen wrote:
> On a kernel built just a few hours ago, it hangs on boot
> right after:
>
> acd0: CDROM at ata0-master PIO4
Get atapicam out and see if that helps..
-Søren
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/ma
It seems Jan Srzednicki wrote:
> > dd if=/dev/acdXtY of=trackY bs=2352
>
> Cool. ;)
Yes, and that has worked for ages...
> Could you give me a hint what to put in devd.conf to get acdXtY files
> created automatically when a CD is inserted?
You just need something to open the acdX device (so the
It seems Vladimir Kushnir wrote:
> > The right way of doing audio graps has been to set the wanted blocksize
> > with CDRIOCSETBLOCKSIZE (not needed if all tracks on the CD is of
> > the same size), then just read from the device. Ioctl's was newer meant
> > to be used to read/write data, its also
It seems Jan Srzednicki wrote:
> > As far as problems with dagrab and cdda2wav are conserned - this is
> > because of removal of CDIOCREADAUDIO ioctl in ATAng (see recent thread
> > "What's happened to CDIOCREADAUDIO & friends")
>
> I've seen it (after posting the original mail, though;). Is there
It seems =?koi8-r?Q?=22?=Ayrton Senna=?koi8-r?Q?=22=20?= wrote:
> This became quite tricky, but the main (and the worst problem) was with ATAng.
> I have Acer's motherboard and IBM's DTLA. Old driver were saying 'Non-ATA 66 cable
> or device' and perfectly worked in UDMA-33 mode. New driver didn't
It seems Thomas Quinot wrote:
> Le 2003-09-18, Jan Srzednicki écrivait :
>
> > Anyway, here's backtrace for atapicam panic I've mentioned. It's
> > triggered by:
> >
> > cdrecord dev=1,1,0 /some/track
>
> Um. Do you see the same crash if both drives contain CDs at boot time?
> If not, this could
It seems Mark Knight wrote:
> Current from approximately 0500 BST on 16th September is giving me
> errors like this from boot:
>
> ad0: WARNING - WRITE_MUL write data underrun 8192>2048
> ad0: WARNING - WRITE_MUL write data underrun 8192>6144
> ad0: WARNING - WRITE_MUL write data underrun 8192>40
It seems Jan Srzednicki wrote:
> > > First of all, the drive still does not get detected properly. Funny
> > > thing is that after some playing with atacontrol attach/detach, it
> > > finally gets detected. And later on, it is normally detected, before.
> > > Same scenario happened like 3 times wit
It seems Jan Srzednicki wrote:
> First of all, the drive still does not get detected properly. Funny
> thing is that after some playing with atacontrol attach/detach, it
> finally gets detected. And later on, it is normally detected, before.
> Same scenario happened like 3 times with ATAng and newe
It seems Vladimir Kushnir wrote:
> Hello,
> We used to have this ioctl in old ATA/ATAPI driver (and still do in
> sys/cdio.h); apparently, it's no longer there with ATAng. Is this a bug or
> feature? And if this was planned what's going to replace it? As it is,
> this change has broken cdparanoia c
It seems Dag-Erling Smørgrav wrote:
> Soren Schmidt <[EMAIL PROTECTED]> writes:
> > Well, the ATA driver has just grown more standard compliant :)
> > You *must* hang around for 31secs to wait for slow devices to come ready,
> > according to the ATA specs. Now I'v
It seems Conrad J. Sabatier wrote:
>
> ATAng will no longer recognize the DVD-ROM device on ata1-master. This is
> without atapicam. The CD-RW drive at ata1-slave is OK, and is being assigned
> to acd0 now.
OK, from you dmesg:
>ata1: reset tp1 mask=03 ostat0=50 ostat1=50
>ata1-master: stat=0
It seems Joachim Strömbergson wrote:
> > Thanks! I guess I'm too impatient these days... Yes, it works after waiting
> > for about 30 seconds. So a correction, it doesn't hang, it's just slow when
> > detecting :).
>
> So now the tousand dollar question becomes "What in the boot contains a
> ti
It seems Petri Helenius wrote:
> The problem of not being able to reboot without a panic seems to persist on
> late current with ATAng and SMP.
The below doesn't say much actually, but I can reboot to my hearts content
on my SMP box here with no problems. What else do you have in that kernel ?
>
It seems Dario Freni wrote:
> > Could you please boot verbose and mail me the output of dmesg ?
>
> Sure. That's in attachment.
Okies, you need to update as there has been changes since this that
should fix the problem.
-Søren
___
[EMAIL PROTECTED] mai
It seems Pav Lucistnik wrote:
>
> This patch works for me. Any chance to get it committed?
I'll look at it...
-Søren
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL P
It seems Dario Freni wrote:
> > ata0: resetting devices ..
> > ata0-slave: FAILURE - ATA_IDENTIFY status=51 error=4
> > done
> >
> > Does anyone recognize this or have any idea why this happens or how I can
> > debug it further to get an idea?
>
> The same here (on a workstation) with an AOpen DV
It seems Larry Rosenman wrote:
> Also, when coming back up after the Panic on the same kernel, we get
> unexpected soft-update
> inconsistencies, cannot write block type errors from FSCK.
>
> Going back to my September 9, 2003 kernel, fsck deals with the same exact
> filesystem just fine.
What
It seems Pete Carah wrote:
>ASUS P5A or P5AB (one of each now) - won't boot without setting
>hw.ata.ata_dma=0. GEOM recognizes the drive itself but then the reads
>of the disklabels fail with a message that I can't find in the source,
>about a DMA failure. System then prompts to mount root and no
It seems Alastair G. Hogge wrote:
> Just a follow up.
>
> I've since been able to get my -CURRENT system running under the new build.
> However the booting process is still slow around those ata?: [MPSAFE]
> messages. Any ideas on getting a speed up?
I'm working on it...
-Søren
___
It seems Ashley Penney wrote:
> Hiya,
>
> I recently upgraded my -current box, only to have my Serial ATA device move
> from ar0 to ad6, making things cry.
Read UPDATING!! (hint you need to include device ataraid in your config).
-Søren
___
[EMAIL PROT
It seems Stefan Ehmann wrote:
> After tonight's cvsup and kernel build my primary slave hard disk gets
> no longer detected.
>
> This is due to the latest update to src/sys/dev/ata/ata-lowlevel.c. When
> i revert from version 1.10 to 1.9 everything is fine again.
>
> So much about the "Hopefully
It seems Shin-ichi Yoshimoto wrote:
> My recent kernel still got the panic when I tried to do CVSup.
>
> # cvsup -g -z -L 2 /home/yosimoto/mk/daemon-supfile 2>&1 | tee
> /var/tmp/log/cvsup.`date "+%m%d.%H.%M.%S"`;
> Parsing supfile "/home/yosimoto/mk/daemon-supfile"
> Connecting to cvsup.jp.FreeB
It seems Nate Lawson wrote:
> With a fresh checkout of last night's -current, I cannot boot my laptop.
> ATAFD panics the box by reusing freed memory. I do not have a floppy
> drive in the laptop and when I do, it's a legacy floppy, not atapi. Here
> are the messages:
>
> [normal ad0/acd0 probe
It seems David Gilbert wrote:
> Soren> Uhm, I'm working on finding the real problem, and I'd like that
> Soren> to be the solution. However the above may be a good workaround
> Soren> for those bitten by this...
>
> Well... is it not possible for malicious hardware to claim to have
> zero blocks (
It seems Petri Helenius wrote:
> It seems that the same bug that initially stopped ataraid working
> at all is there with rebuild:
>
> kompak# atacontrol rebuild 0
> ad4: FAILURE - oversized DMA transfer attempted 131072 > 65536
> ad4: setting up DMA failed
> kompak# atacontrol status 0
> ar0: ATA
It seems Soren Schmidt wrote:
> Forget that, wrong patch, here goes the right one:
DOH! things are not going weel this morning, this patch should be right:
Index: ata-lowlevel.c
===
RCS file: /home/ncvs/src/sys/dev/ata/
It seems Soren Schmidt wrote:
> It seems YazzY wrote:
> > Hi.
> >
> > It can be mounted when I boot the laptop and do not take the card out of
> > the slot.
> > If I eject it and then put it back in, I cannot mount it or dd files to
> > it anymore...
>
It seems YazzY wrote:
> Hi.
>
> It can be mounted when I boot the laptop and do not take the card out of
> the slot.
> If I eject it and then put it back in, I cannot mount it or dd files to
> it anymore...
> Anyway, this bit of dmesg does not look healthy to me. And as I said,
> everything wor
It seems David Gilbert wrote:
> I submitted kern/56572 a few minutes ago. It patches ata-disk.c to
> reject a disk that has zero blocks.
>
> This is a good thing ... malicious or broken disks (compact flash,
> whatever) shouldn't crash machines.
>
> But in this case, the detected ad3 doesn't exi
1 - 100 of 567 matches
Mail list logo
