Re: 2.6.23-rc8-mm2
From: Greg KH <[EMAIL PROTECTED]> Date: Sat, Sep 29, 2007 at 08:19:42AM -0700 > On Sat, Sep 29, 2007 at 05:37:29PM +0800, Dave Young wrote: > > Hi, > > The kernel report warnings about sysfs filename duplicate under > > rc8-mm1 and rc8-mm2. > > 1. > > cut > > sysfs: duplicate filename 'usbcore' can not be created > > WARNING: at fs/sysfs/dir.c:433 sysfs_add_one() > > [] dump_trace+0x1bf/0x1d0 > > [] show_trace_log_lvl+0x18/0x30 > > [] show_trace+0xf/0x20 I get some identical warnings from iftab in userspace: eth1 renamed to switch sysfs: duplicate filename 'switch' can not be created WARNING: at fs/sysfs/dir.c:433 sysfs_add_one() Call Trace: [] sysfs_add_one+0xac/0xe0 [] sysfs_create_link+0xac/0x140 [] device_rename+0x1c2/0x220 [] dev_change_name+0xbc/0x250 [] dev_ifsioc+0x338/0x3a0 [] dev_ioctl+0x36d/0x3c0 [] handle_mm_fault+0x1a5/0x6f0 [] sock_ioctl+0x7d/0x250 [] do_ioctl+0x31/0x90 [] vfs_ioctl+0x21b/0x2d0 [] sys_ioctl+0x4a/0x80 [] system_call+0x7e/0x83 net switch: device_rename: sysfs_create_symlink failed (-17) eth2 renamed to adsl sysfs: duplicate filename 'adsl' can not be created WARNING: at fs/sysfs/dir.c:433 sysfs_add_one() Call Trace: [] sysfs_add_one+0xac/0xe0 [] sysfs_create_link+0xac/0x140 [] device_rename+0x1c2/0x220 [] dev_change_name+0xbc/0x250 [] dev_ifsioc+0x338/0x3a0 [] dev_ioctl+0x36d/0x3c0 [] handle_mm_fault+0x1a5/0x6f0 [] sock_ioctl+0x7d/0x250 [] do_ioctl+0x31/0x90 [] vfs_ioctl+0x21b/0x2d0 [] sys_ioctl+0x4a/0x80 [] system_call+0x7e/0x83 net adsl: device_rename: sysfs_create_symlink failed (-17) switch: no link during initialization. ip_tables: (C) 2000-2006 Netfilter Core Team this happens when iftab renames my network interfaces. Booting 2.6.21-rc1-mm2 said: eth1 renamed to switch eth2 renamed to adsl ip_tables: (C) 2000-2006 Netfilter Core Team 2.6.23-rc4-mm1 said: eth1 renamed to switch net switch: device_rename: sysfs_create_symlink failed (-17) eth2 renamed to adsl net adsl: device_rename: sysfs_create_symlink failed (-17) ip_tables: (C) 2000-2006 Netfilter Core Team .config attached below. Kind regards, Jurriaan # # Automatically generated make config: don't edit # Linux kernel version: 2.6.23-rc8-mm2 # Sat Sep 29 07:37:07 2007 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_NONIRQ_WAKEUP=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_ZONE_DMA32=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_DMI=y CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set # CONFIG_TASKSTATS is not set # CONFIG_USER_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=18 # CONFIG_CGROUPS is not set CONFIG_FAIR_GROUP_SCHED=y CONFIG_FAIR_USER_SCHED=y CONFIG_SYSFS_DEPRECATED=y # CONFIG_RELAY is not set # CONFIG_BLK_DEV_INITRD is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLAB=y # CONFIG_SLUB is not set # CONFIG_SLOB is not set CONFIG_PROC_PAGE_MONITOR=y CONFIG_PROC_KPAGEMAP=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_BLK_DEV_BSG is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y CONFIG_DEFAULT_AS=y # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="anticipatory" # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_X86_PC=y # CONFIG_X86_VSMP is not set CONFIG_MK8=y # CONFIG_MPSC is not set # CONFIG_MCORE2 is not
Re: 2.6.23-rc8-mm2
From: Greg KH [EMAIL PROTECTED] Date: Sat, Sep 29, 2007 at 08:19:42AM -0700 On Sat, Sep 29, 2007 at 05:37:29PM +0800, Dave Young wrote: Hi, The kernel report warnings about sysfs filename duplicate under rc8-mm1 and rc8-mm2. 1. cut sysfs: duplicate filename 'usbcore' can not be created WARNING: at fs/sysfs/dir.c:433 sysfs_add_one() [c010528f] dump_trace+0x1bf/0x1d0 [c0105358] show_trace_log_lvl+0x18/0x30 [c010537f] show_trace+0xf/0x20 I get some identical warnings from iftab in userspace: eth1 renamed to switch sysfs: duplicate filename 'switch' can not be created WARNING: at fs/sysfs/dir.c:433 sysfs_add_one() Call Trace: [802cb99c] sysfs_add_one+0xac/0xe0 [802cc8fc] sysfs_create_link+0xac/0x140 [803fa632] device_rename+0x1c2/0x220 [80500ccc] dev_change_name+0xbc/0x250 [80501198] dev_ifsioc+0x338/0x3a0 [8050156d] dev_ioctl+0x36d/0x3c0 [80271965] handle_mm_fault+0x1a5/0x6f0 [804f215d] sock_ioctl+0x7d/0x250 [80293cb1] do_ioctl+0x31/0x90 [80293f2b] vfs_ioctl+0x21b/0x2d0 [8029402a] sys_ioctl+0x4a/0x80 [8020bc8e] system_call+0x7e/0x83 net switch: device_rename: sysfs_create_symlink failed (-17) eth2 renamed to adsl sysfs: duplicate filename 'adsl' can not be created WARNING: at fs/sysfs/dir.c:433 sysfs_add_one() Call Trace: [802cb99c] sysfs_add_one+0xac/0xe0 [802cc8fc] sysfs_create_link+0xac/0x140 [803fa632] device_rename+0x1c2/0x220 [80500ccc] dev_change_name+0xbc/0x250 [80501198] dev_ifsioc+0x338/0x3a0 [8050156d] dev_ioctl+0x36d/0x3c0 [80271965] handle_mm_fault+0x1a5/0x6f0 [804f215d] sock_ioctl+0x7d/0x250 [80293cb1] do_ioctl+0x31/0x90 [80293f2b] vfs_ioctl+0x21b/0x2d0 [8029402a] sys_ioctl+0x4a/0x80 [8020bc8e] system_call+0x7e/0x83 net adsl: device_rename: sysfs_create_symlink failed (-17) switch: no link during initialization. ip_tables: (C) 2000-2006 Netfilter Core Team this happens when iftab renames my network interfaces. Booting 2.6.21-rc1-mm2 said: eth1 renamed to switch eth2 renamed to adsl ip_tables: (C) 2000-2006 Netfilter Core Team 2.6.23-rc4-mm1 said: eth1 renamed to switch net switch: device_rename: sysfs_create_symlink failed (-17) eth2 renamed to adsl net adsl: device_rename: sysfs_create_symlink failed (-17) ip_tables: (C) 2000-2006 Netfilter Core Team .config attached below. Kind regards, Jurriaan # # Automatically generated make config: don't edit # Linux kernel version: 2.6.23-rc8-mm2 # Sat Sep 29 07:37:07 2007 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_NONIRQ_WAKEUP=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_ZONE_DMA32=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_DMI=y CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION= CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set # CONFIG_TASKSTATS is not set # CONFIG_USER_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=18 # CONFIG_CGROUPS is not set CONFIG_FAIR_GROUP_SCHED=y CONFIG_FAIR_USER_SCHED=y CONFIG_SYSFS_DEPRECATED=y # CONFIG_RELAY is not set # CONFIG_BLK_DEV_INITRD is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLAB=y # CONFIG_SLUB is not set # CONFIG_SLOB is not set CONFIG_PROC_PAGE_MONITOR=y CONFIG_PROC_KPAGEMAP=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_BLK_DEV_BSG is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y
Re: 2.6.23-rc4-mm1 OOPS in forcedeth?
From: Satyam Sharma <[EMAIL PROTECTED]> Date: Sun, Sep 02, 2007 at 06:24:29AM +0530 > Hi Jurriaan, > > > > [EMAIL PROTECTED] wrote: > > > From: Andrew Morton <[EMAIL PROTECTED]> > > > Date: Fri, Aug 31, 2007 at 09:58:22PM -0700 > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc4/2.6.23-rc4-mm1/ > > > > > > > On this machine (Athlon 64 X2 4600, 4 GiB memory, lots of disks), > > > 2.6.23-rc1-mm2 runs fine. 2.6.23-rc4-mm1 reproducably dies within seconds > > > of > > > starting > > > a rsync session on another PC against this machine. > > > > > > NULL pointer dereference > > > code: nv_napi_poll+0x108 > > > trace:net_rx_action+0xab > > > __do_softirq+0x74 > > > call_softirq+0x1c > > > do_softirq+0x3d > > > irq_exit+0x85 > > > do_IRQ+0x85 > > > ret_from_intr+0x0 > > The dmesg you posted below doesn't cover the messages from this oops > itself. As you mentioned you can reproduce this oops easily, please do so, > and post the *full* oops log (if it doesn't get logged to disk, you can > try taking digicam photo, or write down *all* the messages and post here). > I built an x86_64 kernel as per your .config, but don't see any memory > dereference at nv_napi_poll+0x108 -- could be toolchain differences. > There are 4 pictures of oopses here: http://www.xs4all.nl/~thunder7/oops_2623rc4mm1_1.jpg http://www.xs4all.nl/~thunder7/oops_2623rc4mm1_2.jpg http://www.xs4all.nl/~thunder7/oops_2623rc4mm1_3.jpg http://www.xs4all.nl/~thunder7/oops_2623rc4mm1_4.jpg image quality, well, they're readable. Good luck, Jurriaan -- management n. 1. Corporate power elites distinguished primarily by their distance from actual productive work and their chronic failure to manage (see also suit). Spoken derisively, as in "Management decided that ...". 2. Mythically, a vast bureaucracy responsible for all the world's minor irritations. Hackers' satirical public notices are often signed `The Mgt'; this derives from the "Illuminatus" novels (see the Bibliography in Appendix C). Debian (Unstable) GNU/Linux 2.6.23-rc1-mm2 2x2010 bogomips load 0.43 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rc4-mm1 OOPS in forcedeth?
From: Satyam Sharma [EMAIL PROTECTED] Date: Sun, Sep 02, 2007 at 06:24:29AM +0530 Hi Jurriaan, [EMAIL PROTECTED] wrote: From: Andrew Morton [EMAIL PROTECTED] Date: Fri, Aug 31, 2007 at 09:58:22PM -0700 ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc4/2.6.23-rc4-mm1/ On this machine (Athlon 64 X2 4600, 4 GiB memory, lots of disks), 2.6.23-rc1-mm2 runs fine. 2.6.23-rc4-mm1 reproducably dies within seconds of starting a rsync session on another PC against this machine. NULL pointer dereference code: nv_napi_poll+0x108 trace:net_rx_action+0xab __do_softirq+0x74 call_softirq+0x1c do_softirq+0x3d irq_exit+0x85 do_IRQ+0x85 ret_from_intr+0x0 The dmesg you posted below doesn't cover the messages from this oops itself. As you mentioned you can reproduce this oops easily, please do so, and post the *full* oops log (if it doesn't get logged to disk, you can try taking digicam photo, or write down *all* the messages and post here). I built an x86_64 kernel as per your .config, but don't see any memory dereference at nv_napi_poll+0x108 -- could be toolchain differences. There are 4 pictures of oopses here: http://www.xs4all.nl/~thunder7/oops_2623rc4mm1_1.jpg http://www.xs4all.nl/~thunder7/oops_2623rc4mm1_2.jpg http://www.xs4all.nl/~thunder7/oops_2623rc4mm1_3.jpg http://www.xs4all.nl/~thunder7/oops_2623rc4mm1_4.jpg image quality, well, they're readable. Good luck, Jurriaan -- management n. 1. Corporate power elites distinguished primarily by their distance from actual productive work and their chronic failure to manage (see also suit). Spoken derisively, as in Management decided that 2. Mythically, a vast bureaucracy responsible for all the world's minor irritations. Hackers' satirical public notices are often signed `The Mgt'; this derives from the Illuminatus novels (see the Bibliography in Appendix C). Debian (Unstable) GNU/Linux 2.6.23-rc1-mm2 2x2010 bogomips load 0.43 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rc4-mm1 OOPS in forcedeth?
From: Satyam Sharma <[EMAIL PROTECTED]>
Date: Sun, Sep 02, 2007 at 06:24:29AM +0530
>
> The dmesg you posted below doesn't cover the messages from this oops
> itself. As you mentioned you can reproduce this oops easily, please do so,
> and post the *full* oops log (if it doesn't get logged to disk, you can
> try taking digicam photo, or write down *all* the messages and post here).
> I built an x86_64 kernel as per your .config, but don't see any memory
> dereference at nv_napi_poll+0x108 -- could be toolchain differences.
>
> Else, can you run:
> $ gdb ./vmlinux
>
> and then:
> (gdb) l *nv_napi_poll+0x108
>
> and send us the output?
>
That seems to be the easier option:
AMD64 :gdb /usr/src/linux-2.6.23-rc4-mm1/vmlinux
GNU gdb 6.6-debian
(gdb) l *nv_napi_poll+0x108
0x80418f28 is in nv_napi_poll (drivers/net/forcedeth.c:2470).
2465if ((flags & NV_RX2_CHECKSUMMASK) ==
NV_RX2_CHECKSUMOK2)/*ip and tcp */ {
2466skb->ip_summed = CHECKSUM_UNNECESSARY;
2467} else {
2468if ((flags & NV_RX2_CHECKSUMMASK) ==
NV_RX2_CHECKSUMOK1 ||
2469(flags & NV_RX2_CHECKSUMMASK) ==
NV_RX2_CHECKSUMOK3) {
2470skb->ip_summed =
CHECKSUM_UNNECESSARY;
2471}
2472}
2473
2474/* got a valid packet - forward it to the
network core */
(gdb) q
as for toolchain differences: this is Debian Unstable, up-to-date as of
yesterday morning.
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux middle 2.6.23-rc1-mm2 #1 SMP Wed Aug 1 14:58:22 CEST 2007 x86_64 GNU/Linux
Gnu C 4.1.3
Gnu make 3.81
binutils Binutils
util-linux 2.13
mount 2.13
module-init-tools 3.3-pre11
e2fsprogs 1.40.2
reiserfsprogs 3.6.19
Linux C Library6.1
Dynamic linker (ldd) 2.6.1
Procps 3.2.7
Net-tools 1.60
Console-tools 0.2.3
Sh-utils 5.97
Modules Loaded nf_nat_ftp nf_nat_irc nf_conntrack_irc nf_conntrack_ftp
ipt_MASQUERADE iptable_nat nf_nat ipt_REJECT ipt_LOG xt_limit nf_conntrack_ipv4
xt_state xt_tcpudp iptable_filter ip_tables x_tables snd_emu10k1_synth
snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_emu10k1 snd_seq_dummy
snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_rawmidi snd_ac97_codec
ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_device snd_timer
snd_page_alloc snd_util_mem snd_hwdep snd soundcore k8temp it87 hwmon_vid hwmon
i2c_nforce2
Good luck,
Jurriaan
--
His pride could withstand anything. He simply wouldn't care.
Melanie Rawn - Skybowl
Debian (Unstable) GNU/Linux 2.6.23-rc1-mm2 2x2010 bogomips load 0.43
the Jack Vance Integral Edition: http://www.integralarchive.org
-
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 FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rc4-mm1 OOPS in forcedeth?
From: Satyam Sharma [EMAIL PROTECTED]
Date: Sun, Sep 02, 2007 at 06:24:29AM +0530
The dmesg you posted below doesn't cover the messages from this oops
itself. As you mentioned you can reproduce this oops easily, please do so,
and post the *full* oops log (if it doesn't get logged to disk, you can
try taking digicam photo, or write down *all* the messages and post here).
I built an x86_64 kernel as per your .config, but don't see any memory
dereference at nv_napi_poll+0x108 -- could be toolchain differences.
Else, can you run:
$ gdb ./vmlinux
and then:
(gdb) l *nv_napi_poll+0x108
and send us the output?
That seems to be the easier option:
AMD64 :gdb /usr/src/linux-2.6.23-rc4-mm1/vmlinux
GNU gdb 6.6-debian
(gdb) l *nv_napi_poll+0x108
0x80418f28 is in nv_napi_poll (drivers/net/forcedeth.c:2470).
2465if ((flags NV_RX2_CHECKSUMMASK) ==
NV_RX2_CHECKSUMOK2)/*ip and tcp */ {
2466skb-ip_summed = CHECKSUM_UNNECESSARY;
2467} else {
2468if ((flags NV_RX2_CHECKSUMMASK) ==
NV_RX2_CHECKSUMOK1 ||
2469(flags NV_RX2_CHECKSUMMASK) ==
NV_RX2_CHECKSUMOK3) {
2470skb-ip_summed =
CHECKSUM_UNNECESSARY;
2471}
2472}
2473
2474/* got a valid packet - forward it to the
network core */
(gdb) q
as for toolchain differences: this is Debian Unstable, up-to-date as of
yesterday morning.
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux middle 2.6.23-rc1-mm2 #1 SMP Wed Aug 1 14:58:22 CEST 2007 x86_64 GNU/Linux
Gnu C 4.1.3
Gnu make 3.81
binutils Binutils
util-linux 2.13
mount 2.13
module-init-tools 3.3-pre11
e2fsprogs 1.40.2
reiserfsprogs 3.6.19
Linux C Library6.1
Dynamic linker (ldd) 2.6.1
Procps 3.2.7
Net-tools 1.60
Console-tools 0.2.3
Sh-utils 5.97
Modules Loaded nf_nat_ftp nf_nat_irc nf_conntrack_irc nf_conntrack_ftp
ipt_MASQUERADE iptable_nat nf_nat ipt_REJECT ipt_LOG xt_limit nf_conntrack_ipv4
xt_state xt_tcpudp iptable_filter ip_tables x_tables snd_emu10k1_synth
snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_emu10k1 snd_seq_dummy
snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_rawmidi snd_ac97_codec
ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_device snd_timer
snd_page_alloc snd_util_mem snd_hwdep snd soundcore k8temp it87 hwmon_vid hwmon
i2c_nforce2
Good luck,
Jurriaan
--
His pride could withstand anything. He simply wouldn't care.
Melanie Rawn - Skybowl
Debian (Unstable) GNU/Linux 2.6.23-rc1-mm2 2x2010 bogomips load 0.43
the Jack Vance Integral Edition: http://www.integralarchive.org
-
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 FAQ at http://www.tux.org/lkml/
Re: USB subsystem (part of it) hangs
From: Paulo da Silva <[EMAIL PROTECTED]> Date: Fri, Jul 27, 2007 at 02:07:15AM +0100 > This is a bug report. Any further information you may need, please let > me know. > Modules Loaded ndiswrapper problem is, once you load ndiswrapper + the proprietary, closed source windows drivers that go with that, nobody here can tell you what's going wrong, since nobody here can know what goes on inside that driver. So unless you can reproduce it without ndiswrapper, it can't be solved. Kind regards, Jurriaan -- ..and the great tagline hunter crouches silently, text editor at the ready.. Debian (Unstable) GNU/Linux 2.6.22-rc6 2x2010 bogomips load 0.07 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: USB subsystem (part of it) hangs
From: Paulo da Silva [EMAIL PROTECTED] Date: Fri, Jul 27, 2007 at 02:07:15AM +0100 This is a bug report. Any further information you may need, please let me know. Modules Loaded ndiswrapper problem is, once you load ndiswrapper + the proprietary, closed source windows drivers that go with that, nobody here can tell you what's going wrong, since nobody here can know what goes on inside that driver. So unless you can reproduce it without ndiswrapper, it can't be solved. Kind regards, Jurriaan -- ..and the great tagline hunter crouches silently, text editor at the ready.. Debian (Unstable) GNU/Linux 2.6.22-rc6 2x2010 bogomips load 0.07 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: 2.6.21-mm2 boot failure, raid autodetect, bd_set_size+0xb/0x80
From: Andrew Morton <[EMAIL PROTECTED]> Date: Fri, May 11, 2007 at 11:18:09AM -0700 > > Yes, Neil had a whoops and a dud patch spent a day in mainline. > > Hopefully the below revert (from mainline) will fix it. > > > Gitweb: > http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=44ce6294d07555c3d313757105fd44b78208407f > Commit: 44ce6294d07555c3d313757105fd44b78208407f > Parent: 497f050c42e46a4b1f6a9bcd8827fa5d97fe1feb > Author: Linus Torvalds <[EMAIL PROTECTED]> > AuthorDate: Wed May 9 18:51:36 2007 -0700 > Committer: Linus Torvalds <[EMAIL PROTECTED]> > CommitDate: Wed May 9 18:51:36 2007 -0700 > > Revert "md: improve partition detection in md array" > I can boot after applying this patch. Thanks, Jurriaan -- "T'lan Imass were never nothing but trouble," he said. "Always two sides to whatever they did, maybe more than two. Maybe hundreds." Steven Erikson - Deadhouse Gates Debian (Unstable) GNU/Linux 2.6.21-mm2 2x2010 bogomips load 0.42 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: 2.6.21-mm2 boot failure, raid autodetect, bd_set_size+0xb/0x80
From: Andrew Morton [EMAIL PROTECTED] Date: Fri, May 11, 2007 at 11:18:09AM -0700 Yes, Neil had a whoops and a dud patch spent a day in mainline. Hopefully the below revert (from mainline) will fix it. Gitweb: http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=44ce6294d07555c3d313757105fd44b78208407f Commit: 44ce6294d07555c3d313757105fd44b78208407f Parent: 497f050c42e46a4b1f6a9bcd8827fa5d97fe1feb Author: Linus Torvalds [EMAIL PROTECTED] AuthorDate: Wed May 9 18:51:36 2007 -0700 Committer: Linus Torvalds [EMAIL PROTECTED] CommitDate: Wed May 9 18:51:36 2007 -0700 Revert md: improve partition detection in md array I can boot after applying this patch. Thanks, Jurriaan -- T'lan Imass were never nothing but trouble, he said. Always two sides to whatever they did, maybe more than two. Maybe hundreds. Steven Erikson - Deadhouse Gates Debian (Unstable) GNU/Linux 2.6.21-mm2 2x2010 bogomips load 0.42 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: 2.6.21-rc5-mm3 - no boot, "address not 2M aligned"
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Mon, Apr 02, 2007 at 04:49:14PM +0200 > > I used a working 2.6.21-rc3-mm2 tree, patched it up to 2.6.21-rc5-mm3 > and applied your patch. I ended up with the .config later in this email, > and got this error: > > CC arch/x86_64/kernel/head64.o > arch/x86_64/kernel/head64.c: In function 'x86_64_start_kernel': > arch/x86_64/kernel/head64.c:70: error: size of array 'type name' is negative > make[1]: *** [arch/x86_64/kernel/head64.o] Error 1 > make: *** [arch/x86_64/kernel] Error 2 > > After reverting your patch, the build didn't fail, but of course the > kernel won't build. > That should, of course, read 'kernel won't boot'. Sorry, Jurriaan -- Debian (Unstable) GNU/Linux 2.6.21-rc5-mm3 2x4826 bogomips load 0.92 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: 2.6.21-rc5-mm3 - no boot, "address not 2M aligned"
From: Vivek Goyal <[EMAIL PROTECTED]> Date: Mon, Apr 02, 2007 at 05:06:39PM +0530 > On Mon, Apr 02, 2007 at 01:17:45PM +0200, [EMAIL PROTECTED] wrote: > [..] > > > + /* > > > + * Make sure kernel is aligned to 2MB address. Catching it at compile > > > + * time is better. Change your config file and compile the kernel > > > + * for a 2MB aligned address (CONFIG_PHYSICAL_START) > > > + */ > > > + BUILD_BUG_ON(ALIGN(CONFIG_PHYSICAL_START, __KERNEL_ALIGN) > > > + != CONFIG_PHYSICAL_START); > > > + > > > /* clear bss before set_intr_gate with early_idt_handler */ > > > clear_bss(); > > > > > > diff -puN > > > include/asm-x86_64/page.h~x86_64-check-for-config-physical-start-aligned-2M > > > include/asm-x86_64/page.h > > > --- > > > linux-2.6.21-rc5-mm3-vanilla/include/asm-x86_64/page.h~x86_64-check-for-config-physical-start-aligned-2M > > > 2007-04-02 20:50:55.0 +0530 > > > +++ linux-2.6.21-rc5-mm3-vanilla-root/include/asm-x86_64/page.h > > > 2007-04-02 20:51:34.0 +0530 > > > @@ -79,6 +79,7 @@ extern unsigned long phys_base; > > > #endif /* !__ASSEMBLY__ */ > > > > > > #define __PHYSICAL_START CONFIG_PHYSICAL_START > > > +#define __KERNEL_ALIGN 0x20 > > > #define __START_KERNEL (__START_KERNEL_map + __PHYSICAL_START) > > > #define __START_KERNEL_map 0x8000 > > > #define __PAGE_OFFSET 0x8100 > > > _ > > > You will get a compile time error and your compilation will not be > through if your physical address is not 2MB aligned. Just give it a try. > Just gave it a try, but I'm not convinced yet :-) I used a working 2.6.21-rc3-mm2 tree, patched it up to 2.6.21-rc5-mm3 and applied your patch. I ended up with the .config later in this email, and got this error: CC arch/x86_64/kernel/head64.o arch/x86_64/kernel/head64.c: In function 'x86_64_start_kernel': arch/x86_64/kernel/head64.c:70: error: size of array 'type name' is negative make[1]: *** [arch/x86_64/kernel/head64.o] Error 1 make: *** [arch/x86_64/kernel] Error 2 After reverting your patch, the build didn't fail, but of course the kernel won't build. Good luck, Jurriaan # # Automatically generated make config: don't edit # Linux kernel version: 2.6.21-rc5-mm3 # Mon Apr 2 16:38:50 2007 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_ZONE_DMA32=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_DMI=y CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SWAP_PREFETCH=y CONFIG_SYSVIPC=y # CONFIG_IPC_NS is not set CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set # CONFIG_TASKSTATS is not set # CONFIG_UTS_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_CPUSETS is not set CONFIG_SYSFS_DEPRECATED=y # CONFIG_RELAY is not set # CONFIG_BLK_DEV_INITRD is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_EMBEDDED=y # CONFIG_SYSCTL_SYSCALL is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y # CONFIG_VM_EVENT_COUNTERS is not set CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set CONFIG_PAGE_GROUP_BY_MOBILITY=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y # # Process debugging support # CONFIG_UTRACE=y CONFIG_PTRACE=y # # Block layer # CONFIG_BLOCK=y # CONFIG_BLK_DEV_IO_TRACE is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y # CONFIG_IOSCHED_DEADLINE is not set # CONFIG_IOSCHED_CFQ is not set CONFIG_DEFAULT_AS=y # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="anticipatory" # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_VSMP is not set CONFIG_MK8=y # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_INTERNODE_CACHE_BYTES=64
Re: 2.6.21-rc5-mm3 - no boot, "address not 2M aligned"
From: Vivek Goyal <[EMAIL PROTECTED]>
Date: Mon, Apr 02, 2007 at 01:11:59PM +0530
>
> How about attached patch?
>
> o X86_64 kernel should run from 2MB aligned address for two reasons.
> - Performance.
> - For relocatable kernels, page tables are updated based on difference
> between compile time address and load time physical address.
> This difference should be multiple of 2MB as kernel text and data
> is mapped using 2MB pages and PMD should be pointing to a 2MB
> aligned address. Life is simpler if both compile time and load time
> kernel addresses are 2MB aligned.
>
> o Flag the error at compile time if one is trying to build a kernel which
> does not meet alignment restrictions.
>
> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]>
> ---
>
> arch/x86_64/kernel/head64.c |8
> include/asm-x86_64/page.h |1 +
> 2 files changed, 9 insertions(+)
>
> diff -puN
> arch/x86_64/kernel/head64.c~x86_64-check-for-config-physical-start-aligned-2M
> arch/x86_64/kernel/head64.c
> ---
> linux-2.6.21-rc5-mm3-vanilla/arch/x86_64/kernel/head64.c~x86_64-check-for-config-physical-start-aligned-2M
> 2007-04-02 20:46:43.0 +0530
> +++ linux-2.6.21-rc5-mm3-vanilla-root/arch/x86_64/kernel/head64.c
> 2007-04-02 21:20:45.0 +0530
> @@ -62,6 +62,14 @@ void __init x86_64_start_kernel(char * r
> {
> int i;
>
> + /*
> + * Make sure kernel is aligned to 2MB address. Catching it at compile
> + * time is better. Change your config file and compile the kernel
> + * for a 2MB aligned address (CONFIG_PHYSICAL_START)
> + */
> + BUILD_BUG_ON(ALIGN(CONFIG_PHYSICAL_START, __KERNEL_ALIGN)
> + != CONFIG_PHYSICAL_START);
> +
> /* clear bss before set_intr_gate with early_idt_handler */
> clear_bss();
>
> diff -puN
> include/asm-x86_64/page.h~x86_64-check-for-config-physical-start-aligned-2M
> include/asm-x86_64/page.h
> ---
> linux-2.6.21-rc5-mm3-vanilla/include/asm-x86_64/page.h~x86_64-check-for-config-physical-start-aligned-2M
> 2007-04-02 20:50:55.0 +0530
> +++ linux-2.6.21-rc5-mm3-vanilla-root/include/asm-x86_64/page.h
> 2007-04-02 20:51:34.0 +0530
> @@ -79,6 +79,7 @@ extern unsigned long phys_base;
> #endif /* !__ASSEMBLY__ */
>
> #define __PHYSICAL_START CONFIG_PHYSICAL_START
> +#define __KERNEL_ALIGN 0x20
> #define __START_KERNEL (__START_KERNEL_map + __PHYSICAL_START)
> #define __START_KERNEL_map 0x8000
> #define __PAGE_OFFSET 0x8100
> _
I'm only a user, so I'm not uptodate on these addresses and how they
work. However, how does this solve the problem that running
make oldconfig
on a working 2.6.21-rc3-mm2 .config gives an unbootable 2.6.21-rc5-mm3
kernel? If I read things correctly, you now get a BUG, but the kernel
still won't boot. If that is correct, than I, as a user, don't think
that this is the solution that I feel comfortable with.
If the kernel only boots CONFIG_PHYSICAL_START is aligned on a 2MB
address, then we should align it, not BUG out when it's not, and
especially not when it's unaligned through no fault of the user.
Kind regards,
Jurriaan
--
Debian (Unstable) GNU/Linux 2.6.21-rc5-mm3 2x2010 bogomips load 0.89
the Jack Vance Integral Edition: http://www.integralarchive.org
-
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 FAQ at http://www.tux.org/lkml/
Re: 2.6.21-rc5-mm3 - no boot, address not 2M aligned
From: Vivek Goyal [EMAIL PROTECTED]
Date: Mon, Apr 02, 2007 at 01:11:59PM +0530
How about attached patch?
o X86_64 kernel should run from 2MB aligned address for two reasons.
- Performance.
- For relocatable kernels, page tables are updated based on difference
between compile time address and load time physical address.
This difference should be multiple of 2MB as kernel text and data
is mapped using 2MB pages and PMD should be pointing to a 2MB
aligned address. Life is simpler if both compile time and load time
kernel addresses are 2MB aligned.
o Flag the error at compile time if one is trying to build a kernel which
does not meet alignment restrictions.
Signed-off-by: Vivek Goyal [EMAIL PROTECTED]
---
arch/x86_64/kernel/head64.c |8
include/asm-x86_64/page.h |1 +
2 files changed, 9 insertions(+)
diff -puN
arch/x86_64/kernel/head64.c~x86_64-check-for-config-physical-start-aligned-2M
arch/x86_64/kernel/head64.c
---
linux-2.6.21-rc5-mm3-vanilla/arch/x86_64/kernel/head64.c~x86_64-check-for-config-physical-start-aligned-2M
2007-04-02 20:46:43.0 +0530
+++ linux-2.6.21-rc5-mm3-vanilla-root/arch/x86_64/kernel/head64.c
2007-04-02 21:20:45.0 +0530
@@ -62,6 +62,14 @@ void __init x86_64_start_kernel(char * r
{
int i;
+ /*
+ * Make sure kernel is aligned to 2MB address. Catching it at compile
+ * time is better. Change your config file and compile the kernel
+ * for a 2MB aligned address (CONFIG_PHYSICAL_START)
+ */
+ BUILD_BUG_ON(ALIGN(CONFIG_PHYSICAL_START, __KERNEL_ALIGN)
+ != CONFIG_PHYSICAL_START);
+
/* clear bss before set_intr_gate with early_idt_handler */
clear_bss();
diff -puN
include/asm-x86_64/page.h~x86_64-check-for-config-physical-start-aligned-2M
include/asm-x86_64/page.h
---
linux-2.6.21-rc5-mm3-vanilla/include/asm-x86_64/page.h~x86_64-check-for-config-physical-start-aligned-2M
2007-04-02 20:50:55.0 +0530
+++ linux-2.6.21-rc5-mm3-vanilla-root/include/asm-x86_64/page.h
2007-04-02 20:51:34.0 +0530
@@ -79,6 +79,7 @@ extern unsigned long phys_base;
#endif /* !__ASSEMBLY__ */
#define __PHYSICAL_START CONFIG_PHYSICAL_START
+#define __KERNEL_ALIGN 0x20
#define __START_KERNEL (__START_KERNEL_map + __PHYSICAL_START)
#define __START_KERNEL_map 0x8000
#define __PAGE_OFFSET 0x8100
_
I'm only a user, so I'm not uptodate on these addresses and how they
work. However, how does this solve the problem that running
make oldconfig
on a working 2.6.21-rc3-mm2 .config gives an unbootable 2.6.21-rc5-mm3
kernel? If I read things correctly, you now get a BUG, but the kernel
still won't boot. If that is correct, than I, as a user, don't think
that this is the solution that I feel comfortable with.
If the kernel only boots CONFIG_PHYSICAL_START is aligned on a 2MB
address, then we should align it, not BUG out when it's not, and
especially not when it's unaligned through no fault of the user.
Kind regards,
Jurriaan
--
Debian (Unstable) GNU/Linux 2.6.21-rc5-mm3 2x2010 bogomips load 0.89
the Jack Vance Integral Edition: http://www.integralarchive.org
-
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 FAQ at http://www.tux.org/lkml/
Re: 2.6.21-rc5-mm3 - no boot, address not 2M aligned
From: Vivek Goyal [EMAIL PROTECTED] Date: Mon, Apr 02, 2007 at 05:06:39PM +0530 On Mon, Apr 02, 2007 at 01:17:45PM +0200, [EMAIL PROTECTED] wrote: [..] + /* + * Make sure kernel is aligned to 2MB address. Catching it at compile + * time is better. Change your config file and compile the kernel + * for a 2MB aligned address (CONFIG_PHYSICAL_START) + */ + BUILD_BUG_ON(ALIGN(CONFIG_PHYSICAL_START, __KERNEL_ALIGN) + != CONFIG_PHYSICAL_START); + /* clear bss before set_intr_gate with early_idt_handler */ clear_bss(); diff -puN include/asm-x86_64/page.h~x86_64-check-for-config-physical-start-aligned-2M include/asm-x86_64/page.h --- linux-2.6.21-rc5-mm3-vanilla/include/asm-x86_64/page.h~x86_64-check-for-config-physical-start-aligned-2M 2007-04-02 20:50:55.0 +0530 +++ linux-2.6.21-rc5-mm3-vanilla-root/include/asm-x86_64/page.h 2007-04-02 20:51:34.0 +0530 @@ -79,6 +79,7 @@ extern unsigned long phys_base; #endif /* !__ASSEMBLY__ */ #define __PHYSICAL_START CONFIG_PHYSICAL_START +#define __KERNEL_ALIGN 0x20 #define __START_KERNEL (__START_KERNEL_map + __PHYSICAL_START) #define __START_KERNEL_map 0x8000 #define __PAGE_OFFSET 0x8100 _ You will get a compile time error and your compilation will not be through if your physical address is not 2MB aligned. Just give it a try. Just gave it a try, but I'm not convinced yet :-) I used a working 2.6.21-rc3-mm2 tree, patched it up to 2.6.21-rc5-mm3 and applied your patch. I ended up with the .config later in this email, and got this error: CC arch/x86_64/kernel/head64.o arch/x86_64/kernel/head64.c: In function 'x86_64_start_kernel': arch/x86_64/kernel/head64.c:70: error: size of array 'type name' is negative make[1]: *** [arch/x86_64/kernel/head64.o] Error 1 make: *** [arch/x86_64/kernel] Error 2 After reverting your patch, the build didn't fail, but of course the kernel won't build. Good luck, Jurriaan # # Automatically generated make config: don't edit # Linux kernel version: 2.6.21-rc5-mm3 # Mon Apr 2 16:38:50 2007 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_ZONE_DMA32=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_DMI=y CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION= CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SWAP_PREFETCH=y CONFIG_SYSVIPC=y # CONFIG_IPC_NS is not set CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set # CONFIG_TASKSTATS is not set # CONFIG_UTS_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_CPUSETS is not set CONFIG_SYSFS_DEPRECATED=y # CONFIG_RELAY is not set # CONFIG_BLK_DEV_INITRD is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_EMBEDDED=y # CONFIG_SYSCTL_SYSCALL is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y # CONFIG_VM_EVENT_COUNTERS is not set CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set CONFIG_PAGE_GROUP_BY_MOBILITY=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y # # Process debugging support # CONFIG_UTRACE=y CONFIG_PTRACE=y # # Block layer # CONFIG_BLOCK=y # CONFIG_BLK_DEV_IO_TRACE is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y # CONFIG_IOSCHED_DEADLINE is not set # CONFIG_IOSCHED_CFQ is not set CONFIG_DEFAULT_AS=y # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED=anticipatory # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_VSMP is not set CONFIG_MK8=y # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_INTERNODE_CACHE_BYTES=64 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y # CONFIG_MICROCODE is not set CONFIG_X86_MSR=y
Re: 2.6.21-rc5-mm3 - no boot, address not 2M aligned
From: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Mon, Apr 02, 2007 at 04:49:14PM +0200 I used a working 2.6.21-rc3-mm2 tree, patched it up to 2.6.21-rc5-mm3 and applied your patch. I ended up with the .config later in this email, and got this error: CC arch/x86_64/kernel/head64.o arch/x86_64/kernel/head64.c: In function 'x86_64_start_kernel': arch/x86_64/kernel/head64.c:70: error: size of array 'type name' is negative make[1]: *** [arch/x86_64/kernel/head64.o] Error 1 make: *** [arch/x86_64/kernel] Error 2 After reverting your patch, the build didn't fail, but of course the kernel won't build. That should, of course, read 'kernel won't boot'. Sorry, Jurriaan -- Debian (Unstable) GNU/Linux 2.6.21-rc5-mm3 2x4826 bogomips load 0.92 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: 2.6.21-rc5-mm3 - no boot, "address not 2M aligned"
From: Andrew Morton <[EMAIL PROTECTED]> Date: Sat, Mar 31, 2007 at 12:53:03AM -0700 > On Sat, 31 Mar 2007 09:12:20 +0200 Helge Hafting <[EMAIL PROTECTED]> wrote: > > > A new error for me: > > > > loading 2.6.21rc5mm3 > > Bios data check successful > > Destination address not 2M aligned > > -- System halted > > > > > > This is using the same lilo that loads 2.6.18rc5mm1 fine. > > x86-64 > > > > That's new. Does changing the value of CONFIG_RELOCATABLE change anything? > > Please send the .config. > I had the same with this .config from 2.6.21-rc3-mm2 after running 'make oldconfig' and answering N to all new questions. Then, I tweaked some items, mostly to see if there was an 'align kernel' item in there somewhere. Diff between _working_ 2.6.21-rc5-mm3 .config and this 2.6.21-rc3-mm2 .config at the end. Somehow that seems to have adapted 'CONFIG_PHYSICAL_START', maybe that's it? # # Automatically generated make config: don't edit # Linux kernel version: 2.6.21-rc3-mm2 # Tue Mar 13 18:35:46 2007 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_ZONE_DMA32=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_DMI=y CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SWAP_PREFETCH=y CONFIG_SYSVIPC=y # CONFIG_IPC_NS is not set CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set # CONFIG_TASKSTATS is not set # CONFIG_UTS_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_CPUSETS is not set CONFIG_SYSFS_DEPRECATED=y # CONFIG_RELAY is not set # CONFIG_BLK_DEV_INITRD is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_EMBEDDED=y # CONFIG_SYSCTL_SYSCALL is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y # CONFIG_VM_EVENT_COUNTERS is not set CONFIG_CLASSIC_RCU=y # CONFIG_PREEMPT_RCU is not set # CONFIG_RCU_TRACE is not set CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set CONFIG_PAGE_GROUP_BY_MOBILITY=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y # # Process debugging support # CONFIG_UTRACE=y CONFIG_PTRACE=y # # Block layer # CONFIG_BLOCK=y # CONFIG_BLK_DEV_IO_TRACE is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y # CONFIG_IOSCHED_DEADLINE is not set # CONFIG_IOSCHED_CFQ is not set CONFIG_DEFAULT_AS=y # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="anticipatory" # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_VSMP is not set CONFIG_MK8=y # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_INTERNODE_CACHE_BYTES=64 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y # CONFIG_MICROCODE is not set CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_MTRR=y CONFIG_SMP=y # CONFIG_SCHED_SMT is not set CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set CONFIG_PREEMPT_BKL=y # CONFIG_NUMA is not set CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y # CONFIG_SPARSEMEM_STATIC is not set CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_RESOURCES_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_ADAPTIVE_READAHEAD=y CONFIG_NR_CPUS=2 # CONFIG_HOTPLUG_CPU is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_IOMMU=y # CONFIG_CALGARY_IOMMU is not set CONFIG_SWIOTLB=y CONFIG_X86_MCE=y # CONFIG_X86_MCE_INTEL is not set CONFIG_X86_MCE_AMD=y # CONFIG_KEXEC is not set # CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x10 CONFIG_SECCOMP=y # CONFIG_CC_STACKPROTECTOR is not set # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set #
Re: 2.6.21-rc5-mm3 - no boot, address not 2M aligned
From: Andrew Morton [EMAIL PROTECTED] Date: Sat, Mar 31, 2007 at 12:53:03AM -0700 On Sat, 31 Mar 2007 09:12:20 +0200 Helge Hafting [EMAIL PROTECTED] wrote: A new error for me: loading 2.6.21rc5mm3 Bios data check successful Destination address not 2M aligned -- System halted This is using the same lilo that loads 2.6.18rc5mm1 fine. x86-64 That's new. Does changing the value of CONFIG_RELOCATABLE change anything? Please send the .config. I had the same with this .config from 2.6.21-rc3-mm2 after running 'make oldconfig' and answering N to all new questions. Then, I tweaked some items, mostly to see if there was an 'align kernel' item in there somewhere. Diff between _working_ 2.6.21-rc5-mm3 .config and this 2.6.21-rc3-mm2 .config at the end. Somehow that seems to have adapted 'CONFIG_PHYSICAL_START', maybe that's it? # # Automatically generated make config: don't edit # Linux kernel version: 2.6.21-rc3-mm2 # Tue Mar 13 18:35:46 2007 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_ZONE_DMA32=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_DMI=y CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION= CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SWAP_PREFETCH=y CONFIG_SYSVIPC=y # CONFIG_IPC_NS is not set CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set # CONFIG_TASKSTATS is not set # CONFIG_UTS_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_CPUSETS is not set CONFIG_SYSFS_DEPRECATED=y # CONFIG_RELAY is not set # CONFIG_BLK_DEV_INITRD is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_EMBEDDED=y # CONFIG_SYSCTL_SYSCALL is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y # CONFIG_VM_EVENT_COUNTERS is not set CONFIG_CLASSIC_RCU=y # CONFIG_PREEMPT_RCU is not set # CONFIG_RCU_TRACE is not set CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set CONFIG_PAGE_GROUP_BY_MOBILITY=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y # # Process debugging support # CONFIG_UTRACE=y CONFIG_PTRACE=y # # Block layer # CONFIG_BLOCK=y # CONFIG_BLK_DEV_IO_TRACE is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y # CONFIG_IOSCHED_DEADLINE is not set # CONFIG_IOSCHED_CFQ is not set CONFIG_DEFAULT_AS=y # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED=anticipatory # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_VSMP is not set CONFIG_MK8=y # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_INTERNODE_CACHE_BYTES=64 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y # CONFIG_MICROCODE is not set CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_MTRR=y CONFIG_SMP=y # CONFIG_SCHED_SMT is not set CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set CONFIG_PREEMPT_BKL=y # CONFIG_NUMA is not set CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y # CONFIG_SPARSEMEM_STATIC is not set CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_RESOURCES_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_ADAPTIVE_READAHEAD=y CONFIG_NR_CPUS=2 # CONFIG_HOTPLUG_CPU is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_IOMMU=y # CONFIG_CALGARY_IOMMU is not set CONFIG_SWIOTLB=y CONFIG_X86_MCE=y # CONFIG_X86_MCE_INTEL is not set CONFIG_X86_MCE_AMD=y # CONFIG_KEXEC is not set # CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x10 CONFIG_SECCOMP=y # CONFIG_CC_STACKPROTECTOR is not set # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set
2.6.20-rc6-mm1: linker error with arch_setup_additional_pages
From: Andrew Morton <[EMAIL PROTECTED]> Date: Sat, Jan 27, 2007 at 11:49:28PM -0800 > LD init/built-in.o LD .tmp_vmlinux1 fs/built-in.o: In function `load_elf_binary': fs/binfmt_elf.c:978: undefined reference to `arch_setup_additional_pages' make: *** [.tmp_vmlinux1] Error 1 # # Automatically generated make config: don't edit # Linux kernel version: 2.6.20-rc6-mm1 # Sun Jan 28 14:44:26 2007 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_ZONE_DMA32=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_DMI=y CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SWAP_PREFETCH=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set # CONFIG_TASKSTATS is not set # CONFIG_USER_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_CPUSETS is not set CONFIG_SYSFS_DEPRECATED=y # CONFIG_RELAY is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_EMBEDDED=y # CONFIG_SYSCTL_SYSCALL is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y # CONFIG_VM_EVENT_COUNTERS is not set CONFIG_CLASSIC_RCU=y # CONFIG_PREEMPT_RCU is not set # CONFIG_RCU_TRACE is not set CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y # # Block layer # CONFIG_BLOCK=y # CONFIG_BLK_DEV_IO_TRACE is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y # CONFIG_IOSCHED_DEADLINE is not set # CONFIG_IOSCHED_CFQ is not set CONFIG_DEFAULT_AS=y # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="anticipatory" # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_VSMP is not set CONFIG_MK8=y # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_INTERNODE_CACHE_BYTES=64 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y # CONFIG_MICROCODE is not set CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_MTRR=y CONFIG_SMP=y # CONFIG_SCHED_SMT is not set CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set CONFIG_PREEMPT_BKL=y # CONFIG_NUMA is not set CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y # CONFIG_SPARSEMEM_STATIC is not set CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_RESOURCES_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_ADAPTIVE_READAHEAD=y CONFIG_ARCH_HAS_SETUP_ADDITIONAL_PAGES=y CONFIG_NR_CPUS=2 # CONFIG_HOTPLUG_CPU is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_IOMMU=y # CONFIG_CALGARY_IOMMU is not set CONFIG_SWIOTLB=y CONFIG_X86_MCE=y # CONFIG_X86_MCE_INTEL is not set CONFIG_X86_MCE_AMD=y # CONFIG_KEXEC is not set # CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x10 CONFIG_SECCOMP=y # CONFIG_CC_STACKPROTECTOR is not set # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set CONFIG_HZ_1000=y CONFIG_HZ=1000 CONFIG_REORDER=y CONFIG_K8_NB=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_ISA_DMA_API=y CONFIG_GENERIC_PENDING_IRQ=y # # Power management options # CONFIG_PM=y # CONFIG_PM_LEGACY is not set # CONFIG_PM_DEBUG is not set # CONFIG_PM_SYSFS_DEPRECATED is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_AC=y # CONFIG_ACPI_BATTERY is not set CONFIG_ACPI_BUTTON=y # CONFIG_ACPI_VIDEO is not set # CONFIG_ACPI_HOTKEY is not set CONFIG_ACPI_FAN=y # CONFIG_ACPI_DOCK is not set CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_IBM is not set # CONFIG_ACPI_TOSHIBA is not set # CONFIG_ACPI_SONY is not set
2.6.20-rc6-mm1: linker error with arch_setup_additional_pages
From: Andrew Morton [EMAIL PROTECTED] Date: Sat, Jan 27, 2007 at 11:49:28PM -0800 LD init/built-in.o LD .tmp_vmlinux1 fs/built-in.o: In function `load_elf_binary': fs/binfmt_elf.c:978: undefined reference to `arch_setup_additional_pages' make: *** [.tmp_vmlinux1] Error 1 # # Automatically generated make config: don't edit # Linux kernel version: 2.6.20-rc6-mm1 # Sun Jan 28 14:44:26 2007 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_ZONE_DMA32=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_DMI=y CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION= CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SWAP_PREFETCH=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set # CONFIG_TASKSTATS is not set # CONFIG_USER_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_CPUSETS is not set CONFIG_SYSFS_DEPRECATED=y # CONFIG_RELAY is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_EMBEDDED=y # CONFIG_SYSCTL_SYSCALL is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y # CONFIG_VM_EVENT_COUNTERS is not set CONFIG_CLASSIC_RCU=y # CONFIG_PREEMPT_RCU is not set # CONFIG_RCU_TRACE is not set CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y # # Block layer # CONFIG_BLOCK=y # CONFIG_BLK_DEV_IO_TRACE is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y # CONFIG_IOSCHED_DEADLINE is not set # CONFIG_IOSCHED_CFQ is not set CONFIG_DEFAULT_AS=y # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED=anticipatory # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_VSMP is not set CONFIG_MK8=y # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_INTERNODE_CACHE_BYTES=64 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y # CONFIG_MICROCODE is not set CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_MTRR=y CONFIG_SMP=y # CONFIG_SCHED_SMT is not set CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set CONFIG_PREEMPT_BKL=y # CONFIG_NUMA is not set CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y # CONFIG_SPARSEMEM_STATIC is not set CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_RESOURCES_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_ADAPTIVE_READAHEAD=y CONFIG_ARCH_HAS_SETUP_ADDITIONAL_PAGES=y CONFIG_NR_CPUS=2 # CONFIG_HOTPLUG_CPU is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_IOMMU=y # CONFIG_CALGARY_IOMMU is not set CONFIG_SWIOTLB=y CONFIG_X86_MCE=y # CONFIG_X86_MCE_INTEL is not set CONFIG_X86_MCE_AMD=y # CONFIG_KEXEC is not set # CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x10 CONFIG_SECCOMP=y # CONFIG_CC_STACKPROTECTOR is not set # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set CONFIG_HZ_1000=y CONFIG_HZ=1000 CONFIG_REORDER=y CONFIG_K8_NB=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_ISA_DMA_API=y CONFIG_GENERIC_PENDING_IRQ=y # # Power management options # CONFIG_PM=y # CONFIG_PM_LEGACY is not set # CONFIG_PM_DEBUG is not set # CONFIG_PM_SYSFS_DEPRECATED is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_AC=y # CONFIG_ACPI_BATTERY is not set CONFIG_ACPI_BUTTON=y # CONFIG_ACPI_VIDEO is not set # CONFIG_ACPI_HOTKEY is not set CONFIG_ACPI_FAN=y # CONFIG_ACPI_DOCK is not set CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_IBM is not set # CONFIG_ACPI_TOSHIBA is not set # CONFIG_ACPI_SONY is not set
Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
From: Justin Piszcz <[EMAIL PROTECTED]> Date: Sun, Jan 21, 2007 at 11:48:07AM -0500 > > What about all of the changes with NAT? I see that it operates on > level-3/network wise, I enabled that and backward compatiblity support as > well, but when my iptables rules kick in, it says no such driver/etc for > `nat'-- is there a new target for iptables now or did I miss a kernel > option? > Well, I'm typing this on my laptop, connected via my main server to the internet, using SNAT, according to the firehol manpage. The main server runs 2.6.20-rc5, and somewhere in my 2.6.20-rc5 .config, there is CONFIG_NF_NAT=m CONFIG_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=m CONFIG_IP_NF_TARGET_REDIRECT=m CONFIG_IP_NF_TARGET_NETMAP=m CONFIG_IP_NF_TARGET_SAME=m CONFIG_NF_NAT_SNMP_BASIC=m CONFIG_NF_NAT_PROTO_GRE=m CONFIG_NF_NAT_FTP=m CONFIG_NF_NAT_IRC=m CONFIG_NF_NAT_TFTP=m CONFIG_NF_NAT_AMANDA=m CONFIG_NF_NAT_PPTP=m CONFIG_NF_NAT_H323=m CONFIG_NF_NAT_SIP=m and my firewall's manpage says: FIREHOL.CONF(5) User Contributed Perl Documentation FIREHOL.CONF(5) masquerade [reverse | interface] [optional rule parameters] Masquerading is a special from of SNAT (Source NAT) that changes the source of requests when they go out and replaces their original source when replies come in. This way a Linux box can become an internet router for a LAN of clients having unroutable IP addresses. Masquerading takes care to re-map IP addresses and ports as required. Masquerading is "expensive" compared to SNAT because it checks the IP address of the ougoing interface every time for every packet, and therefore it is suggested that if you connect to the internet with a static IP address, to prefer SNAT. while my /etc/firehol/firehol.conf has a part in it like this: # # route access from the clients to the internet # router internet2network inface adsl outface switch masquerade reverse client all accept All in all, NAT is working for me with 2.6.20-rc5. I do remember I had to reselect all the netfilter modules in menuconfig. Good luck, Jurriaan -- > What does ELF stand for (in respect to Linux?) ELF is the first rock group that Ronnie James Dio performed with back in the early 1970's. In constrast, a.out is a misspelling of the French word for the month of August. What the two have in common is beyond me, but Linux users seem to use the two words together. seen on c.o.l.misc Debian (Unstable) GNU/Linux 2.6.20-rc5 2x2011 bogomips load 0.83 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
From: Justin Piszcz <[EMAIL PROTECTED]> Date: Sat, Jan 20, 2007 at 04:03:42PM -0500 > > > My swap is on, 2GB ram and 2GB of swap on this machine. I can't go back > to 2.6.17.13 as it does not recognize the NICs in my machine correctly and > the Alsa Intel HD Audio driver has bugs etc, I guess I am stuck with > 2.6.19.2 :( > Well, if you can't go back, you could always test 2.6.20-rc5. That's why it's out there :-) It can't be any worse! Good luck, Jurriaan -- It might look like I'm doing nothing, but at the cellular level I'm really quite busy. Hans Haas Debian (Unstable) GNU/Linux 2.6.20-rc5 2x2011 bogomips load 1.97 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
From: Justin Piszcz [EMAIL PROTECTED] Date: Sat, Jan 20, 2007 at 04:03:42PM -0500 My swap is on, 2GB ram and 2GB of swap on this machine. I can't go back to 2.6.17.13 as it does not recognize the NICs in my machine correctly and the Alsa Intel HD Audio driver has bugs etc, I guess I am stuck with 2.6.19.2 :( Well, if you can't go back, you could always test 2.6.20-rc5. That's why it's out there :-) It can't be any worse! Good luck, Jurriaan -- It might look like I'm doing nothing, but at the cellular level I'm really quite busy. Hans Haas Debian (Unstable) GNU/Linux 2.6.20-rc5 2x2011 bogomips load 1.97 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
From: Justin Piszcz [EMAIL PROTECTED] Date: Sun, Jan 21, 2007 at 11:48:07AM -0500 What about all of the changes with NAT? I see that it operates on level-3/network wise, I enabled that and backward compatiblity support as well, but when my iptables rules kick in, it says no such driver/etc for `nat'-- is there a new target for iptables now or did I miss a kernel option? Well, I'm typing this on my laptop, connected via my main server to the internet, using SNAT, according to the firehol manpage. The main server runs 2.6.20-rc5, and somewhere in my 2.6.20-rc5 .config, there is CONFIG_NF_NAT=m CONFIG_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=m CONFIG_IP_NF_TARGET_REDIRECT=m CONFIG_IP_NF_TARGET_NETMAP=m CONFIG_IP_NF_TARGET_SAME=m CONFIG_NF_NAT_SNMP_BASIC=m CONFIG_NF_NAT_PROTO_GRE=m CONFIG_NF_NAT_FTP=m CONFIG_NF_NAT_IRC=m CONFIG_NF_NAT_TFTP=m CONFIG_NF_NAT_AMANDA=m CONFIG_NF_NAT_PPTP=m CONFIG_NF_NAT_H323=m CONFIG_NF_NAT_SIP=m and my firewall's manpage says: FIREHOL.CONF(5) User Contributed Perl Documentation FIREHOL.CONF(5) masquerade [reverse | interface] [optional rule parameters] Masquerading is a special from of SNAT (Source NAT) that changes the source of requests when they go out and replaces their original source when replies come in. This way a Linux box can become an internet router for a LAN of clients having unroutable IP addresses. Masquerading takes care to re-map IP addresses and ports as required. Masquerading is expensive compared to SNAT because it checks the IP address of the ougoing interface every time for every packet, and therefore it is suggested that if you connect to the internet with a static IP address, to prefer SNAT. while my /etc/firehol/firehol.conf has a part in it like this: # # route access from the clients to the internet # router internet2network inface adsl outface switch masquerade reverse client all accept All in all, NAT is working for me with 2.6.20-rc5. I do remember I had to reselect all the netfilter modules in menuconfig. Good luck, Jurriaan -- What does ELF stand for (in respect to Linux?) ELF is the first rock group that Ronnie James Dio performed with back in the early 1970's. In constrast, a.out is a misspelling of the French word for the month of August. What the two have in common is beyond me, but Linux users seem to use the two words together. seen on c.o.l.misc Debian (Unstable) GNU/Linux 2.6.20-rc5 2x2011 bogomips load 0.83 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: sata badness in 2.6.20-rc1? [Was: Re: md patches in -mm]
From: Andrew Morton <[EMAIL PROTECTED]> Date: Sun, Dec 17, 2006 at 03:05:39AM -0800 > On Sun, 17 Dec 2006 12:00:12 +0100 > "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote: > > > Okay, I have identified the patch that causes the problem to appear, which > > is > > > > fix-sense-key-medium-error-processing-and-retry.patch > > > > With this patch reverted -rc1-mm1 is happily running on my test box. > > That was rather unexpected. Thanks. > I can confirm that 2.6.20-rc1-mm1 with this patch reverted mounts my raid6 partition without problems. This is x86_64 with SMP. Kind regards, Jurriaan -- HORROR FILM WISDOM: 9. If your car runs out of gas at night, do not go to the nearby deserted-looking house to phone for help. Debian (Unstable) GNU/Linux 2.6.20-rc1 2x2011 bogomips load 7.42 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: sata badness in 2.6.20-rc1? [Was: Re: md patches in -mm]
From: Andrew Morton [EMAIL PROTECTED] Date: Sun, Dec 17, 2006 at 03:05:39AM -0800 On Sun, 17 Dec 2006 12:00:12 +0100 Rafael J. Wysocki [EMAIL PROTECTED] wrote: Okay, I have identified the patch that causes the problem to appear, which is fix-sense-key-medium-error-processing-and-retry.patch With this patch reverted -rc1-mm1 is happily running on my test box. That was rather unexpected. Thanks. I can confirm that 2.6.20-rc1-mm1 with this patch reverted mounts my raid6 partition without problems. This is x86_64 with SMP. Kind regards, Jurriaan -- HORROR FILM WISDOM: 9. If your car runs out of gas at night, do not go to the nearby deserted-looking house to phone for help. Debian (Unstable) GNU/Linux 2.6.20-rc1 2x2011 bogomips load 7.42 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: sata badness in 2.6.20-rc1? [Was: Re: md patches in -mm]
From: Jeff Garzik <[EMAIL PROTECTED]> Date: Fri, Dec 15, 2006 at 04:48:44PM -0500 > The "Re: Linux 2.6.20-rc1" sub-thread that had Jens and Alistair John > Strachan replying seemed to implicate some core block layer badness. > The original problem (not mounting my raid6 partition) is observable in 2.6.20-rc1-mm1, but not in 2.6.20-rc1; ie. 2.6.20-rc1 is good for me. Linux version 2.6.20-rc1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #3 SMP Fri Dec 15 21:19:54 CET 2006 md: Autodetecting RAID arrays. md: autorun ... md: considering sdh1 ... md: adding sdh1 ... md: adding sdg1 ... md: adding sdf1 ... md: adding sde1 ... md: adding sdd1 ... md: adding sdc1 ... md: adding sdb1 ... md: adding sda1 ... md: hdc9 has different UUID to sdh1 md: hdc8 has different UUID to sdh1 md: hdc7 has different UUID to sdh1 md: hdc6 has different UUID to sdh1 md: hdc5 has different UUID to sdh1 md: hda9 has different UUID to sdh1 md: hda8 has different UUID to sdh1 md: hda7 has different UUID to sdh1 md: hda6 has different UUID to sdh1 md: hda5 has different UUID to sdh1 md: created md0 md: bind md: bind md: bind md: bind md: bind md: bind md: bind md: bind md: running: raid5: device sdh1 operational as raid disk 1 raid5: device sdg1 operational as raid disk 0 raid5: device sdf1 operational as raid disk 5 raid5: device sde1 operational as raid disk 6 raid5: device sdd1 operational as raid disk 7 raid5: device sdc1 operational as raid disk 3 raid5: device sdb1 operational as raid disk 2 raid5: device sda1 operational as raid disk 4 raid5: allocated 8462kB for md0 raid5: raid level 6 set md0 active with 8 out of 8 devices, algorithm 2 RAID5 conf printout: --- rd:8 wd:8 disk 0, o:1, dev:sdg1 disk 1, o:1, dev:sdh1 disk 2, o:1, dev:sdb1 disk 3, o:1, dev:sdc1 disk 4, o:1, dev:sda1 disk 5, o:1, dev:sdf1 disk 6, o:1, dev:sde1 disk 7, o:1, dev:sdd1 md0: bitmap initialized from disk: read 15/15 pages, set 1 bits, status: 0 created bitmap (233 pages) for device md0 md: considering hdc9 ... md: adding hdc9 ... md: hdc8 has different UUID to hdc9 md: hdc7 has different UUID to hdc9 md: hdc6 has different UUID to hdc9 md: hdc5 has different UUID to hdc9 md: adding hda9 ... md: hda8 has different UUID to hdc9 md: hda7 has different UUID to hdc9 md: hda6 has different UUID to hdc9 md: hda5 has different UUID to hdc9 md: created md4 md: bind md: bind md: running: raid1: raid set md4 active with 2 out of 2 mirrors md4: bitmap initialized from disk: read 10/10 pages, set 45 bits, status: 0 EXT3 FS on md0, internal journal EXT3-fs: mounted filesystem with ordered data mode. Jurriaan -- And I thought that the Borg were bad... Debian (Unstable) GNU/Linux 2.6.20-rc1 2x4023 bogomips load 5.55 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: sata badness in 2.6.20-rc1? [Was: Re: md patches in -mm]
From: Jeff Garzik [EMAIL PROTECTED] Date: Fri, Dec 15, 2006 at 04:48:44PM -0500 The Re: Linux 2.6.20-rc1 sub-thread that had Jens and Alistair John Strachan replying seemed to implicate some core block layer badness. The original problem (not mounting my raid6 partition) is observable in 2.6.20-rc1-mm1, but not in 2.6.20-rc1; ie. 2.6.20-rc1 is good for me. Linux version 2.6.20-rc1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #3 SMP Fri Dec 15 21:19:54 CET 2006 snip md: Autodetecting RAID arrays. md: autorun ... md: considering sdh1 ... md: adding sdh1 ... md: adding sdg1 ... md: adding sdf1 ... md: adding sde1 ... md: adding sdd1 ... md: adding sdc1 ... md: adding sdb1 ... md: adding sda1 ... md: hdc9 has different UUID to sdh1 md: hdc8 has different UUID to sdh1 md: hdc7 has different UUID to sdh1 md: hdc6 has different UUID to sdh1 md: hdc5 has different UUID to sdh1 md: hda9 has different UUID to sdh1 md: hda8 has different UUID to sdh1 md: hda7 has different UUID to sdh1 md: hda6 has different UUID to sdh1 md: hda5 has different UUID to sdh1 md: created md0 md: bindsda1 md: bindsdb1 md: bindsdc1 md: bindsdd1 md: bindsde1 md: bindsdf1 md: bindsdg1 md: bindsdh1 md: running: sdh1sdg1sdf1sde1sdd1sdc1sdb1sda1 raid5: device sdh1 operational as raid disk 1 raid5: device sdg1 operational as raid disk 0 raid5: device sdf1 operational as raid disk 5 raid5: device sde1 operational as raid disk 6 raid5: device sdd1 operational as raid disk 7 raid5: device sdc1 operational as raid disk 3 raid5: device sdb1 operational as raid disk 2 raid5: device sda1 operational as raid disk 4 raid5: allocated 8462kB for md0 raid5: raid level 6 set md0 active with 8 out of 8 devices, algorithm 2 RAID5 conf printout: --- rd:8 wd:8 disk 0, o:1, dev:sdg1 disk 1, o:1, dev:sdh1 disk 2, o:1, dev:sdb1 disk 3, o:1, dev:sdc1 disk 4, o:1, dev:sda1 disk 5, o:1, dev:sdf1 disk 6, o:1, dev:sde1 disk 7, o:1, dev:sdd1 md0: bitmap initialized from disk: read 15/15 pages, set 1 bits, status: 0 created bitmap (233 pages) for device md0 md: considering hdc9 ... md: adding hdc9 ... md: hdc8 has different UUID to hdc9 md: hdc7 has different UUID to hdc9 md: hdc6 has different UUID to hdc9 md: hdc5 has different UUID to hdc9 md: adding hda9 ... md: hda8 has different UUID to hdc9 md: hda7 has different UUID to hdc9 md: hda6 has different UUID to hdc9 md: hda5 has different UUID to hdc9 md: created md4 md: bindhda9 md: bindhdc9 md: running: hdc9hda9 raid1: raid set md4 active with 2 out of 2 mirrors md4: bitmap initialized from disk: read 10/10 pages, set 45 bits, status: 0 snip EXT3 FS on md0, internal journal EXT3-fs: mounted filesystem with ordered data mode. Jurriaan -- And I thought that the Borg were bad... Debian (Unstable) GNU/Linux 2.6.20-rc1 2x4023 bogomips load 5.55 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options
From: Theodore Tso <[EMAIL PROTECTED]> Date: Thu, Dec 14, 2006 at 10:17:45AM -0500 > > Remove an (incorrect) assertion that NOHIGHMEM is right for more > users, since most systems are coming with at least 1G of memory these > days, and even some laptops have up 4G of memory. Given this (on a system with 1G of memory, this option shouldn't be used) > If you are compiling a kernel which will never run on a machine with > - more than 1 Gigabyte total physical RAM, answer "off" here (default > - choice and suitable for most users). This will result in a "3GB/1GB" > - split: 3GB are mapped so that each process sees a 3GB virtual memory > - space and the remaining part of the 4GB virtual memory space is used > - by the kernel to permanently map as much physical memory as > - possible. > + more than 1 Gigabyte total physical RAM, answer "off" here. wouldn't + 1 Gigabyte or more total physical RAM, answer "off" here. make clearer that even with 1G memory, you shouldn't use this option? Since 1G is quite common, we should, IMHO, be clear about that case. Kind regards, Jurriaan -- They also played a refreshing rendition of Justin's solo material, Twilight Home and Ocean Rising, with Michael Dean wailing in the back while going ballistic on the Djembe. Pax Eternum on a NMA concert at Que Sera, Long Beach, in 2004 Debian (Unstable) GNU/Linux 2.6.19-rc5-mm1 2x4826 bogomips load 1.13 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options
From: Theodore Tso [EMAIL PROTECTED] Date: Thu, Dec 14, 2006 at 10:17:45AM -0500 Remove an (incorrect) assertion that NOHIGHMEM is right for more users, since most systems are coming with at least 1G of memory these days, and even some laptops have up 4G of memory. Given this (on a system with 1G of memory, this option shouldn't be used) If you are compiling a kernel which will never run on a machine with - more than 1 Gigabyte total physical RAM, answer off here (default - choice and suitable for most users). This will result in a 3GB/1GB - split: 3GB are mapped so that each process sees a 3GB virtual memory - space and the remaining part of the 4GB virtual memory space is used - by the kernel to permanently map as much physical memory as - possible. + more than 1 Gigabyte total physical RAM, answer off here. wouldn't + 1 Gigabyte or more total physical RAM, answer off here. make clearer that even with 1G memory, you shouldn't use this option? Since 1G is quite common, we should, IMHO, be clear about that case. Kind regards, Jurriaan -- They also played a refreshing rendition of Justin's solo material, Twilight Home and Ocean Rising, with Michael Dean wailing in the back while going ballistic on the Djembe. Pax Eternum on a NMA concert at Que Sera, Long Beach, in 2004 Debian (Unstable) GNU/Linux 2.6.19-rc5-mm1 2x4826 bogomips load 1.13 the Jack Vance Integral Edition: http://www.integralarchive.org - 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 FAQ at http://www.tux.org/lkml/
Re: PCI bridge setup error in linux-2.4.x (anyone of them)
On Fri, Jun 29, 2001 at 09:00:01PM +0200, Martin Dalecki wrote: > I ahve a PC box at hand, which ist containing 8 PCI slots. > Four of them are sitting behind a PCI bridge. > The error in the new kernel series is that during the > PCI bus setup if a card is sitting behind the bridge, it > will be miracelously detected TWICE. Once in front of the > bridge and once behind the bridge. The initialisation of > the card will then be entierly hossed. > > This00:02.0 PCI bridge: Intel Corporation 80960RP [i960 RP > Microprocessor/Bridge] (rev 03) > 00:02.1 I2O: Intel Corporation 80960RP [i960RP Microprocessor] (rev 03) > 00:03.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 02) > > 00:06.0 System peripheral: Hewlett-Packard Company NetServer Smart IRQ > Router (rev a0) > 00:08.0 VGA compatible controller: Cirrus Logic GD 5446 (rev 45) > 00:0f.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02) > 00:0f.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) > 00:0f.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) > 00:0f.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02) > 00:10.0 Host bridge: Intel Corporation 450NX - 82451NX Memory & I/O > Controller (rev 03) > 00:12.0 Host bridge: Intel Corporation 450NX - 82454NX PCI Expander > Bridge (rev 02) > 02:04.0 Ethernet controller: 3Com Corporation 3c905C-TX [Fast Etherlink] > (rev 74) > oops:~ # > doesn't happen under linux-2.2.x kernel series. > I have an ITI-4280UE multifunction card (two Symbios Logic 875's and a DEC21140 fast ethernet) which also has such a bridge (rev 02, even) and have noticed nothing wrong until 2.4.5-ac19 (haven't tested further). Jurriaan -- ... thy successors will not thank thee for it, but rather shall revile thy works and curse thy name, and word of this might get to thy next employer. Henry Spencer - The Ten Commandments for C programmers (Annotated Ed.) GNU/Linux 2.4.5-ac19 SMP/ReiserFS 2x1402 bogomips load av: 0.00 0.01 0.05 - 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 FAQ at http://www.tux.org/lkml/
Re: PCI bridge setup error in linux-2.4.x (anyone of them)
On Fri, Jun 29, 2001 at 09:00:01PM +0200, Martin Dalecki wrote: I ahve a PC box at hand, which ist containing 8 PCI slots. Four of them are sitting behind a PCI bridge. The error in the new kernel series is that during the PCI bus setup if a card is sitting behind the bridge, it will be miracelously detected TWICE. Once in front of the bridge and once behind the bridge. The initialisation of the card will then be entierly hossed. This00:02.0 PCI bridge: Intel Corporation 80960RP [i960 RP Microprocessor/Bridge] (rev 03) 00:02.1 I2O: Intel Corporation 80960RP [i960RP Microprocessor] (rev 03) 00:03.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 02) 00:06.0 System peripheral: Hewlett-Packard Company NetServer Smart IRQ Router (rev a0) 00:08.0 VGA compatible controller: Cirrus Logic GD 5446 (rev 45) 00:0f.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02) 00:0f.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) 00:0f.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) 00:0f.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02) 00:10.0 Host bridge: Intel Corporation 450NX - 82451NX Memory I/O Controller (rev 03) 00:12.0 Host bridge: Intel Corporation 450NX - 82454NX PCI Expander Bridge (rev 02) 02:04.0 Ethernet controller: 3Com Corporation 3c905C-TX [Fast Etherlink] (rev 74) oops:~ # doesn't happen under linux-2.2.x kernel series. I have an ITI-4280UE multifunction card (two Symbios Logic 875's and a DEC21140 fast ethernet) which also has such a bridge (rev 02, even) and have noticed nothing wrong until 2.4.5-ac19 (haven't tested further). Jurriaan -- ... thy successors will not thank thee for it, but rather shall revile thy works and curse thy name, and word of this might get to thy next employer. Henry Spencer - The Ten Commandments for C programmers (Annotated Ed.) GNU/Linux 2.4.5-ac19 SMP/ReiserFS 2x1402 bogomips load av: 0.00 0.01 0.05 - 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 FAQ at http://www.tux.org/lkml/
Re: Reg installing a patch on linux
> Hi, > Please tell me how to install a patch on linux kernel. I have > downloaded a patch "kernel-patch-2_2_13-kdb_0_6-2.deb". How to install > this patch? I am using a 2.2.14-12 kernel. Can I install the above > patch. > You seem to ask a lot of questions starting with 'Please tell me how', and so far, all of these could have been answered by looking in the source or searching with google. Might I suggest a slight increase in your amount of trying to find things out yourself before posting it to the list? There's archives of this list, there's google, there's dejanews, all of which you don't seem to use. Good luck, Jurriaan - 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 FAQ at http://www.tux.org/lkml/
Re: Reg installing a patch on linux
Hi, Please tell me how to install a patch on linux kernel. I have downloaded a patch kernel-patch-2_2_13-kdb_0_6-2.deb. How to install this patch? I am using a 2.2.14-12 kernel. Can I install the above patch. You seem to ask a lot of questions starting with 'Please tell me how', and so far, all of these could have been answered by looking in the source or searching with google. Might I suggest a slight increase in your amount of trying to find things out yourself before posting it to the list? There's archives of this list, there's google, there's dejanews, all of which you don't seem to use. Good luck, Jurriaan - 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 FAQ at http://www.tux.org/lkml/
Re: (lkml)Re: spindown [was Re: 2.4.6-pre2, pre3 VM Behavior]
On Sun, Jun 17, 2001 at 12:05:10PM +0200, Mike Galbraith wrote: > > It _juuust_ so happens that I was tinkering... what do you think of > something like the below? (and boy do I ever wonder what a certain > box doing slrn stuff thinks of it.. hint hint;) > I'm sorry to say this box doesn't really think any different of it. Everything that's in the cache before running slrn on a big group seems to stay there the whole time, making my active slrn-process use swap. I applied the patch to 2.4.5-ac15, and this was the result: procs memoryswap io system cpu r b w swpd free buff cache si sobibo incs us sy id 0 1 0 11216 2548 183560 264172 1 4 184 343 123 119 2 6 92 0 0 0 11212 2620 183444 264184 0 0 472 12799 1 2 97 0 0 0 11212 1604 183444 264740 0 0 378 0 130 101 2 1 98 0 1 0 11212 1588 184300 263116 0 0 552 1080 277 360 3 14 83 2 0 2 11212 1692 174052 270536 0 0 1860 0 596 976 9 50 40 2 0 2 11212 1588 166732 274816 0 0 1868 5426 643 1050 8 44 48 0 1 0 11212 1588 163276 276888 0 0 1714 1816 580 972 9 17 74 0 1 0 11212 1848 166280 273688 0 0 514 3952 301 355 3 40 57 1 0 0 11212 1592 164232 273872 0 0 1824 3532 632 1083 11 25 64 2 0 2 11212 1980 167304 268792 0 0 1678 0 550 881 8 51 41 0 1 2 11212 1588 163908 271356 0 0 1344 4896 508 753 7 26 67 1 0 0 11212 1588 160896 272756 0 0 1642 1301 574 929 9 22 69 0 1 0 11212 1592 164936 268632 0 0 756 3594 370 467 6 43 51 2 0 3 11212 1596 164380 266552 0 0 1904 2392 604 1017 10 52 37 1 0 0 11212 1592 164752 265844 0 0 1784 2382 623 1000 10 22 69 0 1 0 11212 1592 168528 262256 0 0 810 4176 364 523 5 43 52 0 1 1 11212 1992 169324 259504 0 0 1686 3068 578 999 11 42 47 0 1 0 11212 1588 170696 256332 0 0 1568 1080 532 894 10 20 70 1 0 0 11212 1592 174876 253036 0 0 598 3600 315 420 4 41 55 0 1 1 11212 2316 171592 253892 0 0 1816 3286 616 1073 7 29 64 0 1 0 11212 1588 170380 253968 0 0 1638 840 540 910 13 29 58 0 1 1 11212 2896 168840 253740 0 0 752 4120 342 458 4 45 51 0 1 0 11216 2012 166392 255560 0 0 1352 2458 549 895 8 14 77 2 0 1 11216 1588 170744 250164 0 0 1504 1260 503 791 7 48 45 0 1 1 11224 1588 170704 249948 0 0 874 4106 516 655 6 10 84 0 1 0 11228 1588 170148 248988 0 0 1442 0 466 772 8 20 73 1 0 0 11228 1592 171784 247456 0 0 860 3598 362 495 7 44 48 0 1 0 11228 1588 171864 246212 0 0 1390 3176 510 840 9 41 50 0 1 2 11232 1992 170344 245832 0 0 1676 1808 539 898 10 45 45 1 0 1 10508 1632 168204 246780 0 946 1508 2804 599 920 9 20 71 0 1 0 9496 2020 168904 244880 0 0 936 3620 417 603 5 35 60 1 0 0 9604 2516 164096 247536 0 0 1700 2214 563 1085 11 33 56 0 1 0 16196 1820 162112 255492 0 2 1384 1596 497 1106 8 53 38 1 0 0 19240 3000 158052 260608 0 0 400 3824 373 388 2 14 84 1 1 1 28756 4508 146032 278104 0 0 1688 2140 612 1502 7 60 33 2 0 0 39432 29100 105668 300912 0 18 2108 1178 645 1825 12 52 36 1 0 0 40668 13024 108568 311748 0 0 1674 4992 623 1017 9 12 79 0 1 0 45324 3484 105072 326432 0 0 1876 3624 619 1090 13 24 63 1 0 0 53648 1564 102740 337688 0 18 950 3646 404 857 5 31 63 2 0 0 53672 1604 103356 335680 0 2962 1436 5864 565 976 10 43 47 1 0 1 54380 1920 103516 334320 0 1086 1826 1626 590 1072 13 45 42 0 1 1 54600 6532 99568 333860 0 1006 242 5948 277 2680 2 39 59 0 1 0 54596 1944 103744 331932 0 0 1854 3644 627 1054 11 16 73 1 0 0 54592 1924 102876 331100 0 950 1956 2612 621 1173 11 41 48 1 0 0 54592 1592 103576 329568 0 0 1548 4860 605 1106 11 36 53 0 1 1 54592 1588 102908 328320 0 452 1808 2522 583 1049 11 51 38 0 1 1 54592 1588 101916 327076 0 866 1816 1260 589 1046 11 49 40 0 1 0 54592 2076 99568 327776 0 414 992 5728 459 1314 7 25 67 0 1 0 54592 1588 103928 323824 0 0 968 3646 403 747 5 33 61 1 0 0 54592 2632 100108 325136 0 402 1856 2468 622 1369 13 44 42 0 1 0 54592 1588 101872 322600 0 392 1056 2834 461 802 6 35 60 1 0 1 55644 1724 102108 322404 0 380 1448 2682 501 1032 9 50 41 1 1 1 57388 1588 103068 322056 0 0 1384 1396 471 780 8 37 56 0 1 1 58500 2048 102024 323020 0 368 876 3932 504
Re: (lkml)Re: spindown [was Re: 2.4.6-pre2, pre3 VM Behavior]
On Sun, Jun 17, 2001 at 12:05:10PM +0200, Mike Galbraith wrote: It _juuust_ so happens that I was tinkering... what do you think of something like the below? (and boy do I ever wonder what a certain box doing slrn stuff thinks of it.. hint hint;) I'm sorry to say this box doesn't really think any different of it. Everything that's in the cache before running slrn on a big group seems to stay there the whole time, making my active slrn-process use swap. I applied the patch to 2.4.5-ac15, and this was the result: procs memoryswap io system cpu r b w swpd free buff cache si sobibo incs us sy id 0 1 0 11216 2548 183560 264172 1 4 184 343 123 119 2 6 92 0 0 0 11212 2620 183444 264184 0 0 472 12799 1 2 97 0 0 0 11212 1604 183444 264740 0 0 378 0 130 101 2 1 98 0 1 0 11212 1588 184300 263116 0 0 552 1080 277 360 3 14 83 2 0 2 11212 1692 174052 270536 0 0 1860 0 596 976 9 50 40 2 0 2 11212 1588 166732 274816 0 0 1868 5426 643 1050 8 44 48 0 1 0 11212 1588 163276 276888 0 0 1714 1816 580 972 9 17 74 0 1 0 11212 1848 166280 273688 0 0 514 3952 301 355 3 40 57 1 0 0 11212 1592 164232 273872 0 0 1824 3532 632 1083 11 25 64 2 0 2 11212 1980 167304 268792 0 0 1678 0 550 881 8 51 41 0 1 2 11212 1588 163908 271356 0 0 1344 4896 508 753 7 26 67 1 0 0 11212 1588 160896 272756 0 0 1642 1301 574 929 9 22 69 0 1 0 11212 1592 164936 268632 0 0 756 3594 370 467 6 43 51 2 0 3 11212 1596 164380 266552 0 0 1904 2392 604 1017 10 52 37 1 0 0 11212 1592 164752 265844 0 0 1784 2382 623 1000 10 22 69 0 1 0 11212 1592 168528 262256 0 0 810 4176 364 523 5 43 52 0 1 1 11212 1992 169324 259504 0 0 1686 3068 578 999 11 42 47 0 1 0 11212 1588 170696 256332 0 0 1568 1080 532 894 10 20 70 1 0 0 11212 1592 174876 253036 0 0 598 3600 315 420 4 41 55 0 1 1 11212 2316 171592 253892 0 0 1816 3286 616 1073 7 29 64 0 1 0 11212 1588 170380 253968 0 0 1638 840 540 910 13 29 58 0 1 1 11212 2896 168840 253740 0 0 752 4120 342 458 4 45 51 0 1 0 11216 2012 166392 255560 0 0 1352 2458 549 895 8 14 77 2 0 1 11216 1588 170744 250164 0 0 1504 1260 503 791 7 48 45 0 1 1 11224 1588 170704 249948 0 0 874 4106 516 655 6 10 84 0 1 0 11228 1588 170148 248988 0 0 1442 0 466 772 8 20 73 1 0 0 11228 1592 171784 247456 0 0 860 3598 362 495 7 44 48 0 1 0 11228 1588 171864 246212 0 0 1390 3176 510 840 9 41 50 0 1 2 11232 1992 170344 245832 0 0 1676 1808 539 898 10 45 45 1 0 1 10508 1632 168204 246780 0 946 1508 2804 599 920 9 20 71 0 1 0 9496 2020 168904 244880 0 0 936 3620 417 603 5 35 60 1 0 0 9604 2516 164096 247536 0 0 1700 2214 563 1085 11 33 56 0 1 0 16196 1820 162112 255492 0 2 1384 1596 497 1106 8 53 38 1 0 0 19240 3000 158052 260608 0 0 400 3824 373 388 2 14 84 1 1 1 28756 4508 146032 278104 0 0 1688 2140 612 1502 7 60 33 2 0 0 39432 29100 105668 300912 0 18 2108 1178 645 1825 12 52 36 1 0 0 40668 13024 108568 311748 0 0 1674 4992 623 1017 9 12 79 0 1 0 45324 3484 105072 326432 0 0 1876 3624 619 1090 13 24 63 1 0 0 53648 1564 102740 337688 0 18 950 3646 404 857 5 31 63 2 0 0 53672 1604 103356 335680 0 2962 1436 5864 565 976 10 43 47 1 0 1 54380 1920 103516 334320 0 1086 1826 1626 590 1072 13 45 42 0 1 1 54600 6532 99568 333860 0 1006 242 5948 277 2680 2 39 59 0 1 0 54596 1944 103744 331932 0 0 1854 3644 627 1054 11 16 73 1 0 0 54592 1924 102876 331100 0 950 1956 2612 621 1173 11 41 48 1 0 0 54592 1592 103576 329568 0 0 1548 4860 605 1106 11 36 53 0 1 1 54592 1588 102908 328320 0 452 1808 2522 583 1049 11 51 38 0 1 1 54592 1588 101916 327076 0 866 1816 1260 589 1046 11 49 40 0 1 0 54592 2076 99568 327776 0 414 992 5728 459 1314 7 25 67 0 1 0 54592 1588 103928 323824 0 0 968 3646 403 747 5 33 61 1 0 0 54592 2632 100108 325136 0 402 1856 2468 622 1369 13 44 42 0 1 0 54592 1588 101872 322600 0 392 1056 2834 461 802 6 35 60 1 0 1 55644 1724 102108 322404 0 380 1448 2682 501 1032 9 50 41 1 1 1 57388 1588 103068 322056 0 0 1384 1396 471 780 8 37 56 0 1 1 58500 2048 102024 323020 0 368 876 3932 504
How to I prevent a 100 Mb program from swapping itself (with 512 Mb memory)
I'm running linux-2.4.5-ac15, and I can't seem to make clear to Linux that I'd rather use less cache than use swap for my active program. I can't run a 100 Mb program in 512 Mb memory without swapping parts of the active program? I start a slrn (newsreader) session on a very big newsgroup; 15 headers that are read from disk, then sorted. The process takes about 100 Mb memory, I have 512 Mb, so there should be enough to spare. This is without any special values in /proc, BTW, just the defaults. here we start (the logfile is "vmstat 2") procs memoryswap io system cpu r b w swpd free buff cache si sobibo incs us sy id 0 1 0 8180 103364 86792 257804 15 16 109 156 85 151 6 6 88 0 0 0 8180 103328 86792 257828 6 0 8 0 11381 0 1 99 0 0 0 8152 102800 86792 257864 0 02468 11769 1 0 99 1 0 0 8152 92976 88652 264304 0 0 1136 0 391 635 7 8 85 1 0 0 8152 72700 93704 276452 0 0 2060 4260 701 1141 12 16 71 1 0 0 8152 53348 97780 287576 0 0 1810 3594 608 1057 12 13 75 1 0 0 8152 35516 101452 297956 0 0 1786 3594 616 1027 9 13 77 0 1 1 8160 11376 107952 310756 0 0 2184 6452 731 1236 13 17 70 2 0 1 8160 1588 109112 315664 0 0 1836 1798 597 964 9 32 59 1 0 0 8160 2224 106436 318588 0 0 1578 3750 624 923 10 16 74 3 0 0 8172 1956 109248 315820 0 0 986 3594 402 593 5 36 58 0 1 0 8172 1588 108156 315932 0 0 1878 1996 590 1033 10 34 56 0 1 0 8172 1592 104476 317924 0 0 1336 2580 514 785 7 17 76 1 0 0 8172 1668 107912 313736 0 0 1096 3598 462 650 7 40 53 1 0 0 8172 1780 108448 312740 0 0 1382 3680 520 796 7 39 53 0 1 1 8172 1588 107212 312552 0 0 1778 3604 597 987 9 43 49 1 0 2 8172 1748 104880 313196 0 0 1906 1234 613 1060 11 23 66 0 1 1 8172 2432 107072 308980 0 0 1018 4570 443 695 6 39 55 0 1 1 8172 1588 104880 310532 0 0 1828 1806 589 999 10 39 51 1 0 1 8172 2032 104616 309316 4 0 1492 2570 548 925 8 19 74 0 1 1 8172 1740 106308 306164 0 0 1082 3894 442 678 7 39 54 0 1 1 8172 1588 106056 304992 0 0 1796 2656 603 989 11 45 44 0 1 0 8172 1752 104732 305664 0 0 1310 3082 501 813 7 18 75 0 1 1 8172 2112 104288 304576 0 0 1042 3808 475 703 9 33 57 0 1 0 8140 1592 104400 304076 0 0 1174 514 488 694 5 16 79 0 1 2 8200 1740 105144 302364 0 0 1252 2688 454 831 5 49 46 1 0 0 8388 1596 104128 302276 0 0 1292 1008 478 876 7 51 42 1 0 0 8388 1592 105004 301368 0 0 394 4410 380 434 2 16 82 free space is gone, so let's hit the buffers and start to swap. 0 3 2 11648 2976 105408 302268 0 0 1238 1730 594 15566 3 52 45 0 1 0 33284 15572 87288 328872 0 8 846 1668 383 717 5 72 23 0 1 0 34160 1560 91440 336572 0 0 1502 3596 558 896 7 11 82 1 0 0 34116 1560 95112 329560 0 0 1572 3662 587 915 9 13 77 0 1 0 34604 1560 98780 323048 0 0 1582 3602 586 894 9 13 77 0 1 1 35112 1560 102448 315872 0 0 1832 3604 606 1002 8 17 75 1 0 2 36244 1808 103312 316984 0 0 1834 442 620 999 11 33 56 1 0 0 44836 1592 103132 327536 0 2 1364 4966 525 860 7 32 61 1 0 0 44816 1588 103516 326796 0 166 1350 4282 546 925 8 38 54 1 0 0 44772 2088 100884 327524 0 26 1868 1616 618 1095 12 46 42 1 0 1 44772 1588 101784 326180 0 2 1418 2060 501 994 9 38 53 1 0 0 44772 1768 99704 327772 0 2 700 4884 433 575 6 22 72 0 1 1 44772 1588 100308 326276 0 6 1922 2096 611 1049 11 44 45 1 0 1 44768 2656 102604 322084 0 10 1658 1786 567 1151 7 46 47 1 0 1 44768 1876 101896 322604 0 0 940 5120 466 643 6 12 82 1 0 0 44768 3000 99608 322388 0 0 1644 1480 533 1409 7 42 50 1 0 1 44800 2480 100648 320656 0 6 1622 2304 566 1086 8 54 39 1 0 1 46168 1700 99072 323320 0 0 958 4950 476 716 7 29 64 1 0 0 50824 1592 99512 326356 0 48 1708 2196 583 1033 7 54 39 0 1 1 55288 3044 98584 329060 0 2 1342 1728 495 854 9 59 32 0 1 1 58612 1588 98408 332860 10 6 912 4818 485 764 6 40 54 1 0 0 62768 2032 97168 336944 0 466 1116 1942 462 938 8 60 32 1 0 0 65364 1872 98640 336960 26 574 1510 2246 541 997 11 49 41 0 1 1 66552 1588 98256 337872 0 16 884 3844 478 708 6 36 58 0 1 1 67228 1588 99456 336400 0 1090 962 3112 440
How to I prevent a 100 Mb program from swapping itself (with 512 Mb memory)
I'm running linux-2.4.5-ac15, and I can't seem to make clear to Linux that I'd rather use less cache than use swap for my active program. I can't run a 100 Mb program in 512 Mb memory without swapping parts of the active program? I start a slrn (newsreader) session on a very big newsgroup; 15 headers that are read from disk, then sorted. The process takes about 100 Mb memory, I have 512 Mb, so there should be enough to spare. This is without any special values in /proc, BTW, just the defaults. here we start (the logfile is vmstat 2) procs memoryswap io system cpu r b w swpd free buff cache si sobibo incs us sy id 0 1 0 8180 103364 86792 257804 15 16 109 156 85 151 6 6 88 0 0 0 8180 103328 86792 257828 6 0 8 0 11381 0 1 99 0 0 0 8152 102800 86792 257864 0 02468 11769 1 0 99 1 0 0 8152 92976 88652 264304 0 0 1136 0 391 635 7 8 85 1 0 0 8152 72700 93704 276452 0 0 2060 4260 701 1141 12 16 71 1 0 0 8152 53348 97780 287576 0 0 1810 3594 608 1057 12 13 75 1 0 0 8152 35516 101452 297956 0 0 1786 3594 616 1027 9 13 77 0 1 1 8160 11376 107952 310756 0 0 2184 6452 731 1236 13 17 70 2 0 1 8160 1588 109112 315664 0 0 1836 1798 597 964 9 32 59 1 0 0 8160 2224 106436 318588 0 0 1578 3750 624 923 10 16 74 3 0 0 8172 1956 109248 315820 0 0 986 3594 402 593 5 36 58 0 1 0 8172 1588 108156 315932 0 0 1878 1996 590 1033 10 34 56 0 1 0 8172 1592 104476 317924 0 0 1336 2580 514 785 7 17 76 1 0 0 8172 1668 107912 313736 0 0 1096 3598 462 650 7 40 53 1 0 0 8172 1780 108448 312740 0 0 1382 3680 520 796 7 39 53 0 1 1 8172 1588 107212 312552 0 0 1778 3604 597 987 9 43 49 1 0 2 8172 1748 104880 313196 0 0 1906 1234 613 1060 11 23 66 0 1 1 8172 2432 107072 308980 0 0 1018 4570 443 695 6 39 55 0 1 1 8172 1588 104880 310532 0 0 1828 1806 589 999 10 39 51 1 0 1 8172 2032 104616 309316 4 0 1492 2570 548 925 8 19 74 0 1 1 8172 1740 106308 306164 0 0 1082 3894 442 678 7 39 54 0 1 1 8172 1588 106056 304992 0 0 1796 2656 603 989 11 45 44 0 1 0 8172 1752 104732 305664 0 0 1310 3082 501 813 7 18 75 0 1 1 8172 2112 104288 304576 0 0 1042 3808 475 703 9 33 57 0 1 0 8140 1592 104400 304076 0 0 1174 514 488 694 5 16 79 0 1 2 8200 1740 105144 302364 0 0 1252 2688 454 831 5 49 46 1 0 0 8388 1596 104128 302276 0 0 1292 1008 478 876 7 51 42 1 0 0 8388 1592 105004 301368 0 0 394 4410 380 434 2 16 82 free space is gone, so let's hit the buffers and start to swap. 0 3 2 11648 2976 105408 302268 0 0 1238 1730 594 15566 3 52 45 0 1 0 33284 15572 87288 328872 0 8 846 1668 383 717 5 72 23 0 1 0 34160 1560 91440 336572 0 0 1502 3596 558 896 7 11 82 1 0 0 34116 1560 95112 329560 0 0 1572 3662 587 915 9 13 77 0 1 0 34604 1560 98780 323048 0 0 1582 3602 586 894 9 13 77 0 1 1 35112 1560 102448 315872 0 0 1832 3604 606 1002 8 17 75 1 0 2 36244 1808 103312 316984 0 0 1834 442 620 999 11 33 56 1 0 0 44836 1592 103132 327536 0 2 1364 4966 525 860 7 32 61 1 0 0 44816 1588 103516 326796 0 166 1350 4282 546 925 8 38 54 1 0 0 44772 2088 100884 327524 0 26 1868 1616 618 1095 12 46 42 1 0 1 44772 1588 101784 326180 0 2 1418 2060 501 994 9 38 53 1 0 0 44772 1768 99704 327772 0 2 700 4884 433 575 6 22 72 0 1 1 44772 1588 100308 326276 0 6 1922 2096 611 1049 11 44 45 1 0 1 44768 2656 102604 322084 0 10 1658 1786 567 1151 7 46 47 1 0 1 44768 1876 101896 322604 0 0 940 5120 466 643 6 12 82 1 0 0 44768 3000 99608 322388 0 0 1644 1480 533 1409 7 42 50 1 0 1 44800 2480 100648 320656 0 6 1622 2304 566 1086 8 54 39 1 0 1 46168 1700 99072 323320 0 0 958 4950 476 716 7 29 64 1 0 0 50824 1592 99512 326356 0 48 1708 2196 583 1033 7 54 39 0 1 1 55288 3044 98584 329060 0 2 1342 1728 495 854 9 59 32 0 1 1 58612 1588 98408 332860 10 6 912 4818 485 764 6 40 54 1 0 0 62768 2032 97168 336944 0 466 1116 1942 462 938 8 60 32 1 0 0 65364 1872 98640 336960 26 574 1510 2246 541 997 11 49 41 0 1 1 66552 1588 98256 337872 0 16 884 3844 478 708 6 36 58 0 1 1 67228 1588 99456 336400 0 1090 962 3112 440
Re: [linux-usb-devel] usb.c: USB device not accepting new address=4 (error=-110)
On Sat, Jun 09, 2001 at 06:14:24AM -0700, David Brownell wrote: > Then whatever sets up your ServerWorks ServerSet III LE chipset > needs its PCI IRQ setup fixed ... I'm not sure how to do this. > > Perhaps someone who's familiar with arch/i386/kernel/pci-*.c > irq setup can suggest the right patch for this problem. I think > the "dmesg" output in your original post probably had the info > needed to figure that out. > > - Dave > > > > From: "Ingo Oeser" <[EMAIL PROTECTED]> > > Sent: Saturday, June 09, 2001 12:19 AM > > > > > David Brownell wrote: > > > Can you verify, using /proc/interrupts, that you're actually > > > getting interrupts on irq #30 when these timeouts happen? > > > > I get none: > > 30: 0 0 IO-APIC-level usb-ohci > > > > > One possibility: the timeout happens because the HCD > > > is not getting the interrupts it expects. That would imply > > > that the PCI IRQ setup for this device isn't quite right. > > > Such problems have been seen before. > > > > This seems to be my problem. How can I solve this? > > > > My BIOS cannot set a specific IRQ for USB like other BIOSes do. > > > > And now that you say^W it, I remember sth. like this on > > linux-kernel... I just didn't know the messages... > > A similar problem with USB on a VIA smp board was solved by Jeff Garzik, so you might want to send him some info, like dmesg lspci -vvvxxx Good luck, Jurriaan -- You have nothing to be afraid of. Well, that might not be true in the larger scheme of things, but this ordeal is over, so off you go. Toodle-oo. Fraser, Due South GNU/Linux 2.4.5-ac12 SMP/ReiserFS 2x1402 bogomips load av: 0.49 0.12 0.04 - 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 FAQ at http://www.tux.org/lkml/
Re: [linux-usb-devel] usb.c: USB device not accepting new address=4 (error=-110)
On Sat, Jun 09, 2001 at 06:14:24AM -0700, David Brownell wrote: Then whatever sets up your ServerWorks ServerSet III LE chipset needs its PCI IRQ setup fixed ... I'm not sure how to do this. Perhaps someone who's familiar with arch/i386/kernel/pci-*.c irq setup can suggest the right patch for this problem. I think the dmesg output in your original post probably had the info needed to figure that out. - Dave From: Ingo Oeser [EMAIL PROTECTED] Sent: Saturday, June 09, 2001 12:19 AM David Brownell wrote: Can you verify, using /proc/interrupts, that you're actually getting interrupts on irq #30 when these timeouts happen? I get none: 30: 0 0 IO-APIC-level usb-ohci One possibility: the timeout happens because the HCD is not getting the interrupts it expects. That would imply that the PCI IRQ setup for this device isn't quite right. Such problems have been seen before. This seems to be my problem. How can I solve this? My BIOS cannot set a specific IRQ for USB like other BIOSes do. And now that you say^W it, I remember sth. like this on linux-kernel... I just didn't know the messages... A similar problem with USB on a VIA smp board was solved by Jeff Garzik, so you might want to send him some info, like dmesg lspci -vvvxxx Good luck, Jurriaan -- You have nothing to be afraid of. Well, that might not be true in the larger scheme of things, but this ordeal is over, so off you go. Toodle-oo. Fraser, Due South GNU/Linux 2.4.5-ac12 SMP/ReiserFS 2x1402 bogomips load av: 0.49 0.12 0.04 - 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 FAQ at http://www.tux.org/lkml/
Re: (lkml)2.4.5-ac7 usb-uhci appears twice in /proc/interrupts
On Mon, Jun 04, 2001 at 03:07:56AM -0400, Pavel Roskin wrote: > Hello! > > I don't know, maybe it's Ok, but it looks confusing - usb-uhci is listed > twice on the same IRQ 9. > My Abit VP6 (VIA694) says in dmesg: usb.c: registered new driver hub uhci.c: USB UHCI at I/O 0xa000, IRQ 19 usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected uhci.c: USB UHCI at I/O 0xa400, IRQ 19 usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 2 ports detected uhci.c: Linus Torvalds, Johannes Erdfelt, Randy Dunlap, Georg Acher, Deti Fliegl, Thomas Sailer, Roman Weissgaerber uhci.c: USB Universal Host Controller Interface driver Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. And more, if I read the handbook I get an adapter to get another two usb plugs at the backside. So yes, this motherboard has 2 usb controllers. I think it is okay - you may want to check your own manual. Good luck, Jurriaan -- BOFH excuse #131: telnet: Unable to connect to remote host: Connection refused GNU/Linux 2.4.5-ac7 SMP/ReiserFS 2x1402 bogomips load av: 0.00 0.00 0.00 - 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 FAQ at http://www.tux.org/lkml/
Re: (lkml)2.4.5-ac7 usb-uhci appears twice in /proc/interrupts
On Mon, Jun 04, 2001 at 03:07:56AM -0400, Pavel Roskin wrote: Hello! I don't know, maybe it's Ok, but it looks confusing - usb-uhci is listed twice on the same IRQ 9. My Abit VP6 (VIA694) says in dmesg: usb.c: registered new driver hub uhci.c: USB UHCI at I/O 0xa000, IRQ 19 usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected uhci.c: USB UHCI at I/O 0xa400, IRQ 19 usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 2 ports detected uhci.c: Linus Torvalds, Johannes Erdfelt, Randy Dunlap, Georg Acher, Deti Fliegl, Thomas Sailer, Roman Weissgaerber uhci.c: USB Universal Host Controller Interface driver Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. And more, if I read the handbook I get an adapter to get another two usb plugs at the backside. So yes, this motherboard has 2 usb controllers. I think it is okay - you may want to check your own manual. Good luck, Jurriaan -- BOFH excuse #131: telnet: Unable to connect to remote host: Connection refused GNU/Linux 2.4.5-ac7 SMP/ReiserFS 2x1402 bogomips load av: 0.00 0.00 0.00 - 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 FAQ at http://www.tux.org/lkml/
Re: [PATCH] interrupt problem with MPS 1.4 / not with MPS 1.1 ?
On Sat, Jun 02, 2001 at 03:41:08AM -0400, Jeff Garzik wrote: > > No, I'm afraid it doesn't :-( > > > Thanks for testing. > > Ok, how about this one? This is a more simple version of the logic > presented, which should give you the value that Manfred asked you plug > in manually. > No go, I'm afraid. I wonder why I do see the PCI: Disabling Via external APIC routing messages, but none of the PCI: Via IRQ fixup ... messages that I assume should have been printed Greetings, Jurriaan Total of 2 processors activated (2808.21 BogoMIPS). ENABLING IO-APIC IRQs ...changing IO-APIC physical APIC ID to 2 ... ok. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-5, 2-10, 2-11, 2-15, 2-20, 2-21, 2-22, 2-23 not connected. ..TIMER: vector=49 pin1=2 pin2=0 number of MP IRQ sources: 22. number of IO-APIC #2 registers: 24. testing the IO APIC... IO APIC #2.. register #00: 0200 ...: physical APIC id: 02 register #01: 00178011 ... : max redirection entries: 0017 ... : IO APIC version: 0011 WARNING: unexpected IO-APIC, please mail to [EMAIL PROTECTED] register #02: ... : arbitration: 00 IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 100 0 00000 01 003 03 000 0 01139 02 003 03 000 0 01131 03 003 03 000 0 01141 04 003 03 000 0 01149 05 000 00 100 0 00000 06 003 03 000 0 01151 07 003 03 000 0 01159 08 003 03 000 0 01161 09 003 03 000 0 01169 0a 000 00 100 0 00000 0b 000 00 100 0 00000 0c 003 03 000 0 01171 0d 003 03 000 0 01179 0e 003 03 000 0 01181 0f 000 00 100 0 00000 10 003 03 110 1 01189 11 003 03 110 1 01191 12 003 03 110 1 01199 13 003 03 110 1 011A1 14 000 00 100 0 00000 15 000 00 100 0 00000 16 000 00 100 0 00000 17 000 00 100 0 00000 IRQ to pin mappings: IRQ0 -> 0:2 IRQ1 -> 0:1 IRQ3 -> 0:3 IRQ4 -> 0:4 IRQ6 -> 0:6 IRQ7 -> 0:7 IRQ8 -> 0:8 IRQ9 -> 0:9 IRQ12 -> 0:12 IRQ13 -> 0:13 IRQ14 -> 0:14 IRQ16 -> 0:16 IRQ17 -> 0:17 IRQ18 -> 0:18 IRQ19 -> 0:19 done. Using local APIC timer interrupts. calibrating APIC timer ... . CPU clock speed is 703.1867 MHz. . host bus clock speed is 100.4552 MHz. cpu: 0, clocks: 1004552, slice: 334850 PCI: Probing PCI hardware Unknown bridge resource 0: assuming transparent Unknown bridge resource 2: assuming transparent PCI: Using IRQ router VIA [1106/0686] at 00:07.0 PCI->APIC IRQ transform: (B0,I7,P3) -> 19 PCI->APIC IRQ transform: (B0,I7,P3) -> 19 PCI->APIC IRQ transform: (B0,I10,P0) -> 17 PCI->APIC IRQ transform: (B0,I11,P0) -> 17 PCI->APIC IRQ transform: (B0,I14,P0) -> 18 PCI->APIC IRQ transform: (B1,I0,P0) -> 16 PCI->APIC IRQ transform: (B2,I0,P0) -> 16 PCI->APIC IRQ transform: (B2,I1,P0) -> 17 PCI->APIC IRQ transform: (B2,I2,P0) -> 18 PCI: Disabling Via external APIC routing Linux NET4.0 for Linux 2.4 i2c-core.o: adapter MAVEN:fb0 on i2c-matroxfb registered as adapter 2. usb.c: registered new driver hub uhci.c: USB UHCI at I/O 0xa000, IRQ 19 usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected uhci.c: USB UHCI at I/O 0xa400, IRQ 19 usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 2 ports detected uhci.c: Linus Torvalds, Johannes Erdfelt, Randy Dunlap, Georg Acher, Deti Fliegl, Thomas Sailer, Roman Weissgaerber uhci.c: USB Universal Host Controller Interface driver Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. NET4: Linux TCP/IP 1.0 for NET4.0 hub.c: USB new device connect on bus1/1, assigned device number 2 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=2 (error=-110) hub.c: USB new device connect on bus1/1, assigned device number 3 reiserfs: checking transaction log (device 03:0a) ... Using r5 hash to sort names ReiserFS version 3.6.25 reiserfs: checking transaction log (device 21:04) ... Using r5 hash to sort names ReiserFS version 3.6.25 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=3 (error=-110) reiserfs: checking transaction log (device 22:03) ... Using r5 hash to sort names CPU0 CPU1 0: 4964 8776IO-APIC-edge timer 1: 33 34IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 8:
Re: [PATCH] interrupt problem with MPS 1.4 / not with MPS 1.1 ?
On Fri, Jun 01, 2001 at 04:42:40PM -0400, Jeff Garzik wrote: > Does this patch fix things for you, such that MPS 1.1 and MPS 1.4 both > work? No, I'm afraid it doesn't :-( Here are the dmesg (with some info cut out for brevity), the /proc/interrupts and the lspci -vvvxxx from a 2.4.5-ac6 kernel with this patch. I see in the dmesg the patch is active, but still I get: usb.c: registered new driver hub usb.c: new USB bus registered, assigned bus number 1 usb.c: new USB bus registered, assigned bus number 2 usb.c: registered new driver usb-storage usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=2 (error=-110) usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=3 (error=-110) Good luck, Jurriaan D APIC at: 0xFEE0 Processor #0 Pentium(tm) Pro APIC version 17 Processor #1 Pentium(tm) Pro APIC version 17 I/O APIC #2 Version 17 at 0xFEC0. Processors: 2 Kernel command line: auto BOOT_IMAGE=SuSE-2.4.5ac6 ro root=2101 BOOT_FILE=/boot/prod/vmlinuz-245ac6 video=matrox:vesa:0x11E,fv:80,sgram Initializing CPU#0 Detected 703.169 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 1402.47 BogoMIPS Total of 2 processors activated (2808.21 BogoMIPS). ENABLING IO-APIC IRQs ...changing IO-APIC physical APIC ID to 2 ... ok. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-5, 2-10, 2-11, 2-15, 2-20, 2-21, 2-22, 2-23 not connected. ..TIMER: vector=49 pin1=2 pin2=0 number of MP IRQ sources: 22. number of IO-APIC #2 registers: 24. testing the IO APIC... IO APIC #2.. register #00: 0200 ...: physical APIC id: 02 register #01: 00178011 ... : max redirection entries: 0017 ... : IO APIC version: 0011 WARNING: unexpected IO-APIC, please mail to [EMAIL PROTECTED] register #02: ... : arbitration: 00 IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 100 0 00000 01 003 03 000 0 01139 02 003 03 000 0 01131 03 003 03 000 0 01141 04 003 03 000 0 01149 05 000 00 100 0 00000 06 003 03 000 0 01151 07 003 03 000 0 01159 08 003 03 000 0 01161 09 003 03 000 0 01169 0a 000 00 100 0 00000 0b 000 00 100 0 00000 0c 003 03 000 0 01171 0d 003 03 000 0 01179 0e 003 03 000 0 01181 0f 000 00 100 0 00000 10 003 03 110 1 01189 11 003 03 110 1 01191 12 003 03 110 1 01199 13 003 03 110 1 011A1 14 000 00 100 0 00000 15 000 00 100 0 00000 16 000 00 100 0 00000 17 000 00 100 0 00000 IRQ to pin mappings: IRQ0 -> 0:2 IRQ1 -> 0:1 IRQ3 -> 0:3 IRQ4 -> 0:4 IRQ6 -> 0:6 IRQ7 -> 0:7 IRQ8 -> 0:8 IRQ9 -> 0:9 IRQ12 -> 0:12 IRQ13 -> 0:13 IRQ14 -> 0:14 IRQ16 -> 0:16 IRQ17 -> 0:17 IRQ18 -> 0:18 IRQ19 -> 0:19 done. Using local APIC timer interrupts. calibrating APIC timer ... . CPU clock speed is 703.0694 MHz. . host bus clock speed is 100.4384 MHz. cpu: 0, clocks: 1004384, slice: 334794 CPU0 cpu: 1, clocks: 1004384, slice: 334794 CPU1 checking TSC synchronization across CPUs: passed. mtrr: your CPUs had inconsistent fixed MTRR settings mtrr: your CPUs had inconsistent variable MTRR settings mtrr: probably your BIOS does not setup all CPUs PCI: PCI BIOS revision 2.10 entry at 0xfb3a0, last bus=2 PCI: Using configuration type 1 PCI: Probing PCI hardware Unknown bridge resource 0: assuming transparent Unknown bridge resource 2: assuming transparent PCI: Using IRQ router VIA [1106/0686] at 00:07.0 PCI->APIC IRQ transform: (B0,I7,P3) -> 19 PCI->APIC IRQ transform: (B0,I7,P3) -> 19 PCI->APIC IRQ transform: (B0,I10,P0) -> 17 PCI->APIC IRQ transform: (B0,I11,P0) -> 17 PCI->APIC IRQ transform: (B0,I14,P0) -> 18 PCI->APIC IRQ transform: (B1,I0,P0) -> 16 PCI->APIC IRQ transform: (B2,I0,P0) -> 16 PCI->APIC IRQ transform: (B2,I1,P0) -> 17 PCI->APIC IRQ transform: (B2,I2,P0) -> 18 PCI: Setting Via APIC control PCI: Via IRQ fixup for 00:07.2, from 5 to 19 PCI: Via IRQ fixup for 00:07.3, from 5 to 19 PCI: Via IRQ fixup for 00:07.4, from 0 to 3 Linux NET4.0 for Linux 2.4 i2c-core.o: adapter MAVEN:fb0 on i2c-matroxfb registered as adapter 2. usb.c: registered new driver hub uhci.c: USB UHCI at I/O 0xa000, IRQ 19 usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected uhci.c: USB UHCI at I/O 0xa400, IRQ 19 usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found
Re: [PATCH] interrupt problem with MPS 1.4 / not with MPS 1.1 ?
On Fri, Jun 01, 2001 at 04:42:40PM -0400, Jeff Garzik wrote: Does this patch fix things for you, such that MPS 1.1 and MPS 1.4 both work? No, I'm afraid it doesn't :-( Here are the dmesg (with some info cut out for brevity), the /proc/interrupts and the lspci -vvvxxx from a 2.4.5-ac6 kernel with this patch. I see in the dmesg the patch is active, but still I get: usb.c: registered new driver hub usb.c: new USB bus registered, assigned bus number 1 usb.c: new USB bus registered, assigned bus number 2 usb.c: registered new driver usb-storage usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=2 (error=-110) usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=3 (error=-110) Good luck, Jurriaan D APIC at: 0xFEE0 Processor #0 Pentium(tm) Pro APIC version 17 Processor #1 Pentium(tm) Pro APIC version 17 I/O APIC #2 Version 17 at 0xFEC0. Processors: 2 Kernel command line: auto BOOT_IMAGE=SuSE-2.4.5ac6 ro root=2101 BOOT_FILE=/boot/prod/vmlinuz-245ac6 video=matrox:vesa:0x11E,fv:80,sgram Initializing CPU#0 Detected 703.169 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 1402.47 BogoMIPS snip Total of 2 processors activated (2808.21 BogoMIPS). ENABLING IO-APIC IRQs ...changing IO-APIC physical APIC ID to 2 ... ok. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-5, 2-10, 2-11, 2-15, 2-20, 2-21, 2-22, 2-23 not connected. ..TIMER: vector=49 pin1=2 pin2=0 number of MP IRQ sources: 22. number of IO-APIC #2 registers: 24. testing the IO APIC... IO APIC #2.. register #00: 0200 ...: physical APIC id: 02 register #01: 00178011 ... : max redirection entries: 0017 ... : IO APIC version: 0011 WARNING: unexpected IO-APIC, please mail to [EMAIL PROTECTED] register #02: ... : arbitration: 00 IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 100 0 00000 01 003 03 000 0 01139 02 003 03 000 0 01131 03 003 03 000 0 01141 04 003 03 000 0 01149 05 000 00 100 0 00000 06 003 03 000 0 01151 07 003 03 000 0 01159 08 003 03 000 0 01161 09 003 03 000 0 01169 0a 000 00 100 0 00000 0b 000 00 100 0 00000 0c 003 03 000 0 01171 0d 003 03 000 0 01179 0e 003 03 000 0 01181 0f 000 00 100 0 00000 10 003 03 110 1 01189 11 003 03 110 1 01191 12 003 03 110 1 01199 13 003 03 110 1 011A1 14 000 00 100 0 00000 15 000 00 100 0 00000 16 000 00 100 0 00000 17 000 00 100 0 00000 IRQ to pin mappings: IRQ0 - 0:2 IRQ1 - 0:1 IRQ3 - 0:3 IRQ4 - 0:4 IRQ6 - 0:6 IRQ7 - 0:7 IRQ8 - 0:8 IRQ9 - 0:9 IRQ12 - 0:12 IRQ13 - 0:13 IRQ14 - 0:14 IRQ16 - 0:16 IRQ17 - 0:17 IRQ18 - 0:18 IRQ19 - 0:19 done. Using local APIC timer interrupts. calibrating APIC timer ... . CPU clock speed is 703.0694 MHz. . host bus clock speed is 100.4384 MHz. cpu: 0, clocks: 1004384, slice: 334794 CPU0T0:1004384,T1:669584,D:6,S:334794,C:1004384 cpu: 1, clocks: 1004384, slice: 334794 CPU1T0:1004384,T1:334784,D:12,S:334794,C:1004384 checking TSC synchronization across CPUs: passed. mtrr: your CPUs had inconsistent fixed MTRR settings mtrr: your CPUs had inconsistent variable MTRR settings mtrr: probably your BIOS does not setup all CPUs PCI: PCI BIOS revision 2.10 entry at 0xfb3a0, last bus=2 PCI: Using configuration type 1 PCI: Probing PCI hardware Unknown bridge resource 0: assuming transparent Unknown bridge resource 2: assuming transparent PCI: Using IRQ router VIA [1106/0686] at 00:07.0 PCI-APIC IRQ transform: (B0,I7,P3) - 19 PCI-APIC IRQ transform: (B0,I7,P3) - 19 PCI-APIC IRQ transform: (B0,I10,P0) - 17 PCI-APIC IRQ transform: (B0,I11,P0) - 17 PCI-APIC IRQ transform: (B0,I14,P0) - 18 PCI-APIC IRQ transform: (B1,I0,P0) - 16 PCI-APIC IRQ transform: (B2,I0,P0) - 16 PCI-APIC IRQ transform: (B2,I1,P0) - 17 PCI-APIC IRQ transform: (B2,I2,P0) - 18 PCI: Setting Via APIC control PCI: Via IRQ fixup for 00:07.2, from 5 to 19 PCI: Via IRQ fixup for 00:07.3, from 5 to 19 PCI: Via IRQ fixup for 00:07.4, from 0 to 3 Linux NET4.0 for Linux 2.4 snip i2c-core.o: adapter MAVEN:fb0 on i2c-matroxfb registered as adapter 2. usb.c: registered new driver hub uhci.c: USB UHCI at I/O 0xa000, IRQ 19 usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected uhci.c: USB UHCI at I/O 0xa400, IRQ 19 usb.c: new USB
Re: [PATCH] interrupt problem with MPS 1.4 / not with MPS 1.1 ?
On Sat, Jun 02, 2001 at 03:41:08AM -0400, Jeff Garzik wrote: No, I'm afraid it doesn't :-( Thanks for testing. Ok, how about this one? This is a more simple version of the logic presented, which should give you the value that Manfred asked you plug in manually. No go, I'm afraid. I wonder why I do see the PCI: Disabling Via external APIC routing messages, but none of the PCI: Via IRQ fixup ... messages that I assume should have been printed Greetings, Jurriaan Total of 2 processors activated (2808.21 BogoMIPS). ENABLING IO-APIC IRQs ...changing IO-APIC physical APIC ID to 2 ... ok. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-5, 2-10, 2-11, 2-15, 2-20, 2-21, 2-22, 2-23 not connected. ..TIMER: vector=49 pin1=2 pin2=0 number of MP IRQ sources: 22. number of IO-APIC #2 registers: 24. testing the IO APIC... IO APIC #2.. register #00: 0200 ...: physical APIC id: 02 register #01: 00178011 ... : max redirection entries: 0017 ... : IO APIC version: 0011 WARNING: unexpected IO-APIC, please mail to [EMAIL PROTECTED] register #02: ... : arbitration: 00 IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 100 0 00000 01 003 03 000 0 01139 02 003 03 000 0 01131 03 003 03 000 0 01141 04 003 03 000 0 01149 05 000 00 100 0 00000 06 003 03 000 0 01151 07 003 03 000 0 01159 08 003 03 000 0 01161 09 003 03 000 0 01169 0a 000 00 100 0 00000 0b 000 00 100 0 00000 0c 003 03 000 0 01171 0d 003 03 000 0 01179 0e 003 03 000 0 01181 0f 000 00 100 0 00000 10 003 03 110 1 01189 11 003 03 110 1 01191 12 003 03 110 1 01199 13 003 03 110 1 011A1 14 000 00 100 0 00000 15 000 00 100 0 00000 16 000 00 100 0 00000 17 000 00 100 0 00000 IRQ to pin mappings: IRQ0 - 0:2 IRQ1 - 0:1 IRQ3 - 0:3 IRQ4 - 0:4 IRQ6 - 0:6 IRQ7 - 0:7 IRQ8 - 0:8 IRQ9 - 0:9 IRQ12 - 0:12 IRQ13 - 0:13 IRQ14 - 0:14 IRQ16 - 0:16 IRQ17 - 0:17 IRQ18 - 0:18 IRQ19 - 0:19 done. Using local APIC timer interrupts. calibrating APIC timer ... . CPU clock speed is 703.1867 MHz. . host bus clock speed is 100.4552 MHz. cpu: 0, clocks: 1004552, slice: 334850 PCI: Probing PCI hardware Unknown bridge resource 0: assuming transparent Unknown bridge resource 2: assuming transparent PCI: Using IRQ router VIA [1106/0686] at 00:07.0 PCI-APIC IRQ transform: (B0,I7,P3) - 19 PCI-APIC IRQ transform: (B0,I7,P3) - 19 PCI-APIC IRQ transform: (B0,I10,P0) - 17 PCI-APIC IRQ transform: (B0,I11,P0) - 17 PCI-APIC IRQ transform: (B0,I14,P0) - 18 PCI-APIC IRQ transform: (B1,I0,P0) - 16 PCI-APIC IRQ transform: (B2,I0,P0) - 16 PCI-APIC IRQ transform: (B2,I1,P0) - 17 PCI-APIC IRQ transform: (B2,I2,P0) - 18 PCI: Disabling Via external APIC routing Linux NET4.0 for Linux 2.4 i2c-core.o: adapter MAVEN:fb0 on i2c-matroxfb registered as adapter 2. usb.c: registered new driver hub uhci.c: USB UHCI at I/O 0xa000, IRQ 19 usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected uhci.c: USB UHCI at I/O 0xa400, IRQ 19 usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 2 ports detected uhci.c: Linus Torvalds, Johannes Erdfelt, Randy Dunlap, Georg Acher, Deti Fliegl, Thomas Sailer, Roman Weissgaerber uhci.c: USB Universal Host Controller Interface driver Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. NET4: Linux TCP/IP 1.0 for NET4.0 hub.c: USB new device connect on bus1/1, assigned device number 2 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=2 (error=-110) hub.c: USB new device connect on bus1/1, assigned device number 3 reiserfs: checking transaction log (device 03:0a) ... Using r5 hash to sort names ReiserFS version 3.6.25 reiserfs: checking transaction log (device 21:04) ... Using r5 hash to sort names ReiserFS version 3.6.25 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=3 (error=-110) reiserfs: checking transaction log (device 22:03) ... Using r5 hash to sort names CPU0 CPU1 0: 4964 8776IO-APIC-edge timer 1: 33 34IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 8: 2 0IO-APIC-edge rtc 14:
Re: interrupt problem with MPS 1.4 / not with MPS 1.1 ?
On Fri, Jun 01, 2001 at 07:28:33PM +0200, Manfred Spraul wrote: > [EMAIL PROTECTED] wrote: > > > > :setpci -s 00:07.2 INTERRUPT_LINE=15 > > :lspci -vx -s 00:07.2 > > 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 >[UHCI]) > > Subsystem: Unknown device 0925:1234 > > Flags: bus master, medium devsel, latency 32, IRQ 19 > > I/O ports at a000 [size=32] > > Capabilities: [80] Power Management version 2 > > 30: 00 00 00 00 80 00 00 00 00 00 00 00 15 04 00 > > :setpci -s 00:07.2 INTERRUPT_LINE=19 > > :lspci -vx -s 00:07.2 > > 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 >[UHCI]) > > Subsystem: Unknown device 0925:1234 > > Flags: bus master, medium devsel, latency 32, IRQ 19 > > I/O ports at a000 [size=32] > > Capabilities: [80] Power Management version 2 > > 30: 00 00 00 00 80 00 00 00 00 00 00 00 19 04 00 00 > > > > So that is correct. I'll attach all the information from the MPS 1.4 > > reboot, in which 00:07.2 happily points at 05, while everything else > > thinks it's at 19. > > > > Could you compile uhci as a module, set the configuration to MPS1.4 and > find out with which interrupt line setting it works. > I'd try both > > setpci -s 00:07.2 INTERRUPT_LINE=13 no change, still this in /var/log/messages: Jun 1 20:57:48 middle kernel: uhci.c: USB Universal Host Controller Interface driver Jun 1 20:57:48 middle kernel: hub.c: USB new device connect on bus1/1, assigned device number 2 Jun 1 20:57:51 middle kernel: usb_control/bulk_msg: timeout Jun 1 20:57:51 middle kernel: usb.c: USB device not accepting new address=2 (error=-110) Jun 1 20:57:51 middle kernel: hub.c: USB new device connect on bus1/1, assigned device number 3 Jun 1 20:57:54 middle kernel: usb_control/bulk_msg: timeout Jun 1 20:57:54 middle kernel: usb.c: USB device not accepting new address=3 (error=-110) > setpci -s 00:07.2 INTERRUPT_LINE=3 > [even if 13 works, please try 03 as well. 13 is hexadecimal==19] Bingo!! Jun 1 20:59:34 middle kernel: Type: Direct-Access ANSI SCSI revision: 02 Jun 1 20:59:34 middle kernel: Attached scsi removable disk sda at scsi3, channel 0, id 0, lun 0 Jun 1 20:59:34 middle kernel: sda : READ CAPACITY failed. Jun 1 20:59:34 middle kernel: sda : status = 1, message = 00, host = 0, driver = 08 Jun 1 20:59:34 middle kernel: sda : extended sense code = 2 Jun 1 20:59:34 middle kernel: sda : block size assumed to be 512 bytes, disk size 1GB. Jun 1 20:59:34 middle kernel: sda: I/O error: dev 08:00, sector 0 Jun 1 20:59:34 middle kernel: unable to read partition table Jun 1 20:59:34 middle kernel: WARNING: USB Mass Storage data integrity not assured Jun 1 20:59:34 middle kernel: USB Mass Storage device found at 2 > > The via ac97 sound driver contains an irq fixup for this problem. Either > a similar fixup is necessary in the uhci driver, or the fixup from the > ac97 driver could be moved to the pci-quirks and applied to all devices > in the southbridge. > Just to be sure, the lspci -vvvxxx reading of 07.2 after this setpci -s 00:07.2 INTERRUPT_LINE=3 with MPS=1.4 in the bios: 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: interrupt problem with MPS 1.4 / not with MPS 1.1 ?
On Thu, May 31, 2001 at 11:56:44AM -0700, Greg KH wrote: > Is the BIOS set to "Plug and Play supported OS" somewhere? If not, try > enabling it. > It wasn't set, but with it set there is no difference. Greetings, Jurriaan -- IF MICROSOFT BUILT CARS.. New seats would force everyone to have the same size butt. GNU/Linux 2.4.5-ac5 SMP/ReiserFS 2x1402 bogomips load av: 0.87 0.42 0.16 - 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 FAQ at http://www.tux.org/lkml/
Re: unmount issues with 2.4.5-ac5, 3ware, and ReiserFS (was: kernel-2.4.5
On Thu, May 31, 2001 at 05:04:50PM -0500, Jordan wrote:
> Alan Cox wrote:
> >
> > > I'm staying on 2.4.5-ac5 for whatever it's worth (putting my life on the
> > > line for the community? kidding...) and will report anything new. I will
> > > be on the lookout for later ac patches, 2.4.6 ... and hopefully anything
> > > anybody can share with me about this. I hope we'll see an end to these
> >
> > Can you tell me if 2.4.5-ac4 is ok. ac5 has a small 'obviously correct'
> > reiserfs module unload change that seems the first suspect
> >
> > 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 FAQ at http://www.tux.org/lkml/
>
> I have seen this same problem with unmounting in 2.4.5-ac5, it was
> perfectly fine in 2.4.5-ac3 and ac4. I would guess the module unload is
> what did it.
>
2.4.5-ac4 was fine, 2.4.5-ac5:
/space in /etc/fstab:
/dev/hda10 /space1 reiserfsdefaults 1 2
strace umount /space1:
open("/usr/lib/locale/en_US/LC_TIME", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=2441, ...}) = 0
old_mmap(NULL, 2441, PROT_READ, MAP_PRIVATE, 3, 0) = 0x4001f000
close(3)= 0
open("/usr/lib/locale/en_US/LC_NUMERIC", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=44, ...}) = 0
old_mmap(NULL, 44, PROT_READ, MAP_PRIVATE, 3, 0) = 0x4002
close(3)= 0
open("/usr/lib/locale/en_US/LC_CTYPE", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=104804, ...}) = 0
old_mmap(NULL, 104804, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40137000
close(3)= 0
SYS_199(0x40131ad8, 0, 0x40132760, 0x40130210, 0) = 0
semop(1074993880, 0x40130210, 0)= 0
brk(0x8056000) = 0x8056000
readlink("/space1", 0xbfffe51c, 4095) = -1 EINVAL (Invalid argument)
open("/etc/mtab", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=680, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x40021000
read(3, "/dev/hde1 / ext2 rw 0 0\nproc /pr"..., 4096) = 680
read(3, "", 4096) = 0
close(3)= 0
munmap(0x40021000, 4096)= 0
oldumount("/space1"
and there it hangs. The kernel doesn't hang, but while 'mount' displays
/space1 as mounted, ls /space1/ says nothing. df -m reveals:
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/hda102015 907 1005 48% /space1
Good luck,
Jurriaan
--
The music in my heart I bore long after it was heard no more.
William Wordsworth
GNU/Linux 2.4.5-ac5 SMP/ReiserFS 2x1402 bogomips load av: 5.60 2.71 1.16
-
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 FAQ at http://www.tux.org/lkml/
Re: interrupt problem with MPS 1.4 / not with MPS 1.1 ?
On Fri, Jun 01, 2001 at 01:20:23AM -0400, Jeff Garzik wrote: > Looking at the diff of "lspci -vvvxxx" between MPS1.1 and MPS1.4 (on the > same system) may be quite useful... maybe I missed the earlier "lspci > -vvvxxx", but I only see one here... Yep, I didn't want to keep sending long messages. Here goes: diff pci_11 pci_14: -- 4c4 < Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR-Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 06 11 91 06 06 00 10 a2 c4 00 00 06 00 08 00 00 10: 08 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 7b 14 04 a2 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset- FastB2B- Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 06 11 98 85 07 00 30 22 00 00 04 06 00 00 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 00 f0 00 00 00 20: 00 d6 f0 d8 00 d4 f0 d5 00 00 00 00 00 00 00 00 30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 0c 00 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) Subsystem: ABIT Computer Corp.: Unknown device Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Reset- FastB2B- 00: 11 10 24 00 07 01 80 02 02 00 04 06 08 20 01 00 10: 00 00 00 00 00 00 00 00 00 02 02 20 91 91 80 22 20: 00 d9 f0 da f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 00 00:0a.0 SCSI storage controller: Symbios Logic Inc. (formerly NCR) 53c860 (rev 13) Subsystem: Symbios Logic Inc. (formerly NCR): Unknown device 1000 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] [size=128K] Capabilities: [60] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 03 11 04 00 05 00 30 02 03 00 80 01 08 78 00 00 10: 01 b8 00 00 01 bc 00 00 01 c0 00 00 01 c4 00 00 20: 01 c8 00 00 00 00 00 00 00 00 00 00 03 11 01 00 30: 00 00 00 00 60 00 00 00 00 00 00 00 0a 01 08 08 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 03) (prog-if 00 [VGA]) Subsystem: Matrox Graphics, Inc. Millennium G400 32Mb SGRAM Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- [disabled] [size=64K] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [f0] AGP version 2.0 Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2 Command: RQ=31 SBA+ AGP+ 64bit- FW- Rate=x1 00: 2b 10 25 05 07 00 90 02 03 00 00 03 08 20 00 00 10: 08 00 00 d4 00 00 00 d6 00 00 00 d7 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 2b 10 f8 19 30: 00 00 00 00 dc 00 00 00 00 00 00 00 0f 01 10 20 02:00.0 SCSI storage controller: Symbios Logic Inc. (formerly NCR) 53c875 (rev 04) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- [disabled] [size=64K] 00: 00 10 0f 00 47 00 00 02 04 00 00 01 08 48 00 00 10: 01 90 00 00 00 10 00 da 00 00 00 da 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 0f 01 11 40 02:01.0 SCSI storage controller: Symbios Logic Inc. (formerly NCR) 53c875 (rev 04) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- [disabled] [size=64K] 00: 00 10 0f 00 47 00 00 02 04 00 00 01 08 48 00 00 10: 01 94 00 00 00 20 00 da 00 30 00 da 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00
Re: interrupt problem with MPS 1.4 / not with MPS 1.1 ?
On Fri, Jun 01, 2001 at 01:20:23AM -0400, Jeff Garzik wrote: Looking at the diff of lspci -vvvxxx between MPS1.1 and MPS1.4 (on the same system) may be quite useful... maybe I missed the earlier lspci -vvvxxx, but I only see one here... Yep, I didn't want to keep sending long messages. Here goes: diff pci_11 pci_14: -- 4c4 Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR+ --- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- I see, this isn't going to work. I'll insert the complete dump from mps 1.1 here, followed by the same from 1.4: 00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4) Subsystem: ABIT Computer Corp.: Unknown device a204 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR+ Latency: 8 Region 0: Memory at d000 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 2.0 Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2 Command: RQ=0 SBA- AGP- 64bit- FW- Rate=none Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 06 11 91 06 06 00 10 a2 c4 00 00 06 00 08 00 00 10: 08 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 7b 14 04 a2 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- Latency: 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: f000-0fff Memory behind bridge: d600-d8ff Prefetchable memory behind bridge: d400-d5ff BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- Reset- FastB2B- Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 06 11 98 85 07 00 30 22 00 00 04 06 00 00 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 00 f0 00 00 00 20: 00 d6 f0 d8 00 d4 f0 d5 00 00 00 00 00 00 00 00 30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 0c 00 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) Subsystem: ABIT Computer Corp.: Unknown device Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 06 11 86 06 87 00 10 02 40 00 01 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 7b 14 00 00 30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00 00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP]) Subsystem: VIA Technologies, Inc. Bus Master IDE Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 Region 4: I/O ports at a800 [size=16] Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 06 11 71 05 07 00 90 02 06 8a 01 01 00 20 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 a8 00 00 00 00 00 00 00 00 00 00 06 11 71 05 30: 00 00 00 00 c0 00 00 00 00 00 00 00 ff 00 00 00 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32, cache line size 08 Interrupt: pin D routed to IRQ 5 Region 4: I/O ports at a000 [size=32] Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Re: unmount issues with 2.4.5-ac5, 3ware, and ReiserFS (was: kernel-2.4.5
On Thu, May 31, 2001 at 05:04:50PM -0500, Jordan wrote:
Alan Cox wrote:
I'm staying on 2.4.5-ac5 for whatever it's worth (putting my life on the
line for the community? kidding...) and will report anything new. I will
be on the lookout for later ac patches, 2.4.6 ... and hopefully anything
anybody can share with me about this. I hope we'll see an end to these
Can you tell me if 2.4.5-ac4 is ok. ac5 has a small 'obviously correct'
reiserfs module unload change that seems the first suspect
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 FAQ at http://www.tux.org/lkml/
I have seen this same problem with unmounting in 2.4.5-ac5, it was
perfectly fine in 2.4.5-ac3 and ac4. I would guess the module unload is
what did it.
2.4.5-ac4 was fine, 2.4.5-ac5:
/space in /etc/fstab:
/dev/hda10 /space1 reiserfsdefaults 1 2
strace umount /space1:
open(/usr/lib/locale/en_US/LC_TIME, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=2441, ...}) = 0
old_mmap(NULL, 2441, PROT_READ, MAP_PRIVATE, 3, 0) = 0x4001f000
close(3)= 0
open(/usr/lib/locale/en_US/LC_NUMERIC, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=44, ...}) = 0
old_mmap(NULL, 44, PROT_READ, MAP_PRIVATE, 3, 0) = 0x4002
close(3)= 0
open(/usr/lib/locale/en_US/LC_CTYPE, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=104804, ...}) = 0
old_mmap(NULL, 104804, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40137000
close(3)= 0
SYS_199(0x40131ad8, 0, 0x40132760, 0x40130210, 0) = 0
semop(1074993880, 0x40130210, 0)= 0
brk(0x8056000) = 0x8056000
readlink(/space1, 0xbfffe51c, 4095) = -1 EINVAL (Invalid argument)
open(/etc/mtab, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=680, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x40021000
read(3, /dev/hde1 / ext2 rw 0 0\nproc /pr..., 4096) = 680
read(3, , 4096) = 0
close(3)= 0
munmap(0x40021000, 4096)= 0
oldumount(/space1
and there it hangs. The kernel doesn't hang, but while 'mount' displays
/space1 as mounted, ls /space1/ says nothing. df -m reveals:
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/hda102015 907 1005 48% /space1
Good luck,
Jurriaan
--
The music in my heart I bore long after it was heard no more.
William Wordsworth
GNU/Linux 2.4.5-ac5 SMP/ReiserFS 2x1402 bogomips load av: 5.60 2.71 1.16
-
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 FAQ at http://www.tux.org/lkml/
Re: interrupt problem with MPS 1.4 / not with MPS 1.1 ?
On Thu, May 31, 2001 at 11:56:44AM -0700, Greg KH wrote: Is the BIOS set to Plug and Play supported OS somewhere? If not, try enabling it. It wasn't set, but with it set there is no difference. Greetings, Jurriaan -- IF MICROSOFT BUILT CARS.. New seats would force everyone to have the same size butt. GNU/Linux 2.4.5-ac5 SMP/ReiserFS 2x1402 bogomips load av: 0.87 0.42 0.16 - 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 FAQ at http://www.tux.org/lkml/
Re: interrupt problem with MPS 1.4 / not with MPS 1.1 ?
On Fri, Jun 01, 2001 at 07:28:33PM +0200, Manfred Spraul wrote: [EMAIL PROTECTED] wrote: :setpci -s 00:07.2 INTERRUPT_LINE=15 :lspci -vx -s 00:07.2 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 Flags: bus master, medium devsel, latency 32, IRQ 19 I/O ports at a000 [size=32] Capabilities: [80] Power Management version 2 30: 00 00 00 00 80 00 00 00 00 00 00 00 15 04 00 :setpci -s 00:07.2 INTERRUPT_LINE=19 :lspci -vx -s 00:07.2 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 Flags: bus master, medium devsel, latency 32, IRQ 19 I/O ports at a000 [size=32] Capabilities: [80] Power Management version 2 30: 00 00 00 00 80 00 00 00 00 00 00 00 19 04 00 00 So that is correct. I'll attach all the information from the MPS 1.4 reboot, in which 00:07.2 happily points at 05, while everything else thinks it's at 19. Could you compile uhci as a module, set the configuration to MPS1.4 and find out with which interrupt line setting it works. I'd try both setpci -s 00:07.2 INTERRUPT_LINE=13 no change, still this in /var/log/messages: Jun 1 20:57:48 middle kernel: uhci.c: USB Universal Host Controller Interface driver Jun 1 20:57:48 middle kernel: hub.c: USB new device connect on bus1/1, assigned device number 2 Jun 1 20:57:51 middle kernel: usb_control/bulk_msg: timeout Jun 1 20:57:51 middle kernel: usb.c: USB device not accepting new address=2 (error=-110) Jun 1 20:57:51 middle kernel: hub.c: USB new device connect on bus1/1, assigned device number 3 Jun 1 20:57:54 middle kernel: usb_control/bulk_msg: timeout Jun 1 20:57:54 middle kernel: usb.c: USB device not accepting new address=3 (error=-110) setpci -s 00:07.2 INTERRUPT_LINE=3 [even if 13 works, please try 03 as well. 13 is hexadecimal==19] Bingo!! Jun 1 20:59:34 middle kernel: Type: Direct-Access ANSI SCSI revision: 02 Jun 1 20:59:34 middle kernel: Attached scsi removable disk sda at scsi3, channel 0, id 0, lun 0 Jun 1 20:59:34 middle kernel: sda : READ CAPACITY failed. Jun 1 20:59:34 middle kernel: sda : status = 1, message = 00, host = 0, driver = 08 Jun 1 20:59:34 middle kernel: sda : extended sense code = 2 Jun 1 20:59:34 middle kernel: sda : block size assumed to be 512 bytes, disk size 1GB. Jun 1 20:59:34 middle kernel: sda: I/O error: dev 08:00, sector 0 Jun 1 20:59:34 middle kernel: unable to read partition table Jun 1 20:59:34 middle kernel: WARNING: USB Mass Storage data integrity not assured Jun 1 20:59:34 middle kernel: USB Mass Storage device found at 2 The via ac97 sound driver contains an irq fixup for this problem. Either a similar fixup is necessary in the uhci driver, or the fixup from the ac97 driver could be moved to the pci-quirks and applied to all devices in the southbridge. Just to be sure, the lspci -vvvxxx reading of 07.2 after this setpci -s 00:07.2 INTERRUPT_LINE=3 with MPS=1.4 in the bios: 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32, cache line size 08 Interrupt: pin D routed to IRQ 19 Region 4: I/O ports at a000 [size=32] Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 06 11 38 30 07 00 10 02 16 00 03 0c 08 20 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 a0 00 00 00 00 00 00 00 00 00 00 25 09 34 12 30: 00 00 00 00 80 00 00 00 00 00 00 00 03 04 00 00 40: 00 10 03 00 02 00 32 e0 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 /proc/interrupts: CPU0 CPU1 0: 22004 24207IO-APIC-edge timer 1: 2073 2617IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 8: 2 0IO-APIC-edge rtc 14:240241IO-APIC-edge ide0 16:53420075342450 IO-APIC-level
Re: interrupt problem with MPS 1.4 / not with MPS 1.1 ?
On Thu, May 31, 2001 at 10:45:17PM +0200, Manfred Spraul wrote: > [EMAIL PROTECTED] wrote: > > > > 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 >[UHCI]) > > Subsystem: Unknown device 0925:1234 > > Flags: bus master, medium devsel, latency 32, IRQ 5 > > I/O ports at a000 [size=32] > > Capabilities: [80] Power Management version 2 > > 30: 00 00 00 00 80 00 00 00 00 00 00 00 05 04 00 00 > > > > 0x3X is at 5, not at 3. > > > You still run with MPS 1.1. > It should be 3 or 19 after you reboot with MPS 1.4. > > Could you please try the following commands as root, but just before > rebooting. It'll kill the USB controller. > > #setpci -s 00:07.2 INTERRUPT_LINE=15 > #lspci -vx -s 00:07.2 > <<< 0x3C should be 15 > #setpci -s 00:07.2 INTERRUPT_LINE=19 > #lspci -vx -s 00:07.2 > <<< 0x3C is now either 19 or 3 > :setpci -s 00:07.2 INTERRUPT_LINE=15 :lspci -vx -s 00:07.2 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 Flags: bus master, medium devsel, latency 32, IRQ 19 I/O ports at a000 [size=32] Capabilities: [80] Power Management version 2 30: 00 00 00 00 80 00 00 00 00 00 00 00 15 04 00 00 :setpci -s 00:07.2 INTERRUPT_LINE=19 :lspci -vx -s 00:07.2 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 Flags: bus master, medium devsel, latency 32, IRQ 19 I/O ports at a000 [size=32] Capabilities: [80] Power Management version 2 30: 00 00 00 00 80 00 00 00 00 00 00 00 19 04 00 00 So that is correct. I'll attach all the information from the MPS 1.4 reboot, in which 00:07.2 happily points at 05, while everything else thinks it's at 19. 0: 000f - 0010 (reserved) BIOS-e820: 0010 - 1fff (usable) BIOS-e820: 1fff - 1fff3000 (ACPI NVS) BIOS-e820: 1fff3000 - 2000 (ACPI data) BIOS-e820: fec0 - fec01000 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: - 0001 (reserved) found SMP MP-table at 000f5770 hm, page 000f5000 reserved twice. hm, page 000f6000 reserved twice. hm, page 000f1000 reserved twice. hm, page 000f2000 reserved twice. On node 0 totalpages: 131056 zone(0): 4096 pages. zone(1): 126960 pages. zone(2): 0 pages. Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: OEM0 Product ID: PROD APIC at: 0xFEE0 Processor #0 Pentium(tm) Pro APIC version 17 Processor #1 Pentium(tm) Pro APIC version 17 I/O APIC #2 Version 17 at 0xFEC0. Processors: 2 Kernel command line: auto BOOT_IMAGE=SuSE-2.4.5ac5 ro root=2101 BOOT_FILE=/boot/prod/vmlinuz-245ac5 video=matrox:vesa:0x11E,fv:80,sgram Total of 2 processors activated (2808.21 BogoMIPS). ENABLING IO-APIC IRQs ...changing IO-APIC physical APIC ID to 2 ... ok. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-5, 2-10, 2-11, 2-15, 2-20, 2-21, 2-22, 2-23 not connected. ..TIMER: vector=49 pin1=2 pin2=0 number of MP IRQ sources: 22. number of IO-APIC #2 registers: 24. testing the IO APIC... IO APIC #2.. register #00: 0200 ...: physical APIC id: 02 register #01: 00178011 ... : max redirection entries: 0017 ... : IO APIC version: 0011 WARNING: unexpected IO-APIC, please mail to [EMAIL PROTECTED] register #02: ... : arbitration: 00 IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 100 0 00000 01 003 03 000 0 01139 02 003 03 000 0 01131 03 003 03 000 0 01141 04 003 03 000 0 01149 05 000 00 100 0 00000 06 003 03 000 0 01151 07 003 03 000 0 01159 08 003 03 000 0 01161 09 003 03 000 0 01169 0a 000 00 100 0 00000 0b 000 00 100 0 00000 0c 003 03 000 0 01171 0d 003 03 000 0 01179 0e 003 03 000 0 01181 0f 000 00 100 0 00000 10 003 03 110 1 01189 11 003 03 110 1 01191 12 003 03 110 1 01199 13 003 03 110 1 011A1 14 000 00 100 0 00000 15 000 00 100 0 00000 16 000 00 100 0 00000 17 000 00 100 0 00000 IRQ to pin mappings: IRQ0 -> 0:2 IRQ1 -> 0:1 IRQ3 -> 0:3 IRQ4 -> 0:4 IRQ6 -> 0:6 IRQ7 -> 0:7 IRQ8 -> 0:8 IRQ9 -> 0:9 IRQ12 -> 0:12 IRQ13 -> 0:13 IRQ14 -> 0:14 IRQ16
Re: [lkml]Re: [lkml]Re: interrupt problem with MPS 1.4 / not with MPS 1.1 ?
On Thu, May 31, 2001 at 10:21:55PM +0200, Manfred Spraul wrote: > > > > I know that with MPS 1.4, the USB controller finds itself at an > > unshared interrupt 19. I can't reboot at the moment to check. > > > lspci -vxxx -s 00:07.0 > > the APIC sits in the southbridge. > the low 2 bits of offset 0x58 must be set [route USB IRQ to APIC], and > > lspci -vx -s 00:07.2 > > offset 0x3C must be set to 3 [19 & 15] > > There was some discussion about the same problem with the sound part of > the southbridge. > > What are the current values of these registers? > current, as in MPS 1.1: 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) Subsystem: ABIT Computer Corp.: Unknown device Flags: bus master, stepping, medium devsel, latency 0 Capabilities: [c0] Power Management version 2 50: 02 76 04 00 00 f0 ab 50 1f 06 ff 08 00 00 00 00 I'd say the lower 2 bits at 0x58 are set. 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at a000 [size=32] Capabilities: [80] Power Management version 2 30: 00 00 00 00 80 00 00 00 00 00 00 00 05 04 00 00 0x3X is at 5, not at 3. Greetings, Jurriaan -- Endora is where we are, and you need to know that describing this place is like dancing to no music. Peter Hedges - What's eating Gilbert Grape GNU/Linux 2.4.5-ac4 SMP/ReiserFS 2x1402 bogomips load av: 0.02 0.01 0.00 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: interrupt problem with MPS 1.4 / not with MPS 1.1 ?
On Thu, May 31, 2001 at 11:06:42AM -0700, Greg KH wrote: > On Thu, May 31, 2001 at 08:39:08PM +0200, [EMAIL PROTECTED] wrote: > > What information would be necessary to debug this? > > Which kernel version? > > greg k-h > 2.4.5-ac4, but I rebooted in 2.4.4 and it did the same. I'll try and add some info here (from the bios= MPS 1.1 case!) I have the following expansion cards: Matrox G400 agp video-card ITI 4280 dual-UW scsi + fast ethernet card NCR860 ultra-scsi card Soundblaster Live! 5.1 card from dmesg: Total of 2 processors activated (2808.21 BogoMIPS). ENABLING IO-APIC IRQs ...changing IO-APIC physical APIC ID to 2 ... ok. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22, 2-23 not connected. ..TIMER: vector=49 pin1=2 pin2=0 number of MP IRQ sources: 16. number of IO-APIC #2 registers: 24. testing the IO APIC... IO APIC #2.. register #00: 0200 ...: physical APIC id: 02 register #01: 00178011 ... : max redirection entries: 0017 ... : IO APIC version: 0011 WARNING: unexpected IO-APIC, please mail to [EMAIL PROTECTED] register #02: ... : arbitration: 00 IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 100 0 00000 01 003 03 000 0 01139 02 003 03 000 0 01131 03 003 03 000 0 01141 04 003 03 000 0 01149 05 003 03 110 1 01151 06 003 03 000 0 01159 07 003 03 000 0 01161 08 003 03 000 0 01169 09 003 03 000 0 01171 0a 003 03 110 1 01179 0b 003 03 110 1 01181 0c 003 03 000 0 01189 0d 003 03 000 0 01191 0e 003 03 000 0 01199 0f 003 03 110 1 011A1 10 000 00 100 0 00000 11 000 00 100 0 00000 12 000 00 100 0 00000 13 000 00 100 0 00000 14 000 00 100 0 00000 15 000 00 100 0 00000 16 000 00 100 0 00000 17 000 00 100 0 00000 IRQ to pin mappings: IRQ0 -> 0:2 IRQ1 -> 0:1 IRQ3 -> 0:3 IRQ4 -> 0:4 IRQ5 -> 0:5 IRQ6 -> 0:6 IRQ7 -> 0:7 IRQ8 -> 0:8 IRQ9 -> 0:9 IRQ10 -> 0:10 IRQ11 -> 0:11 IRQ12 -> 0:12 IRQ13 -> 0:13 IRQ14 -> 0:14 IRQ15 -> 0:15 done. Using local APIC timer interrupts. calibrating APIC timer ... . CPU clock speed is 703.1338 MHz. . host bus clock speed is 100.4475 MHz. cpu: 0, clocks: 1004475, slice: 334825 CPU0 cpu: 1, clocks: 1004475, slice: 334825 CPU1 checking TSC synchronization across CPUs: passed. mtrr: your CPUs had inconsistent variable MTRR settings mtrr: probably your BIOS does not setup all CPUs PCI: PCI BIOS revision 2.10 entry at 0xfb3a0, last bus=2 PCI: Using configuration type 1 PCI: Probing PCI hardware Unknown bridge resource 0: assuming transparent Unknown bridge resource 2: assuming transparent PCI: Using IRQ router VIA [1106/0686] at 00:07.0 Linux NET4.0 for Linux 2.4 usb.c: registered new driver hub uhci.c: USB UHCI at I/O 0xa000, IRQ 5 usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected uhci.c: USB UHCI at I/O 0xa400, IRQ 5 usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 2 ports detected uhci.c: Linus Torvalds, Johannes Erdfelt, Randy Dunlap, Georg Acher, Deti Fliegl, Thomas Sailer, Roman Weissgaerber uhci.c: USB Universal Host Controller Interface driver Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. NET4: Linux TCP/IP 1.0 for NET4.0 Freeing unused kernel memory: 248k freed hub.c: USB new device connect on bus1/1, assigned device number 2 scsi3 : SCSI emulation for USB Mass Storage devices Vendor: IOMEGAModel: ZIP 250 Rev: 61.T Type: Direct-Access ANSI SCSI revision: 02 Attached scsi removable disk sda at scsi3, channel 0, id 0, lun 0 sda : READ CAPACITY failed. sda : status = 1, message = 00, host = 0, driver = 08 sda : extended sense code = 2 sda : block size assumed to be 512 bytes, disk size 1GB. sda: I/O error: dev 08:00, sector 0 unable to read partition table WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 2 Adding Swap: 1047776k swap-space (priority -1) from lspci: 00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4) Subsystem: ABIT Computer Corp.: Unknown device a204 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
interrupt problem with MPS 1.4 / not with MPS 1.1 ?
Hardware: Abit VP6 (Via 694x) x86/SMP motherboard with USB controller If I set the bios for MPS 1.1, USB runs fine. If I set the bios for MPS 1.4, I get this: May 31 13:08:06 middle kernel: hub.c: USB new device connect on bus1/1, assigned device number 4 May 31 13:08:09 middle kernel: usb_control/bulk_msg: timeout May 31 13:08:09 middle kernel: usb.c: USB device not accepting new address=4 (error=-110) May 31 13:08:09 middle kernel: hub.c: USB new device connect on bus1/1, assigned device number 5 May 31 13:08:12 middle kernel: usb_control/bulk_msg: timeout May 31 13:08:12 middle kernel: usb.c: USB device not accepting new address=5 (error=-110) May 31 13:08:12 middle kernel: hub.c: USB new device connect on bus1/1, assigned device number 6 May 31 13:08:15 middle kernel: usb_control/bulk_msg: timeout May 31 13:08:15 middle kernel: usb.c: USB device not accepting new address=6 (error=-110) May 31 13:08:16 middle kernel: hub.c: USB new device connect on bus1/1, assigned device number 7 May 31 13:08:19 middle kernel: usb_control/bulk_msg: timeout May 31 13:08:19 middle kernel: usb.c: USB device not accepting new address=7 (error=-110) May 31 13:08:19 middle kernel: hub.c: USB new device connect on bus1/1, assigned device number 8 May 31 13:08:22 middle kernel: usb_control/bulk_msg: timeout May 31 13:08:22 middle kernel: usb.c: USB device not accepting new address=8 (error=-110) May 31 13:08:22 middle kernel: hub.c: USB new device connect on bus1/1, assigned device number 9 Now I understand this mail doesn't have all the necessary info, but my question is: What information would be necessary to debug this? dmesg /var/log/messages lspci -vv (or -x?) or more? Jurriaan -- BOFH excuse #57: Groundskeepers stole the root password GNU/Linux 2.4.5-ac4 SMP/ReiserFS 2x1402 bogomips load av: 0.41 0.11 0.03 - 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 FAQ at http://www.tux.org/lkml/
interrupt problem with MPS 1.4 / not with MPS 1.1 ?
Hardware: Abit VP6 (Via 694x) x86/SMP motherboard with USB controller If I set the bios for MPS 1.1, USB runs fine. If I set the bios for MPS 1.4, I get this: May 31 13:08:06 middle kernel: hub.c: USB new device connect on bus1/1, assigned device number 4 May 31 13:08:09 middle kernel: usb_control/bulk_msg: timeout May 31 13:08:09 middle kernel: usb.c: USB device not accepting new address=4 (error=-110) May 31 13:08:09 middle kernel: hub.c: USB new device connect on bus1/1, assigned device number 5 May 31 13:08:12 middle kernel: usb_control/bulk_msg: timeout May 31 13:08:12 middle kernel: usb.c: USB device not accepting new address=5 (error=-110) May 31 13:08:12 middle kernel: hub.c: USB new device connect on bus1/1, assigned device number 6 May 31 13:08:15 middle kernel: usb_control/bulk_msg: timeout May 31 13:08:15 middle kernel: usb.c: USB device not accepting new address=6 (error=-110) May 31 13:08:16 middle kernel: hub.c: USB new device connect on bus1/1, assigned device number 7 May 31 13:08:19 middle kernel: usb_control/bulk_msg: timeout May 31 13:08:19 middle kernel: usb.c: USB device not accepting new address=7 (error=-110) May 31 13:08:19 middle kernel: hub.c: USB new device connect on bus1/1, assigned device number 8 May 31 13:08:22 middle kernel: usb_control/bulk_msg: timeout May 31 13:08:22 middle kernel: usb.c: USB device not accepting new address=8 (error=-110) May 31 13:08:22 middle kernel: hub.c: USB new device connect on bus1/1, assigned device number 9 Now I understand this mail doesn't have all the necessary info, but my question is: What information would be necessary to debug this? dmesg /var/log/messages lspci -vv (or -x?) or more? Jurriaan -- BOFH excuse #57: Groundskeepers stole the root password GNU/Linux 2.4.5-ac4 SMP/ReiserFS 2x1402 bogomips load av: 0.41 0.11 0.03 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: interrupt problem with MPS 1.4 / not with MPS 1.1 ?
On Thu, May 31, 2001 at 11:06:42AM -0700, Greg KH wrote: On Thu, May 31, 2001 at 08:39:08PM +0200, [EMAIL PROTECTED] wrote: What information would be necessary to debug this? Which kernel version? greg k-h 2.4.5-ac4, but I rebooted in 2.4.4 and it did the same. I'll try and add some info here (from the bios= MPS 1.1 case!) I have the following expansion cards: Matrox G400 agp video-card ITI 4280 dual-UW scsi + fast ethernet card NCR860 ultra-scsi card Soundblaster Live! 5.1 card from dmesg: Total of 2 processors activated (2808.21 BogoMIPS). ENABLING IO-APIC IRQs ...changing IO-APIC physical APIC ID to 2 ... ok. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22, 2-23 not connected. ..TIMER: vector=49 pin1=2 pin2=0 number of MP IRQ sources: 16. number of IO-APIC #2 registers: 24. testing the IO APIC... IO APIC #2.. register #00: 0200 ...: physical APIC id: 02 register #01: 00178011 ... : max redirection entries: 0017 ... : IO APIC version: 0011 WARNING: unexpected IO-APIC, please mail to [EMAIL PROTECTED] register #02: ... : arbitration: 00 IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 100 0 00000 01 003 03 000 0 01139 02 003 03 000 0 01131 03 003 03 000 0 01141 04 003 03 000 0 01149 05 003 03 110 1 01151 06 003 03 000 0 01159 07 003 03 000 0 01161 08 003 03 000 0 01169 09 003 03 000 0 01171 0a 003 03 110 1 01179 0b 003 03 110 1 01181 0c 003 03 000 0 01189 0d 003 03 000 0 01191 0e 003 03 000 0 01199 0f 003 03 110 1 011A1 10 000 00 100 0 00000 11 000 00 100 0 00000 12 000 00 100 0 00000 13 000 00 100 0 00000 14 000 00 100 0 00000 15 000 00 100 0 00000 16 000 00 100 0 00000 17 000 00 100 0 00000 IRQ to pin mappings: IRQ0 - 0:2 IRQ1 - 0:1 IRQ3 - 0:3 IRQ4 - 0:4 IRQ5 - 0:5 IRQ6 - 0:6 IRQ7 - 0:7 IRQ8 - 0:8 IRQ9 - 0:9 IRQ10 - 0:10 IRQ11 - 0:11 IRQ12 - 0:12 IRQ13 - 0:13 IRQ14 - 0:14 IRQ15 - 0:15 done. Using local APIC timer interrupts. calibrating APIC timer ... . CPU clock speed is 703.1338 MHz. . host bus clock speed is 100.4475 MHz. cpu: 0, clocks: 1004475, slice: 334825 CPU0T0:1004464,T1:669632,D:7,S:334825,C:1004475 cpu: 1, clocks: 1004475, slice: 334825 CPU1T0:1004464,T1:334800,D:14,S:334825,C:1004475 checking TSC synchronization across CPUs: passed. mtrr: your CPUs had inconsistent variable MTRR settings mtrr: probably your BIOS does not setup all CPUs PCI: PCI BIOS revision 2.10 entry at 0xfb3a0, last bus=2 PCI: Using configuration type 1 PCI: Probing PCI hardware Unknown bridge resource 0: assuming transparent Unknown bridge resource 2: assuming transparent PCI: Using IRQ router VIA [1106/0686] at 00:07.0 Linux NET4.0 for Linux 2.4 usb.c: registered new driver hub uhci.c: USB UHCI at I/O 0xa000, IRQ 5 usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected uhci.c: USB UHCI at I/O 0xa400, IRQ 5 usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 2 ports detected uhci.c: Linus Torvalds, Johannes Erdfelt, Randy Dunlap, Georg Acher, Deti Fliegl, Thomas Sailer, Roman Weissgaerber uhci.c: USB Universal Host Controller Interface driver Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. NET4: Linux TCP/IP 1.0 for NET4.0 Freeing unused kernel memory: 248k freed hub.c: USB new device connect on bus1/1, assigned device number 2 scsi3 : SCSI emulation for USB Mass Storage devices Vendor: IOMEGAModel: ZIP 250 Rev: 61.T Type: Direct-Access ANSI SCSI revision: 02 Attached scsi removable disk sda at scsi3, channel 0, id 0, lun 0 sda : READ CAPACITY failed. sda : status = 1, message = 00, host = 0, driver = 08 sda : extended sense code = 2 sda : block size assumed to be 512 bytes, disk size 1GB. sda: I/O error: dev 08:00, sector 0 unable to read partition table WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 2 Adding Swap: 1047776k swap-space (priority -1) from lspci: 00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4) Subsystem: ABIT Computer Corp.: Unknown device a204 Control: I/O- Mem+ BusMaster+
Re: [lkml]Re: [lkml]Re: interrupt problem with MPS 1.4 / not with MPS 1.1 ?
On Thu, May 31, 2001 at 10:21:55PM +0200, Manfred Spraul wrote: I know that with MPS 1.4, the USB controller finds itself at an unshared interrupt 19. I can't reboot at the moment to check. lspci -vxxx -s 00:07.0 the APIC sits in the southbridge. the low 2 bits of offset 0x58 must be set [route USB IRQ to APIC], and lspci -vx -s 00:07.2 offset 0x3C must be set to 3 [19 15] There was some discussion about the same problem with the sound part of the southbridge. What are the current values of these registers? current, as in MPS 1.1: 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) Subsystem: ABIT Computer Corp.: Unknown device Flags: bus master, stepping, medium devsel, latency 0 Capabilities: [c0] Power Management version 2 50: 02 76 04 00 00 f0 ab 50 1f 06 ff 08 00 00 00 00 I'd say the lower 2 bits at 0x58 are set. 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at a000 [size=32] Capabilities: [80] Power Management version 2 30: 00 00 00 00 80 00 00 00 00 00 00 00 05 04 00 00 0x3X is at 5, not at 3. Greetings, Jurriaan -- Endora is where we are, and you need to know that describing this place is like dancing to no music. Peter Hedges - What's eating Gilbert Grape GNU/Linux 2.4.5-ac4 SMP/ReiserFS 2x1402 bogomips load av: 0.02 0.01 0.00 - 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 FAQ at http://www.tux.org/lkml/
Re: interrupt problem with MPS 1.4 / not with MPS 1.1 ?
On Thu, May 31, 2001 at 10:45:17PM +0200, Manfred Spraul wrote: [EMAIL PROTECTED] wrote: 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at a000 [size=32] Capabilities: [80] Power Management version 2 30: 00 00 00 00 80 00 00 00 00 00 00 00 05 04 00 00 0x3X is at 5, not at 3. You still run with MPS 1.1. It should be 3 or 19 after you reboot with MPS 1.4. Could you please try the following commands as root, but just before rebooting. It'll kill the USB controller. #setpci -s 00:07.2 INTERRUPT_LINE=15 #lspci -vx -s 00:07.2 0x3C should be 15 #setpci -s 00:07.2 INTERRUPT_LINE=19 #lspci -vx -s 00:07.2 0x3C is now either 19 or 3 :setpci -s 00:07.2 INTERRUPT_LINE=15 :lspci -vx -s 00:07.2 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 Flags: bus master, medium devsel, latency 32, IRQ 19 I/O ports at a000 [size=32] Capabilities: [80] Power Management version 2 30: 00 00 00 00 80 00 00 00 00 00 00 00 15 04 00 00 :setpci -s 00:07.2 INTERRUPT_LINE=19 :lspci -vx -s 00:07.2 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 Flags: bus master, medium devsel, latency 32, IRQ 19 I/O ports at a000 [size=32] Capabilities: [80] Power Management version 2 30: 00 00 00 00 80 00 00 00 00 00 00 00 19 04 00 00 So that is correct. I'll attach all the information from the MPS 1.4 reboot, in which 00:07.2 happily points at 05, while everything else thinks it's at 19. 0: 000f - 0010 (reserved) BIOS-e820: 0010 - 1fff (usable) BIOS-e820: 1fff - 1fff3000 (ACPI NVS) BIOS-e820: 1fff3000 - 2000 (ACPI data) BIOS-e820: fec0 - fec01000 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: - 0001 (reserved) found SMP MP-table at 000f5770 hm, page 000f5000 reserved twice. hm, page 000f6000 reserved twice. hm, page 000f1000 reserved twice. hm, page 000f2000 reserved twice. On node 0 totalpages: 131056 zone(0): 4096 pages. zone(1): 126960 pages. zone(2): 0 pages. Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: OEM0 Product ID: PROD APIC at: 0xFEE0 Processor #0 Pentium(tm) Pro APIC version 17 Processor #1 Pentium(tm) Pro APIC version 17 I/O APIC #2 Version 17 at 0xFEC0. Processors: 2 Kernel command line: auto BOOT_IMAGE=SuSE-2.4.5ac5 ro root=2101 BOOT_FILE=/boot/prod/vmlinuz-245ac5 video=matrox:vesa:0x11E,fv:80,sgram Total of 2 processors activated (2808.21 BogoMIPS). ENABLING IO-APIC IRQs ...changing IO-APIC physical APIC ID to 2 ... ok. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-5, 2-10, 2-11, 2-15, 2-20, 2-21, 2-22, 2-23 not connected. ..TIMER: vector=49 pin1=2 pin2=0 number of MP IRQ sources: 22. number of IO-APIC #2 registers: 24. testing the IO APIC... IO APIC #2.. register #00: 0200 ...: physical APIC id: 02 register #01: 00178011 ... : max redirection entries: 0017 ... : IO APIC version: 0011 WARNING: unexpected IO-APIC, please mail to [EMAIL PROTECTED] register #02: ... : arbitration: 00 IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 100 0 00000 01 003 03 000 0 01139 02 003 03 000 0 01131 03 003 03 000 0 01141 04 003 03 000 0 01149 05 000 00 100 0 00000 06 003 03 000 0 01151 07 003 03 000 0 01159 08 003 03 000 0 01161 09 003 03 000 0 01169 0a 000 00 100 0 00000 0b 000 00 100 0 00000 0c 003 03 000 0 01171 0d 003 03 000 0 01179 0e 003 03 000 0 01181 0f 000 00 100 0 00000 10 003 03 110 1 01189 11 003 03 110 1 01191 12 003 03 110 1 01199 13 003 03 110 1 011A1 14 000 00 100 0 00000 15 000 00 100 0 00000 16 000 00 100 0 00000 17 000 00 100 0 00000 IRQ to pin mappings: IRQ0 - 0:2 IRQ1 - 0:1 IRQ3 - 0:3 IRQ4 - 0:4 IRQ6 - 0:6 IRQ7 - 0:7 IRQ8 - 0:8 IRQ9 - 0:9 IRQ12 - 0:12 IRQ13 - 0:13 IRQ14 - 0:14 IRQ16 - 0:16 IRQ17 - 0:17 IRQ18 - 0:18 IRQ19 - 0:19
2.4.4-ac6: timeout waiting for DMA on hpt370 / ibm DJNA drive
I got these messages in 2.4.4-ac5, and now in 2.4.4-ac6, when I expire
my news-spool. In 2.4.4, there's no problem expring my newsspool and
running 2 bonnie's in the background.
May 11 00:47:25 middle kernel: hdg: timeout waiting for DMA
May 11 00:47:25 middle kernel: ide_dmaproc: chipset supported ide_dma_timeout func
only: 14
May 11 00:47:25 middle kernel: hdg: irq timeout: status=0x58 { DriveReady SeekComplete
DataRequest }
May 11 00:56:20 middle kernel: hdg: timeout waiting for DMA
May 11 00:56:20 middle kernel: ide_dmaproc: chipset supported ide_dma_timeout func
only: 14
May 11 00:56:20 middle kernel: hdg: irq timeout: status=0x58 { DriveReady SeekComplete
DataRequest }
May 11 00:56:30 middle kernel: hdg: timeout waiting for DMA
May 11 00:56:30 middle kernel: ide_dmaproc: chipset supported ide_dma_timeout func
only: 14
May 11 00:56:30 middle kernel: hdg: irq timeout: status=0x58 { DriveReady SeekComplete
DataRequest }
Info from 2.4.4:
block: queued sectors max/low 340506kB/209434kB, 1024 slots per queue
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio
HPT370: IDE controller on PCI bus 00 dev 70
HPT370: chipset revision 3
HPT370: not 100% native mode: will probe irqs later
ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:DMA, hdf:pio
ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA, hdh:pio
hda: Maxtor 33073H3, ATA DISK drive
hde: IBM-DTLA-307045, ATA DISK drive
hdg: IBM-DJNA-372200, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0xdc00-0xdc07,0xe002 on irq 10
ide3 at 0xe400-0xe407,0xe802 on irq 10
hda: 60032448 sectors (30737 MB) w/2048KiB Cache, CHS=3736/255/63, UDMA(100)
hde: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=89355/16/63, UDMA(100)
hdg: 44150400 sectors (22605 MB) w/1966KiB Cache, CHS=43800/16/63, UDMA(33)
Partition check:
hda: hda1 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 > hda4
hde: [PTBL] [5606/255/63] hde1 hde2 hde3 hde4
hdg: hdg1 hdg2 hdg3 hdg4
Floppy drive(s): fd0 is 1.44M
HPT370 Chipset.
--- Primary Channel Secondary Channel -
enabled enabled
--- drive0 - drive1 drive0 -- drive1 --
DMA enabled:yes no yes no
UDMA
DMA
PIO
Good luck,
Jurriaan
--
BOFH excuse #24:
network packets travelling uphill (use a carrier pigeon)
GNU/Linux 2.4.4 SMP/ReiserFS 2x1402 bogomips load av: 0.42 0.10 0.03
-
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 FAQ at http://www.tux.org/lkml/
2.4.4-ac6: timeout waiting for DMA on hpt370 / ibm DJNA drive
I got these messages in 2.4.4-ac5, and now in 2.4.4-ac6, when I expire
my news-spool. In 2.4.4, there's no problem expring my newsspool and
running 2 bonnie's in the background.
May 11 00:47:25 middle kernel: hdg: timeout waiting for DMA
May 11 00:47:25 middle kernel: ide_dmaproc: chipset supported ide_dma_timeout func
only: 14
May 11 00:47:25 middle kernel: hdg: irq timeout: status=0x58 { DriveReady SeekComplete
DataRequest }
May 11 00:56:20 middle kernel: hdg: timeout waiting for DMA
May 11 00:56:20 middle kernel: ide_dmaproc: chipset supported ide_dma_timeout func
only: 14
May 11 00:56:20 middle kernel: hdg: irq timeout: status=0x58 { DriveReady SeekComplete
DataRequest }
May 11 00:56:30 middle kernel: hdg: timeout waiting for DMA
May 11 00:56:30 middle kernel: ide_dmaproc: chipset supported ide_dma_timeout func
only: 14
May 11 00:56:30 middle kernel: hdg: irq timeout: status=0x58 { DriveReady SeekComplete
DataRequest }
Info from 2.4.4:
block: queued sectors max/low 340506kB/209434kB, 1024 slots per queue
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio
HPT370: IDE controller on PCI bus 00 dev 70
HPT370: chipset revision 3
HPT370: not 100% native mode: will probe irqs later
ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:DMA, hdf:pio
ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA, hdh:pio
hda: Maxtor 33073H3, ATA DISK drive
hde: IBM-DTLA-307045, ATA DISK drive
hdg: IBM-DJNA-372200, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0xdc00-0xdc07,0xe002 on irq 10
ide3 at 0xe400-0xe407,0xe802 on irq 10
hda: 60032448 sectors (30737 MB) w/2048KiB Cache, CHS=3736/255/63, UDMA(100)
hde: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=89355/16/63, UDMA(100)
hdg: 44150400 sectors (22605 MB) w/1966KiB Cache, CHS=43800/16/63, UDMA(33)
Partition check:
hda: hda1 hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda4
hde: [PTBL] [5606/255/63] hde1 hde2 hde3 hde4
hdg: hdg1 hdg2 hdg3 hdg4
Floppy drive(s): fd0 is 1.44M
HPT370 Chipset.
--- Primary Channel Secondary Channel -
enabled enabled
--- drive0 - drive1 drive0 -- drive1 --
DMA enabled:yes no yes no
UDMA
DMA
PIO
Good luck,
Jurriaan
--
BOFH excuse #24:
network packets travelling uphill (use a carrier pigeon)
GNU/Linux 2.4.4 SMP/ReiserFS 2x1402 bogomips load av: 0.42 0.10 0.03
-
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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Linux 2.4.4-ac5; hpt370 & new dma setup
On Sat, May 05, 2001 at 02:37:53PM -0400, Ed Tomlinson wrote:
> [EMAIL PROTECTED] wrote:
>
> >> 2.4.4-ac5
> >> o Fix DMA setup on hpt366/370 (Tim Hockin)
> >
> > I see definite changes; on heavy disk-access I got the following:
> >
> > hdg: timeout waiting for dma
> > ide_dmaproc: chipset supported ide_dma_timeout func only:14
> > hdg: irq timeout: status = 0x58 { DriveReady SeekComplete DataRequest}
> >
> > this was repeated several times, and ide3 was being reset, but the
> > kernel hung anyway after 5 minutes of waiting.
> >
> > I must have an unlucky set of hardware (via chipset VP6 board, Live!,
> > ibm drives).
>
> Funny I have had the same problem with 2.4.4 only with a pdc20267 (reported
> to lkml with topic '[BUG] pdc20267 and dma timeouts') Is there some problem
> with resets on ide2/3?
>
I never saw it before, and this isn't the first time I've expired my
news-spool, did a make -j5 and a man -k at the same time.
Jurriaan
--
Backup Not Found (A)ssasinate Bill Gates (R)etry (K)eep trying until 6 am?
GNU/Linux 2.4.4 SMP/ReiserFS 2x1743 bogomips load av: 0.00 0.00 0.00
-
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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Linux 2.4.4-ac5; hpt370 new dma setup
On Sat, May 05, 2001 at 02:37:53PM -0400, Ed Tomlinson wrote:
[EMAIL PROTECTED] wrote:
2.4.4-ac5
o Fix DMA setup on hpt366/370 (Tim Hockin)
I see definite changes; on heavy disk-access I got the following:
hdg: timeout waiting for dma
ide_dmaproc: chipset supported ide_dma_timeout func only:14
hdg: irq timeout: status = 0x58 { DriveReady SeekComplete DataRequest}
this was repeated several times, and ide3 was being reset, but the
kernel hung anyway after 5 minutes of waiting.
I must have an unlucky set of hardware (via chipset VP6 board, Live!,
ibm drives).
Funny I have had the same problem with 2.4.4 only with a pdc20267 (reported
to lkml with topic '[BUG] pdc20267 and dma timeouts') Is there some problem
with resets on ide2/3?
I never saw it before, and this isn't the first time I've expired my
news-spool, did a make -j5 and a man -k at the same time.
Jurriaan
--
Backup Not Found (A)ssasinate Bill Gates (R)etry (K)eep trying until 6 am?
GNU/Linux 2.4.4 SMP/ReiserFS 2x1743 bogomips load av: 0.00 0.00 0.00
-
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 FAQ at http://www.tux.org/lkml/
Linux 2.4.4-ac5; hpt370 & new dma setup
On Fri, May 04, 2001 at 11:24:58PM +0100, Alan Cox wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
>
> Intermediate diffs are available from
>
> http://www.bzimage.org
>
> Please test this code **carefully** if using an HPT366/370 IDE controller as
> there are driver changes there. Otherwise its mostly just catching up with
> the bugfixes.
>
> 2.4.4-ac5
> o Fix DMA setup on hpt366/370 (Tim Hockin)
I see definite changes; on heavy disk-access I got the following:
hdg: timeout waiting for dma
ide_dmaproc: chipset supported ide_dma_timeout func only:14
hdg: irq timeout: status = 0x58 { DriveReady SeekComplete DataRequest}
this was repeated several times, and ide3 was being reset, but the
kernel hung anyway after 5 minutes of waiting.
I must have an unlucky set of hardware (via chipset VP6 board, Live!,
ibm drives).
The following output is from 2.4.3-ac12:
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio
HPT370: IDE controller on PCI bus 00 dev 70
HPT370: chipset revision 3
HPT370: not 100% native mode: will probe irqs later
ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:DMA, hdf:pio
ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA, hdh:pio
hda: Maxtor 33073H3, ATA DISK drive
hde: IBM-DTLA-307045, ATA DISK drive
hdg: IBM-DJNA-372200, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0xdc00-0xdc07,0xe002 on irq 10
ide3 at 0xe400-0xe407,0xe802 on irq 10
hda: 60032448 sectors (30737 MB) w/2048KiB Cache, CHS=3736/255/63, UDMA(100)
hde: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=89355/16/63, UDMA(44)
hdg: 44150400 sectors (22605 MB) w/1966KiB Cache, CHS=43800/16/63, UDMA(33)
Partition check:
hda: hda1 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 > hda4
hde: [PTBL] [5606/255/63] hde1 hde2 hde3 hde4
hdg: hdg1 hdg2 hdg3 hdg4
/proc/interrupts:
CPU0 CPU1
0: 31793 13448IO-APIC-edge timer
1: 1974 1033IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
7: 0 0 IO-APIC-level usb-uhci, usb-uhci
8: 2 0IO-APIC-edge rtc
10: 12499 12543 IO-APIC-level ide2, ide3, EMU10K1
11:245239 IO-APIC-level sym53c8xx, PCnet/PCI II 79C970A
14: 26781 6762IO-APIC-edge ide0
NMI: 0 0
LOC: 45155 45154
ERR: 0
MIS: 0
lspci -n:
00:00.0 Class 0600: 1106:0691 (rev c4)
00:01.0 Class 0604: 1106:8598
00:07.0 Class 0601: 1106:0686 (rev 40)
00:07.1 Class 0101: 1106:0571 (rev 06)
00:07.2 Class 0c03: 1106:3038 (rev 16)
00:07.3 Class 0c03: 1106:3038 (rev 16)
00:07.4 Class 0680: 1106:3057 (rev 40)
00:0a.0 Class 0100: 1000:0006 (rev 13)
00:0b.0 Class 0200: 1022:2000 (rev 16)
00:0d.0 Class 0401: 1102:0002 (rev 07)
00:0d.1 Class 0980: 1102:7002 (rev 07)
00:0e.0 Class 0180: 1103:0004 (rev 03)
01:00.0 Class 0300: 102b:0525 (rev 03)
lspci -v:
00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4)
Subsystem: ABIT Computer Corp.: Unknown device a204
Flags: bus master, medium devsel, latency 8
Memory at d000 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 2.0
Capabilities: [c0] Power Management version 2
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP]
(prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: d600-d8ff
Prefetchable memory behind bridge: d400-d5ff
Capabilities: [80] Power Management version 2
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
Subsystem: ABIT Computer Corp.: Unknown device
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: [c0] Power Management version 2
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06) (prog-if 8a
[Master SecP PriP])
Subsystem: VIA Technologies, Inc. Bus Master IDE
Flags: bus master, medium devsel, latency 32
I/O ports at c000 [size=16]
Capabilities: [c0] Power Management version 2
00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 [UHCI])
Subsystem: Unknown device 0925:1234
Flags: bus master, medium devsel, latency 32, IRQ 7
I/O ports at c400 [size=32]
Capabilities: [80] Power Management version 2
00:07.3 USB Controller: VIA Technologies, Inc. UHCI USB
Linux 2.4.4-ac5; hpt370 new dma setup
On Fri, May 04, 2001 at 11:24:58PM +0100, Alan Cox wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
Intermediate diffs are available from
http://www.bzimage.org
Please test this code **carefully** if using an HPT366/370 IDE controller as
there are driver changes there. Otherwise its mostly just catching up with
the bugfixes.
2.4.4-ac5
o Fix DMA setup on hpt366/370 (Tim Hockin)
I see definite changes; on heavy disk-access I got the following:
hdg: timeout waiting for dma
ide_dmaproc: chipset supported ide_dma_timeout func only:14
hdg: irq timeout: status = 0x58 { DriveReady SeekComplete DataRequest}
this was repeated several times, and ide3 was being reset, but the
kernel hung anyway after 5 minutes of waiting.
I must have an unlucky set of hardware (via chipset VP6 board, Live!,
ibm drives).
The following output is from 2.4.3-ac12:
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio
HPT370: IDE controller on PCI bus 00 dev 70
HPT370: chipset revision 3
HPT370: not 100% native mode: will probe irqs later
ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:DMA, hdf:pio
ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA, hdh:pio
hda: Maxtor 33073H3, ATA DISK drive
hde: IBM-DTLA-307045, ATA DISK drive
hdg: IBM-DJNA-372200, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0xdc00-0xdc07,0xe002 on irq 10
ide3 at 0xe400-0xe407,0xe802 on irq 10
hda: 60032448 sectors (30737 MB) w/2048KiB Cache, CHS=3736/255/63, UDMA(100)
hde: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=89355/16/63, UDMA(44)
hdg: 44150400 sectors (22605 MB) w/1966KiB Cache, CHS=43800/16/63, UDMA(33)
Partition check:
hda: hda1 hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda4
hde: [PTBL] [5606/255/63] hde1 hde2 hde3 hde4
hdg: hdg1 hdg2 hdg3 hdg4
/proc/interrupts:
CPU0 CPU1
0: 31793 13448IO-APIC-edge timer
1: 1974 1033IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
7: 0 0 IO-APIC-level usb-uhci, usb-uhci
8: 2 0IO-APIC-edge rtc
10: 12499 12543 IO-APIC-level ide2, ide3, EMU10K1
11:245239 IO-APIC-level sym53c8xx, PCnet/PCI II 79C970A
14: 26781 6762IO-APIC-edge ide0
NMI: 0 0
LOC: 45155 45154
ERR: 0
MIS: 0
lspci -n:
00:00.0 Class 0600: 1106:0691 (rev c4)
00:01.0 Class 0604: 1106:8598
00:07.0 Class 0601: 1106:0686 (rev 40)
00:07.1 Class 0101: 1106:0571 (rev 06)
00:07.2 Class 0c03: 1106:3038 (rev 16)
00:07.3 Class 0c03: 1106:3038 (rev 16)
00:07.4 Class 0680: 1106:3057 (rev 40)
00:0a.0 Class 0100: 1000:0006 (rev 13)
00:0b.0 Class 0200: 1022:2000 (rev 16)
00:0d.0 Class 0401: 1102:0002 (rev 07)
00:0d.1 Class 0980: 1102:7002 (rev 07)
00:0e.0 Class 0180: 1103:0004 (rev 03)
01:00.0 Class 0300: 102b:0525 (rev 03)
lspci -v:
00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4)
Subsystem: ABIT Computer Corp.: Unknown device a204
Flags: bus master, medium devsel, latency 8
Memory at d000 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 2.0
Capabilities: [c0] Power Management version 2
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP]
(prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: d600-d8ff
Prefetchable memory behind bridge: d400-d5ff
Capabilities: [80] Power Management version 2
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
Subsystem: ABIT Computer Corp.: Unknown device
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: [c0] Power Management version 2
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06) (prog-if 8a
[Master SecP PriP])
Subsystem: VIA Technologies, Inc. Bus Master IDE
Flags: bus master, medium devsel, latency 32
I/O ports at c000 [size=16]
Capabilities: [c0] Power Management version 2
00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if 00 [UHCI])
Subsystem: Unknown device 0925:1234
Flags: bus master, medium devsel, latency 32, IRQ 7
I/O ports at c400 [size=32]
Capabilities: [80] Power Management version 2
00:07.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) (prog-if
rtc: lost some interrupts / mga_flush_ioctl *ERROR* lock not held
Should I be worried about these? May 4 08:09:29 middle kernel: rtc: lost some interrupts at 256Hz. May 4 08:09:38 middle last message repeated 2 times May 4 08:09:56 middle kernel: rtc: lost some interrupts at 1024Hz. May 4 08:10:05 middle kernel: [drm:mga_flush_ioctl] *ERROR* lock not held May 4 08:14:39 middle kernel: rtc: lost some interrupts at 512Hz. May 4 08:15:07 middle last message repeated 4 times May 4 08:16:06 middle kernel: rtc: lost some interrupts at 256Hz. May 4 08:16:09 middle kernel: [drm:mga_flush_ioctl] *ERROR* lock not held May 4 08:17:33 middle kernel: rtc: lost some interrupts at 512Hz. May 4 08:18:01 middle last message repeated 12 times this is an X-session during heavy IDE-UDMA disk activity. Linux 2.4.4, i86-SMP system (Abit VP6, via chipset), Matrox G400. Thanks, Jurriaan -- These, then, were Srenki, men whose virtue was the excess of vice, who with leaden zest performed quintessential evil and so redeemed their fellows from turpitude. Jack Vance - The Gray Prince. GNU/Linux 2.4.4 SMP/ReiserFS 2x1743 bogomips load av: 0.05 0.02 0.01 - 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 FAQ at http://www.tux.org/lkml/
rtc: lost some interrupts / mga_flush_ioctl *ERROR* lock not held
Should I be worried about these? May 4 08:09:29 middle kernel: rtc: lost some interrupts at 256Hz. May 4 08:09:38 middle last message repeated 2 times May 4 08:09:56 middle kernel: rtc: lost some interrupts at 1024Hz. May 4 08:10:05 middle kernel: [drm:mga_flush_ioctl] *ERROR* lock not held May 4 08:14:39 middle kernel: rtc: lost some interrupts at 512Hz. May 4 08:15:07 middle last message repeated 4 times May 4 08:16:06 middle kernel: rtc: lost some interrupts at 256Hz. May 4 08:16:09 middle kernel: [drm:mga_flush_ioctl] *ERROR* lock not held May 4 08:17:33 middle kernel: rtc: lost some interrupts at 512Hz. May 4 08:18:01 middle last message repeated 12 times this is an X-session during heavy IDE-UDMA disk activity. Linux 2.4.4, i86-SMP system (Abit VP6, via chipset), Matrox G400. Thanks, Jurriaan -- These, then, were Srenki, men whose virtue was the excess of vice, who with leaden zest performed quintessential evil and so redeemed their fellows from turpitude. Jack Vance - The Gray Prince. GNU/Linux 2.4.4 SMP/ReiserFS 2x1743 bogomips load av: 0.05 0.02 0.01 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: Mounting an external USB host-powered ZIP 250 drive hangs in mount()
On Sun, Apr 29, 2001 at 09:13:46PM -0700, Matthew Dharm wrote: > I see you're using the alternate uhci driver... are hte results the same > with the other UHCI driver? I have read in the help-files that that was the one to use on this VIA694 motherboard. > > Can you turn on usb mass storage verbose debuggig (compile option) and then > send me the logs? > I'll do that. In the meantime, 2.4.4 does work - so it's something in the ac12 kernel that prevents it from working. Unfortunately I can't try ac13 or ac14, since the pcnet32 code doesn't compile in those. Jurriaan -- And money rides while people crawl And another quiet night goes by Oysterband - Another quiet night in England GNU/Linux 2.4.4 SMP/ReiserFS 2x1743 bogomips load av: 0.27 0.06 0.02 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: Mounting an external USB host-powered ZIP 250 drive hangs in mount()
On Sun, Apr 29, 2001 at 09:13:46PM -0700, Matthew Dharm wrote: I see you're using the alternate uhci driver... are hte results the same with the other UHCI driver? I have read in the help-files that that was the one to use on this VIA694 motherboard. Can you turn on usb mass storage verbose debuggig (compile option) and then send me the logs? I'll do that. In the meantime, 2.4.4 does work - so it's something in the ac12 kernel that prevents it from working. Unfortunately I can't try ac13 or ac14, since the pcnet32 code doesn't compile in those. Jurriaan -- And money rides while people crawl And another quiet night goes by Oysterband - Another quiet night in England GNU/Linux 2.4.4 SMP/ReiserFS 2x1743 bogomips load av: 0.27 0.06 0.02 - 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 FAQ at http://www.tux.org/lkml/
Mounting an external USB host-powered ZIP 250 drive hangs in mount()
I cannot seem to mount my external USB host-powered 250 Mb zip-drive in
Linux-2.4.3-ac12. This is a freshly rebooted machine, rebooted with the
zip-drive attached and a zip-disk inside that Windows-2000 will read
without problems.
dmesg:
uhci.c: USB UHCI at I/O 0xc400, IRQ 7
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
uhci.c: USB UHCI at I/O 0xc800, IRQ 7
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 32768)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 240k freed
hub.c: USB new device connect on bus1/1, assigned device number 2
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: IOMEGAModel: ZIP 250 Rev: 61.T
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
sda : READ CAPACITY failed.
sda : status = 1, message = 00, host = 0, driver = 08
sda : extended sense code = 2
sda : block size assumed to be 512 bytes, disk size 1GB.
sda: I/O error: dev 08:00, sector 0
unable to read partition table
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
==
IRQ 7 is an unshared IRQ.
I've read that the 'READ CAPACITY failed' indicates there is no disk
in the drive - but there is.
/proc/scsi/usb-storage-0/1:
Host scsi1: usb-storage
Vendor: Iomega
Product: USB Zip 250
Serial Number: 003240BCC4D11622
Protocol: Transparent SCSI
Transport: Bulk
GUID: 059b0032003240bcc4d11622
All seems fine, but when I do
mount /dev/sda4 /mnt
the whole kernel hangs, including the keyboard and the network.
Windows-2000 on the same hardware can access the device. If I strace the
mount progress, it hangs in
mount("/dev/sda4", "/mnt", "vfat", 0xc0ed000, 0
I've searched the web, searched the mailing lists at usb/sourceforge,
and I seem to be alone in this.
Hardware:
Abit VP6, dual P3/866
512 Mb memory
gcc-2.95.3
SuSE 7.1 basis
linux-2.4.3-ac12
Kernel config:
CONFIG_USB=y
CONFIG_USB_UHCI_ALT=y
CONFIG_USB_STORAGE=y
CONFIG_SCSI=y
CONFIG_SCSI_DEBUG_QUEUES=y
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_SYM53C8XX=y
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=4
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
CONFIG_SCSI_NCR53C8XX_SYNC=20
CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT=y
I thought that would do the trick?
Thanks for any help that prevents me from rebooting into Windows-2000
every time!
Jurriaan
--
I have transcended that phase in my intellectual growth where I discover
humour in simple freakishness. What exists is real, therefore it is tragic,
since whatever lives must die. Only fantasy, the vapors rising from sheer
nonsense, can now excite my laughter.
Jack Vance - Lyonesse II - The Green Pearl
GNU/Linux 2.4.3-ac12 SMP/ReiserFS 2x1743 bogomips load av: 0.05 0.03 0.00
-
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 FAQ at http://www.tux.org/lkml/
Mounting an external USB host-powered ZIP 250 drive hangs in mount()
I cannot seem to mount my external USB host-powered 250 Mb zip-drive in Linux-2.4.3-ac12. This is a freshly rebooted machine, rebooted with the zip-drive attached and a zip-disk inside that Windows-2000 will read without problems. dmesg: uhci.c: USB UHCI at I/O 0xc400, IRQ 7 usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected uhci.c: USB UHCI at I/O 0xc800, IRQ 7 usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 2 ports detected Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 4096 buckets, 32Kbytes TCP: Hash tables configured (established 32768 bind 32768) NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 240k freed hub.c: USB new device connect on bus1/1, assigned device number 2 scsi1 : SCSI emulation for USB Mass Storage devices Vendor: IOMEGAModel: ZIP 250 Rev: 61.T Type: Direct-Access ANSI SCSI revision: 02 Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0 sda : READ CAPACITY failed. sda : status = 1, message = 00, host = 0, driver = 08 sda : extended sense code = 2 sda : block size assumed to be 512 bytes, disk size 1GB. sda: I/O error: dev 08:00, sector 0 unable to read partition table WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 2 == IRQ 7 is an unshared IRQ. I've read that the 'READ CAPACITY failed' indicates there is no disk in the drive - but there is. /proc/scsi/usb-storage-0/1: Host scsi1: usb-storage Vendor: Iomega Product: USB Zip 250 Serial Number: 003240BCC4D11622 Protocol: Transparent SCSI Transport: Bulk GUID: 059b0032003240bcc4d11622 All seems fine, but when I do mount /dev/sda4 /mnt the whole kernel hangs, including the keyboard and the network. Windows-2000 on the same hardware can access the device. If I strace the mount progress, it hangs in mount(/dev/sda4, /mnt, vfat, 0xc0ed000, 0 I've searched the web, searched the mailing lists at usb/sourceforge, and I seem to be alone in this. Hardware: Abit VP6, dual P3/866 512 Mb memory gcc-2.95.3 SuSE 7.1 basis linux-2.4.3-ac12 Kernel config: CONFIG_USB=y CONFIG_USB_UHCI_ALT=y CONFIG_USB_STORAGE=y CONFIG_SCSI=y CONFIG_SCSI_DEBUG_QUEUES=y CONFIG_SCSI_MULTI_LUN=y CONFIG_SCSI_CONSTANTS=y CONFIG_SCSI_SYM53C8XX=y CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=4 CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32 CONFIG_SCSI_NCR53C8XX_SYNC=20 CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT=y I thought that would do the trick? Thanks for any help that prevents me from rebooting into Windows-2000 every time! Jurriaan -- I have transcended that phase in my intellectual growth where I discover humour in simple freakishness. What exists is real, therefore it is tragic, since whatever lives must die. Only fantasy, the vapors rising from sheer nonsense, can now excite my laughter. Jack Vance - Lyonesse II - The Green Pearl GNU/Linux 2.4.3-ac12 SMP/ReiserFS 2x1743 bogomips load av: 0.05 0.03 0.00 - 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 FAQ at http://www.tux.org/lkml/
pcnet32.c: PCI posting bug prevents 2.4.3-ac14 compilation
This one is new - 2.4.3-ac12 built without problems. make[3]: Entering directory `/usr/src/linux-2.4.3-ac14/drivers/net' gcc -D__KERNEL__ -I/usr/src/linux-2.4.3-ac14/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -m preferred-stack-boundary=2 -march=i686-c -o pcnet32.o pcnet32.c pcnet32.c:1385: warning: #warning "PCI posting bug" pcnet32.c:327: pcnet32_pci_tbl causes a section type conflict make[3]: *** [pcnet32.o] Error 1 make[3]: Leaving directory `/usr/src/linux-2.4.3-ac14/drivers/net' I must confess, that the meaning of the warning isn't clear to me, but that's a warning. The session-type conflict is even more vague. Reading the patch I don't see any obvious hints. I'm using Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/specs gcc version 2.95.3 20010315 (release) on a SuSE 7.1 base system. Thanks! Jurriaan -- If something was not wrong things would not be right. Sergeant Ortega - Zorro GNU/Linux 2.4.3-ac12 SMP/ReiserFS 2x1743 bogomips load av: 0.13 0.03 0.01 - 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 FAQ at http://www.tux.org/lkml/
pcnet32.c: PCI posting bug prevents 2.4.3-ac14 compilation
This one is new - 2.4.3-ac12 built without problems. make[3]: Entering directory `/usr/src/linux-2.4.3-ac14/drivers/net' gcc -D__KERNEL__ -I/usr/src/linux-2.4.3-ac14/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -m preferred-stack-boundary=2 -march=i686-c -o pcnet32.o pcnet32.c pcnet32.c:1385: warning: #warning PCI posting bug pcnet32.c:327: pcnet32_pci_tbl causes a section type conflict make[3]: *** [pcnet32.o] Error 1 make[3]: Leaving directory `/usr/src/linux-2.4.3-ac14/drivers/net' I must confess, that the meaning of the warning isn't clear to me, but that's a warning. The session-type conflict is even more vague. Reading the patch I don't see any obvious hints. I'm using Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/specs gcc version 2.95.3 20010315 (release) on a SuSE 7.1 base system. Thanks! Jurriaan -- If something was not wrong things would not be right. Sergeant Ortega - Zorro GNU/Linux 2.4.3-ac12 SMP/ReiserFS 2x1743 bogomips load av: 0.13 0.03 0.01 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: Matrox FB console driver
On Tue, Apr 24, 2001 at 06:19:31AM -0500, Andy Carlson wrote: > time prime before x > real1m23.535s > user0m40.550s > sys 0m42.980s > > /proc/mtrr before x > reg00: base=0x ( 0MB), size= 256MB: write-back, count=1 > reg01: base=0xfd80 (4056MB), size= 4MB: write-combining, count=1 > > time prime after x > real0m48.732s > user0m41.070s > sys 0m7.690s > > /proc/mtrr after x > reg00: base=0x ( 0MB), size= 256MB: write-back, count=1 > reg01: base=0xfd80 (4056MB), size= 4MB: write-combining, count=1 > > time prime in X > real0m42.835s > user0m41.180s > sys 0m1.710s > Well, it isn't that. Still, it was recently discussed that X might leave some settings in the video-card (Matrox). So I tried the following: time spdtest.sh before X with spdtest.sh: #!/bin/sh i=1 while [ $i -lt 500 ] do clear echo $i cat test.out; i=`expr $i + 1` done and after X, no change. This is a G400/32 Mb with framebuffer @ 1600x1200x16bpp, and X 4.0.3, same resolution. Kernel 2.4.3-ac12, Abit VP6 dual P3/866. There was no significant change in any of the reported times. I don't know. Your problem is interesting. Do other programs have this too? Jurriaan -- And the gosts of hope walk silent halls At the death of the promised land All is gone, all is gone But these changing winds can turn cold and hostile New Model Army GNU/Linux 2.4.3-ac12 SMP/ReiserFS 2x1743 bogomips load av: 0.00 0.03 0.01 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: Matrox FB console driver
On Tue, Apr 24, 2001 at 06:19:31AM -0500, Andy Carlson wrote: time prime before x real1m23.535s user0m40.550s sys 0m42.980s /proc/mtrr before x reg00: base=0x ( 0MB), size= 256MB: write-back, count=1 reg01: base=0xfd80 (4056MB), size= 4MB: write-combining, count=1 time prime after x real0m48.732s user0m41.070s sys 0m7.690s /proc/mtrr after x reg00: base=0x ( 0MB), size= 256MB: write-back, count=1 reg01: base=0xfd80 (4056MB), size= 4MB: write-combining, count=1 time prime in X real0m42.835s user0m41.180s sys 0m1.710s Well, it isn't that. Still, it was recently discussed that X might leave some settings in the video-card (Matrox). So I tried the following: time spdtest.sh before X with spdtest.sh: #!/bin/sh i=1 while [ $i -lt 500 ] do clear echo $i cat test.out; i=`expr $i + 1` done and after X, no change. This is a G400/32 Mb with framebuffer @ 1600x1200x16bpp, and X 4.0.3, same resolution. Kernel 2.4.3-ac12, Abit VP6 dual P3/866. There was no significant change in any of the reported times. I don't know. Your problem is interesting. Do other programs have this too? Jurriaan -- And the gosts of hope walk silent halls At the death of the promised land All is gone, all is gone But these changing winds can turn cold and hostile New Model Army GNU/Linux 2.4.3-ac12 SMP/ReiserFS 2x1743 bogomips load av: 0.00 0.03 0.01 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Matrox FB console driver
On Mon, Apr 23, 2001 at 08:06:11PM -0500, Andy Carlson wrote: > I was playing around with a program that I was using to time differences > between kernels (a silly prime program that puts out 100 primes). I > noticed a very strange behaviour. On a fresh boot, with the Penguin > pictures that the Matrox FB driver puts up, the prime program runs > 1 minute, 30 seconds. If I reset, it still runs 1M30S. If I start X, > and exit, it runs 48 seconds. Is this a known behaviour? Thanks. is there any change in /proc/mtrr before and after X? Good luck, Jurriaan -- BOFH excuse #176: vapors from evaporating sticky-note adhesives GNU/Linux 2.4.3-ac12 SMP/ReiserFS 2x1743 bogomips load av: 0.13 0.03 0.01 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Matrox FB console driver
On Mon, Apr 23, 2001 at 08:06:11PM -0500, Andy Carlson wrote: I was playing around with a program that I was using to time differences between kernels (a silly prime program that puts out 100 primes). I noticed a very strange behaviour. On a fresh boot, with the Penguin pictures that the Matrox FB driver puts up, the prime program runs 1 minute, 30 seconds. If I reset, it still runs 1M30S. If I start X, and exit, it runs 48 seconds. Is this a known behaviour? Thanks. is there any change in /proc/mtrr before and after X? Good luck, Jurriaan -- BOFH excuse #176: vapors from evaporating sticky-note adhesives GNU/Linux 2.4.3-ac12 SMP/ReiserFS 2x1743 bogomips load av: 0.13 0.03 0.01 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: ac10 ide-cd oopses on boot
On Thu, Apr 19, 2001 at 09:55:46PM -0500, Jordan wrote: > Bill Nottingham wrote: > > > > J . A . Magallon ([EMAIL PROTECTED]) said: > > > > Can you back out the ide-cd changes Jens did and see if that fixes it ? > > > > > > Reverted the changes in ide-cd.[hc], and same result. > > > > You want to back out the stuff from drivers/cdrom/cdrom.c; I backed > > out the parts of the patch new there to ac10, and it worked again > > for me... > > > That worked here as well...here is a patch that should restore > linux/drivers/cdrom/cdrom.c back to its working ac9 state from ac10. > 2.4.3-ac10 wouldn't boot for me without this patch. I have only scsi cdrom(s) on an symbios 860: Attached devices: Host: scsi0 Channel: 00 Id: 02 Lun: 00 Vendor: PLEXTOR Model: CD-R PX-R412C Rev: 1.03 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: SONY Model: SDT-5000 Rev: 330B Type: Sequential-AccessANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 05 Lun: 00 Vendor: PLEXTOR Model: CD-ROM PX-32TS Rev: 1.02 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: TOSHIBA Model: DVD-ROM SD-M1401 Rev: 1008 Type: CD-ROM ANSI SCSI revision: 02 With this patch, it boots just fine. Good luck, Jurriaan -- And all the while, all the while, I still hear that call To the land of gold and poison that beckons to us all Do you think you're so brave just to go running to that which beckons to us all? New Model Army - Valleys of Green and Grey GNU/Linux 2.4.3-ac10 SMP/ReiserFS 2x1743 bogomips load av: 0.20 0.05 0.01 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: ac10 ide-cd oopses on boot
On Thu, Apr 19, 2001 at 09:55:46PM -0500, Jordan wrote: Bill Nottingham wrote: J . A . Magallon ([EMAIL PROTECTED]) said: Can you back out the ide-cd changes Jens did and see if that fixes it ? Reverted the changes in ide-cd.[hc], and same result. You want to back out the stuff from drivers/cdrom/cdrom.c; I backed out the parts of the patch new there to ac10, and it worked again for me... That worked here as well...here is a patch that should restore linux/drivers/cdrom/cdrom.c back to its working ac9 state from ac10. snip patch; can be found on lkml 2.4.3-ac10 wouldn't boot for me without this patch. I have only scsi cdrom(s) on an symbios 860: Attached devices: Host: scsi0 Channel: 00 Id: 02 Lun: 00 Vendor: PLEXTOR Model: CD-R PX-R412C Rev: 1.03 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: SONY Model: SDT-5000 Rev: 330B Type: Sequential-AccessANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 05 Lun: 00 Vendor: PLEXTOR Model: CD-ROM PX-32TS Rev: 1.02 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: TOSHIBA Model: DVD-ROM SD-M1401 Rev: 1008 Type: CD-ROM ANSI SCSI revision: 02 With this patch, it boots just fine. Good luck, Jurriaan -- And all the while, all the while, I still hear that call To the land of gold and poison that beckons to us all Do you think you're so brave just to go running to that which beckons to us all? New Model Army - Valleys of Green and Grey GNU/Linux 2.4.3-ac10 SMP/ReiserFS 2x1743 bogomips load av: 0.20 0.05 0.01 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: [PATCH] matroxfb and mga XF4 driver coexistence...
On Thu, Apr 12, 2001 at 09:28:44AM -0400, Chris Meadors wrote: > On Thu, 12 Apr 2001, Rafael E. Herrera wrote: > > If the problem occurs whithout the frame buffer on, the problem seems to > > be on the X server. > > Exactly. That is what I'm saying. I've seen the problem with the > returning to VESA text modes from XFree 4.0 anytime I use the hallib, with > 2.2 and 2.4 kernels. If I compile an X server without the hallib it's > fine (G450 users don't have that option, and I like my dual head). > > If X changes the mode upon starting it should put it back when it is done. > Of course, but if we can fix the problem by making the kernel smaller, what possible motive could you have for opposing it other than 'but it doesn't solve _my_ problems!' ? Good luck, Jurriaan -- HORROR FILM WISDOM: 7. If you're running from the monster, you will most likely trip or fall. If you are female you can bet on it. GNU/Linux 2.4.3-ac4 SMP/ReiserFS 2x1743 bogomips load av: 0.03 0.01 0.02 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: [PATCH] matroxfb and mga XF4 driver coexistence...
On Thu, Apr 12, 2001 at 09:28:44AM -0400, Chris Meadors wrote: On Thu, 12 Apr 2001, Rafael E. Herrera wrote: If the problem occurs whithout the frame buffer on, the problem seems to be on the X server. Exactly. That is what I'm saying. I've seen the problem with the returning to VESA text modes from XFree 4.0 anytime I use the hallib, with 2.2 and 2.4 kernels. If I compile an X server without the hallib it's fine (G450 users don't have that option, and I like my dual head). If X changes the mode upon starting it should put it back when it is done. Of course, but if we can fix the problem by making the kernel smaller, what possible motive could you have for opposing it other than 'but it doesn't solve _my_ problems!' ? Good luck, Jurriaan -- HORROR FILM WISDOM: 7. If you're running from the monster, you will most likely trip or fall. If you are female you can bet on it. GNU/Linux 2.4.3-ac4 SMP/ReiserFS 2x1743 bogomips load av: 0.03 0.01 0.02 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: [lkml]Re: Matrox G400 Dualhead
On Sun, Apr 01, 2001 at 07:40:36AM -0700, James Simmons wrote: > > >If I use X on an accelerated, normal Matrox screen, my monitor complains > >on exit: > > > >fH 49.4 KHz, fV 39.8 Hz > > > >(and it doesn't sync at 40 Hz vertical refresh :-( ). > > > >This is _half_ of the normal 80 Hz. Using fbset -a "1600x1200-80" before > >X, of after X, doesn't do anything. Does anybody know what to hack out > >in X to get it to _not_ reset my G400 to some unusable state? 3.3.6 was > >didn't do this. I can use the framebuffer-screen just fine, but I miss > >the DGA extension. > > Try adding this to your XF86Config file: > > Section "Device" > ... > Option UseFBDev > ... > EndSection > A very neat trick. X can now be ended correctly. Unfortunately, any scrolling on any VT afterwards gives me a corrupted screen - parts of the screen from other VT's are inserted below, or over the cursor position, and at 'half-line' intervals. In typing this email, I've seen it 5 times already. I'm willing to test anything - but the corruption is alway gone after I switch VT's. So getting a screendump is not easy. Thanks! Jurriaan -- Send lawyers, guns, and money, The shit has hit the fan. Warren Zevon GNU/Linux 2.4.2-ac28 SMP/ReiserFS 2x1743 bogomips load av: 0.98 0.54 0.21 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: [lkml]Re: Matrox G400 Dualhead
On Sun, Apr 01, 2001 at 07:40:36AM -0700, James Simmons wrote: If I use X on an accelerated, normal Matrox screen, my monitor complains on exit: fH 49.4 KHz, fV 39.8 Hz (and it doesn't sync at 40 Hz vertical refresh :-( ). This is _half_ of the normal 80 Hz. Using fbset -a "1600x1200-80" before X, of after X, doesn't do anything. Does anybody know what to hack out in X to get it to _not_ reset my G400 to some unusable state? 3.3.6 was didn't do this. I can use the framebuffer-screen just fine, but I miss the DGA extension. Try adding this to your XF86Config file: Section "Device" ... Option UseFBDev ... EndSection A very neat trick. X can now be ended correctly. Unfortunately, any scrolling on any VT afterwards gives me a corrupted screen - parts of the screen from other VT's are inserted below, or over the cursor position, and at 'half-line' intervals. In typing this email, I've seen it 5 times already. I'm willing to test anything - but the corruption is alway gone after I switch VT's. So getting a screendump is not easy. Thanks! Jurriaan -- Send lawyers, guns, and money, The shit has hit the fan. Warren Zevon GNU/Linux 2.4.2-ac28 SMP/ReiserFS 2x1743 bogomips load av: 0.98 0.54 0.21 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: Matrox G400 Dualhead
On Sat, Mar 31, 2001 at 05:46:38PM +, J Brook wrote: > > I have a similar problem with my G450, booting into the framebuffer, > > then loading xdm and working in X, and then switching back to the > > console. I may have another detail to add in that when I switch back > > to the console from X, my monitor blanks and displays the warning > > that the frequencies are out of range. > > I think I have a work around. Boot up 2.4.3 with the framebuffer > enabled as normal. Log in as root and use the fbset program to change > the settings for all the framebuffers. > eg. > > fbset -a 1024x768-70 > > or whatever works for you. fbset has its own man page. > > This makes everything hunky-dory for me, in that after running fbset > I > can go in and out of X without ever losing the video signal. > Well, that certainly doesn't work for me (2.4.2-ac28, G400): fbset -i: mode "1600x1200-80" # D: 205.846 MHz, H: 99.347 kHz, V: 79.989 Hz geometry 1600 1200 1600 5241 16 timings 4858 272 48 32 5 152 5 accel true rgba 5/11,6/5,5/0,0/0 endmode Frame buffer device information: Name: MATROX Address : 0xd400 Size: 16773120 Type: PACKED PIXELS Visual : TRUECOLOR XPanStep: 8 YPanStep: 1 YWrapStep : 0 LineLength : 3200 MMIO Address: 0xd600 MMIO Size : 16384 Accelerator : Matrox G400 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 03) (prog-if 00 [VGA]) Subsystem: Matrox Graphics, Inc. Millennium G400 32Mb SGRAM Flags: bus master, medium devsel, latency 32, IRQ 10 Memory at d400 (32-bit, prefetchable) [size=32M] Memory at d600 (32-bit, non-prefetchable) [size=16K] Memory at d700 (32-bit, non-prefetchable) [size=8M] Expansion ROM at [disabled] [size=64K] Capabilities: If I use X on an accelerated, normal Matrox screen, my monitor complains on exit: fH 49.4 KHz, fV 39.8 Hz (and it doesn't sync at 40 Hz vertical refresh :-( ). This is _half_ of the normal 80 Hz. Using fbset -a "1600x1200-80" before X, of after X, doesn't do anything. Does anybody know what to hack out in X to get it to _not_ reset my G400 to some unusable state? 3.3.6 was didn't do this. I can use the framebuffer-screen just fine, but I miss the DGA extension. Thanks, Jurriaan -- BOFH excuse #329: Server depressed, needs Prozak GNU/Linux 2.4.2-ac28 SMP/ReiserFS 2x1743 bogomips load av: 0.20 0.05 0.01 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: Matrox G400 Dualhead
On Sat, Mar 31, 2001 at 05:46:38PM +, J Brook wrote: I have a similar problem with my G450, booting into the framebuffer, then loading xdm and working in X, and then switching back to the console. I may have another detail to add in that when I switch back to the console from X, my monitor blanks and displays the warning that the frequencies are out of range. I think I have a work around. Boot up 2.4.3 with the framebuffer enabled as normal. Log in as root and use the fbset program to change the settings for all the framebuffers. eg. fbset -a 1024x768-70 or whatever works for you. fbset has its own man page. This makes everything hunky-dory for me, in that after running fbset I can go in and out of X without ever losing the video signal. Well, that certainly doesn't work for me (2.4.2-ac28, G400): fbset -i: mode "1600x1200-80" # D: 205.846 MHz, H: 99.347 kHz, V: 79.989 Hz geometry 1600 1200 1600 5241 16 timings 4858 272 48 32 5 152 5 accel true rgba 5/11,6/5,5/0,0/0 endmode Frame buffer device information: Name: MATROX Address : 0xd400 Size: 16773120 Type: PACKED PIXELS Visual : TRUECOLOR XPanStep: 8 YPanStep: 1 YWrapStep : 0 LineLength : 3200 MMIO Address: 0xd600 MMIO Size : 16384 Accelerator : Matrox G400 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 03) (prog-if 00 [VGA]) Subsystem: Matrox Graphics, Inc. Millennium G400 32Mb SGRAM Flags: bus master, medium devsel, latency 32, IRQ 10 Memory at d400 (32-bit, prefetchable) [size=32M] Memory at d600 (32-bit, non-prefetchable) [size=16K] Memory at d700 (32-bit, non-prefetchable) [size=8M] Expansion ROM at unassigned [disabled] [size=64K] Capabilities: available only to root If I use X on an accelerated, normal Matrox screen, my monitor complains on exit: fH 49.4 KHz, fV 39.8 Hz (and it doesn't sync at 40 Hz vertical refresh :-( ). This is _half_ of the normal 80 Hz. Using fbset -a "1600x1200-80" before X, of after X, doesn't do anything. Does anybody know what to hack out in X to get it to _not_ reset my G400 to some unusable state? 3.3.6 was didn't do this. I can use the framebuffer-screen just fine, but I miss the DGA extension. Thanks, Jurriaan -- BOFH excuse #329: Server depressed, needs Prozak GNU/Linux 2.4.2-ac28 SMP/ReiserFS 2x1743 bogomips load av: 0.20 0.05 0.01 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: Linux 2.4.2ac19
On Mon, Mar 12, 2001 at 09:19:17PM +0100, J . A . Magallon wrote: > > On 03.12 Alan Cox wrote: > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/ > > > > Silly idea: could you put the full path of the bz2 patch instead of only > the dir ? > I have another idea: would it be possible to start a new tree alan/2.4.3/ when the 2.4.3 patches begin? Piling everything in 2.4/ isn't making things clearer. Jurriaan -- When you stick your fingers in the mains, its not the imaginary component which you will feel. >From an EIST lecturer GNU/Linux 2.4.2-ac19 SMP/ReiserFS 2x1743 bogomips load av: 0.02 0.12 0.08 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: Linux 2.4.2ac19
On Mon, Mar 12, 2001 at 09:19:17PM +0100, J . A . Magallon wrote: On 03.12 Alan Cox wrote: ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/ Silly idea: could you put the full path of the bz2 patch instead of only the dir ? I have another idea: would it be possible to start a new tree alan/2.4.3/ when the 2.4.3 patches begin? Piling everything in 2.4/ isn't making things clearer. Jurriaan -- When you stick your fingers in the mains, its not the imaginary component which you will feel. From an EIST lecturer GNU/Linux 2.4.2-ac19 SMP/ReiserFS 2x1743 bogomips load av: 0.02 0.12 0.08 - 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 FAQ at http://www.tux.org/lkml/
2.4.2-ac13 es1370.o module and verbose bug reporting
make -C arch/i386/lib modules_install
make[1]: Entering directory `/usr/src/linux-2.4.2-ac13/arch/i386/lib'
make[1]: Nothing to be done for `modules_install'.
make[1]: Leaving directory `/usr/src/linux-2.4.2-ac13/arch/i386/lib'
cd /lib/modules/2.4.2-ac13; \
mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.2-ac13; fi
depmod: *** Unresolved symbols in /lib/modules/2.4.2-ac13/kernel/drivers/sound/es1370.o
depmod: do_BUG
CONFIG_SOUND_ES1370=m
CONFIG_DEBUG_BUGVERBOSE=y
If I set
CONFIG_DEBUG_BUGVERBOSE=n
it works as expected.
Good luck,
Jurriaan
--
The documentation is in Japanese. Good luck.
Rich
GNU/Linux 2.4.2-ac12 SMP/ReiserFS 2x1743 bogomips load av: 0.34 0.08 0.02
-
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 FAQ at http://www.tux.org/lkml/
2.4.2-ac13 es1370.o module and verbose bug reporting
make -C arch/i386/lib modules_install
make[1]: Entering directory `/usr/src/linux-2.4.2-ac13/arch/i386/lib'
make[1]: Nothing to be done for `modules_install'.
make[1]: Leaving directory `/usr/src/linux-2.4.2-ac13/arch/i386/lib'
cd /lib/modules/2.4.2-ac13; \
mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.2-ac13; fi
depmod: *** Unresolved symbols in /lib/modules/2.4.2-ac13/kernel/drivers/sound/es1370.o
depmod: do_BUG
CONFIG_SOUND_ES1370=m
CONFIG_DEBUG_BUGVERBOSE=y
If I set
CONFIG_DEBUG_BUGVERBOSE=n
it works as expected.
Good luck,
Jurriaan
--
The documentation is in Japanese. Good luck.
Rich
GNU/Linux 2.4.2-ac12 SMP/ReiserFS 2x1743 bogomips load av: 0.34 0.08 0.02
-
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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: reiserfs: still problems with tail conversion
On Sat, Feb 24, 2001 at 04:45:04PM +0100, Arjan Filius wrote: > Hello, > > I tried Erik's trigger-program. > > After some test i thing it's memory related, and it seems to match the > other reports i saw on lkm. > With my 384M ram i was not able te reproduce it. > With "mem=32M" linux hang while starting a test oracle-db. > However i tried (not repeated tests, and after a fresh reboot): > ram=128M ; Triggered > ram=138M ; Triggered > ram=180M ; Triggered > ram=192M ; NOT Triggered > ram=250M ; NOT Triggered > ram=256M ; NOT Triggered > > These results say that it memory dependent, and perhaps memory use > dependent. > With the mem=180M i did some additional tests: > > reisertest; triggered > free ; shows only 60M on cached data and 8192 files*8192 > bytes=64M > /sbin/swapout 100M; make sure enough cache to hold 64M data > reisertest; NOT Triggered > While leaving the data, and executing reisertest in a new dir i'm > triggring it again! > > So i think i can say, it's triggerable when the cache has no space to hold > all the data (64M), but i didn't extensive tests. > I can't confirm that. This machine has 512 Mb memory: free total used free sharedbuffers cached Mem:512940 144916 368024 0 12052 106552 -/+ buffers/cache: 26312 486628 Swap: 1992052 01992052 total used free sharedbuffers cached Mem:512940 144924 368016 0 12052 106552 -/+ buffers/cache: 26320 486620 Swap: 1992052 01992052 Jurriaan -- BOFH excuse #167: excessive collisions & not enough packet ambulances GNU/Linux 2.4.2-ac3 SMP/ReiserFS 2x1730 bogomips load av: 0.26 0.06 0.02 - 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 FAQ at http://www.tux.org/lkml/
Re: reiserfs: still problems with tail conversion
On Fri, Feb 23, 2001 at 11:19:49PM +0100, Erik Mouw wrote: > I got them immediately at the first run, which more or less was what I > expected because reiserfs ate one of my mailfolders that way (only a > CVS log folder, so nothing special was lost). You have to remove the > files between runs, otherwise the same blocks seem to be allocated to > the files. > > I'll upgrade to linux-2.4.2 to see if it solves the problem. (was > running 2.4.2-pre4 + your patch) > kernel 2.4.2-ac3, gcc-2.95.2, libc-2.1.3, SuSE-7.0 base system. Using ReiserFS 3.5.x disk format, binutils-2.10, x86(P3/866)-SMP system. The program from Erik did the following: Creating 8192 files ... done Appending to the files ... done Checking files for null bytes ... reiser-0.test contains null bytes reiser-1.test contains null bytes reiser-2.test contains null bytes reiser-3.test contains null bytes reiser-4.test contains null bytes reiser-08189.test contains null bytes reiser-08190.test contains null bytes reiser-08191.test contains null bytes Checking done Good luck, Jurriaan -- Backup Not Found (A)ssasinate Bill Gates (R)etry (K)eep trying until 6 am? GNU/Linux 2.4.2-ac3 SMP/ReiserFS 2x1730 bogomips load av: 0.08 0.02 0.01 - 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 FAQ at http://www.tux.org/lkml/
Re: reiserfs: still problems with tail conversion
On Fri, Feb 23, 2001 at 11:19:49PM +0100, Erik Mouw wrote: I got them immediately at the first run, which more or less was what I expected because reiserfs ate one of my mailfolders that way (only a CVS log folder, so nothing special was lost). You have to remove the files between runs, otherwise the same blocks seem to be allocated to the files. I'll upgrade to linux-2.4.2 to see if it solves the problem. (was running 2.4.2-pre4 + your patch) kernel 2.4.2-ac3, gcc-2.95.2, libc-2.1.3, SuSE-7.0 base system. Using ReiserFS 3.5.x disk format, binutils-2.10, x86(P3/866)-SMP system. The program from Erik did the following: Creating 8192 files ... done Appending to the files ... done Checking files for null bytes ... reiser-0.test contains null bytes reiser-1.test contains null bytes reiser-2.test contains null bytes reiser-3.test contains null bytes reiser-4.test contains null bytes snip a lot of lines reiser-08189.test contains null bytes reiser-08190.test contains null bytes reiser-08191.test contains null bytes Checking done Good luck, Jurriaan -- Backup Not Found (A)ssasinate Bill Gates (R)etry (K)eep trying until 6 am? GNU/Linux 2.4.2-ac3 SMP/ReiserFS 2x1730 bogomips load av: 0.08 0.02 0.01 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]Re: reiserfs: still problems with tail conversion
On Sat, Feb 24, 2001 at 04:45:04PM +0100, Arjan Filius wrote: Hello, I tried Erik's trigger-program. After some test i thing it's memory related, and it seems to match the other reports i saw on lkm. With my 384M ram i was not able te reproduce it. With "mem=32M" linux hang while starting a test oracle-db. However i tried (not repeated tests, and after a fresh reboot): ram=128M ; Triggered ram=138M ; Triggered ram=180M ; Triggered ram=192M ; NOT Triggered ram=250M ; NOT Triggered ram=256M ; NOT Triggered These results say that it memory dependent, and perhaps memory use dependent. With the mem=180M i did some additional tests: reisertest; triggered free ; shows only 60M on cached data and 8192 files*8192 bytes=64M /sbin/swapout 100M; make sure enough cache to hold 64M data reisertest; NOT Triggered While leaving the data, and executing reisertest in a new dir i'm triggring it again! So i think i can say, it's triggerable when the cache has no space to hold all the data (64M), but i didn't extensive tests. I can't confirm that. This machine has 512 Mb memory: free total used free sharedbuffers cached Mem:512940 144916 368024 0 12052 106552 -/+ buffers/cache: 26312 486628 Swap: 1992052 01992052 after the failing test total used free sharedbuffers cached Mem:512940 144924 368016 0 12052 106552 -/+ buffers/cache: 26320 486620 Swap: 1992052 01992052 Jurriaan -- BOFH excuse #167: excessive collisions not enough packet ambulances GNU/Linux 2.4.2-ac3 SMP/ReiserFS 2x1730 bogomips load av: 0.26 0.06 0.02 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]2.2.19pre13: Are there network problem with a low-bandwidth link?
On Mon, Feb 19, 2001 at 08:38:43AM -0500, TenThumbs wrote: > When I am a) using modem ppp connection and b) downloading a file from a > reasonably fast server so that the incoming connection is saturated, > then attempting to open a new network tcp connection while this is going > on fails quite regularly. The user app gets a ECONNRESET error. > > This never happens if the link is idle or lightly loaded. Heavy load is > extremely important. > I also saw this when my 2.2.19pre12/13 workstation connected to a 2.2.19pre8 isdn-router. When downloading a large file via ftp at max speed, other connections don't 'get through'. Perhaps other people can agree/disagree on this? Jurriaan -- I never deny, I never contradict. I sometimes forget. Benjamin Disraeli GNU/Linux 2.4.1-ac19 SMP/ReiserFS 2x1402 bogomips load av: 0.01 0.06 0.26 - 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 FAQ at http://www.tux.org/lkml/
Re: [lkml]2.2.19pre13: Are there network problem with a low-bandwidth link?
On Mon, Feb 19, 2001 at 08:38:43AM -0500, TenThumbs wrote: When I am a) using modem ppp connection and b) downloading a file from a reasonably fast server so that the incoming connection is saturated, then attempting to open a new network tcp connection while this is going on fails quite regularly. The user app gets a ECONNRESET error. snip This never happens if the link is idle or lightly loaded. Heavy load is extremely important. I also saw this when my 2.2.19pre12/13 workstation connected to a 2.2.19pre8 isdn-router. When downloading a large file via ftp at max speed, other connections don't 'get through'. Perhaps other people can agree/disagree on this? Jurriaan -- I never deny, I never contradict. I sometimes forget. Benjamin Disraeli GNU/Linux 2.4.1-ac19 SMP/ReiserFS 2x1402 bogomips load av: 0.01 0.06 0.26 - 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 FAQ at http://www.tux.org/lkml/
Re: 2.2.19pre10 locks up hard on unloading the isdn module 'hisax.o' - 2.2.19pre11 does too!
>SMP machine, 2x P3/700 on an Abit VP6.
>Never any trouble with the earlier 2.2.19pre's.
>
>a strace shows the hang to be in the delete_module("hisax") call.
>
>I'm having trouble with the sysrq-key, but I hope this is enough since
>there were some changes w.r.t. modules/locking etc. in pre10.
>
It's Linux, after all, so 2 minutes after creating this email
2.2.19pre11's announcement was here. I just tested it, and it has the
same problem.
from my config:
ISDN subsystem
#
CONFIG_ISDN=m
CONFIG_ISDN_PPP=y
CONFIG_ISDN_PPP_VJ=y
CONFIG_ISDN_DRV_HISAX=m
CONFIG_HISAX_EURO=y
CONFIG_HISAX_W6692=y
Now, it's just one more crash and back to 2.2.19pre9 for me!
Good luck,
Jurriaan
--
When God is on the Bodhran
The atoms want to dance
Oysterband - In your eyes
GNU/Linux 2.2.19pre11 SMP/ReiserFS 2x1402 bogomips load av: 0.05 0.34 0.20
-
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 FAQ at http://www.tux.org/lkml/
2.2.19pre10 locks up hard on unloading the isdn module 'hisax.o'
SMP machine, 2x P3/700 on an Abit VP6.
Never any trouble with the earlier 2.2.19pre's.
a strace shows the hang to be in the delete_module("hisax") call.
I'm having trouble with the sysrq-key, but I hope this is enough since
there were some changes w.r.t. modules/locking etc. in pre10.
Good luck,
Jurriaan
--
The guy sure looks like plantfood to me
Little Shop of Horrors
GNU/Linux 2.2.19pre10 SMP/ReiserFS 2x1402 bogomips load av: 0.02 0.05 0.05
-
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 FAQ at http://www.tux.org/lkml/
