On Wed, Jan 17, 2001 at 11:32:35AM -0800, Linus Torvalds wrote:
However, for socket-socket, we would not have such an advantage. A
socket-socket sendfile() would not avoid any copies the way the
networking is done today. That _may_ change, of course. But it might
not. And I'd rather tell
On Thu, Jan 18, 2001 at 10:04:28PM +0100, Andrea Arcangeli wrote:
NAGLE algorithm is only one, CORK algorithm is another different algorithm. So
probably it would be not appropriate to mix CORK and NAGLE under the name
"CONTROL_NAGLING", but certainly I agree they could stay together under
On Thu, May 10, 2001 at 08:59:24PM +0200, Jes Sorensen wrote:
Thanks, I'll put that in the next driver release as well.
Good. The only bad thing is that even with this fix, the card doesn't
work (recieves, but never transmits). I'll have to look into it
later, when I find time.
OG.
-
To
On Wed, May 23, 2001 at 07:07:38PM +1000, Keith Owens wrote:
On Wed, 23 May 2001 09:17:08 +0200 (CEST),
Geert Uytterhoeven [EMAIL PROTECTED] wrote:
On Wed, 23 May 2001, Keith Owens wrote:
Is drivers/char/ser_a2232fw.ax supposed to be included? Nothing uses it.
It's the source for the
On Sat, Sep 30, 2000 at 11:29:13PM +0100, Alan Cox wrote:
If you get
a link error or a module load error about bad_udelay let me know.
insmod pcmcia_core.o from pcmcia 3.1.20 gets the T-shirt.
OG.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Mon, Sep 18, 2000 at 05:51:43PM -0700, Linus Torvalds wrote:
Why would this not have happened for a module?
I agree that the thing looks fishy. But this is not new code, and it has
worked previously. What changed?
Maybe nobody ever insmod'ed a module for a scsi device they don't
have?
On Tue, Sep 19, 2000 at 04:11:30PM -0700, David S. Miller wrote:
Unfortunately, gcc does not make inline functions as cheap as "macros
with type checking". There are extra costs and often the register
allocator cannot cope and stuff starts getting spilled to the stack.
It is supposedly on
On Wed, Nov 29, 2000 at 04:40:29PM +, Tigran Aivazian wrote:
b) what should be the return of access(W_OK) (or, the same, open() for
write with switched uid) for devices on a readonly-mounted filesystems?
Should the majority win? I.e. should we say OK, as we do now?
My gut feeling on
On Fri, Dec 01, 2000 at 09:05:23AM -0800, T. Camp wrote:
Hmm didn't know that, from the user-land portable C perspective I'm in the
habit of zero'ing everything. - thanks.
It's a requirement of the ISO C standard that all global/static (not
local) variables are initialized to 0 is not
On Fri, Nov 17, 2000 at 03:27:28PM -0500, Richard B. Johnson wrote:
Then, you read the port as a WORD (16 bits). If nothing responds,
you get the value of 0x. If somebody is responding, you will
read something if it's enabled for writes by devices (reads by the CPU).
What guarantees you
A typo prevents the tigon 1 firmware to be included when tigon 1
support is active. Null pointer dereference in
ace_load_firmware-ace_copy as a result.
Patch trivial and even tested (aka, the module loads without oopsing
with a tigon 1 inside).
OG.
--- linux/drivers/net/acenic_firmware.h
On Tue, May 01, 2001 at 12:31:12PM -0400, Eric S. Raymond wrote:
You are proposing an interface that will handle easy cases but blow
up in the user's face in any hard one. That's poor design, frustrating
the user exactly when he/she most needs help.
Yeah, but what is the current method, vi?
On Mon, Jun 18, 2001 at 10:58:57PM -0400, Shawn Starr wrote:
When diffing 2.4.6-pre2 pre3 I noticed some reiserfs code was changed.
This seems to cause VFS to panic via reiserfs.
Anyone else notice this?
I don't, and I boot on reiserfs.
OG.
-
To unsubscribe from this list: send the line
What is the Right Way[tm] as of 2.4.6 to allocate 16Mb as 4K pages and
get the pci bus address for each page? Bonus points is they're
virtually contiguous, but that's not necessary. IIRC, the old
vmalloc-then-walk-the-pagetables trick is considered out-of-bounds
nowadays.
OG.
-
To
On Tue, Jul 03, 2001 at 11:37:28PM -0400, Rick Hohensee wrote:
In other words, if you know the push sequence of your C compiler's
function calls, you don't need asm();.
You are very much forgetting _inline_ asm. And if you think that's
unimportant for performance, well, as Al would say, go
On Wed, Mar 28, 2001 at 03:04:46PM +0100, Simon Williams wrote:
I think their point was that a program could only change permissions
of a file that was owned by the same owner. If a file is owned by a
different user has no write permissions for any user, the program
can't modify the file or
On Wed, Mar 28, 2001 at 04:49:26PM +0100, Simon Williams wrote:
What I meant was that if a file is owned by root with permissions of,
say, 555 (r-xr-xr-x), not setuid or setgid, then another executable
run as a non-root user cannot modify it or change the permissions to
7 (rwx).
It's already
mount --bind is a very nice tool to create multiple / directories for
diskless workstations. Or, well, would be, if knfsd accepted to
export them.
I didn't try with 2.4.3 yet, only with an earlier version, does it
work there? Or is it on womeone's todo? Doesn't seem that
impossible, at least
Sorry for replying to Alan's reply, I missed the original mail.
+#define ata_id_has_AN(id) \
+ ((id[76] (~id[76])) ((id)[78] (1 5)))
(a ~a) (b 32)
I don't think that does what you think it does, because at that point
it's a funny way to write 0 ((0 or 1) binary-and (0 or 32)).
On Tue, Apr 24, 2007 at 08:49:04AM -0700, Kristen Carlson Accardi wrote:
On Tue, 24 Apr 2007 12:23:04 +0200
Olivier Galibert [EMAIL PROTECTED] wrote:
Sorry for replying to Alan's reply, I missed the original mail.
+#define ata_id_has_AN(id) \
+ ((id[76] (~id[76
On Tue, Apr 24, 2007 at 01:53:27PM -0700, Kristen Carlson Accardi wrote:
Check to see if an ATAPI device supports Asynchronous Notification.
If so, enable it.
changes from last version:
* fix typo in ata_id_has_AN and make word 76 test more clear
* If we fail to set the AN feature, just
On Tue, Apr 24, 2007 at 04:41:58PM -0700, Linus Torvalds wrote:
How many different magic ioctl's does the thing introduce? Is it really
just *two* entry-points (and how simple are they, interface-wise), and
nothing else?
Aren't you a little late to the party here? The userland version is
On Mon, Feb 12, 2007 at 03:43:14PM +0900, Ian Kent wrote:
On Thu, 2007-02-08 at 11:33 +0900, Ian Kent wrote:
On Wed, 2007-02-07 at 19:18 +0100, Olivier Galibert wrote:
On Thu, Feb 08, 2007 at 03:07:41AM +0900, Ian Kent wrote:
It may be better to update to a later kernel so I don't have
On Tue, Feb 13, 2007 at 09:52:39AM +0900, Ian Kent wrote:
Indeed.
Which kernel can you use?
I believe that 2200 had another problem so can you use an fc5 kernel
later than that?
I've ported your patch to 2257 (nothing special, only moved lines),
and it seems to work beautifully. I'm
On Tue, Feb 13, 2007 at 09:07:27AM -0500, Chuck Ebbert wrote:
Olivier Galibert wrote:
On Tue, Feb 13, 2007 at 09:52:39AM +0900, Ian Kent wrote:
Indeed.
Which kernel can you use?
I believe that 2200 had another problem so can you use an fc5 kernel
later than that?
I've ported your
On Tue, Feb 13, 2007 at 09:06:24PM +0300, Sergei Organov wrote:
I agree that making strxxx() family special is not a good idea. So what
do we do for a random foo(char*) called with an 'unsigned char*'
argument? Silence? Hmmm... It's not immediately obvious that it's indeed
harmless. Yet
On Tue, Feb 13, 2007 at 10:57:24PM +0100, Ingo Molnar wrote:
* Davide Libenzi davidel@xmailserver.org wrote:
Open issues:
If this is going to be a generic AIO subsystem:
- Cancellation of pending request
How about implementing aio_cancel() as a NOP. Can anyone prove that the
On Wed, Feb 14, 2007 at 02:35:15AM +0900, Ian Kent wrote:
On Tue, 2007-02-13 at 16:54 +0100, Olivier Galibert wrote:
Don't they require autofs5 to be of any use though? That's not going
to be in fc until it's out of beta I guess.
Not really?
[EMAIL PROTECTED] ~]$ cat /etc/redhat
On Thu, Mar 22, 2007 at 02:33:14PM +, Al Viro wrote:
Correction: current ABI is crap. To set the thing up you need to open
it and issue an ioctl. Which is a bloody bad idea, for obvious reasons...
Agreed. What would be a right way? Global device ala ptmx/tun/tap?
New syscall? Something
On Wed, Apr 04, 2007 at 12:14:34PM +0100, Alan Cox wrote:
If you want hierarchy, create it:
/sys/blah/serial/controllerX/portY
and keeping them all under the ttyS? major keeps the simple
cases working sanely too.
Currently yes you could do that, but that would break all the back
On Wed, Apr 04, 2007 at 07:15:32PM +0100, Russell King wrote:
*However* you still run into the issue that you do not know how many
serial ports you will need to register a tty driver with the tty layer.
Solve that technical problem and the idea of having a single namespace
for chosen serial
On Thu, Nov 15, 2007 at 06:59:34AM +0100, Rene Herman wrote:
Totally unrelated indeed so why are spouting crap? If the kohab list has a
problem take it up with them but keep ALSA out of it. alsa-devel has only
ever moderated out spam -- nothing else.
That is incorrect. Hopefully it is the
On Mon, Dec 17, 2007 at 06:08:59PM +0200, Boaz Harrosh wrote:
Below fixes a deadly typo. Might as well be included in 2.6.24
You're sure ? scsi_for_each_sg includes a (sg)++ already...
scsi_for_each_sg(cmnd, sglist, cblk-sglen, i) {
sg-data =
T'was done as a21101c46ca5b4320e31408853cdcbf7cb1ce4ed. The system is
a latitude x300 (i855GM). With '1', the old default, I can close and
re-open the lid and have nothing happening. With '0' the screen turns
black with the mouse cursor left frozen on top of it and the computer
crashed.
Original thread btw:
http://www.ussg.indiana.edu/hypermail/linux/kernel/9907.0/0132.html
OG.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the
On Thu, Nov 22, 2007 at 07:17:14PM +0100, Jan Kara wrote:
Hi,
I guess subject says it all - why is FIBMAP ioctl restricted only to
root (CAP_SYS_RAWIO)? Corresponding ioctl for XFS is allowed without any
special capabilities so we are inconsistent here too...
Would anyone mind if the
On Mon, Nov 26, 2007 at 05:17:18PM +0100, Jan Engelhardt wrote:
rpm -b does not work in opensuse anymore (redirects you to use rpmbuild), and
I
bet fedora will do the same, so if you don't have rpm-build, tough luck for
make rpm.
The point, if I understand it correctly, was that when
On Fri, Jan 04, 2008 at 11:38:29AM -0500, Alan Stern wrote:
How about changing it to say unavailable? That doesn't imply
permanence.
How about not changing a userland-visible interface gratuitously?
OG.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
On Wed, Oct 24, 2007 at 11:12:42AM +0200, Jens Axboe wrote:
sg_set_buf() also sets length and offset, sg_set_page() is just a mirror
of that. So I'd prefer to keep the naming.
Hmmm, sg_set_phys/sg_set_virt to be more symmetrical to
sg_phys/sg_virt?
OG.
-
To unsubscribe from this list: send
On Wed, Oct 24, 2007 at 03:38:04PM +0200, Jens Axboe wrote:
(please don't drop cc lists)
Sorry. Reactions of people to Cc vary...
That doesn't make any sense. Both sg_set_buf() and sg_set_page() set the
same thing in the sg entry, the input is just different. It has nothing
to do with
On Wed, Sep 26, 2007 at 07:57:38PM +0930, David Newall wrote:
As has been said, there are thousands of ways to break out of a chroot.
It's just that one of them should not be that chroot lets you walk out.
chroot does not allow you to walk out if you're in. It only allows
you to walk
On Wed, Sep 26, 2007 at 08:43:44PM +0930, David Newall wrote:
Olivier Galibert wrote:
chroot does not allow you to walk out if you're in.
You're mistaken. Or more properly, further use of chroot lets you walk
out. This really has been said before, and before, and before.
chroot
On Mon, Oct 01, 2007 at 09:04:44AM -0700, Linus Torvalds wrote:
For example, you security guys still debate inodes vs pathnames, as if
that was an either-or issue.
Quite frankly, I'm not a security person, but I can tell a bad argument
from a good one. And an argument that says inodes _or_
On Tue, Oct 02, 2007 at 11:49:04PM +0200, Jimmy wrote:
Also, how about a list of PROS, explain to me whats so cool about it?
People who do binary-only drivers have a much better chance of not
doing a derivative work when they only use non-EXPORT_GPL exports, and
as a result not being in the
On Fri, Aug 24, 2007 at 05:43:47AM -0700, SL Baur wrote:
Who uses code like this, by the way?
People who think Posix is an example to follow maybe? Not sure if it
would go past the maintainers though :-)
# define PTHREAD_MUTEX_INITIALIZER \
{ { 0, 0, 0, 0, 0, { 0 } } }
# ifdef __USE_GNU
#
On Wed, Apr 25, 2007 at 08:16:51PM +0100, Matt Sealey wrote:
+#define ata_id_has_AN(id) \
+ ( (((id)[76] != 0x) ((id)[76] != 0x)) \
+ ((id)[78] (1 5)) )
??
--- 2.6-git.orig/include/linux/libata.h
+++ 2.6-git/include/linux/libata.h
@@ -136,6 +136,7 @@ enum {
On Wed, Apr 25, 2007 at 11:50:45AM -0700, Linus Torvalds wrote:
.. but if the alternative is a feature that just isn't worth it, and
likely to not only have its own bugs, but cause bugs elsewhere? (And yes,
I believe STD is both of those. There's a reason it's called STD. Go
to google and
On Thu, Apr 26, 2007 at 01:09:53PM +0200, Pavel Machek wrote:
#define SNAPSHOT_SET_IMAGE_SIZE _IOW(SNAPSHOT_IOC_MAGIC, 6,
unsigned long)
So I'm not supposed to be able to suspend the 16Gb-ram, 32bits servers
I have here?
OG.
-
To unsubscribe from this list: send the line
On Fri, Apr 27, 2007 at 06:50:56AM +1000, Nigel Cunningham wrote:
I'm perfectly willing to think through some alternate approach if you
suggest something or prod my thinking in a new direction, but I'm afraid
I just can't see right now how we can achieve what you're after.
Ok, what about this
On Thu, Apr 26, 2007 at 03:49:51PM -0700, David Lang wrote:
swap partitions are limited to 2G (or at least they were a couple of months
ago when I last checked). I also don't want to run the risk of having a box
try to _use_ 16G worth of swap. I'd rather have the box hit OOM first.
They
On Tue, Apr 05, 2005 at 03:28:01PM -0400, Jeff Garzik wrote:
* Most firmwares are a -collection- of images and data. The firmware
infrastructure should load an -archive- of firmwares and associated data
values.
Why don't you use multiple firmware loading calls with different
names? Maybe
On Thu, Apr 07, 2005 at 10:17:15AM +0200, Xavier Bestel wrote:
Le jeudi 07 avril 2005 à 10:04 +0200, David Schmitt a écrit :
Then I would like to exercise my right under the GPL to aquire the source
code
for the firmware (and the required compilers, starting with genfw.c which
is
...or more importantly, is it allowed. Kernel is FC3 2.6.10-1.766.
The latest iscsi driver[1] blows on a 32K-long request for a tape write
which followed this path:
[f8cef985] iscsi_queuecommand+0x161/0x2f1 [iscsi_tcp]
[f883f724] scsi_dispatch_cmd+0x1e9/0x24f [scsi_mod]
[f88440ff]
On Tue, Apr 19, 2005 at 09:50:08AM +0100, Christoph Hellwig wrote:
On Tue, Apr 19, 2005 at 10:47:30AM +0200, Olivier Galibert wrote:
...or more importantly, is it allowed. Kernel is FC3 2.6.10-1.766.
Yes, it's allowed.
Thanks. Pages in that case are continuous then, right?
OG
If I get a struct page * from a call to alloc_pages with a non-zero
order, how do I get the struct page * of te following pages from the
same allocation in order to use them in calls to tcp_sendpage?
If there a documentation somewhere whcih would answer this kind of
questions? Couldn't find
I'm starting to install some fedora core 3 systems in an environment
where 64bits SGIs are still serving the home directories. They have
the bug/feature that required the 2.4 patch to hack the 64bits
cookies[1]. The 2.6 kernel I just found still can't compensate by
itself for the issue.
Is
a minor patch in another part of dir.c.
OG.
Signed-off-by: Olivier Galibert [EMAIL PROTECTED]
fs/nfs/dir.c | 53 +-
fs/nfs/inode.c|1
include/linux/nfs_mount.h |3 +-
3 files changed, 51 insertions(+), 6 deletions
On Thu, Feb 10, 2005 at 10:20:44AM -0500, Trond Myklebust wrote:
A permanent fix probably ought to involve removing our current
dependency on using the server-generated readdir cookies as
telldir/seekdir offsets.
Remplacing it by? As in, I'm ready to do and test the code if I have
a decent
On Thu, Feb 10, 2005 at 04:40:33PM -0800, Greg KH wrote:
- autoload programs for usb, scsi, and pci modules. These
programs determine what module needs to be loaded when the
kernel emits a hotplug event for these types of devices. This
works just like the
On Mon, Feb 14, 2005 at 04:03:43PM -0800, Larry McVoy wrote:
And how does the CVS gateway not provide this today?
The CVS gateway does not reach the rest of bkbits.net. For instance
the ipw2200 tree since they miss some of the files in their tarball
distribution.
And long ago I offered what
On Tue, Feb 15, 2005 at 12:29:06PM -0500, Trond Myklebust wrote:
lau den 22.01.2005 Klokka 21:34 (+0100) skreiv Andreas Gruenbacher:
Solaris nfsacl workaround
NACK. No hacks.
That's the second time I see you refusing an interoperability patch
without bothering to say what would be
On Tue, Feb 15, 2005 at 05:43:24PM -0500, Trond Myklebust wrote:
ty den 15.02.2005 Klokka 21:35 (+0100) skreiv Olivier Galibert:
That's the second time I see you refusing an interoperability patch
without bothering to say what would be acceptable. Do we need a fork
between knfsd-pure
On Tue, Feb 15, 2005 at 06:37:19PM -0500, Trond Myklebust wrote:
on den 16.02.2005 Klokka 00:02 (+0100) skreiv Olivier Galibert:
Resolving the problem and/or cleaning the code, no. Telling what kind
of patch would be acceptable is your responsability, yes.
Read the patch, read
On Wed, Feb 16, 2005 at 06:45:27PM +0900, Clemens Schwaighofer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/15/2005 09:19 PM, kernel wrote:
Just catching up on this thread. I guess I'm ultimately surprised that
the developers here don't create a system *they* like with
change, not contents) in the nfs_do_filldir par
of the dir.c change to account for the dirent addition to apply to
2.6.11. I can update it if useful.
OG.
Signed-off-by: Olivier Galibert [EMAIL PROTECTED]
fs/nfs/dir.c | 114 ++---
fs/nfs
On Mon, Mar 21, 2005 at 12:46:58PM -0500, Trond Myklebust wrote:
må den 21.03.2005 Klokka 17:21 (+0100) skreiv Olivier Galibert:
Patch is against a fedora core 3 2.6.10, it requires minor
modifications (context change, not contents) in the nfs_do_filldir par
of the dir.c change to account
On Mon, Mar 21, 2005 at 07:22:16PM -0500, Trond Myklebust wrote:
This sort of thing worries me: I think we can do better by hooking
lseek() on directories. I'll see what I can do.
And the patch is buggy somehow, sometimes loses entries. Keep it on
hold whie I trace the probm and fix it please.
On Tue, Mar 22, 2005 at 05:00:07PM +0100, Olivier Galibert wrote:
On Mon, Mar 21, 2005 at 07:22:16PM -0500, Trond Myklebust wrote:
This sort of thing worries me: I think we can do better by hooking
lseek() on directories. I'll see what I can do.
And the patch is buggy somehow, sometimes
On Tue, Mar 29, 2005 at 11:00:30AM -0800, David Schwartz wrote:
Since the GPL permits their removal, removing them cannot be
circumventing
the GPL. Since the GPL is the only license and the license permits you to
remove them, they cannot be a license enforcement mechanism. How can you
On Tue, Mar 29, 2005 at 12:31:42PM -0400, Horst von Brand wrote:
Sorry, but an /interfase/ is there to do exactly that. It can be placed
under copyright protection as code, but /using/ it just can't be considered
a derived work. It makes no sense that if I get a description (docu,
example
On Wed, Mar 30, 2005 at 10:29:43AM -0800, Shankar Unni wrote:
Jean Delvare wrote:
v = p-field;
if (!p) return;
can be seen as equivalent to
if (!p) return;
v = p-field;
Heck, no.
You're missing the side-effect of a null pointer dereference crash (for
p-field)
On Wed, Jan 26, 2005 at 11:38:15AM -0500, linux-os wrote:
On Wed, 26 Jan 2005, Rik van Riel wrote:
With some programs the 2.6 kernel can end up allocating memory
at address zero, for a non-MAP_FIXED mmap call! This causes
problems with some programs and is generally rude to do. This
simple
On Wed, Jan 26, 2005 at 01:20:53PM -0500, linux-os wrote:
On Wed, 26 Jan 2005, Olivier Galibert wrote:
Given that the man page itself says that unless you're using MAP_FIXED
start is only a hint and you should use 0 if you don't care things can
get real annoying real fast. Imagine if you want
On Wed, Feb 02, 2005 at 10:18:27PM +1000, [EMAIL PROTECTED] wrote:
your concerns would be valid if this was impossible to achieve by an
exploit, sadly, you'd be wrong too, it's possible to force an exploited
application to call something like dl_make_stack_executable() and then
execute the
On Sat, Jul 14, 2012 at 12:33:51AM +0200, Jesper Juhl wrote:
How about we start cutting down on the options and start saying a Linux
system will provide feature x and y - always
Stuff like (and I'm just pulling random stuff out here) - ASLR, seccomp,
250HZ minimum etc etc.. We could cut
On Tue, Aug 16, 2005 at 07:04:34PM +0530, Mukund JB. wrote:
Dear Lennart,
I have bought a entermultimedia USB 2.0 21-in-1 card.
There are no Linux driver support in the CD provided.
Can u suggest me what is best bug (USB card reader) with Linux driver
support in the Market.
It doesn't
On Tue, Aug 23, 2005 at 05:16:05PM -0400, [EMAIL PROTECTED] wrote:
Why doesn't initramfs use tmpfs instead of ramfs, because
tmpfs is more robust?
I know tmpfs is larger, but at least it should be an option.
Also, tar should be an option instead of cpio for the archiver,
because tar is
On Mon, Jan 29, 2007 at 08:45:28PM -0800, Andrew Morton wrote:
-x86_64-mm-share-whats-shareable.patch
-x86_64-mm-only-call-unreachable_devices-when-type-1-is-available.patch
-x86_64-mm-only-map-whats-necessary.patch
-x86_64-mm-detect-and-support-the-e7520-and-the-945g-gz-p-pl.patch
On Tue, Jan 30, 2007 at 01:26:31AM -0800, Andrew Morton wrote:
Len, what was in that merge anyway? Lots of renaming and shuffling things
around - the sorts of things which are safe as long as they compile OK. But
was there much substantive material in there as well?
It seems heavy in
On Sun, Jan 07, 2007 at 11:42:09AM -0800, Jesse Barnes wrote:
This patch updates Oliver's MMConfig bridge detection patches with support
for 915G bridges. It seems to work ok on my 915GM laptop.
Looks ok to me.
I also tried adding 965 support, but it doesn't work (at least not on my
G965
On Sun, Jan 07, 2007 at 11:44:16AM -0800, Jesse Barnes wrote:
For reference, here's the probe routine I tried for 965, probably something
dumb wrong with it that I'm not seeing atm.
It shouldn't have mattered in your case, but base_address is limited
to 32bits. There is a 32 bits reserved
Is there a way to know if there has been I/O error(s) on a specific
disk or partition since boot other than parsing dmesg and hoping it's
both still there and in the expected format?
Of course that's if the error didn't kill the system in the first
place :-)
OG.
-
To unsubscribe from this
On Wed, Dec 20, 2006 at 02:38:51PM +0100, Arjan van de Ven wrote:
[1] What kind of latency would be allowed? Would an implementation be
allowed to power up the phy say once per minute or once per 5 minutes to
see if there is link? The implementation could do this progressively;
first poll
On Wed, Dec 20, 2006 at 04:34:17PM +0100, Arjan van de Ven wrote:
5 seconds is unfair and unrealistic though. The *hardware* negotiation
before link is seen can easily take upto 45 seconds already.
That's a network topology/hardware issue (spanning tree fun) that
software or even the hardware
Sorry I missed the original email, but what is the chipset (name, pci
ID) of the board(s) with the problematic bios?
OG.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
such additions on, they're left out for now.
Signed-off-by: Jesse Barnes [EMAIL PROTECTED]
Signed-off-by: Olivier Galibert [EMAIL PROTECTED]
Andrew, you sent me a series of emails to tell me the patches had
moved to another subsystem tree, can you tell me which one? There is
at least an anti
sd 0:0:0:0: SCSI error: return code = 0x0802
sda: Current: sense key: Hardware Error
ASC=0x42 ASCQ=0x0
Info fld=0x400802c
end_request: I/O error, dev sda, sector 202369
Aborting journal on device sda1.
journal commit I/O error
ext3_abort called.
EXT3-fs error (device sda1):
On Mon, Jan 15, 2007 at 06:45:40PM +, Alan wrote:
On Mon, 15 Jan 2007 18:16:02 +0100
Olivier Galibert [EMAIL PROTECTED] wrote:
sd 0:0:0:0: SCSI error: return code = 0x0802
sda: Current: sense key: Hardware Error
ASC=0x42 ASCQ=0x0
I'll give you a clue: The words Hardware
On Tue, Jan 16, 2007 at 12:27:17AM +0100, Stefan Richter wrote:
On 15 Jan, Olivier Galibert wrote:
sd 0:0:0:0: SCSI error: return code = 0x0802
sda: Current: sense key: Hardware Error
ASC=0x42 ASCQ=0x0
The Additional Sense Code means power-on or self-test failure FWIW.
(SPC-4
On Mon, Jan 15, 2007 at 11:14:52PM +, Alan wrote:
If you pull the drive and test it in another box does it show the same ?
I'm going to try that. The prolem requires 3-7 days to appear, so I
won't know immediatly.
And what does a scsi verify have to say ?
Running, looks like it's gonna
On Tue, Jan 16, 2007 at 03:47:52PM +, Alan wrote:
The drives do that automatically, and the SCSI verify did it for him too
if there were any other problems.
The SCSI verify didn't see a thing, I'm gonna do the disk swapping
dance.
OG.
-
To unsubscribe from this list: send the line
On Sun, Jan 14, 2007 at 06:27:18AM +0900, OGAWA Hirofumi wrote:
This rejects a broken MCFG tables on Asus etc.
Arjan and Andi suggest this.
And I agree completely with the principle. If you don't know the
chipset on a first-name basis, trash the MCFG unless it's squeaky
clean (or you don't
On Mon, Jan 08, 2007 at 01:27:15PM -0800, Jesse Barnes wrote:
On Monday, January 8, 2007 12:45 pm, Olivier Galibert wrote:
On Sun, Jan 07, 2007 at 11:44:16AM -0800, Jesse Barnes wrote:
For reference, here's the probe routine I tried for 965, probably
something dumb wrong with it that I'm
On Mon, Jan 15, 2007 at 11:14:52PM +, Alan wrote:
Both smart and the internal blade diagnostics say everything is a-ok
with the drive, there hasn't been any error ever except a bunch of
corrected ECC ones, and no more than with a similar drive in another
working blade. Hence my
Done in 5 steps, at Andi's very reasonable request:
1/5: PCI MMConfig: Share what's shareable.
Share code between i386 and x86-64
2/5: PCI MMConfig: Only call unreachable_devices() when type 1 is available.
Trivial fix.
3/5: PCI MMConfig: Only map what's necessary.
Trivial fix too.
4/5:
The x86-64 mmconfig code always map a range of MMCONFIG_APER_MAX
bytes, i.e. 256MB, whatever the number of accessible busses is. Fix
it, and add the end of the zone in the printk while we're at it.
Signed-off-by: Olivier Galibert [EMAIL PROTECTED]
---
arch/x86_64/pci/mmconfig.c |9
Put back the resource reservation as per
4c6e052adfe285ede5884e4e8c4d33af33932c13 but use it *only* when the
range(s) come from a chipset probe instead of the bios.
Signed-off-by: Olivier Galibert [EMAIL PROTECTED]
---
arch/i386/pci/mmconfig-shared.c | 33 +
1
i386 and x86-64 pci mmconfig code have a lot in common. So share
what's shareable between the two.
Signed-off-by: Olivier Galibert [EMAIL PROTECTED]
---
arch/i386/pci/Makefile |2 +-
arch/i386/pci/mmconfig-shared.c | 88 +++
arch/i386/pci
It seems that the only way to reliably support mmconfig in the
presence of funky biosen is to detect the hostbridge and read where
the window is mapped from its registers. Do that for the E7520 and
the 945G/GZ/P/PL for a start.
Signed-off-by: Olivier Galibert [EMAIL PROTECTED]
---
arch/i386/pci
unreachable_devices compares between the results of pci configuration
accesses through type1 and mmconfig, so it should be called only if
type1 actually works in the first place.
Signed-off-by: Olivier Galibert [EMAIL PROTECTED]
---
arch/i386/pci/mmconfig-shared.c |3 ++-
1 files changed, 2
1 - 100 of 293 matches
Mail list logo
