* Re: [ANNOUNCE] Cooperative Linux
From: Karim Yaghmour @ 2004-01-25 20:01 UTC (permalink / raw)
To: Dan Aloni; +Cc: Linux Kernel List
In-Reply-To: <20040125193518.GA32013@callisto.yi.org>
Dan Aloni wrote:
> The bottom line is that it allows us to run Linux on an unmodified
> Windows 2000/XP system in a practical way (the user just launches
> an app), and it may eventually bring Linux to a large sector of desktop
> computer users who wouldn't even care about trying to install a
> dual boot system or boot a Linux live CD (like Knoppix).
>
> Screen-shots and further details at:
>
> http://www.colinux.org
Cool!
> Our motto is:
>
> "If Linux runs on every architecture, why should another
> operating system be in its way?"
Indeed.
> coLinux is similar to plex86 in a way that it implements a Linux-specific
> lightweight VM with I/O virtualization. However, it is designed to be
> mostly host-OS independent, so that with minimal porting efforts it
> would be possible to run it under Solaris, Linux itself, or any operating
> system that supports loading kernel drivers, under any architecture that
> uses an MMU. Unlike other virtualization methods, it doesn't base its
> implementation on exceptions that are caused by instructions.
Right, that's the way to go with an OS for which the source is available.
Have you looked at the work that's been going on with the Adeos nanokernel:
http://www.opersys.com/adeos/index.html
Some of the infrastructure required by all these virtualization solutions
is fairly similar.
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546
^ permalink raw reply
* Fix xbow.c compilation
From: Andreas Schwab @ 2004-01-25 19:54 UTC (permalink / raw)
To: linux-ia64
This fixes a conflicting declaration in xbow.c.
--- linux-2.6.1/arch/ia64/sn/io/sn2/xbow.c.~1~ 2004-01-25 20:22:21.000000000 +0100
+++ linux-2.6.1/arch/ia64/sn/io/sn2/xbow.c 2004-01-25 20:41:37.000000000 +0100
@@ -153,7 +153,7 @@ xbow_attach(vertex_hdl_t conn)
#if DEBUG && ATTACH_DEBUG
char name[MAXDEVNAME];
#endif
- static void xbow_errintr_handler(int, void *, struct pt_regs *);
+ static irqreturn_t xbow_errintr_handler(int, void *, struct pt_regs *);
#if DEBUG && ATTACH_DEBUG
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
^ permalink raw reply
* [PATCH] [APM] Is this the correct way to fix suspend bug introduced in 2.6.0-test4?
From: Michael Schierl @ 2004-01-25 19:50 UTC (permalink / raw)
To: fr, linux-laptop; +Cc: linux-kernel, mochel
Hi,
the patch below (against 2.6.1-mm5) fixes my APM problems (my laptop, Acer
TravelMate 210TEV (Celeron 700, 128 MB RAM), hangs after resuming from APM
since 2.6.0-test4).
I found the "fix" by trying to "reversely" backport the changes from
patch-2.6.0-test4.bz2 into 2.6.1-mm5 (the old device_suspend code calls
sysdev_suspend, the new one does not; so what do I lose if I call
sysdev_suspend myself?). This trial-and-error-approach finally led into the
patch below (which works great for me).
Most likely this is not the cleanest way to do this; but since I don't even
know what this sysdev_suspend does (except that it does something that
seems to be vital for making my laptop resume...), i don't know how to make
it better...
If you have any suggestions, tell me (or change it yourself and submit it),
if you think that's okay like that, please submit that to the guy who is
responsible for 2.6 (is it Linus or Andrew? did not follow lkml recently).
TIA,
Michael
PS: if possible, please CC me in yout replies
====== apm-bug-introduced-in-test4.patch ======
--- linux-2.6.1-mm5/arch/i386/kernel/apm.c.old Sun Jan 25 14:48:27 2004
+++ linux-2.6.1-mm5/arch/i386/kernel/apm.c Sun Jan 25 16:10:43 2004
@@ -234,6 +234,9 @@ extern spinlock_t i8253_lock;
extern unsigned long get_cmos_time(void);
extern void machine_real_restart(unsigned char *, int);
+extern int sysdev_resume(void);
+extern int sysdev_suspend(u32 state);
+
#if defined(CONFIG_APM_DISPLAY_BLANK) && defined(CONFIG_VT)
extern int (*console_blank_hook)(int);
#endif
@@ -1199,6 +1202,7 @@ static int suspend(int vetoable)
}
device_suspend(3);
+ sysdev_suspend(3);
/* serialize with the timer interrupt */
write_seqlock_irq(&xtime_lock);
@@ -1232,6 +1236,7 @@ static int suspend(int vetoable)
if (err != APM_SUCCESS)
apm_error("suspend", err);
err = (err == APM_SUCCESS) ? 0 : -EIO;
+ sysdev_resume();
device_resume();
pm_send_all(PM_RESUME, (void *)0);
queue_event(APM_NORMAL_RESUME, NULL);
@@ -1250,6 +1255,7 @@ static void standby(void)
{
int err;
+ sysdev_suspend(3);
/* serialize with the timer interrupt */
write_seqlock_irq(&xtime_lock);
/* If needed, notify drivers here */
@@ -1259,6 +1265,7 @@ static void standby(void)
err = set_system_power_state(APM_STATE_STANDBY);
if ((err != APM_SUCCESS) && (err != APM_NO_ERROR))
apm_error("standby", err);
+ sysdev_resume();
}
static apm_event_t get_event(void)
^ permalink raw reply
* Re: 2.6.2-rc1 / ACPI sleep / irqbalance / kirqd / pentium 4 HT problems on Uniwill N258SA0
From: Zwane Mwaikambo @ 2004-01-25 15:28 UTC (permalink / raw)
To: Huw Rogers; +Cc: Linux Kernel, linux-laptop
In-Reply-To: <20040124233749.5637.COUNT0@localnet.com>
On Sun, 25 Jan 2004, Huw Rogers wrote:
> irqbalance just locks up the machine totally, hard power-off needed, no
> traces in the logs. Probably some issue (race?) with it writing to
> /proc/irq/X/smp_affinity. And how is irqbalance supposed to play with
> kirqd anyway? Grepping this list and others doesn't give any kind of an
> answer. But disabling it gives all interrupts to cpu0 (looking at
> /proc/interrupts). kirqd apparently only balances between CPU packages,
> not between HT siblings (info gleaned from this list).
Does this happen with the 'noirqbalance' kernel parameter?
^ permalink raw reply
* Re: 2.6.1-mm5, kernel panic "Interrupt not syncing"
From: Zwane Mwaikambo @ 2004-01-25 15:24 UTC (permalink / raw)
To: Mike; +Cc: linux-kernel
In-Reply-To: <pan.2004.01.25.13.51.36.497433@kordik.net>
On Sun, 25 Jan 2004, Mike wrote:
> On Fri, 23 Jan 2004 09:58:40 -0500, Mike wrote:
>
> > I have run 2.6.0-test.* kernels, 2.6.1-mm1 and 4 and they all boot fine.
> > When I go to 2.6.1-mm5 I get a kernel panic and the boot freezes. The
> > messages go by so quick I can't tell at what point it is doing this but
> > the last line is interrupt not syncing. Any ideas? I have gone back to
> > 2.6.1-mm4 so I can boot but I was interested in mm5 because it has ALSA
> > 1.01 and I was hoping that would solve my lockup when I got to a web page
> > with a lot of flash problem but not being able to boot is even worse. :-)
> >
> > Any ideas on the problem or advice on how to debug this would be most
> > appreciated.
> >
> > Mike
> No ideas? I can wait to try a newer kernel but I am concerned that the 20
> or so kernels I used before booted without problems then all of a sudden
> 2.6.1-mm5 does not. Should I just ignore the problem and try a newer
> kernel? Is anyone else using 2.6.1-mm5 successfully?
Kernel config please? Could you perhaps manage to get a tad bit more
information from the panic? Also send over a dmesg from a working boot.
Ta
^ permalink raw reply
* Re: Troubles Compiling 2.6.1 on SuSE 9
From: Sam Ravnborg @ 2004-01-25 19:55 UTC (permalink / raw)
To: Marco Rebsamen; +Cc: Sam Ravnborg, linux-kernel
In-Reply-To: <200401251827.23510.mrebsamen@swissonline.ch>
> I get many messages:
> modprobe: modprobe: Can't open dependencies file /lib/
> modules/2.4.21-99-default/modules.dep (no such file or dir.)
Strange, you are building a 2.6 kernel.
Did you execute this as root?
Sam
^ permalink raw reply
* 2.6.2-pre1-mm? all Oops on boot
From: John Stoffel @ 2004-01-25 19:46 UTC (permalink / raw)
To: linux-kernel
Hi all,
I've been trying to move up from 2.6.1-mm4 to the newer kernels, but
they've all be crashing and oopsing on my when I boot. I'm on an Dual
Xeon PIII, 550mhz, 768mb RAM, Dell Precision 610MT system. It's
debian, latest stable/unstable/testing stuff. Which might be my
downfall, but since 2.6.1-mm4 seems to be reasonably stable... who
knows.
Since this is my main machine, I've copied down by hand most (but not
all) of the most recent Oops I got when trying to boot 2.6.2-rc1-mm3
this morning. This should be pretty accurate, but no promises.
Oops: 0003 [#1]
SMP DEBUG_PAGEALLOC
CPU: 0
EIP: 0060: [<c011c7de>] Not tainted VLI
EFLAGS: 00010202
EIP is at do_test_wp_bit+0xe/0x20
eax: 0000000 ebx: 000000c4 ecx: 00101025 edx: 0057a027
es: 00000435 edi: 00000b4d ebp: c04e3f90 esp: c04e3f90
ds: 007b es: 007b ss: 0068
.
.
.
Call Trace:
test_wp_bit+0x23/0x70
mem_init+0x19f/0x2220
_stext+0x0/0x80
start_kernel+0xec/0x1b0
I've also attached my .config that I'm using:
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
# CONFIG_CLEAN_COMPILE is not set
CONFIG_STANDALONE=y
CONFIG_BROKEN=y
CONFIG_BROKEN_ON_SMP=y
#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_IKCONFIG is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y
#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
#
# Processor support
#
#
# Select all processors your kernel should support
#
# CONFIG_CPU_386 is not set
CONFIG_CPU_486=y
CONFIG_CPU_586=y
CONFIG_CPU_586TSC=y
CONFIG_CPU_586MMX=y
CONFIG_CPU_686=y
CONFIG_CPU_PENTIUMII=y
CONFIG_CPU_PENTIUMIII=y
# CONFIG_CPU_PENTIUMM is not set
# CONFIG_CPU_PENTIUM4 is not set
# CONFIG_CPU_K6 is not set
# CONFIG_CPU_K7 is not set
# CONFIG_CPU_K8 is not set
# CONFIG_CPU_CRUSOE is not set
# CONFIG_CPU_WINCHIPC6 is not set
# CONFIG_CPU_WINCHIP2 is not set
# CONFIG_CPU_WINCHIP3D is not set
# CONFIG_CPU_CYRIXIII is not set
# CONFIG_CPU_VIAC3_2 is not set
CONFIG_CPU_INTEL=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_F00F_BUG=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_ALIGNMENT_16=y
CONFIG_X86_BAD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
# CONFIG_X86_4G is not set
# CONFIG_X86_SWITCH_PAGETABLES is not set
# CONFIG_X86_4G_VM_LAYOUT is not set
# CONFIG_X86_UACCESS_INDIRECT is not set
# CONFIG_X86_HIGH_ENTRY is not set
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_SMP=y
CONFIG_NR_CPUS=8
# CONFIG_SCHED_SMT is not set
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_MATH_EMULATION=y
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_REGPARM is not set
#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set
#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_ASUS=m
CONFIG_ACPI_TOSHIBA=m
CONFIG_ACPI_DEBUG=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_RELAXED_AML is not set
# CONFIG_X86_PM_TIMER is not set
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_USE_VECTOR is not set
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_HOTPLUG=y
#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
CONFIG_PCMCIA_PROBE=y
#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y
#
# Device Drivers
#
#
# Generic Driver Options
#
# CONFIG_FW_LOADER is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=y
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y
#
# Plug and Play support
#
CONFIG_PNP=y
CONFIG_PNP_DEBUG=y
#
# Protocols
#
CONFIG_ISAPNP=y
CONFIG_PNPBIOS=y
# CONFIG_PNPBIOS_PROC_FS is not set
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
CONFIG_BLK_DEV_NBD=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_LBD=y
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_TASKFILE_IO is not set
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_MAX_SD_DISKS=16
CONFIG_CHR_DEV_ST=y
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_REPORT_LUNS=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AACRAID is not set
CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_CMDS_PER_DEVICE=32
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_BUILD_FIRMWARE is not set
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX_CONFIG=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA23XX is not set
# CONFIG_SCSI_SEAGATE is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set
#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=y
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
CONFIG_MD_RAID5=y
# CONFIG_MD_RAID6 is not set
# CONFIG_MD_MULTIPATH is not set
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_IOCTL_V4 is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
CONFIG_IEEE1394=m
#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
CONFIG_IEEE1394_OUI_DB=y
#
# Device Drivers
#
#
# Texas Instruments PCILynx requires I2C
#
CONFIG_IEEE1394_OHCI1394=m
#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
# CONFIG_IEEE1394_ETH1394 is not set
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_IEEE1394_CMP=m
# CONFIG_IEEE1394_AMDTP is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Macintosh device drivers
#
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_IPV6 is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_NETFILTER is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_NET_POCKET is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DLt
# CONFIG_STALDRV is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
CONFIG_SERIAL_8250_ACPI=y
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_PRINTER=y
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set
#
# Mice
#
CONFIG_BUSMOUSE=y
# CONFIG_QIC02_TAPE is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=y
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
t set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set
#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
#
# USB support
#
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_UHCI_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=m
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
# CONFIG_USB_STORAGE_HP8200e is not set
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
CONFIGnot set
#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GADGET is not set
#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
# CONFIG_EXT2_FS_POSIX_ACL is not set
# CONFIG_EXT2_FS_SECURITY is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FSRITY is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
#
# Library routines
#
CONFIG_CRC32=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_PC=y
^ permalink raw reply
* 2.6.2-rc1-bk3 patch fails
From: Mike Keehan @ 2004-01-25 19:43 UTC (permalink / raw)
To: linux-kernel
Applying the above patch to 2.6.1 gets failure in:-
. Makefile
. arch/i386/kernel/cpu/mcheck/non-fatal.c
. drivers/cdrom/cdrom.c
. drivers/input/joydev.c
. drivers/input/keyboard/atkbd.c
. drivers/md/Kconfig
. drivers/md/raid6.h (doesn't exist)
I control C'd out of the rest. The BK snapshots on
kernel.org aren't meant to be applied cumulatively,
are they?
Mike
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/
^ permalink raw reply
* [ANNOUNCE] Cooperative Linux
From: Dan Aloni @ 2004-01-25 19:35 UTC (permalink / raw)
To: Linux Kernel List
Hello fellow developers, kernel hackers, and open source contributors,
Cooperative Linux is a port of the Linux kernel which allows it
to run cooperatively under other operating systems in ring0 without
hardware emulation, based on very minimal changes in the architecture
dependent code and almost no changes in functionality.
The bottom line is that it allows us to run Linux on an unmodified
Windows 2000/XP system in a practical way (the user just launches
an app), and it may eventually bring Linux to a large sector of desktop
computer users who wouldn't even care about trying to install a
dual boot system or boot a Linux live CD (like Knoppix).
Screen-shots and further details at:
http://www.colinux.org
Our motto is:
"If Linux runs on every architecture, why should another
operating system be in its way?"
coLinux is similar to plex86 in a way that it implements a Linux-specific
lightweight VM with I/O virtualization. However, it is designed to be
mostly host-OS independent, so that with minimal porting efforts it
would be possible to run it under Solaris, Linux itself, or any operating
system that supports loading kernel drivers, under any architecture that
uses an MMU. Unlike other virtualization methods, it doesn't base its
implementation on exceptions that are caused by instructions.
Cooperative Linux is like the kernel mode equivalent of User Mode Linux.
It relies on the host OS kernel-space interfaces rather than relying on
host OS user-space interfaces.
Currently, it is stable enough (on some common hardware configurations)
for running a fully functional KNOPPIX/Debian system on Windows (see
website screen-shots).
Another project close to achieving that goal is the Windows port of
User Mode Linux (http://umlwin32.sf.net).
Project page:
http://sourceforge.net/projects/colinux
Thank you for your time,
- The coLinux development team.
This Open Source project is sponsored and produced by AIST, 2004
http://www.aist.go.jp/
--
Dan Aloni
da-x@gmx.net
^ permalink raw reply
* Re: user space multicast routing interface
From: jamal @ 2004-01-25 19:35 UTC (permalink / raw)
To: David Lamparter; +Cc: netdev
In-Reply-To: <4013FEC9.1070900@diac24.net>
Hi,
consider using a BPF filter to capture only IGMP.
If you google nicely she may tell you something useful.
cheers,
jamal
On Sun, 2004-01-25 at 12:37, David Lamparter wrote:
> Hi,
>
> [...skip down if you don't like long "sorry for mailing" mails ;)]
>
> first of all, please excuse me mailing to netdev for a not directly
> kernel related Linux networking question - i didn't find any other place
> where i could ask...
>
> I recently started playing around with multicast routing for educational
> purposes; multicast client software was easy to write, ran well and
> there were lots of docs about setsockopts etc.
>
> Continuing on my way, I'm trying to write a simple IGMP querier now, but
> even getting started turns out to be pretty difficult here, almost no
> docs exist (well, the FreeBSD manpage...). I tried everything coming to
> my mind, but i wasn't even able to get to receiving all IGMP packets on
> an interface.
>
> [...stop skipping here]
>
> so, 2 questions:
> * what sockopts are neccessary to get all IGMP packets (all multicast
> groups) on a raw socket? (MRT_INIT / MRT_ADD_VIF should do it, but it
> doesn't work)
> * is it possible to bind VIFs to interface indices? in ipmr.c / struct
> vifctl there is no ifindex parameter (real interface, not vif)
>
> as you can see from the 2nd question, i at least tried reading the
> kernel source (2.6.1), but i don't know the stack so its difficult to
> understand...
>
> David Lamparter
>
>
>
> Appended: testing code for IGMP
>
> no error messages on 2.6.1, interface has
> <BROADCAST,MULTICAST,ALLMULTI,UP> flags while code is running, vif shows
> up under /proc/net/ip_mr_vif:
> Interface BytesIn PktsIn BytesOut PktsOut Flags Local Remote
> 1 eth0 0 0 0 0 08000 160216AC 00000000
>
> <cut includes for space issues>
>
> #define E(x) if (x) printf ("error doing %s: %d [%s]\n", \
> #x, errno, strerror (errno));
> int main(int argc, char **argv)
> {
> int mrouter_s4; int p = 1; struct vifctl vc;
>
> mrouter_s4 = socket(AF_INET, SOCK_RAW, IPPROTO_IGMP);
> E(setsockopt(mrouter_s4, IPPROTO_IP, MRT_INIT,
> (void *)&p, sizeof(p)));
>
> memset(&vc, 0, sizeof(vc));
> vc.vifc_vifi = vc.vifc_threshold = 1;
> vc.vifc_rate_limit = 4096;
> vc.vifc_lcl_addr.s_addr = inet_addr(argv[1]);
> E(setsockopt(mrouter_s4, IPPROTO_IP, MRT_ADD_VIF,
> (void *)&vc, sizeof(vc)));
>
> while(1) {
> char buf[4096]; struct sockaddr_in sender;
> socklen_t sendsize = sizeof(sender);
> int size = recvfrom(mrouter_s4, buf, 4096, 0,
> (struct sockaddr *) &sender, &sendsize);
> printf ("got %d from %s\n", size,
> inet_ntoa(sender.sin_addr));
> }
> }
>
>
>
>
>
>
^ permalink raw reply
* Re: [RFC/PATCH] IMQ port to 2.6
From: David S. Miller @ 2004-01-25 19:25 UTC (permalink / raw)
To: sebek64; +Cc: linux-kernel, netdev, kaber
In-Reply-To: <20040125152419.GA3208@penguin.localdomain>
From: sebek64@post.cz (Marcel Sebek)
Date: Sun, 25 Jan 2004 16:24:19 +0100
I have ported IMQ driver from 2.4 to 2.6.2-rc1.
Original version was from http://trash.net/~kaber/imq/.
Patrick, do you mind if I merge this 2.6.x port into my tree?
^ permalink raw reply
* Re: [PATCH] aha1542: queuecommand: change panic() to return
From: James Bottomley @ 2004-01-25 19:34 UTC (permalink / raw)
To: Randy.Dunlap; +Cc: SCSI Mailing List
In-Reply-To: <20040124220006.48dd7746.rddunlap@osdl.org>
On Sun, 2004-01-25 at 00:00, Randy.Dunlap wrote:
> cptr = (struct chain *) SCpnt->host_scribble;
> if (cptr == NULL)
> - panic("aha1542.c: unable to allocate DMA memory\n");
> + return 1;
> for (i = 0; i < SCpnt->use_sg; i++) {
> if (sgpnt[i].length == 0 || SCpnt->use_sg > 16 ||
This is really not right. If you look, the driver has already claimed a
cdb for the command, so it will leak scarce resources in this error
path.
Also a better return might be SCSI_MLQUEUE_HOST_BUSY, since this would
be a global resource shortage for all commands.
James
^ permalink raw reply
* Re: Linux 2.4.25-pre7 - no DRQ after issuing WRITE
From: Gabor Z. Papp @ 2004-01-25 19:33 UTC (permalink / raw)
To: Marcelo Tosatti; +Cc: linux-kernel, Bartlomiej Zolnierkiewicz
In-Reply-To: <Pine.LNX.4.58L.0401251714400.1311@logos.cnet>
* Marcelo Tosatti <marcelo.tosatti@cyclades.com>:
| > Here we go: http://gzp.odpn.net/tmp/linux-2.4.25-pre7/
| >
| > The "no DRQ after issuing WRITE" problem with 2 120GB Seagate
...
| I'm not IDE expert, but these errors look like hardware fault for me
| (Bartlomiej CCed).
|
| What about 2.6 and older 2.4 kernels on the same hardware ?
Same kernel works fine in a non-sw-raid environment, when I can't
stress enough the harddisks to fail. When I boot NetBSD 1.6.1, I'm
able to read-write the disks nonstop without any error. Thats why I
think its not hw problem, but I would like to use Linux 2.4, so I'm
waiting for Bartlomiej.
| -------------
| Mounted devfs on /dev
| Freeing unused kernel memory: 116k freed
| hde: dma_timer_expiry: dma status == 0x21
| hdg: dma_timer_expiry: dma status == 0x21
| hde: error waiting for DMA
| hde: dma timeout retry: status=0x7f { DriveReady DeviceFault SeekComplete
| DataRequest CorrectedError Index Error }
| hde: dma timeout retry: error=0x7f { DriveStatusError UncorrectableError
| SectorIdNotFound TrackZeroNotFound AddrMarkNotFound },
| LBAsect=9343692930943, high=556927, low=8355711, sector=4352
| hde: DMA disabled
| hdg: error waiting for DMA
| hdg: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest
| }
| hdg: status error: status=0x50 { DriveReady SeekComplete }
| hdg: no DRQ after issuing MULTWRITE
| hdg: status timeout: status=0xd0 { Busy }
^ permalink raw reply
* rtl8169 problem and 2.4.23
From: Daniel Egger @ 2004-01-25 19:32 UTC (permalink / raw)
To: Linux Kernel Mailinglist
[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]
Hija,
I just discovered that the interface doesn't account outgoing bytes, so
although I'm shoveling GBs over NFS to another machine, ifconfig and
/proc/net/dev both state that the card hasn't transmitted anything:
eth2 Link encap:Ethernet HWaddr 00:08:01:a3:64:97,
inet addr:192.168.11.2 Bcast:192.168.11.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:297638 errors:0 dropped:0 overruns:0 frame:0
TX packets:1334930 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:45831863 (43.7 MiB) TX bytes:0 (0.0 b)
Interrupt:4 Base address:0xff00
Furthermore the performance is really scary slow: I'm not even getting
100Base-T speeds from an Athlon XP to my G4 PowerBook under MacOS X over
a PtP connection.
What is interesting though is that the machine produces interrupt errors
which only occur when the card is active:
CPU0
0: 110545371 XT-PIC timer
1: 2 XT-PIC keyboard
2: 0 XT-PIC cascade
3: 35665 XT-PIC ohci1394
4: 4314949 XT-PIC eth2
8: 4 XT-PIC rtc
12: 87125964 XT-PIC eth0
14: 6035586 XT-PIC ide0
15: 6986897 XT-PIC ide1
NMI: 0
LOC: 110544807
ERR: 10905
MIS: 0
And this is this output of the driver at initialisation:
r8169 Gigabit Ethernet driver 1.2 loaded
PCI: Found IRQ 4 for device 00:0d.0
r8169: PCI device 00:0d.0: unknown chip version, assuming RTL-8169
r8169: PCI device 00:0d.0: TxConfig = 0x800000
eth2: Identified chip type is 'RTL-8169'.
eth2: RealTek RTL8169 Gigabit Ethernet at 0xe093ff00, 00:08:01:a3:64:97, IRQ 4
eth2: Auto-negotiation Enabled.
eth2: 1000Mbps Full-duplex operation.
--
Servus,
Daniel
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 481 bytes --]
^ permalink raw reply
* Re: howto configuring kernel and modules.conf for automatic loading of ide-scsi
From: pa3gcu @ 2004-01-25 19:30 UTC (permalink / raw)
To: Agri, linux-newbie
In-Reply-To: <20040125211055.10e7943a.agri@desnol.ru>
On Sunday 25 January 2004 19:10, Agri wrote:
> here... i want to mention one strange thing...
> if i "touch" for hd? device "hided" by ide-scsi kmod will request for a
> module and system will load ide-scsi... curious... don't you think?
Too be honest i have no clue as to what you mean however i never have any
problem with loading of modules, normally speaking i never have to use
modprobe, i only use modprobe if i do things via scripts and that only to
make sure the module is loaded otheriwse the sript would need to do all sorts
of checks first.
I dont know if you tryed my suggestion i made in my last mail on this subject,
another is simply add;
append="hdX=ide-scsi"
X= a,b,c or d on your system, to /etc/lilo.conf and rerun lilo or do the
equivilant under grub if thats what you use.
As you said you did not like the idea of loading modules at boottime but i
think you should reconsider as that in itself does not hinder or slow down
your system one bit.
--
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply
* boot rom
From: ShadowRage @ 2004-01-25 19:28 UTC (permalink / raw)
To: linux-8086
I know elks creates a minix boot rom, how can I do this for a minix system with a 386 kernel? (eg, standard) kernel
I know it uses bootblocks in linux-86
just how..
--
AcidChat IRC Network
www.acidchat.net
free chatrooms!
^ permalink raw reply
* Re: GCC-3.4 reorders asm() with -O2
From: Andi Kleen @ 2004-01-25 19:28 UTC (permalink / raw)
To: Ralf Baechle; +Cc: jh, echristo, hubicka, eager, gcc, linux-mips
In-Reply-To: <20040125182643.GA25020@linux-mips.org>
On Sun, 25 Jan 2004 19:26:43 +0100
Ralf Baechle <ralf@linux-mips.org> wrote:
> On Sun, Jan 25, 2004 at 12:03:51PM -0500, Daniel Jacobowitz wrote:
>
> > It is. Ralf already knows about the problem, I think - we leave
> > markers outside of functions which define an entry point, save some
> > additional registers to the stack, and try to fall through to the
> > following function. If the function gets emitted elsewhere, obviously,
> > we've lost :)
> >
> > [This is save_static_function...]
>
> I only recently fixed the problem with the save_static() inline function
> which of course was fragile, speculating on the compiler doing the
> right thing ... I'll cook up a fix ...
You can always use __attribute__((noinline))
-Andi
^ permalink raw reply
* Re: Is there a way to keep the 2.6 kjournald from writing to idle disks? (to allow spin-downs)
From: Felipe Alfaro Solana @ 2004-01-25 19:26 UTC (permalink / raw)
To: Lutz Vieweg; +Cc: Linux Kernel Mailinglist
In-Reply-To: <40140B0A.90707@isg.de>
On Sun, 2004-01-25 at 19:29, Lutz Vieweg wrote:
> Hi everyone,
>
> I run a server that usually doesn't have to do anything on the local filesystems,
> it just needs to answer some requests and perform some computations in RAM.
>
> So I use the "hdparm -S 123" parameter setting to keep the (IDE) system disk from
> spinning unneccessarily.
>
> Alas, since an upgrade to kernel 2.6 and ext3 filesystem, I cannot find a way to
> let the harddisk spin down - I found out that "kjournald" writes a few blocks every
> few seconds.
>
> As I wouldn't like to downgrade to ext2: Is there any way to keep the 2.6 kjournald
> from writing to idle disks?
>
> I cannot see a good reason why kjournald would write when there are no dirty buffers -
> but still it does.
Have you tried playing with the laptop-mode patch? It's already in the
-mm kernel tree from Andrew Morton. I've been playing with it a little
(just a few minutes) and seems keep the disks spun down for some time.
However, I haven't been able to get it suit my needs, since I use apps
like Evolution which are continuously writting to the disk.
If you are willing to play with it, I recommend you downloading the
latest -mm patch from http://www.kernel.org, untar the sources and then
read Documentation/laptop-mode.txt.
^ permalink raw reply
* [PATCH 2.0.39] put_last_free() defined, but not used
From: Coywolf Qi Hunt @ 2004-01-25 19:23 UTC (permalink / raw)
To: tao, linux-kernel
Hello,
In 2.0.39, the function put_last_free() in fs/file_table.c is defined,
but no longer get used.
Should it be removed?
thanks
--- fs/file_table.c.orig 1994-10-21 07:39:36.000000000 +0800
+++ fs/file_table.c 2004-01-26 03:10:38.000000000 +0800
@@ -52,20 +52,6 @@
prev->f_next = next;
}
-/*
- * Insert a file structure at the end of the list of available ones.
- */
-static inline void put_last_free(struct file *file)
-{
- struct file *next, *prev;
-
- next = first_file;
- file->f_next = next;
- prev = next->f_prev;
- next->f_prev = file;
- file->f_prev = prev;
- prev->f_next = file;
-}
/*
* Allocate a new memory page for file structures and
^ permalink raw reply
* Re: Linux 2.4.25-pre7 - no DRQ after issuing WRITE
From: Marcelo Tosatti @ 2004-01-25 19:20 UTC (permalink / raw)
To: Gabor Z. Papp; +Cc: Marcelo Tosatti, linux-kernel, Bartlomiej Zolnierkiewicz
In-Reply-To: <x6ptd8l7so@gzp>
On Sun, 25 Jan 2004, Gabor Z. Papp wrote:
> * Marcelo Tosatti <marcelo.tosatti@cyclades.com>:
>
> | Please help testing! :)
>
> Here we go: http://gzp.odpn.net/tmp/linux-2.4.25-pre7/
>
> The "no DRQ after issuing WRITE" problem with 2 120GB Seagate
> harddisk. I don't think its hw problem, because these disks are fine
> in other environment. More "load" related, without running them in sw
> raid mode, the problem doesn't hit me so quickly.
Hi Gabor,
I'm not IDE expert, but these errors look like hardware fault for me
(Bartlomiej CCed).
What about 2.6 and older 2.4 kernels on the same hardware ?
-------------
Mounted devfs on /dev
Freeing unused kernel memory: 116k freed
hde: dma_timer_expiry: dma status == 0x21
hdg: dma_timer_expiry: dma status == 0x21
hde: error waiting for DMA
hde: dma timeout retry: status=0x7f { DriveReady DeviceFault SeekComplete
DataRequest CorrectedError Index Error }
hde: dma timeout retry: error=0x7f { DriveStatusError UncorrectableError
SectorIdNotFound TrackZeroNotFound AddrMarkNotFound },
LBAsect=9343692930943, high=556927, low=8355711, sector=4352
hde: DMA disabled
hdg: error waiting for DMA
hdg: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest
}
hdg: status error: status=0x50 { DriveReady SeekComplete }
hdg: no DRQ after issuing MULTWRITE
hdg: status timeout: status=0xd0 { Busy }
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
^ permalink raw reply
* Re: [RFC/PATCH] IMQ port to 2.6
From: jamal @ 2004-01-25 19:22 UTC (permalink / raw)
To: Tomas Szepe; +Cc: linux-kernel, netdev
In-Reply-To: <20040125164431.GA31548@louise.pinerecords.com>
There has been no real good reason as to why IMQ is needed to begin
with. It may be easy to use and has been highly publized (which is
always a dangerous thing in Linux).
Maybe lets take a step back and see how people use it. How and why do
you use IMQ? Is this because you couldnt use the ingress qdisc?
Note, the abstraction to begin with is in the wrong place - it sure is
an easy and nice looking hack. So is the current ingress qdisc, but we
are laying that to rest with TC extensions.
cheers,
jamal
On Sun, 2004-01-25 at 11:44, Tomas Szepe wrote:
> On Jan-25 2004, Sun, 16:24 +0100
> Marcel Sebek <sebek64@post.cz> wrote:
>
> > I have ported IMQ driver from 2.4 to 2.6.2-rc1.
> > Original version was from http://trash.net/~kaber/imq/.
> > ...
>
> It would definitely be nice to see IMQ merged at last.
^ permalink raw reply
* Re: mpspec.h, mach_mpspec.h
From: Randy.Dunlap @ 2004-01-25 19:19 UTC (permalink / raw)
To: Sam Ravnborg; +Cc: jamagallon, linux-kernel, akpm
In-Reply-To: <20040125191106.GA3203@mars.ravnborg.org>
On Sun, 25 Jan 2004 20:11:06 +0100 Sam Ravnborg <sam@ravnborg.org> wrote:
| >
| > Workaround is to add -I/usr/src/linux/include/asm/mach-default.
|
| i386 at least always include:
| -Iinclude/asm-i386/mach-default
| Which should let gcc include the file in question.
|
| Try to compile with V=1 and post the full command line to gcc.
JAM, how are you building the sensors modules?
I.e., is this just a "make modules" or are you building
modules that are outside of the kernel tree?
--
~Randy
^ permalink raw reply
* Re: Support for newer gcc/gas options
From: Dimitri Torfs @ 2004-01-25 19:17 UTC (permalink / raw)
To: Maciej W. Rozycki; +Cc: linux-mips
In-Reply-To: <Pine.LNX.4.55.0401221700510.16353@jurand.ds.pg.gda.pl>
On Thu, Jan 22, 2004 at 05:10:23PM +0100, Maciej W. Rozycki wrote:
>
> Thanks for digging into it. Actually after fixing the typos I've noticed
> gcc 2.95.4 always implies the ISA from the ABI unless overridden and
> -mabi=64 implies -mips4, so it bails out with -march/-mcpu set to
> something like r4600. This also proves the uncertainity about what's
> passed to gas and so far including an ISA specification in gas settings is
> tolerable if carefully chosen. So here's a set of new updates -- now the
> ISA specifier is removed from gcc flags only if it actually works and the
> ISA specifier for gas is untouched.
>
> Hopefully this is the last attempt. Please try it.
>
Ok for me (tested the HEAD one).
Dimitri
--
Dimitri Torfs | NSCE
dimitri@sonycom.com | The Corporate Village
tel: +32 2 7008541 | Da Vincilaan 7 - D1
fax: +32 2 7008622 | B-1935 Zaventem - Belgium
^ permalink raw reply
* Re: Installing freedos
From: Bart Oldeman @ 2004-01-25 19:16 UTC (permalink / raw)
To: linux-msdos
In-Reply-To: <401410C6.2060505@my.home>
On Sun, 25 Jan 2004, Jan Willem Stumpel wrote:
> Wouldn't it be nice if freedos could be installed with a command like
>
> installfreedos <directory>
>
> Instantly transforming <directory> into a dosemu-bootable C:
> drive, with a sub-directory full of DOS utilities?
>
> Or is this already possible?
yes, it's called "dosemu -install". possible with the installation from
source and the RPM. That might simplify a bit of the "dummies" page --
I'll have another look at that later; for this week I think I should take
a break from DOSEMU. It eats too much time right now.
Bart
^ permalink raw reply
* RE: FW: Submission for S2io 10GbE driver
From: jamal @ 2004-01-25 19:14 UTC (permalink / raw)
To: Leonid Grossman; +Cc: netdev
In-Reply-To: <002501c3e2b5$543c45e0$0400a8c0@S2IOtech.com>
On Sat, 2004-01-24 at 15:04, Leonid Grossman wrote:
> These schemes could be complimentary, right now we do see that different
> thresholds need to be programmed for regular and Jumbo traffic.
>
> One thing I did not mention is that our ASIC supports several
> utilization thresholds on per interrupt basis (up to 64 MSI-X
> interrupts). There are also independent tx and rx queues, and each can
> have it's own interrupt. There is a pretty large number of parameters
> that traffic could be steered upon, packet size is one of them.
>
Would be interesting to see what these queue selection parameters are.
For example, an extremely important thing to avoid is reordering of
packets. You reorder packets on a TCP flow and you perfomance goes
beserk.
> So, if you want to have different interrupt moderation schemes for
> different packet sizes, you just need to steer packets to separate
> queues based upon size, and then assign a separate MSI interrupt to
> these queues and set different utilization thresholds for different
> interrupts. At any given workload, you will be getting interrupts at
> different rate for small and for big packets.
Does sound interesting, but i am suspcious about reordering; i.e you
dont want a 64 byte packet from one flow to be in a different queue
than another which is 1500 bytes. The 2 packet must be processed
strictly in FIFO manner.
> Anyway, you are right there are many interrupt moderation schemes that
> host driver can deploy, our goal was to provide a flexible hardware
> assist.
So is it possible to program it such that if a threshold interupt rate
is crossed it adjusts its mitigation values? actually i should say its
the second order effect that is of interest to the threshold i.e the
integral of the interupt arrival rate.
cheers,
jamal
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.