| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
do support 64bit addresses, the current SCRIPTS code supports only 32bit
addresses causing data corruption for buffer addresses >4GB. This problem
affects 64bit machines with more than 4GB RAM or amd64 with 4GB and
memory hole remapping.
Work-around this problem with a bus_dma tag that requests bounce-buffers
for addresses >4GB. This causes some overhead, but given the maximum SCSI
bus speed of 160MB/s compared, the effect should hardly be noticeable.
The problem was reported by Mike Watters (mike at mwatters net) who also
verified that this fix cures the problem.
Since this change is a NOOP on systems with less than 4GB RAM and fixes
data corruption (in RAM and on disk) on systems with more than 4GB, I hope
that this change is accepted for 8.0.
MFC after: 3 days (pending approval)
|
| |
|
|
|
|
|
|
|
|
| |
- Remove most of direct relations between ATA(4) peripherial and controller
levels. It makes logic more transparent and is a mandatory step to wrap
ATA(4) controller level into ATA-native CAM SIM.
- Tune AHCI and SATA2 SiI drivers memory allocation a bit to allow bigger
I/O transaction sizes without additional cost.
|
|
|
|
|
|
| |
PR: 139230
Submitted by: pluknet <pluknet@gmail.com>
MFC after: 1 week
|
|
|
|
|
| |
Sync connection speed reporting with kernel.
Report speed in identify command, same as done by inquiry.
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Reduce code duplication in ATA XPT and PMP driver.
- Move PIO size setting from ada driver to ATA XPT. It is XPT business
to negotiate transfer details. ada driver is now stateless.
- Report PIO size to SIM. It is required for correct PATA SIM operation.
- Tune PMP scan timings. It workarounds some problems with SiI.
- If reset hapens during PMP initialization - restart it.
- Introduce early-initialized periph drivers, which are used during initial
scan process. Use it for xpt, probe, aprobe and pmp. It gives pmp chance
to finish scan before mountroot and numerate devices in right order.
|
|
|
|
|
|
|
|
| |
There is no need to use the lower 4 bits of the unit number to store the
device type number. Just use 0 and 1 to distinguish them. devfs also
guarantees that there can never be an open call on a device that has a
unit number different to 0 and 1, so there is no need to check for this
in open().
|
|
|
|
|
|
|
|
|
|
|
|
| |
d_uid, d_gid and d_mode are unused, because permissions are stored in
cdevpriv nowadays. d_kind doesn't seem to be used at all. We no longer
keep a list of cdevsw's, so d_list is also unused.
uid_t and gid_t are 32 bits, but mode_t is 16 bits, Because of alignment
constraints of d_kind, we can safely turn it into three 32-bit integers.
d_kind and d_list is equal in size to three pointers.
Discussed with: kib
|
|
|
|
|
|
| |
Ensure target/lun passed from user-level supported on this bus.
Scanning unsupported IDs causes different issues from duplicate
devices to system crash.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
zfs_access() instead of vaccess() in this case as well.
- If VADMIN is specified with another V* flag (unlikely) call both
zfs_access() and vaccess() after spliting V* flags.
This fixes "dirtying snapshot!" panic.
PR: kern/139806
Reported by: Carl Chave <carl@chave.us>
In co-operation with: jh
MFC after: 3 days
|
|
|
|
|
|
| |
input to be in non-buffering mode so that input lines are logged
as they occur rather than being saved up until a buffer's worth of
input has been logged.
|
|
|
|
| |
This adds support for Marvell 6042/7042 chips and Adaptec 1430SA controller.
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
- Don't bother to assign vb until we know we have enough space
- Add variables for sx2, sy2, dx2, dy2 so that these aren't
calculated over and over, also reduce chance of errors.
- Use switch to assign color/format
MFC after: 3 days
|
|
|
|
|
|
|
| |
* Fix the main loop to search all buffers before sleeping.
* Remove dead code
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
- We don't need to check malloc return values with M_WAITOK
- remove variables that we don't really need
- cleanup the error paths by just calling drm_sg_cleanup()
- fix drm_sg_cleanup() to be safe to call at any time
MFC after: 2 weeks
|
| |
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
| |
PR: 124202
Submitted by: Andre Albsmeier <Andre.Albsmeier@siemens.com>
Reviewed by: gibbs
MFC after: 1 week
|
|
|
|
|
| |
compares with a low address (0x1000) and a high address
(the KVA kernel stack).
|
|
|
|
|
|
|
|
|
| |
bspatch thus does not verify file hashes, and that consequently it
is recommended that users store hashes separately and verify files
before and after running bspatch.
Requested by: BugMagnet
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
| |
lock and curproc->p_sigacts->ps_mtx. Reschedule_signals may need to have
ps_mtx locked to decide and wakeup a thread, causing recursion on the
mutex.
Inform kern_sigprocmask() and reschedule_signals() about lock state
of the ps_mtx by new flag SIGPROCMASK_PS_LOCKED to avoid recursion.
Reported and tested by: keramida
MFC after: 1 month
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
- More descriptive error messages when failing to parse components during
attach.
|
|
|
|
|
| |
Approved by: rrs (mentor)
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
and sum them to form the total counts.
PR: bin/135893
Submitted by: Mikolaj Golub to my trociny of gmail
MFC after: 1 week
|
|
|
|
|
|
| |
testing Adaptec's vendor driver.
Submitted by: Adaptec, driver 17517
|
| |
|
|
|
|
|
|
| |
included in "device scbus".
MFC after: 3 days
|
|
|
|
|
|
|
| |
the fallback of using the filter as an interrupt handler, as it is no
longer needed.
Discussed with: scottl, jhb
|
|
|
|
|
|
|
| |
with proc lock held.
Reported and tested by: Mykola Dzham freebsd at levsha org ua
MFC after: 1 month
|
|
|
|
| |
mode on those CPUs that need it.
|
| |
|
|
|
|
|
| |
Submitted by: Mikolaj Golub to my trociny of gmail
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
portion of the capture buffer (db_capture_bufoff vs db_capture_bufsize).
This could result in outputting garbage (e.g. lots of 'p' characters if
DIAGNOSTIC is enabled) after the end of the capture buffer. While here,
fix a spelling nit.
Reported by: Mikolaj Golub to my trociny of gmail
MFC after: 3 days
|
|
|
|
|
|
| |
SATA controllers, like those found on the G5 Xserve.
Reviewed by: mav
|
|
|
|
|
|
|
|
|
|
| |
obsoleted in 1996 by ATA-2, and crashes some modern hardware like some
revisions of the Serverworks K2 SATA controller. Even very ancient
hardware seems not to require it. In the unlikely event this causes
problems, the previous behavior can be re-enabled by defining
ATA_LEGACY_SUPPORT at the top of this file.
Reviewed by: Alexander Motin <mav@freebsd.org>
|
|
|
|
| |
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
|
| |
of nanotime(). Reflect this change in a manpage.
Reviewed by: phk, markm
|
|
|
|
| |
Reviewed by: phk, markm
|
|
|
|
|
|
|
|
|
|
|
|
| |
partially fixed on amd64 earlier. Rather than forcing linux_mmap_common()
to use a 32-bit offset, have it accept a 64-bit file offset. This offset
is then passed to the real mmap() call. Rather than inventing a structure
to hold the normal linux_mmap args that has a 64-bit offset, just pass
each of the arguments individually to linux_mmap_common() since that more
closes matches the existing style of various kern_foo() functions.
Submitted by: Christian Zander @ Nvidia
MFC after: 1 week
|
|
|
|
|
|
| |
PR: 137758
Submitted by: Henning Petersen <henning.petersen@t-online.de>
MFC after: 1 week
|
|
|
|
|
| |
Submitted by: Ulrich Spoerlein (1)
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
later on would try to free it, leading to a crash.
PR: 93998
Submitted by: neel
MFC after: 1 week
|
|
|
|
| |
driver.
|
|
|
|
|
|
| |
PR: 138130
Submitted by: Patroklos Argyroudis <argp@census-labs.com>
MFC after: 1 week
|
|
|
|
|
| |
Noted by: jhb
MFC after: 1 month
|
|
|
|
|
|
| |
PR: 138374
Submitted by: Patroklos Argyroudis <argp@census-labs.com>
MFC after: 1 week
|