Date: Fri, 17 Jun 2011 08:09:25 +0000 From: Alexander Best <arundel@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: two issues after upgrading to a more up-to-date HEAD Message-ID: <20110617080925.GA68431@freebsd.org> In-Reply-To: <20110616102601.GA68610@freebsd.org> References: <20110616102601.GA68610@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu Jun 16 11, Alexander Best wrote: > hi there, i reverted my kernel back to r222890. everything works fine now and both issues i mentioned below dissapeared. i also discovered another issue with the more recent kernel: i was getting errno -128 with a lot of apps. but only the first time i ran them. e.g. with git: 1) -128 2) OK 3) -128 4) OK 5) ... the same with stuff like ./configure or ee(1). first time failures while running or saving; second time it works. this as well was fixed by reverting back to r222890. cheers. alex > > i'm running HEAD on amd64. yesterday i updated my kernel to r223109. i'm now > seeing two issues, which weren't there beforehand: > > 1) > ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 > ada0: <SAMSUNG SP2504C VT100-50> ATA-7 SATA 2.x device > ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada0: Command Queueing enabled > ada0: 238474MB (488395055 512 byte sectors: 16H 63S/T 16383C) > ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 > ada1: <SAMSUNG HD103SJ 1AJ10001> ATA-8 SATA 2.x device > ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada1: Command Queueing enabled > ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) > xpt_action_default: CCB type 0xe not supported > xpt_action_default: CCB type 0xe not supported > xpt_action_default: CCB type 0xe not supported > cd0 at ahcich2 bus 0 scbus2 target 0 lun 0 > cd0: <HL-DT-ST DVDRAM GH24NS50 XP02> Removable CD-ROM SCSI-0 device > SMP: AP CPU #1 Launched! > cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes) > cd0: cd present [2291664 x 2048 byte records] > > ^^ i suspect the xpt_action_default messages have been introduced by the recent > CAM changes. they appear to be harmless though. > > 2) > dumpon: ioctl(DIOCSKERNELDUMP): Device not configured > /etc/rc: WARNING: unable to specify /dev/label/swapfs as a dump device > > /dev/label/swapfs is a perfect swap partition and worked without any problems > beforehand. specifying the device node instead of the label makes no > difference: > > taku% dumpon /dev/ada1p1 > dumpon: ioctl(DIOCSKERNELDUMP): Device not configured > otaku% gpart show > => 34 488394988 ada0 GPT (232G) > 34 128 1 freebsd-boot (64k) > 162 16777216 - free - (8.0G) > 16777378 471617644 3 freebsd-ufs (224G) > > => 34 1953525101 ada1 GPT (931G) > 34 20971520 1 freebsd-swap (10G) > 20971554 4194304 2 freebsd-ufs (2.0G) > 25165858 1928359277 3 freebsd-ufs (919G) > > otaku% glabel status > Name Status Components > label/boot N/A ada0p1 > gptid/e52df583-e446-11de-bb92-000fb58207c8 N/A ada0p1 > ufs/rootfs N/A ada0p3 > label/swapfs N/A ada1p1 > ufs/varfs N/A ada1p2 > ufs/usrfs N/A ada1p3 > iso9660/Futurama Season 6 Ep 1-8 720p N/A cd0 > > cheers. > alex > > -- > a13x -- a13x
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110617080925.GA68431>