Very Computer

by **David Weinehal** » Thu, 17 Jan 2002 10:20:17

> > > after that it builds for me ... but it crashes at boot time

> > Config? Arch? Compiler?

> Let me reboot with the crashing kernel for tracing ...

> x86 UP Athlon gcc-3.0.3

Let me suggest gcc-2.95.3 or gcc-2.96-whatever

/David Weinehall
_ _

// Maintainer of the v2.0 kernel // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/ </ Full colour fire </
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

by **Robert Lov** » Thu, 17 Jan 2002 10:40:12

> Uh, brlock.c probably should be including threads.h...

lib/brlock.c includes include/linux/sched.h which includes
include/linux/threads.h ...

Robert Love

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

by **Andre Hedric** » Thu, 17 Jan 2002 10:40:13

Well if you look at it closely, that function.

"ide_raw_build_sglist()"

is not called except from the user-space diagnostics ioctl

You that is getting called with from a BIO request, there will be major
request completion problems.

That is there to allow a future "Alex Viro" suggestion be considered.

> Date: Tue, 15 Jan 2002 16:43:58 -0800 (PST)

> If it's not in the IDE driver, I'm at a loss.

> That "#if 1" buisness in the new ide-dma.c code looks
> really suspicious...

Andre Hedrick
Linux Disk Certification Project Linux ATA Development

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

by **Christopher Turcksi** » Sat, 19 Jan 2002 07:20:17

> > Well, I actually disagree on this. For large include files (fs.h is the
> > worst), and complicated arrangement, this technique eliminates spurious
> > includes and saves a lot on compile time (really!).

> Numbers please.

The GNU C preprocessor remembers if an include file was completely
inside an #ifndef/#endif conditional (modulo whitespace and comments)
and will skip the #include for the same file if the macro in #ifndef is
already defined. I suspect putting guards around the include will not
save any more time.

bfn,

IBM Global Services
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Very Computer

2.5.3-pre1 compile error

2.5.3-pre1 compile error

2.5.3-pre1 compile error

2.5.3-pre1 compile error

2.5.3-pre1 compile error