* 2.6.0-test8-mm1
@ 2003-10-20 9:05 ` Andrew Morton
0 siblings, 0 replies; 61+ messages in thread
From: Andrew Morton @ 2003-10-20 9:05 UTC (permalink / raw)
To: linux-kernel, linux-mm
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test8/2.6.0-test8-mm1
. Included a much updated fbdev patch. Anyone who is using framebuffers,
please test this.
. Quite a large number of stability fixes.
Changes since 2.6.0-test7-mm1:
-RD0-initrd-B6.patch
-sjcd-usercopy-checks.patch
-might_sleep-vs-jiffies-wrap.patch
-selinux-add-policyvers.patch
-mandocs-case-fix.patch
-swapon-handle-no-readpage.patch
-reiserfs-url-fixes.patch
-numaq-mpc-warning-fix.patch
-invalidate_inodes-speedup.patch
-invalidate_inodes-speedup-fixes.patch
-ide-piix-fallback-fix.patch
-ext3-i_disksize-locking-fix.patch
-applicom-fixes.patch
-acl-signedness-fix.patch
-saa7134-build-fix.patch
-ide-write-barrier-support.patch
-jbd-barrier-selection.patch
Merged
-vma-split-truncate-race-fix.patch
-vma-split-truncate-race-fix-tweaks.patch
+vma-split-truncate-race-fix-2.patch
Fix a race between vma_split() and truncation (rebased to Linus's tree)
+devfs-initrd-fix.patch
Fix initrd when devfs is in use
-ppc64-semaphore-reimplementation.patch
Dropped; it didn't solve the starvation problems anyway.
-ppc64-sym2-fix.patch
No longer needed.
-cursor-flashing-fix.patch
-radeonfb-line_length-fix.patch
Fixed in fbdev.patch
+fbdev-restore-pci-ids.patch
Fix AGP compilation.
+limit_regions-syncup.patch
Backport 2.4's ia32 "mem=" fix.
+ia32-efi-asm-warning-fix.patch
+ia32-efi-support-mem-equals-fix.patch
+efi-constant-sizing-fix.patch
More fixes for the EFI patch.
+fix-sqrt.patch
Fix int_sqrt().
scale-min_free_kbytes.patch
Fixed version.
+cdrom-allocation-try-harder.patch
Avoid order-4 memory allocations failures when opening CDROM devices.
+atp870u-oops-fix.patch
Fix an init-time oops in this driver.
+tmpfs-01-ENAMETOOLONG.patch
+tmpfs-02-gid-fix.patch
+tmpfs-03-swapoff-truncate-race.patch
+tmpfs-04-getpage-truncate-race.patch
+tmpfs-05-writepage-truncate-race.patch
+tmpfs-06-i_size_write.patch
+tmpfs-07-write-mark_page_accessed.patch
tmpfs fixes.
+quota-locking-fix.patch
Quota deadlock fix.
+export-system_running.patch
+might_sleep-early-bogons.patch
Stomp all the early might_sleep() warnings.
+constant_test_bit-doesnt-like-zwanes-gcc.patch
Workaround a gcc bug.
+slab-leak-detector.patch
+slab-leak-detector-tweaks.patch
A slab debugging tool for finding memory leaks: do
echo "slab-name 0 0 0" > /proc/slabinfo
and the kernel will inspect each live object in that cache and will print
out the code address from which the allocation was performed.
+digi_accelport-oops-fix.patch
Fix an oops in this driver.
+microcode-build-fix.patch
Microcode compile fix
+early-serial-registration-fix.patch
Fix crashes with early printk console registration.
+mtd-warning-fixes.patch
Fix a couple of warnings.
+early_serial_setup-range-check.patch
Another early printk fix.
+elf-verify-interpreter-arch.patch
Additional checks when loading ELF interpreters.
+journal_write_metadata_buffer-kfree-fix.patch
Fix kfree of an incorrect address.
+jbd-leak-fix.patch
Fix ext3 memory leak.
+kmem_freepages-BUG-fix.patch
Fix a BUG which can strike in slab.
+register_cpu-fix.patch
Dunno what this does really. Someone want to send me a decent changelog
for once?
+elv-select.patch
Runtime selectable I/O schedulers.
+elv-init-cleanup.patch
Elevator initialisation cleanups.
+bluetooth-no-procfs-fix.patch
Fix bluetooth compile with CONFIG_PROCFS=n
+gcc-Os.patch
Compile with -Os
+printk-handle-bad-pointers.patch
Make printk kinder when passed nearly-NULL pointers.
+kcapi-build-fix.patch
ISDN compile fix
+drm-module_init-retval-fix.patch
Fix an error code.
+parport_pc-resource-release-fix.patch
Fix an oopsable resource leak in parport_pc.
+3c527-smp-update.patch
Update this driver, make it work on SMP.
+3c527-module-license.patch
It is GPLed.
+no-mca-oops-fix.patch
+mca_find_unused_adapter-oops-fix.patch
Fix a couple of oopses when running CONFIG_MCA kernels on non-MCA hardware.
+register_netdevice-retval-fix.patch
Fix error code propagation.
+ext3-latency-fix.patch
Improved scheduling latency in ext3.
+ipc-msg-race-fix.patch
Fix oopsable race in SVSV IPC message tx/rx.
+iosched-oops-fixes.patch
Fix use-uninitialised in the deadline and AS I/O schedulers.
+pcm_native-deadlock-fix.patch
Fix a deadlock in the sound drivers.
+4g4g-wp-test-fix.patch
Fix a crash when doing the early WP detect with the 4g/4g split enabled.
+O_DIRECT-race-fixes-rework-XFS-fix-fix.patch
EXPORT_SYMBOL() fix.
All 178 patches:
mm.patch
add -mmN to EXTRAVERSION
kgdb-ga.patch
kgdb stub for ia32 (George Anzinger's one)
kgdbL warning fix
kgdb-buff-too-big.patch
kgdb buffer overflow fix
kgdb-warning-fix.patch
kgdbL warning fix
kgdb-build-fix.patch
kgdb-spinlock-fix.patch
kgdb-fix-debug-info.patch
kgdb: CONFIG_DEBUG_INFO fix
kgdb-cpumask_t.patch
kgdb-x86_64-fixes.patch
x86_64 fixes
kgdb-over-ethernet.patch
kgdb-over-ethernet patch
kgdb-over-ethernet-fixes.patch
kgdb-over-ethernet fixlets
kgdb-CONFIG_NET_POLL_CONTROLLER.patch
kgdb: replace CONFIG_KGDB with CONFIG_NET_RX_POLL in net drivers
kgdb-handle-stopped-NICs.patch
kgdb: handle netif_stopped NICs
eepro100-poll-controller.patch
tlan-poll_controller.patch
tulip-poll_controller.patch
tg3-poll_controller.patch
kgdb: tg3 poll_controller
8139too-poll_controller.patch
8139too poll controller
kgdb-eth-smp-fix.patch
kgdb-over-ethernet: fix SMP
kgdb-eth-reattach.patch
kgdb-skb_reserve-fix.patch
kgdb-over-ethernet: skb_reserve() fix
must-fix.patch
should-fix.patch
vma-split-truncate-race-fix-2.patch
fix split_vma vs. invalidate_mmap_range_list race
devfs-initrd-fix.patch
Fix initrd with devfs enabled
RD1-cdrom_ioctl-B6.patch
RD2-ioctl-B6.patch
RD2-ioctl-B6-fix.patch
RD2-ioctl-B6 fixes
RD3-cdrom_open-B6.patch
RD4-open-B6.patch
RD5-cdrom_release-B6.patch
RD6-release-B6.patch
RD7-presto_journal_close-B6.patch
RD8-f_mapping-B6.patch
RD9-f_mapping2-B6.patch
RD10-i_sem-B6.patch
RD11-f_mapping3-B6.patch
RD12-generic_osync_inode-B6.patch
RD13-bd_acquire-B6.patch
RD14-generic_write_checks-B6.patch
RD15-I_BDEV-B6.patch
RD16-rest-B6.patch
serio-01-renaming.patch
serio: rename serio_[un]register_slave_port to __serio_[un]register_port
serio-02-race-fix.patch
serio: possible race between port removal and kseriod
serio-03-blacklist.patch
Add black list to handler<->device matching
serio-04-synaptics-cleanup.patch
Synaptics: code cleanup
serio-05-reconnect-facility.patch
serio: reconnect facility
serio-06-synaptics-use-reconnect.patch
Synaptics: use serio_reconnect
acpi_off-fix.patch
fix acpi=off
cfq-4.patch
CFQ io scheduler
CFQ fixes
config_spinline.patch
uninline spinlocks for profiling accuracy.
ppc64-bar-0-fix.patch
Allow PCI BARs that start at 0
ppc64-reloc_hide.patch
sym-do-160.patch
make the SYM driver do 160 MB/sec
input-use-after-free-checks.patch
input layer debug checks
fbdev.patch
framebbuffer driver update
fbdev-restore-pci-ids.patch
aic7xxx-parallel-build-fix.patch
fix parallel builds for aic7xxx
ramdisk-cleanup.patch
intel8x0-cleanup.patch
intel8x0 cleanups
uml-update.patch
Update UML to 2.6.0-test5
pdflush-diag.patch
kobject-oops-fixes.patch
fix oopses is kobject parent is removed before child
futex-uninlinings.patch
futex uninlining
zap_page_range-debug.patch
zap_page_range() debug
acpi-thinkpad-fix.patch
APCI fix for thinkpads
scsi-handle-zero-length-requests.patch
scsi: handle zero-length requests
call_usermodehelper-retval-fix-3.patch
Make call_usermodehelper report exit status
asus-L5-fix.patch
Asus L5 framebuffer fix
jffs-use-daemonize.patch
tulip-NAPI-support.patch
tulip NAPI support
tulip-napi-disable.patch
tulip NAPI: disable poll in close
get_user_pages-handle-VM_IO.patch
limit_regions-syncup.patch
ia32 limit_regions update
dynamic-irq_vector-allocation.patch
dynamic irq_vector allocation for ia32
ia32-MSI-support.patch
Updated ia32 MSI Patches
ia32-MSI-support-tweaks.patch
ia32-efi-support.patch
EFI support for ia32
ia32-efi-asm-warning-fix.patch
efi warning fix
ia32-efi-support-mem-equals-fix.patch
CONFIG_ACPI_EFI-defaults-off.patch
ia32-efi-support-warning-fixes.patch
ia32-efi-support-tidy.patch
ia32-efi-other-arch-fix.patch
fix EFI for ppc64, ia64
efi-constant-sizing-fix.patch
efi: warning fixes
support-zillions-of-scsi-disks.patch
support many SCSI disks
SGI-IOC4-IDE-chipset-support.patch
Add support for SGI's IOC4 chipset
sparc32-sched_clock.patch
unmap_vmas-warning-fix.patch
Fix unmap_vmas() compile warning
pcibios_test_irq-fix.patch
Fix pcibios test IRQ handler return
fixmap-in-proc-pid-maps.patch
report user-readable fixmap area in /proc/PID/maps
ajdtimex-vs-gettimeofday.patch
Time precision, adjtime(x) vs. gettimeofday
i82365-sysfs-ordering-fix.patch
Fix init_i82365 sysfs ordering oops
pci_set_power_state-might-sleep.patch
compat_ioctl-cleanup.patch
cleanup of compat_ioctl functions
fix-sqrt.patch
sqrt() fixes
scale-min_free_kbytes.patch
scale the initial value of min_free_kbytes
cdrom-allocation-try-harder.patch
Use __GFP_REPEAT for cdrom buffer
atp870u-oops-fix.patch
atp870u oops fix
sym-2.1.18f.patch
CONFIG_STANDALONE-default-to-n.patch
Make CONFIG_STANDALONE default to N
nosysfs.patch
tmpfs-01-ENAMETOOLONG.patch
tmpfs 1/7 LTP ENAMETOOLONG
tmpfs-02-gid-fix.patch
tmpfs 2/7 LTP S_ISGID dir
tmpfs-03-swapoff-truncate-race.patch
tmpfs 3/7 swapoff/truncate race
tmpfs-04-getpage-truncate-race.patch
tmpfs 4/7 getpage/truncate race
tmpfs-05-writepage-truncate-race.patch
tmpfs 5/7 writepage/truncate race
tmpfs-06-i_size_write.patch
tmpfs 6/7 write i_size_write
tmpfs-07-write-mark_page_accessed.patch
tmpfs 7/7 write mark_page_accessed
quota-locking-fix.patch
Quota locking fix
export-system_running.patch
export system_running to other files
might_sleep-early-bogons.patch
Kill early might_sleep warnings
constant_test_bit-doesnt-like-zwanes-gcc.patch
gcc bug workaround for constant_test_bit()
slab-leak-detector.patch
slab leak detector
slab-leak-detector-tweaks.patch
digi_accelport-oops-fix.patch
digi_acceleport.c has bogus "address of" operator
microcode-build-fix.patch
fix microcode.c for older gcc's
early-serial-registration-fix.patch
serial console registration bugfix
mtd-warning-fixes.patch
Fix mtd printk warnings
early_serial_setup-range-check.patch
early_serial_setup array bounds check
elf-verify-interpreter-arch.patch
fs/binfmt_elf.c:load_elf_binary() doesn't verify interpreter arch
journal_write_metadata_buffer-kfree-fix.patch
JBD kfree() fix
jbd-leak-fix.patch
Fix JBD memory leak
kmem_freepages-BUG-fix.patch
fix low-memory BUG in slab
register_cpu-fix.patch
Subject: [PATCH] fix for register_cpu()
elv-select.patch
disk scheduler selection
elv-init-cleanup.patch
elv_init cleanup
bluetooth-no-procfs-fix.patch
fix bluetooh broken compilation when PROC_FS=n.
gcc-Os.patch
Use -Os for compilation
printk-handle-bad-pointers.patch
make printk more robust with "null" pointers
kcapi-build-fix.patch
kcapi.c CONFIG_MODULES=n build fix
drm-module_init-retval-fix.patch
DRM modprobe retval fix
parport_pc-resource-release-fix.patch
parport_pc not releasing all ioports
3c527-smp-update.patch
SMP support on 3c527 net driver
3c527-module-license.patch
Add 3c527 module license.
no-mca-oops-fix.patch
Fix oops with CONFIG_MCA=y
mca_find_unused_adapter-oops-fix.patch
Fix another CONFIG_MCA=y oops
register_netdevice-retval-fix.patch
register_netdevice return val fix
ext3-latency-fix.patch
ext3 scheduling latency fix
ipc-msg-race-fix.patch
ipc msg race fix
iosched-oops-fixes.patch
io scheduler oops fixes
pcm_native-deadlock-fix.patch
pcm_native locking fix
keyboard-repeat-rate-setting-fix.patch
keyboard repeat rate setting fix
list_del-debug.patch
list_del debug check
print-build-options-on-oops.patch
print a few config options on oops
show_task-free-stack-fix.patch
show_task() fix and cleanup
oops-dump-preceding-code.patch
i386 oops output: dump preceding code
lockmeter.patch
printk-oops-mangle-fix.patch
disentangle printk's whilst oopsing on SMP
4g-2.6.0-test2-mm2-A5.patch
4G/4G split patch
4G/4G: remove debug code
4g4g: pmd fix
4g/4g: fixes from Bill
4g4g: fpu emulation fix
4g/4g usercopy atomicity fix
4G/4G: remove debug code
4g4g: pmd fix
4g/4g: fixes from Bill
4g4g: fpu emulation fix
4g/4g usercopy atomicity fix
4G/4G preempt on vstack
4G/4G: even number of kmap types
4g4g: fix __get_user in slab
4g4g: Remove extra .data.idt section definition
4g/4g linker error (overlapping sections)
4G/4G: remove debug code
4g4g: pmd fix
4g/4g: fixes from Bill
4g4g: fpu emulation fix
4g4g: show_registers() fix
4g/4g usercopy atomicity fix
4g4g: debug flags fix
4g4g: Fix wrong asm-offsets entry
cyclone time fixmap fix
4G/4G preempt on vstack
4G/4G: even number of kmap types
4g4g: fix __get_user in slab
4g4g: Remove extra .data.idt section definition
4g/4g linker error (overlapping sections)
4G/4G: remove debug code
4g4g: pmd fix
4g/4g: fixes from Bill
4g4g: fpu emulation fix
4g4g: show_registers() fix
4g/4g usercopy atomicity fix
4g4g: debug flags fix
4g4g: Fix wrong asm-offsets entry
cyclone time fixmap fix
use direct_copy_{to,from}_user for kernel access in mm/usercopy.c
4G/4G might_sleep warning fix
4g/4g pagetable accounting fix
4g4g-athlon-prefetch-handling-fix.patch
4g4g-wp-test-fix.patch
Fix 4G/4G and WP test lockup
ppc-fixes.patch
make mm4 compile on ppc
aic7xxx_old-oops-fix.patch
O_DIRECT-race-fixes-rollup.patch
DIO fixes forward port and AIO-DIO fix
O_DIRECT race fixes comments
O_DRIECT race fixes fix fix fix
DIO locking rework
O_DIRECT-race-fixes-rework-XFS-fix.patch
O_DIRECT XFS fix
O_DIRECT-race-fixes-rework-XFS-fix-fix.patch
aio-01-retry.patch
AIO: Core retry infrastructure
Fix aio process hang on EINVAL
AIO: flush workqueues before destroying ioctx'es
AIO: hold the context lock across unuse_mm
task task_lock in use_mm()
4g4g-aio-hang-fix.patch
Fix AIO and 4G-4G hang
aio-refcounting-fix.patch
aio ref count in io_submit_one
aio-retry-elevated-refcount.patch
aio: extra ref count during retry
aio-splice-runlist.patch
Splice AIO runlist for fairer handling of multiple io contexts
aio-02-lockpage_wq.patch
AIO: Async page wait
aio-03-fs_read.patch
AIO: Filesystem aio read
aio-04-buffer_wq.patch
AIO: Async buffer wait
lock_buffer_wq fix
aio-05-fs_write.patch
AIO: Filesystem aio write
aio-06-bread_wq.patch
AIO: Async block read
aio-07-ext2getblk_wq.patch
AIO: Async get block for ext2
O_SYNC-speedup-2.patch
speed up O_SYNC writes
O_SYNC-speedup-2-f_mapping-fixes.patch
aio-09-o_sync.patch
aio O_SYNC
AIO: fix a BUG
Unify o_sync changes for aio and regular writes
aio-O_SYNC-fix bits got lost
aio: writev nr_segs fix
More AIO O_SYNC related fixes
aio-09-o_sync-f_mapping-fixes.patch
gang_lookup_next.patch
Change the page gang lookup API
aio-gang_lookup-fix.patch
AIO gang lookup fixes
aio-O_SYNC-short-write-fix.patch
Fix for O_SYNC short writes
aio-12-readahead.patch
AIO: readahead fixes
aio O_DIRECT no readahead
Unified page range readahead for aio and regular reads
aio-12-readahead-f_mapping-fix.patch
aio-readahead-speedup.patch
Readahead issues and AIO read speedup
^ permalink raw reply [flat|nested] 61+ messages in thread
* 2.6.0-test8-mm1
@ 2003-10-20 9:05 ` Andrew Morton
0 siblings, 0 replies; 61+ messages in thread
From: Andrew Morton @ 2003-10-20 9:05 UTC (permalink / raw)
To: linux-kernel, linux-mm
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test8/2.6.0-test8-mm1
. Included a much updated fbdev patch. Anyone who is using framebuffers,
please test this.
. Quite a large number of stability fixes.
Changes since 2.6.0-test7-mm1:
-RD0-initrd-B6.patch
-sjcd-usercopy-checks.patch
-might_sleep-vs-jiffies-wrap.patch
-selinux-add-policyvers.patch
-mandocs-case-fix.patch
-swapon-handle-no-readpage.patch
-reiserfs-url-fixes.patch
-numaq-mpc-warning-fix.patch
-invalidate_inodes-speedup.patch
-invalidate_inodes-speedup-fixes.patch
-ide-piix-fallback-fix.patch
-ext3-i_disksize-locking-fix.patch
-applicom-fixes.patch
-acl-signedness-fix.patch
-saa7134-build-fix.patch
-ide-write-barrier-support.patch
-jbd-barrier-selection.patch
Merged
-vma-split-truncate-race-fix.patch
-vma-split-truncate-race-fix-tweaks.patch
+vma-split-truncate-race-fix-2.patch
Fix a race between vma_split() and truncation (rebased to Linus's tree)
+devfs-initrd-fix.patch
Fix initrd when devfs is in use
-ppc64-semaphore-reimplementation.patch
Dropped; it didn't solve the starvation problems anyway.
-ppc64-sym2-fix.patch
No longer needed.
-cursor-flashing-fix.patch
-radeonfb-line_length-fix.patch
Fixed in fbdev.patch
+fbdev-restore-pci-ids.patch
Fix AGP compilation.
+limit_regions-syncup.patch
Backport 2.4's ia32 "mem=" fix.
+ia32-efi-asm-warning-fix.patch
+ia32-efi-support-mem-equals-fix.patch
+efi-constant-sizing-fix.patch
More fixes for the EFI patch.
+fix-sqrt.patch
Fix int_sqrt().
scale-min_free_kbytes.patch
Fixed version.
+cdrom-allocation-try-harder.patch
Avoid order-4 memory allocations failures when opening CDROM devices.
+atp870u-oops-fix.patch
Fix an init-time oops in this driver.
+tmpfs-01-ENAMETOOLONG.patch
+tmpfs-02-gid-fix.patch
+tmpfs-03-swapoff-truncate-race.patch
+tmpfs-04-getpage-truncate-race.patch
+tmpfs-05-writepage-truncate-race.patch
+tmpfs-06-i_size_write.patch
+tmpfs-07-write-mark_page_accessed.patch
tmpfs fixes.
+quota-locking-fix.patch
Quota deadlock fix.
+export-system_running.patch
+might_sleep-early-bogons.patch
Stomp all the early might_sleep() warnings.
+constant_test_bit-doesnt-like-zwanes-gcc.patch
Workaround a gcc bug.
+slab-leak-detector.patch
+slab-leak-detector-tweaks.patch
A slab debugging tool for finding memory leaks: do
echo "slab-name 0 0 0" > /proc/slabinfo
and the kernel will inspect each live object in that cache and will print
out the code address from which the allocation was performed.
+digi_accelport-oops-fix.patch
Fix an oops in this driver.
+microcode-build-fix.patch
Microcode compile fix
+early-serial-registration-fix.patch
Fix crashes with early printk console registration.
+mtd-warning-fixes.patch
Fix a couple of warnings.
+early_serial_setup-range-check.patch
Another early printk fix.
+elf-verify-interpreter-arch.patch
Additional checks when loading ELF interpreters.
+journal_write_metadata_buffer-kfree-fix.patch
Fix kfree of an incorrect address.
+jbd-leak-fix.patch
Fix ext3 memory leak.
+kmem_freepages-BUG-fix.patch
Fix a BUG which can strike in slab.
+register_cpu-fix.patch
Dunno what this does really. Someone want to send me a decent changelog
for once?
+elv-select.patch
Runtime selectable I/O schedulers.
+elv-init-cleanup.patch
Elevator initialisation cleanups.
+bluetooth-no-procfs-fix.patch
Fix bluetooth compile with CONFIG_PROCFS=n
+gcc-Os.patch
Compile with -Os
+printk-handle-bad-pointers.patch
Make printk kinder when passed nearly-NULL pointers.
+kcapi-build-fix.patch
ISDN compile fix
+drm-module_init-retval-fix.patch
Fix an error code.
+parport_pc-resource-release-fix.patch
Fix an oopsable resource leak in parport_pc.
+3c527-smp-update.patch
Update this driver, make it work on SMP.
+3c527-module-license.patch
It is GPLed.
+no-mca-oops-fix.patch
+mca_find_unused_adapter-oops-fix.patch
Fix a couple of oopses when running CONFIG_MCA kernels on non-MCA hardware.
+register_netdevice-retval-fix.patch
Fix error code propagation.
+ext3-latency-fix.patch
Improved scheduling latency in ext3.
+ipc-msg-race-fix.patch
Fix oopsable race in SVSV IPC message tx/rx.
+iosched-oops-fixes.patch
Fix use-uninitialised in the deadline and AS I/O schedulers.
+pcm_native-deadlock-fix.patch
Fix a deadlock in the sound drivers.
+4g4g-wp-test-fix.patch
Fix a crash when doing the early WP detect with the 4g/4g split enabled.
+O_DIRECT-race-fixes-rework-XFS-fix-fix.patch
EXPORT_SYMBOL() fix.
All 178 patches:
mm.patch
add -mmN to EXTRAVERSION
kgdb-ga.patch
kgdb stub for ia32 (George Anzinger's one)
kgdbL warning fix
kgdb-buff-too-big.patch
kgdb buffer overflow fix
kgdb-warning-fix.patch
kgdbL warning fix
kgdb-build-fix.patch
kgdb-spinlock-fix.patch
kgdb-fix-debug-info.patch
kgdb: CONFIG_DEBUG_INFO fix
kgdb-cpumask_t.patch
kgdb-x86_64-fixes.patch
x86_64 fixes
kgdb-over-ethernet.patch
kgdb-over-ethernet patch
kgdb-over-ethernet-fixes.patch
kgdb-over-ethernet fixlets
kgdb-CONFIG_NET_POLL_CONTROLLER.patch
kgdb: replace CONFIG_KGDB with CONFIG_NET_RX_POLL in net drivers
kgdb-handle-stopped-NICs.patch
kgdb: handle netif_stopped NICs
eepro100-poll-controller.patch
tlan-poll_controller.patch
tulip-poll_controller.patch
tg3-poll_controller.patch
kgdb: tg3 poll_controller
8139too-poll_controller.patch
8139too poll controller
kgdb-eth-smp-fix.patch
kgdb-over-ethernet: fix SMP
kgdb-eth-reattach.patch
kgdb-skb_reserve-fix.patch
kgdb-over-ethernet: skb_reserve() fix
must-fix.patch
should-fix.patch
vma-split-truncate-race-fix-2.patch
fix split_vma vs. invalidate_mmap_range_list race
devfs-initrd-fix.patch
Fix initrd with devfs enabled
RD1-cdrom_ioctl-B6.patch
RD2-ioctl-B6.patch
RD2-ioctl-B6-fix.patch
RD2-ioctl-B6 fixes
RD3-cdrom_open-B6.patch
RD4-open-B6.patch
RD5-cdrom_release-B6.patch
RD6-release-B6.patch
RD7-presto_journal_close-B6.patch
RD8-f_mapping-B6.patch
RD9-f_mapping2-B6.patch
RD10-i_sem-B6.patch
RD11-f_mapping3-B6.patch
RD12-generic_osync_inode-B6.patch
RD13-bd_acquire-B6.patch
RD14-generic_write_checks-B6.patch
RD15-I_BDEV-B6.patch
RD16-rest-B6.patch
serio-01-renaming.patch
serio: rename serio_[un]register_slave_port to __serio_[un]register_port
serio-02-race-fix.patch
serio: possible race between port removal and kseriod
serio-03-blacklist.patch
Add black list to handler<->device matching
serio-04-synaptics-cleanup.patch
Synaptics: code cleanup
serio-05-reconnect-facility.patch
serio: reconnect facility
serio-06-synaptics-use-reconnect.patch
Synaptics: use serio_reconnect
acpi_off-fix.patch
fix acpi=off
cfq-4.patch
CFQ io scheduler
CFQ fixes
config_spinline.patch
uninline spinlocks for profiling accuracy.
ppc64-bar-0-fix.patch
Allow PCI BARs that start at 0
ppc64-reloc_hide.patch
sym-do-160.patch
make the SYM driver do 160 MB/sec
input-use-after-free-checks.patch
input layer debug checks
fbdev.patch
framebbuffer driver update
fbdev-restore-pci-ids.patch
aic7xxx-parallel-build-fix.patch
fix parallel builds for aic7xxx
ramdisk-cleanup.patch
intel8x0-cleanup.patch
intel8x0 cleanups
uml-update.patch
Update UML to 2.6.0-test5
pdflush-diag.patch
kobject-oops-fixes.patch
fix oopses is kobject parent is removed before child
futex-uninlinings.patch
futex uninlining
zap_page_range-debug.patch
zap_page_range() debug
acpi-thinkpad-fix.patch
APCI fix for thinkpads
scsi-handle-zero-length-requests.patch
scsi: handle zero-length requests
call_usermodehelper-retval-fix-3.patch
Make call_usermodehelper report exit status
asus-L5-fix.patch
Asus L5 framebuffer fix
jffs-use-daemonize.patch
tulip-NAPI-support.patch
tulip NAPI support
tulip-napi-disable.patch
tulip NAPI: disable poll in close
get_user_pages-handle-VM_IO.patch
limit_regions-syncup.patch
ia32 limit_regions update
dynamic-irq_vector-allocation.patch
dynamic irq_vector allocation for ia32
ia32-MSI-support.patch
Updated ia32 MSI Patches
ia32-MSI-support-tweaks.patch
ia32-efi-support.patch
EFI support for ia32
ia32-efi-asm-warning-fix.patch
efi warning fix
ia32-efi-support-mem-equals-fix.patch
CONFIG_ACPI_EFI-defaults-off.patch
ia32-efi-support-warning-fixes.patch
ia32-efi-support-tidy.patch
ia32-efi-other-arch-fix.patch
fix EFI for ppc64, ia64
efi-constant-sizing-fix.patch
efi: warning fixes
support-zillions-of-scsi-disks.patch
support many SCSI disks
SGI-IOC4-IDE-chipset-support.patch
Add support for SGI's IOC4 chipset
sparc32-sched_clock.patch
unmap_vmas-warning-fix.patch
Fix unmap_vmas() compile warning
pcibios_test_irq-fix.patch
Fix pcibios test IRQ handler return
fixmap-in-proc-pid-maps.patch
report user-readable fixmap area in /proc/PID/maps
ajdtimex-vs-gettimeofday.patch
Time precision, adjtime(x) vs. gettimeofday
i82365-sysfs-ordering-fix.patch
Fix init_i82365 sysfs ordering oops
pci_set_power_state-might-sleep.patch
compat_ioctl-cleanup.patch
cleanup of compat_ioctl functions
fix-sqrt.patch
sqrt() fixes
scale-min_free_kbytes.patch
scale the initial value of min_free_kbytes
cdrom-allocation-try-harder.patch
Use __GFP_REPEAT for cdrom buffer
atp870u-oops-fix.patch
atp870u oops fix
sym-2.1.18f.patch
CONFIG_STANDALONE-default-to-n.patch
Make CONFIG_STANDALONE default to N
nosysfs.patch
tmpfs-01-ENAMETOOLONG.patch
tmpfs 1/7 LTP ENAMETOOLONG
tmpfs-02-gid-fix.patch
tmpfs 2/7 LTP S_ISGID dir
tmpfs-03-swapoff-truncate-race.patch
tmpfs 3/7 swapoff/truncate race
tmpfs-04-getpage-truncate-race.patch
tmpfs 4/7 getpage/truncate race
tmpfs-05-writepage-truncate-race.patch
tmpfs 5/7 writepage/truncate race
tmpfs-06-i_size_write.patch
tmpfs 6/7 write i_size_write
tmpfs-07-write-mark_page_accessed.patch
tmpfs 7/7 write mark_page_accessed
quota-locking-fix.patch
Quota locking fix
export-system_running.patch
export system_running to other files
might_sleep-early-bogons.patch
Kill early might_sleep warnings
constant_test_bit-doesnt-like-zwanes-gcc.patch
gcc bug workaround for constant_test_bit()
slab-leak-detector.patch
slab leak detector
slab-leak-detector-tweaks.patch
digi_accelport-oops-fix.patch
digi_acceleport.c has bogus "address of" operator
microcode-build-fix.patch
fix microcode.c for older gcc's
early-serial-registration-fix.patch
serial console registration bugfix
mtd-warning-fixes.patch
Fix mtd printk warnings
early_serial_setup-range-check.patch
early_serial_setup array bounds check
elf-verify-interpreter-arch.patch
fs/binfmt_elf.c:load_elf_binary() doesn't verify interpreter arch
journal_write_metadata_buffer-kfree-fix.patch
JBD kfree() fix
jbd-leak-fix.patch
Fix JBD memory leak
kmem_freepages-BUG-fix.patch
fix low-memory BUG in slab
register_cpu-fix.patch
Subject: [PATCH] fix for register_cpu()
elv-select.patch
disk scheduler selection
elv-init-cleanup.patch
elv_init cleanup
bluetooth-no-procfs-fix.patch
fix bluetooh broken compilation when PROC_FS=n.
gcc-Os.patch
Use -Os for compilation
printk-handle-bad-pointers.patch
make printk more robust with "null" pointers
kcapi-build-fix.patch
kcapi.c CONFIG_MODULES=n build fix
drm-module_init-retval-fix.patch
DRM modprobe retval fix
parport_pc-resource-release-fix.patch
parport_pc not releasing all ioports
3c527-smp-update.patch
SMP support on 3c527 net driver
3c527-module-license.patch
Add 3c527 module license.
no-mca-oops-fix.patch
Fix oops with CONFIG_MCA=y
mca_find_unused_adapter-oops-fix.patch
Fix another CONFIG_MCA=y oops
register_netdevice-retval-fix.patch
register_netdevice return val fix
ext3-latency-fix.patch
ext3 scheduling latency fix
ipc-msg-race-fix.patch
ipc msg race fix
iosched-oops-fixes.patch
io scheduler oops fixes
pcm_native-deadlock-fix.patch
pcm_native locking fix
keyboard-repeat-rate-setting-fix.patch
keyboard repeat rate setting fix
list_del-debug.patch
list_del debug check
print-build-options-on-oops.patch
print a few config options on oops
show_task-free-stack-fix.patch
show_task() fix and cleanup
oops-dump-preceding-code.patch
i386 oops output: dump preceding code
lockmeter.patch
printk-oops-mangle-fix.patch
disentangle printk's whilst oopsing on SMP
4g-2.6.0-test2-mm2-A5.patch
4G/4G split patch
4G/4G: remove debug code
4g4g: pmd fix
4g/4g: fixes from Bill
4g4g: fpu emulation fix
4g/4g usercopy atomicity fix
4G/4G: remove debug code
4g4g: pmd fix
4g/4g: fixes from Bill
4g4g: fpu emulation fix
4g/4g usercopy atomicity fix
4G/4G preempt on vstack
4G/4G: even number of kmap types
4g4g: fix __get_user in slab
4g4g: Remove extra .data.idt section definition
4g/4g linker error (overlapping sections)
4G/4G: remove debug code
4g4g: pmd fix
4g/4g: fixes from Bill
4g4g: fpu emulation fix
4g4g: show_registers() fix
4g/4g usercopy atomicity fix
4g4g: debug flags fix
4g4g: Fix wrong asm-offsets entry
cyclone time fixmap fix
4G/4G preempt on vstack
4G/4G: even number of kmap types
4g4g: fix __get_user in slab
4g4g: Remove extra .data.idt section definition
4g/4g linker error (overlapping sections)
4G/4G: remove debug code
4g4g: pmd fix
4g/4g: fixes from Bill
4g4g: fpu emulation fix
4g4g: show_registers() fix
4g/4g usercopy atomicity fix
4g4g: debug flags fix
4g4g: Fix wrong asm-offsets entry
cyclone time fixmap fix
use direct_copy_{to,from}_user for kernel access in mm/usercopy.c
4G/4G might_sleep warning fix
4g/4g pagetable accounting fix
4g4g-athlon-prefetch-handling-fix.patch
4g4g-wp-test-fix.patch
Fix 4G/4G and WP test lockup
ppc-fixes.patch
make mm4 compile on ppc
aic7xxx_old-oops-fix.patch
O_DIRECT-race-fixes-rollup.patch
DIO fixes forward port and AIO-DIO fix
O_DIRECT race fixes comments
O_DRIECT race fixes fix fix fix
DIO locking rework
O_DIRECT-race-fixes-rework-XFS-fix.patch
O_DIRECT XFS fix
O_DIRECT-race-fixes-rework-XFS-fix-fix.patch
aio-01-retry.patch
AIO: Core retry infrastructure
Fix aio process hang on EINVAL
AIO: flush workqueues before destroying ioctx'es
AIO: hold the context lock across unuse_mm
task task_lock in use_mm()
4g4g-aio-hang-fix.patch
Fix AIO and 4G-4G hang
aio-refcounting-fix.patch
aio ref count in io_submit_one
aio-retry-elevated-refcount.patch
aio: extra ref count during retry
aio-splice-runlist.patch
Splice AIO runlist for fairer handling of multiple io contexts
aio-02-lockpage_wq.patch
AIO: Async page wait
aio-03-fs_read.patch
AIO: Filesystem aio read
aio-04-buffer_wq.patch
AIO: Async buffer wait
lock_buffer_wq fix
aio-05-fs_write.patch
AIO: Filesystem aio write
aio-06-bread_wq.patch
AIO: Async block read
aio-07-ext2getblk_wq.patch
AIO: Async get block for ext2
O_SYNC-speedup-2.patch
speed up O_SYNC writes
O_SYNC-speedup-2-f_mapping-fixes.patch
aio-09-o_sync.patch
aio O_SYNC
AIO: fix a BUG
Unify o_sync changes for aio and regular writes
aio-O_SYNC-fix bits got lost
aio: writev nr_segs fix
More AIO O_SYNC related fixes
aio-09-o_sync-f_mapping-fixes.patch
gang_lookup_next.patch
Change the page gang lookup API
aio-gang_lookup-fix.patch
AIO gang lookup fixes
aio-O_SYNC-short-write-fix.patch
Fix for O_SYNC short writes
aio-12-readahead.patch
AIO: readahead fixes
aio O_DIRECT no readahead
Unified page range readahead for aio and regular reads
aio-12-readahead-f_mapping-fix.patch
aio-readahead-speedup.patch
Readahead issues and AIO read speedup
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 9:05 ` 2.6.0-test8-mm1 Andrew Morton
(?)
@ 2003-10-20 9:40 ` Kirill Korotaev
2003-10-20 9:49 ` 2.6.0-test8-mm1 Andrew Morton
-1 siblings, 1 reply; 61+ messages in thread
From: Kirill Korotaev @ 2003-10-20 9:40 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
Hi!
> -invalidate_inodes-speedup.patch
> -invalidate_inodes-speedup-fixes.patch
Why did you decide to drop these patches out instead of adding fix for them?
Kirill
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 9:40 ` 2.6.0-test8-mm1 Kirill Korotaev
@ 2003-10-20 9:49 ` Andrew Morton
2003-10-20 11:05 ` 2.6.0-test8-mm1 Peter Lieverdink
0 siblings, 1 reply; 61+ messages in thread
From: Andrew Morton @ 2003-10-20 9:49 UTC (permalink / raw)
To: dev; +Cc: linux-kernel
Kirill Korotaev <dev@sw.ru> wrote:
>
> Hi!
>
> > -invalidate_inodes-speedup.patch
> > -invalidate_inodes-speedup-fixes.patch
> Why did you decide to drop these patches out instead of adding fix for them?
>
I would have had to get down, sort out what the heck is happening,
completely review and test these patches. It's not a thing which
I want to be spending time on now.
If someone wants to send me a complete, documented and well-tested patch
then I can drop it in for testing, with a view to merge post-2.6.0.
(I'm also not particularly happy about adding eight(sixteen) bytes to every
inode just to speed up unmount. It's worth thinking about alternatives,
although there are few).
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 9:49 ` 2.6.0-test8-mm1 Andrew Morton
@ 2003-10-20 11:05 ` Peter Lieverdink
2003-10-20 18:49 ` 2.6.0-test8-mm1 Helge Hafting
0 siblings, 1 reply; 61+ messages in thread
From: Peter Lieverdink @ 2003-10-20 11:05 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
Re the new framebuffer code, it appears to not work on matroxfb.
On bootup the console gets as far as:
...
found SMP MP-table at 000f4db0
hm, page 000f4000 reserved twice.
And then it stops, whereas normally the framebuffer would kick in with a pengiun and continue booting.
I boot the kernel with "video=matroxfb:vesa:0x192". When I disable it with "video=matroxfb:off" the system
boots fine.
- Peter.
--
System/Network Administrator Creative Contingencies P/L
http://www.cafuego.net/pgp-key.php for pgp key
Registered Linux user #108200 http://counter.li.org
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 9:05 ` 2.6.0-test8-mm1 Andrew Morton
(?)
(?)
@ 2003-10-20 11:18 ` Thomas Schlichter
-1 siblings, 0 replies; 61+ messages in thread
From: Thomas Schlichter @ 2003-10-20 11:18 UTC (permalink / raw)
To: linux-kernel, linux-mm; +Cc: Andrew Morton
[-- Attachment #1.1: Type: text/plain, Size: 421 bytes --]
On Monday 20 October 2003 11:05, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test8/2
>.6.0-test8-mm1
~~ snip ~~
> +fix-sqrt.patch
>
> Fix int_sqrt().
I really like this one... ;-)
The problem ist that oom_kill.c assumes that int_sqrt() never returns 0. So we
could get a division by zero there :-(
The attached patch fixes that...
Regards
Thomas
[-- Attachment #1.2: fix-oom_kill.diff --]
[-- Type: text/x-diff, Size: 538 bytes --]
--- linux-2.6.0-test8-mm1/mm/oom_kill.c.orig Mon Oct 20 12:49:58 2003
+++ linux-2.6.0-test8-mm1/mm/oom_kill.c Mon Oct 20 12:52:55 2003
@@ -63,8 +63,8 @@
cpu_time = (p->utime + p->stime) >> (SHIFT_HZ + 3);
run_time = (get_jiffies_64() - p->start_time) >> (SHIFT_HZ + 10);
- points /= int_sqrt(cpu_time);
- points /= int_sqrt(int_sqrt(run_time));
+ points /= cpu_time ? int_sqrt(cpu_time) : 1;
+ points /= run_time ? int_sqrt(int_sqrt(run_time)) : 1;
/*
* Niced processes are most likely less important, so double
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 9:05 ` 2.6.0-test8-mm1 Andrew Morton
` (2 preceding siblings ...)
(?)
@ 2003-10-20 13:22 ` Jonathan Brown
2003-10-20 15:00 ` 2.6.0-test8-mm1 Antonio Dolcetta
-1 siblings, 1 reply; 61+ messages in thread
From: Jonathan Brown @ 2003-10-20 13:22 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Mon, 2003-10-20 at 10:05, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test8/2.6.0-test8-mm1
>
>
> . Included a much updated fbdev patch. Anyone who is using framebuffers,
> please test this.
radeon fb is completely broken. Previously I would get multicoloured
garbled text under the penguin over all characters that were visible
before radeon fb loaded, but this would scroll away. Now i still get the
garbled screen, but every character on the screen has an extra white
pixel on producing a grid effect. The kernel then oppses.
This is with a Radeon Mobility M6 LY.
--
Jonathan Brown
http://emergence.uk.net/
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 13:22 ` 2.6.0-test8-mm1 Jonathan Brown
@ 2003-10-20 15:00 ` Antonio Dolcetta
2003-10-20 16:32 ` 2.6.0-test8-mm1 Jonathan Brown
0 siblings, 1 reply; 61+ messages in thread
From: Antonio Dolcetta @ 2003-10-20 15:00 UTC (permalink / raw)
To: akpm; +Cc: linux-kernel
On Mon, 20 Oct 2003 14:22:40 +0100
Jonathan Brown <jbrown@emergence.uk.net> wrote:
> On Mon, 2003-10-20 at 10:05, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test8/2.6.0-test8-mm1
> >
> >
> > . Included a much updated fbdev patch. Anyone who is using framebuffers,
> > please test this.
>
> radeon fb is completely broken. Previously I would get multicoloured
> garbled text under the penguin over all characters that were visible
> before radeon fb loaded, but this would scroll away. Now i still get the
> garbled screen, but every character on the screen has an extra white
> pixel on producing a grid effect. The kernel then oppses.
>
> This is with a Radeon Mobility M6 LY.
>
>
Working perfectly here with radeon 9000
I start it without passing any option to the kernel and it guesses the
correct resolution from BIOS (laptop)
radeonfb_pci_register BEGIN
radeonfb: probed DDR SGRAM 65536k videoram
radeonfb: Invalid ROM signature 0 should be 0xaa55
radeonfb: ref_clk=2700, ref_div=67, xclk=16600 defaults
Starting monitor auto detection...
Non-DDC laptop panel detected
radeonfb: Monitor 1 type LCD found
radeonfb: Monitor 2 type no found
radeonfb: Asssuming panel size 1400x1050
radeonfb: ATI Radeon Lf Mobility M9 DDR SGRAM 64 MB
radeonfb_pci_register END
this is actually the first time the radeon framebuffer has worked for me
that's great!
--
Antonio Dolcetta
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 9:05 ` 2.6.0-test8-mm1 Andrew Morton
@ 2003-10-20 15:32 ` John Cherry
-1 siblings, 0 replies; 61+ messages in thread
From: John Cherry @ 2003-10-20 15:32 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
Full compile stats for mm builds at...
http://developer.osdl.org/cherry/compile/
Kernel version: 2.6.0-test8-mm1
Kernel build:
Making bzImage (defconfig): 0 warnings, 0 errors
Making modules (defconfig): 0 warnings, 0 errors
Making bzImage (allnoconfig): 0 warnings, 0 errors
Making bzImage (allyesconfig): 183 warnings, 0 errors
Making modules (allyesconfig): 13 warnings, 0 errors
Making bzImage (allmodconfig): 3 warnings, 0 errors
Making modules (allmodconfig): 223 warnings, 0 errors
John
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
@ 2003-10-20 15:32 ` John Cherry
0 siblings, 0 replies; 61+ messages in thread
From: John Cherry @ 2003-10-20 15:32 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
Full compile stats for mm builds at...
http://developer.osdl.org/cherry/compile/
Kernel version: 2.6.0-test8-mm1
Kernel build:
Making bzImage (defconfig): 0 warnings, 0 errors
Making modules (defconfig): 0 warnings, 0 errors
Making bzImage (allnoconfig): 0 warnings, 0 errors
Making bzImage (allyesconfig): 183 warnings, 0 errors
Making modules (allyesconfig): 13 warnings, 0 errors
Making bzImage (allmodconfig): 3 warnings, 0 errors
Making modules (allmodconfig): 223 warnings, 0 errors
John
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 9:05 ` 2.6.0-test8-mm1 Andrew Morton
` (4 preceding siblings ...)
(?)
@ 2003-10-20 16:11 ` Thomas Schlichter
2003-10-20 21:48 ` 2.6.0-test8-mm1 Andrew Morton
-1 siblings, 1 reply; 61+ messages in thread
From: Thomas Schlichter @ 2003-10-20 16:11 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
[-- Attachment #1: Type: text/plain, Size: 3088 bytes --]
On Monday 20 October 2003 11:05, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test8/2
>.6.0-test8-mm1
>
>
> . Included a much updated fbdev patch. Anyone who is using framebuffers,
> please test this.
>
> . Quite a large number of stability fixes.
I've got a problem with NFS!
If the kernel NFS server (nfs-utils 1.0.6) is started I get following Oops:
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
c0163c36
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
CPU: 0
EIP: 0060:[invalidate_list+37/211] Not tainted VLI
EFLAGS: 00010203
EIP is at invalidate_list+0x25/0xd3
eax: cded1e00 ebx: c13a80c0 ecx: c02e83a0 edx: cf35c000
esi: 00000000 edi: cf35df38 ebp: 00000000 esp: cf35df10
ds: 007b es: 007b ss: 0068
Process exportfs (pid: 1029, threadinfo=cf35c000 task=cefac0c0)
Stack: 00000000 00000000 cded1e00 cf35c000 cf35df38 cffe7c88 c0163d22 c02e8390
cded1e00 cf35df38 cf35df38 cf35df38 cd584980 cded1e00 c02e8640 cffe7c88
c01542f9 cded1e00 0000000e cf35c000 d1a2fde0 c0154bca cded1e00 cded1e00
Call Trace:
[invalidate_inodes+62/162] invalidate_inodes+0x3e/0xa2
[generic_shutdown_super+109/375] generic_shutdown_super+0x6d/0x177
[kill_anon_super+14/56] kill_anon_super+0xe/0x38
[deactivate_super+82/144] deactivate_super+0x52/0x90
[__fput+228/235] __fput+0xe4/0xeb
[sys_nfsservctl+257/267] sys_nfsservctl+0x101/0x10b
[syscall_call+7/11] syscall_call+0x7/0xb
Code: fb ff 5b 5e 5f c3 55 31 ed 57 56 53 50 50 8b 44 24 1c 8b 7c 24 24 c7 04
24
<6>note: exportfs[1029] exited with preempt_count 2
bad: scheduling while atomic!
Call Trace:
[schedule+60/1207] schedule+0x3c/0x4b7
[unmap_vmas+336/471] unmap_vmas+0x150/0x1d7
[exit_mmap+104/339] exit_mmap+0x68/0x153
[mmput+123/184] mmput+0x7b/0xb8
[do_exit+345/836] do_exit+0x159/0x344
[do_divide_error+0/167] do_divide_error+0x0/0xa7
[do_page_fault+784/1105] do_page_fault+0x310/0x451
[update_process_times+41/47] update_process_times+0x29/0x2f
[update_wall_time+11/51] update_wall_time+0xb/0x33
[do_timer+76/193] do_timer+0x4c/0xc1
[do_timer_interrupt+55/224] do_timer_interrupt+0x37/0xe0
[timer_interrupt+40/71] timer_interrupt+0x28/0x47
[rcu_process_callbacks+203/220] rcu_process_callbacks+0xcb/0xdc
[tasklet_action+58/89] tasklet_action+0x3a/0x59
[profile_hook+28/49] profile_hook+0x1c/0x31
[do_page_fault+0/1105] do_page_fault+0x0/0x451
[error_code+47/56] error_code+0x2f/0x38
[invalidate_list+37/211] invalidate_list+0x25/0xd3
[invalidate_inodes+62/162] invalidate_inodes+0x3e/0xa2
[generic_shutdown_super+109/375] generic_shutdown_super+0x6d/0x177
[kill_anon_super+14/56] kill_anon_super+0xe/0x38
[deactivate_super+82/144] deactivate_super+0x52/0x90
[__fput+228/235] __fput+0xe4/0xeb
[sys_nfsservctl+257/267] sys_nfsservctl+0x101/0x10b
[syscall_call+7/11] syscall_call+0x7/0xb
It just worked smoothly with 2.6.0-test7-mm1!
Regards
Thomas
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 15:00 ` 2.6.0-test8-mm1 Antonio Dolcetta
@ 2003-10-20 16:32 ` Jonathan Brown
2003-10-21 7:28 ` 2.6.0-test8-mm1 Antonio Dolcetta
0 siblings, 1 reply; 61+ messages in thread
From: Jonathan Brown @ 2003-10-20 16:32 UTC (permalink / raw)
To: Antonio Dolcetta; +Cc: linux-kernel
Well I compiled radeonfb as a module and got this error:
WARNING:
/lib/modules/2.6.0-test8-mm1/kernel/drivers/video/aty/radeonfb.ko needs
unknown symbol release_console_sem
so the module wont load. I presume you are compiling in radeonfb?
I'm running this on an IBM X31 laptop and it works great on
2.6.0-test7-mm1, except temporary screen corruption when radeonfb loads:
radeonfb_pci_register BEGIN
radeonfb: ref_clk=2700, ref_div=60, xclk=14400 from BIOS
radeonfb: probed DDR SGRAM 16384k videoram
radeon_get_moninfo: bios 4 scratch = 1000044
radeonfb: panel ID string: 1024x768
radeonfb: detected DFP panel size from BIOS: 1024x768
radeonfb: ATI Radeon M6 LY DDR SGRAM 16 MB
radeonfb: DVI port LCD monitor connected
radeonfb: CRT port no monitor connected
radeonfb_pci_register END
On Mon, 2003-10-20 at 16:00, Antonio Dolcetta wrote:
>
> Working perfectly here with radeon 9000
>
> I start it without passing any option to the kernel and it guesses the
> correct resolution from BIOS (laptop)
>
> radeonfb_pci_register BEGIN
> radeonfb: probed DDR SGRAM 65536k videoram
> radeonfb: Invalid ROM signature 0 should be 0xaa55
> radeonfb: ref_clk=2700, ref_div=67, xclk=16600 defaults
> Starting monitor auto detection...
> Non-DDC laptop panel detected
> radeonfb: Monitor 1 type LCD found
> radeonfb: Monitor 2 type no found
> radeonfb: Asssuming panel size 1400x1050
> radeonfb: ATI Radeon Lf Mobility M9 DDR SGRAM 64 MB
> radeonfb_pci_register END
>
>
> this is actually the first time the radeon framebuffer has worked for me
> that's great!
--
Jonathan Brown
http://emergence.uk.net/
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 11:05 ` 2.6.0-test8-mm1 Peter Lieverdink
@ 2003-10-20 18:49 ` Helge Hafting
2003-10-21 11:06 ` 2.6.0-test8-mm1 [matroxfb not working] Jurriaan
0 siblings, 1 reply; 61+ messages in thread
From: Helge Hafting @ 2003-10-20 18:49 UTC (permalink / raw)
To: Peter Lieverdink; +Cc: Andrew Morton, linux-kernel
On Mon, Oct 20, 2003 at 09:05:39PM +1000, Peter Lieverdink wrote:
> Re the new framebuffer code, it appears to not work on matroxfb.
> On bootup the console gets as far as:
>
> ...
> found SMP MP-table at 000f4db0
> hm, page 000f4000 reserved twice.
>
> And then it stops, whereas normally the framebuffer would kick in with a pengiun and continue booting.
> I boot the kernel with "video=matroxfb:vesa:0x192". When I disable it with "video=matroxfb:off" the system
> boots fine.
>
2.6.0-test8-mm1 won't start with matroxfb for me either.
I have
video=matroxfb:vesa:0x1BB
This works with 2.6.0-test8, I get two nice penguins.
With mm1 all I get is lilo printing loading linux...
and then everything stops. There isn't even a mode switch,
and no fsck on startup after using reset.
Helge Hafting
^ permalink raw reply [flat|nested] 61+ messages in thread
* [BUG] Re: 2.6.0-test8-mm1
2003-10-20 9:05 ` 2.6.0-test8-mm1 Andrew Morton
` (5 preceding siblings ...)
(?)
@ 2003-10-20 19:21 ` Ramón Rey Vicente
2003-10-20 20:10 ` Andrew Morton
-1 siblings, 1 reply; 61+ messages in thread
From: Ramón Rey Vicente @ 2003-10-20 19:21 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]
Hi.
The same problem with other kernel versions. I get it trying to delete
my local 2.6 svn repository:
EXT3-fs error (device hdb1): ext3_free_blocks: Freeing blocks in system
zones - Block = 512, count = 1
Aborting journal on device hdb1.
ext3_free_blocks: aborting transaction: Journal has aborted in
__ext3_journal_get_undo_access<2>EXT3-fs error (device hdb1) in
ext3_free_blocks: Journal has aborted
ext3_reserve_inode_write: aborting transaction: Journal has aborted in
__ext3_journal_get_write_access<2>EXT3-fs error (device hdb1) in
ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device hdb1) in ext3_truncate: Journal has aborted
ext3_reserve_inode_write: aborting transaction: Journal has aborted in
__ext3_journal_get_write_access<2>EXT3-fs error (device hdb1) in
ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device hdb1) in ext3_orphan_del: Journal has aborted
ext3_reserve_inode_write: aborting transaction: Journal has aborted in
__ext3_journal_get_write_access<2>EXT3-fs error (device hdb1) in
ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device hdb1) in ext3_delete_inode: Journal has aborted
ext3_abort called.
EXT3-fs abort (device hdb1): ext3_journal_start: Detected aborted
journal
Remounting filesystem read-only
--
Ramón Rey Vicente <ramon dot rey at hispalinux dot es>
jabber ID <rreylinux at jabber dot org>
GPG public key ID 0xBEBD71D5 -> http://pgp.escomposlinux.org/
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [BUG] Re: 2.6.0-test8-mm1
2003-10-20 19:21 ` [BUG] 2.6.0-test8-mm1 Ramón Rey Vicente
@ 2003-10-20 20:10 ` Andrew Morton
0 siblings, 0 replies; 61+ messages in thread
From: Andrew Morton @ 2003-10-20 20:10 UTC (permalink / raw)
To: ramon.rey; +Cc: rrey, linux-kernel, linux-mm
Ramón Rey Vicente <rrey@ranty.pantax.net> wrote:
>
> The same problem with other kernel versions. I get it trying to delete
> my local 2.6 svn repository:
>
> EXT3-fs error (device hdb1): ext3_free_blocks: Freeing blocks in system
> zones - Block = 512, count = 1
This is consistent with a corrupted filesystem. Have you forced a fsck
against that partition?
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [BUG] Re: 2.6.0-test8-mm1
@ 2003-10-20 20:10 ` Andrew Morton
0 siblings, 0 replies; 61+ messages in thread
From: Andrew Morton @ 2003-10-20 20:10 UTC (permalink / raw)
To: ramon.rey; +Cc: rrey, linux-kernel, linux-mm
Ramon Rey Vicente <rrey@ranty.pantax.net> wrote:
>
> The same problem with other kernel versions. I get it trying to delete
> my local 2.6 svn repository:
>
> EXT3-fs error (device hdb1): ext3_free_blocks: Freeing blocks in system
> zones - Block = 512, count = 1
This is consistent with a corrupted filesystem. Have you forced a fsck
against that partition?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 16:11 ` 2.6.0-test8-mm1 Thomas Schlichter
@ 2003-10-20 21:48 ` Andrew Morton
0 siblings, 0 replies; 61+ messages in thread
From: Andrew Morton @ 2003-10-20 21:48 UTC (permalink / raw)
To: Thomas Schlichter; +Cc: linux-kernel, linux-mm
Thomas Schlichter <schlicht@uni-mannheim.de> wrote:
>
> On Monday 20 October 2003 11:05, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test8/2
> >.6.0-test8-mm1
> >
> >
> > . Included a much updated fbdev patch. Anyone who is using framebuffers,
> > please test this.
> >
> > . Quite a large number of stability fixes.
>
> I've got a problem with NFS!
> If the kernel NFS server (nfs-utils 1.0.6) is started I get following Oops:
>
> Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> Unable to handle kernel NULL pointer dereference at virtual address 00000000
> printing eip:
> c0163c36
> *pde = 00000000
> Oops: 0000 [#1]
> PREEMPT
> CPU: 0
> EIP: 0060:[invalidate_list+37/211] Not tainted VLI
A colleague here has discovered that this crash is repeatable, but goes
away when the radeon driver is disabled.
Are you using that driver?
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
@ 2003-10-20 21:48 ` Andrew Morton
0 siblings, 0 replies; 61+ messages in thread
From: Andrew Morton @ 2003-10-20 21:48 UTC (permalink / raw)
To: Thomas Schlichter; +Cc: linux-kernel, linux-mm
Thomas Schlichter <schlicht@uni-mannheim.de> wrote:
>
> On Monday 20 October 2003 11:05, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test8/2
> >.6.0-test8-mm1
> >
> >
> > . Included a much updated fbdev patch. Anyone who is using framebuffers,
> > please test this.
> >
> > . Quite a large number of stability fixes.
>
> I've got a problem with NFS!
> If the kernel NFS server (nfs-utils 1.0.6) is started I get following Oops:
>
> Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> Unable to handle kernel NULL pointer dereference at virtual address 00000000
> printing eip:
> c0163c36
> *pde = 00000000
> Oops: 0000 [#1]
> PREEMPT
> CPU: 0
> EIP: 0060:[invalidate_list+37/211] Not tainted VLI
A colleague here has discovered that this crash is repeatable, but goes
away when the radeon driver is disabled.
Are you using that driver?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [BUG] Re: 2.6.0-test8-mm1
2003-10-20 20:10 ` Andrew Morton
(?)
@ 2003-10-20 21:53 ` Ramón Rey Vicente
-1 siblings, 0 replies; 61+ messages in thread
From: Ramón Rey Vicente @ 2003-10-20 21:53 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
El lun, 20-10-2003 a las 22:10, Andrew Morton escribió:
> Ramón Rey Vicente <rrey@ranty.pantax.net> wrote:
> >
> > The same problem with other kernel versions. I get it trying to delete
> > my local 2.6 svn repository:
> >
> > EXT3-fs error (device hdb1): ext3_free_blocks: Freeing blocks in system
> > zones - Block = 512, count = 1
>
> This is consistent with a corrupted filesystem. Have you forced a fsck
> against that partition?
Ups, yes, it seems the filesystem was corrupted/inconsistent but with a
fsck now all is OK. Sorry for this. :-X
--
Ramón Rey Vicente <ramon dot rey at hispalinux dot es>
jabber ID <rreylinux at jabber dot org>
GPG public key ID 0xBEBD71D5 -> http://pgp.escomposlinux.org/
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 21:48 ` 2.6.0-test8-mm1 Andrew Morton
(?)
@ 2003-10-20 22:01 ` Thomas Schlichter
2003-10-20 22:17 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-21 0:14 ` 2.6.0-test8-mm1 Valdis.Kletnieks
-1 siblings, 2 replies; 61+ messages in thread
From: Thomas Schlichter @ 2003-10-20 22:01 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
[-- Attachment #1.1: Type: text/plain, Size: 589 bytes --]
On Monday 20 October 2003 23:48, Andrew Morton wrote:
> A colleague here has discovered that this crash is repeatable, but goes
> away when the radeon driver is disabled.
>
> Are you using that driver?
No, I'm not... I use the vesafb driver. Do you think disabling this could cure
the Oops?
Btw. a similar Oops at the same place occours when the uhci-hcd module is
unloaded...
The attached patch prevents the kernel from Oopsing, so it seems some inode
lists are corrupted (NULL terminated!). Don't know how the FB driver could be
the reason...
Regards
Thomas
[-- Attachment #1.2: hack-invalidate_list.diff --]
[-- Type: text/x-diff, Size: 670 bytes --]
--- linux-2.6.0-test8-mm1/fs/inode.c.orig Mon Oct 20 20:52:26 2003
+++ linux-2.6.0-test8-mm1/fs/inode.c Mon Oct 20 22:43:52 2003
@@ -292,14 +292,16 @@
int busy = 0, count = 0;
next = head->next;
- for (;;) {
- struct list_head * tmp = next;
+ while (next != head) {
struct inode * inode;
-
- next = next->next;
- if (tmp == head)
+#if 1
+ if (!next) {
+ printk(KERN_ERR "Badness in invalidate_list() !\n");
break;
- inode = list_entry(tmp, struct inode, i_list);
+ }
+#endif
+ inode = list_entry(next, struct inode, i_list);
+ next = next->next;
if (inode->i_sb != sb)
continue;
invalidate_inode_buffers(inode);
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 22:01 ` 2.6.0-test8-mm1 Thomas Schlichter
@ 2003-10-20 22:17 ` Andrew Morton
2003-10-21 0:14 ` 2.6.0-test8-mm1 Valdis.Kletnieks
1 sibling, 0 replies; 61+ messages in thread
From: Andrew Morton @ 2003-10-20 22:17 UTC (permalink / raw)
To: Thomas Schlichter; +Cc: linux-kernel, linux-mm
Thomas Schlichter <schlicht@uni-mannheim.de> wrote:
>
> On Monday 20 October 2003 23:48, Andrew Morton wrote:
> > A colleague here has discovered that this crash is repeatable, but goes
> > away when the radeon driver is disabled.
> >
> > Are you using that driver?
>
> No, I'm not... I use the vesafb driver. Do you think disabling this could cure
> the Oops?
It might. Could you test it please?
There's nothing in -mm which touches the inode list management code, so a
random scribble or misbehaving driver is likely.
> Btw. a similar Oops at the same place occours when the uhci-hcd module is
> unloaded...
How similar?
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
@ 2003-10-20 22:17 ` Andrew Morton
0 siblings, 0 replies; 61+ messages in thread
From: Andrew Morton @ 2003-10-20 22:17 UTC (permalink / raw)
To: Thomas Schlichter; +Cc: linux-kernel, linux-mm
Thomas Schlichter <schlicht@uni-mannheim.de> wrote:
>
> On Monday 20 October 2003 23:48, Andrew Morton wrote:
> > A colleague here has discovered that this crash is repeatable, but goes
> > away when the radeon driver is disabled.
> >
> > Are you using that driver?
>
> No, I'm not... I use the vesafb driver. Do you think disabling this could cure
> the Oops?
It might. Could you test it please?
There's nothing in -mm which touches the inode list management code, so a
random scribble or misbehaving driver is likely.
> Btw. a similar Oops at the same place occours when the uhci-hcd module is
> unloaded...
How similar?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 22:17 ` 2.6.0-test8-mm1 Andrew Morton
(?)
@ 2003-10-20 22:30 ` Thomas Schlichter
2003-10-21 0:43 ` 2.6.0-test8-mm1 Thomas Schlichter
-1 siblings, 1 reply; 61+ messages in thread
From: Thomas Schlichter @ 2003-10-20 22:30 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
On Tuesday 21 October 2003 00:17, Andrew Mortonwrote:
> Thomas Schlichter <schlicht@uni-mannheim.de> wrote:
> > On Monday 20 October 2003 23:48, Andrew Morton wrote:
> > > A colleague here has discovered that this crash is repeatable, but goes
> > > away when the radeon driver is disabled.
> > >
> > > Are you using that driver?
> >
> > No, I'm not... I use the vesafb driver. Do you think disabling this could
> > cure the Oops?
>
> It might. Could you test it please?
I will, but currently I compile 2.6.0-test8. I want to try if this works...
I also want to try test8-mm1 without the -Os patch, you never know... ;-)
> There's nothing in -mm which touches the inode list management code, so a
> random scribble or misbehaving driver is likely.
Yes, or some part of the kernel compiled false...
(After some problems with erlier gcc's I don't trust my curent 3.3.1 that
much...)
> > Btw. a similar Oops at the same place occours when the uhci-hcd module is
> > unloaded...
>
> How similar?
Very similar (I think it came from deactivate_super(), too), but it seems not
to be logged...
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 22:01 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-20 22:17 ` 2.6.0-test8-mm1 Andrew Morton
@ 2003-10-21 0:14 ` Valdis.Kletnieks
2003-10-21 0:27 ` 2.6.0-test8-mm1 Andrew Morton
1 sibling, 1 reply; 61+ messages in thread
From: Valdis.Kletnieks @ 2003-10-21 0:14 UTC (permalink / raw)
To: Thomas Schlichter; +Cc: Andrew Morton, linux-kernel, linux-mm
[-- Attachment #1: Type: text/plain, Size: 6389 bytes --]
On Tue, 21 Oct 2003 00:01:01 +0200, Thomas Schlichter said:
> No, I'm not... I use the vesafb driver. Do you think disabling this could cure
> the Oops?
>
> Btw. a similar Oops at the same place occours when the uhci-hcd module is
> unloaded...
>
> The attached patch prevents the kernel from Oopsing, so it seems some inode
> lists are corrupted (NULL terminated!). Don't know how the FB driver could be
> the reason...
I was seeing similar issues where the system would fail to find /sbin/init because
things were dying while still on the initrd, and put Thomas' patch on (although I added a
WARN_ON(1) so we'd get a stack trace in addition to the printk). And then things
got *really* bizarre...
While at work, in its docking station, it would complain while running things
from /linuxrc off the initrd (it complained while firing up SELinux):
SELinux: initialized (dev , type rootfs), uses genfs_contexts
SELinux: initialized (dev , type sysfs), uses genfs_contexts
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
c015ec37
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
CPU: 0
EIP: 0060:[<c015ec37>] Not tainted VLI
EFLAGS: 00010246
EIP is at __iget+0x25/0x6e
eax: 00000000 ebx: 00000000 ecx: cfddc088 edx: cfddc080
esi: cfddc080 edi: c1303308 ebp: cff95dbc esp: cff95db8
ds: 007b es: 007b ss: 0068
Process load_policy (pid: 16, threadinfo=cff94000 task=cff97940)
Stack: cfddc080 cff95dcc c015f5a7 cfddc080 cff94000 cff95df0 c01d7377 cfddc080
c1303300 00000000 cffd2bc0 cffd0c40 cffd0c00 cff94000 cff95e10 c01db157
cffd0c00 cffd2bc0 cffd2bc8 cff95e20 c0386170 c04c7ca0 cff95f54 c01e026d
Call Trace:
[<c015f5a7>] igrab+0x20/0x42
[<c01d7377>] superblock_doinit+0x227/0x28b
[<c01db157>] selinux_complete_init+0x96/0xe5
[<c01e026d>] security_load_policy+0xaf/0x25c
[<c013e88e>] handle_mm_fault+0x6d/0x10c
[<c0118a15>] do_page_fault+0x153/0x4a1
[<c01358a2>] __rmqueue+0xc3/0x123
[<c0135935>] rmqueue_bulk+0x33/0x78
[<c0145128>] map_area_pmd+0x50/0x7b
[<c01188c2>] do_page_fault+0x0/0x4a1
[<c0367b93>] error_code+0x2f/0x38
[<c01e915a>] __copy_from_user_ll+0x3c/0x5a
[<c01db6a7>] sel_write_load+0xd0/0xec
[<c0149d2d>] vfs_write+0xae/0xdc
[<c0149dce>] sys_write+0x2c/0x47
[<c0367187>] syscall_call+0x7/0xb
Code: b6 fe ff ff 5d c3 55 89 e5 53 8b 55 08 8b 42 1c 85 c0 74 05 ff 42 1c eb 58
ff 42 1c f6 82 34 01 00 00 0f 75 46 8d 4a 08 8b 59 04 <39> 0b 74 08 0f 0b 94 00
13 5f 38 c0 8b 42 08 39 48 04 74 08 0f
<6>note: load_policy[16] exited with preempt_count 1
bad: scheduling while atomic!
Call Trace:
[<c011a0df>] schedule+0x3c/0x4b7
[<c013d302>] unmap_vmas+0x13c/0x1be
[<c0140832>] exit_mmap+0x60/0x14b
[<c011bcb2>] mmput+0x7d/0xbd
[<c011f33b>] do_exit+0x163/0x351
[<c010c68a>] do_divide_error+0x0/0xad
[<c0118c10>] do_page_fault+0x34e/0x4a1
[<c01240a2>] update_wall_time+0xd/0x37
[<c01243c0>] do_timer+0x4e/0xc6
[<c0110f0f>] timer_interrupt+0x5a/0x118
[<c01208f6>] do_softirq+0x4a/0x91
[<c010d6de>] do_IRQ+0x121/0x138
[<c01188c2>] do_page_fault+0x0/0x4a1
[<c0367b93>] error_code+0x2f/0x38
[<c01d007b>] udf_UTF8toCS0+0xf2/0x178
[<c015ec37>] __iget+0x25/0x6e
[<c015f5a7>] igrab+0x20/0x42
[<c01d7377>] superblock_doinit+0x227/0x28b
[<c01db157>] selinux_complete_init+0x96/0xe5
[<c01e026d>] security_load_policy+0xaf/0x25c
[<c013e88e>] handle_mm_fault+0x6d/0x10c
[<c0118a15>] do_page_fault+0x153/0x4a1
[<c01358a2>] __rmqueue+0xc3/0x123
[<c0135935>] rmqueue_bulk+0x33/0x78
[<c0145128>] map_area_pmd+0x50/0x7b
[<c01188c2>] do_page_fault+0x0/0x4a1
[<c0367b93>] error_code+0x2f/0x38
[<c01e915a>] __copy_from_user_ll+0x3c/0x5a
[<c01db6a7>] sel_write_load+0xd0/0xec
[<c0149d2d>] vfs_write+0xae/0xdc
[<c0149dce>] sys_write+0x2c/0x47
[<c0367187>] syscall_call+0x7/0xb
Badness in invalidate_list() !
Badness in invalidate_list at fs/inode.c:299
Call Trace:
[<c015ee28>] invalidate_list+0x54/0x104
[<c015ef24>] invalidate_inodes+0x4c/0xb9
[<c014ed0c>] generic_shutdown_super+0x7f/0x18d
[<c014f6c2>] kill_anon_super+0x10/0x40
[<c014eb6b>] deactivate_super+0x6f/0xb7
[<c0161c77>] sys_umount+0x5f/0x67
[<c0149d4f>] vfs_write+0xd0/0xdc
[<c0149dce>] sys_write+0x2c/0x47
[<c0161c8c>] sys_oldumount+0xd/0xf
[<c0367187>] syscall_call+0x7/0xb
Badness in invalidate_list() !
Badness in invalidate_list at fs/inode.c:299
Call Trace:
[<c015ee28>] invalidate_list+0x54/0x104
[<c015ef24>] invalidate_inodes+0x4c/0xb9
[<c014ed2f>] generic_shutdown_super+0xa2/0x18d
[<c014f6c2>] kill_anon_super+0x10/0x40
[<c014eb6b>] deactivate_super+0x6f/0xb7
[<c0161c77>] sys_umount+0x5f/0x67
[<c0149d4f>] vfs_write+0xd0/0xdc
[<c0149dce>] sys_write+0x2c/0x47
[<c0161c8c>] sys_oldumount+0xd/0xf
[<c0367187>] syscall_call+0x7/0xb
If trying to boot to 'single' or initlevel 3 or 5, it would then wedge up trying to mount
the local filesystems. I got the above by using init=/bin/bash and doing a dmesg onto
a writeable filesystem I hand-mounted. So obviously things were very ill, and the patch
merely let the system live long enough for me to get a dmesg to run.
Now for the *really* weird part - at the office, the early dmesg has:
Console: switching to colour frame buffer device 160x64
pty: 256 Unix98 ptys configured
I came home, and rebooted the laptop - same kernel, same everything except it
wasn't docked, and it crashed... *partial* oops follows, my pen was dying so
I got what seemed most important:
Console: switching to colour frame buffer device 160x64
Unable to handle kernel NULL pointer dereference at virtual address 00000068
...
EIP is at create_dir+0x1f/0x8f
....
sysfs_create_dir+0x5a/0x70
create_dir+0x15/0x39
kobject_add+0xb2/0x107
cdev_add+0xe/0x4c
tty_register_driver+0x112/0x213
pty_init+0x2db/0x40b
do_initcalls_0x35/0x87
init+0x32/0x10e
init+0x0/0x10e
kernel_thread_helper+0x5/0xb
Never got as far as saying 256 ptys.
(reproducible, from a power-off it did it same way 3 times in a row). So
whatever was giving it indigestion was (a) *very* early on and (b) different
when my laptop was docked and undocked. I'm guessing something ACPI-related,
because when undocked I'm shy an Ethernet controller that's in the dock.
However, the only new patches in -mm1 that seem to go near acpi are the EFI and
MSI patches - and I checked, neither is config'ed into the kernel.
This ring any bells? What you want tested? etc etc....
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 0:14 ` 2.6.0-test8-mm1 Valdis.Kletnieks
@ 2003-10-21 0:27 ` Andrew Morton
0 siblings, 0 replies; 61+ messages in thread
From: Andrew Morton @ 2003-10-21 0:27 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: schlicht, linux-kernel, linux-mm
Valdis.Kletnieks@vt.edu wrote:
>
> This ring any bells? What you want tested? etc etc....
Can you try disabling all fbdev stuff in config?
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
@ 2003-10-21 0:27 ` Andrew Morton
0 siblings, 0 replies; 61+ messages in thread
From: Andrew Morton @ 2003-10-21 0:27 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: schlicht, linux-kernel, linux-mm
Valdis.Kletnieks@vt.edu wrote:
>
> This ring any bells? What you want tested? etc etc....
Can you try disabling all fbdev stuff in config?
----- End forwarded message -----
--
"The software industry today survives only through an unstated agreement
not to stir things up too much. We must hope this lawsuit [by SCO] isn't
the big stirring spoon." -- Ian Lance Taylor, Linux Journal, June 2003
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 22:30 ` 2.6.0-test8-mm1 Thomas Schlichter
@ 2003-10-21 0:43 ` Thomas Schlichter
0 siblings, 0 replies; 61+ messages in thread
From: Thomas Schlichter @ 2003-10-21 0:43 UTC (permalink / raw)
To: Andrew Morton, Valdis.Kletnieks; +Cc: linux-kernel, linux-mm
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
On Tuesday 21 October 2003 00:30, I wrote:
> On Tuesday 21 October 2003 00:17, Andrew Mortonwrote:
> > Thomas Schlichter <schlicht@uni-mannheim.de> wrote:
> > > On Monday 20 October 2003 23:48, Andrew Morton wrote:
> > > > A colleague here has discovered that this crash is repeatable, but
> > > > goes away when the radeon driver is disabled.
> > > >
> > > > Are you using that driver?
> > >
> > > No, I'm not... I use the vesafb driver. Do you think disabling this
> > > could cure the Oops?
> >
> > It might. Could you test it please?
>
> I will, but currently I compile 2.6.0-test8. I want to try if this works...
> I also want to try test8-mm1 without the -Os patch, you never know... ;-)
OK, 2.6.0-test8 worked, 2.6.0-test8-mm1 without any FB support, too!!
So I didn't test reverting the -Os patch...
> > There's nothing in -mm which touches the inode list management code, so a
> > random scribble or misbehaving driver is likely.
>
> Yes, or some part of the kernel compiled false...
> (After some problems with erlier gcc's I don't trust my curent 3.3.1 that
> much...)
It seems my gcc 3.3.1 works the way it should... ;-)
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 0:27 ` 2.6.0-test8-mm1 Andrew Morton
(?)
@ 2003-10-21 0:46 ` Valdis.Kletnieks
2003-10-21 1:56 ` 2.6.0-test8-mm1 Andrew Morton
-1 siblings, 1 reply; 61+ messages in thread
From: Valdis.Kletnieks @ 2003-10-21 0:46 UTC (permalink / raw)
To: Andrew Morton; +Cc: schlicht, linux-kernel, linux-mm
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
On Mon, 20 Oct 2003 17:27:32 PDT, Andrew Morton said:
> Valdis.Kletnieks@vt.edu wrote:
> >
> > This ring any bells? What you want tested? etc etc....
>
> Can you try disabling all fbdev stuff in config?
OK.. That booted just fine, didn't hang in pty_init, didn't hit the
WARN_ON added to fs_inoce.c.
So we have:
works:
# CONFIG_FB is not set
Doesn't work:
CONFIG_FB=y
CONFIG_FB_VESA=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
I've not had a chance to play binary search on those options yet.. Graphics
card is an NVidia GeForce 440Go, and was previous working just fine with
framebuffer over on vc1-6 and NVidia's driver on an XFree86 on vc7. (OK, I
admit I didn't stress test the framebuffer side much past "penguins and
scroiled text"...)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 0:46 ` 2.6.0-test8-mm1 Valdis.Kletnieks
@ 2003-10-21 1:56 ` Andrew Morton
0 siblings, 0 replies; 61+ messages in thread
From: Andrew Morton @ 2003-10-21 1:56 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: schlicht, linux-kernel, linux-mm, James Simmons
Valdis.Kletnieks@vt.edu wrote:
>
> On Mon, 20 Oct 2003 17:27:32 PDT, Andrew Morton said:
> > Valdis.Kletnieks@vt.edu wrote:
> > >
> > > This ring any bells? What you want tested? etc etc....
> >
> > Can you try disabling all fbdev stuff in config?
>
> OK.. That booted just fine, didn't hang in pty_init, didn't hit the
> WARN_ON added to fs_inoce.c.
>
> So we have:
>
> works:
> # CONFIG_FB is not set
>
> Doesn't work:
> CONFIG_FB=y
> CONFIG_FB_VESA=y
> CONFIG_FRAMEBUFFER_CONSOLE=y
> CONFIG_PCI_CONSOLE=y
> CONFIG_FONT_8x8=y
> CONFIG_FONT_8x16=y
> CONFIG_LOGO=y
> CONFIG_LOGO_LINUX_MONO=y
> CONFIG_LOGO_LINUX_VGA16=y
> CONFIG_LOGO_LINUX_CLUT224=y
>
> I've not had a chance to play binary search on those options yet.. Graphics
> card is an NVidia GeForce 440Go, and was previous working just fine with
> framebuffer over on vc1-6 and NVidia's driver on an XFree86 on vc7. (OK, I
> admit I didn't stress test the framebuffer side much past "penguins and
> scroiled text"...)
>
Thanks. You're now the third person (schlicht@uni-mannheim.de,
jeremy@goop.org) who reports that the weird oopses (usually in
invalidate_list()) go away when the fbdev code is disabled.
You're using vesafb on nvidia, Jeremy is using vesafb on either radeon or
nvidia, not sure about Thomas.
Has anyone tried CONFIG_DEBUG_SLAB and CONFIG_DEBUG_PAGEALLOC, see if that
turns anything up?
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
@ 2003-10-21 1:56 ` Andrew Morton
0 siblings, 0 replies; 61+ messages in thread
From: Andrew Morton @ 2003-10-21 1:56 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: schlicht, linux-kernel, linux-mm, James Simmons
Valdis.Kletnieks@vt.edu wrote:
>
> On Mon, 20 Oct 2003 17:27:32 PDT, Andrew Morton said:
> > Valdis.Kletnieks@vt.edu wrote:
> > >
> > > This ring any bells? What you want tested? etc etc....
> >
> > Can you try disabling all fbdev stuff in config?
>
> OK.. That booted just fine, didn't hang in pty_init, didn't hit the
> WARN_ON added to fs_inoce.c.
>
> So we have:
>
> works:
> # CONFIG_FB is not set
>
> Doesn't work:
> CONFIG_FB=y
> CONFIG_FB_VESA=y
> CONFIG_FRAMEBUFFER_CONSOLE=y
> CONFIG_PCI_CONSOLE=y
> CONFIG_FONT_8x8=y
> CONFIG_FONT_8x16=y
> CONFIG_LOGO=y
> CONFIG_LOGO_LINUX_MONO=y
> CONFIG_LOGO_LINUX_VGA16=y
> CONFIG_LOGO_LINUX_CLUT224=y
>
> I've not had a chance to play binary search on those options yet.. Graphics
> card is an NVidia GeForce 440Go, and was previous working just fine with
> framebuffer over on vc1-6 and NVidia's driver on an XFree86 on vc7. (OK, I
> admit I didn't stress test the framebuffer side much past "penguins and
> scroiled text"...)
>
Thanks. You're now the third person (schlicht@uni-mannheim.de,
jeremy@goop.org) who reports that the weird oopses (usually in
invalidate_list()) go away when the fbdev code is disabled.
You're using vesafb on nvidia, Jeremy is using vesafb on either radeon or
nvidia, not sure about Thomas.
Has anyone tried CONFIG_DEBUG_SLAB and CONFIG_DEBUG_PAGEALLOC, see if that
turns anything up?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 1:56 ` 2.6.0-test8-mm1 Andrew Morton
(?)
@ 2003-10-21 2:54 ` Valdis.Kletnieks
-1 siblings, 0 replies; 61+ messages in thread
From: Valdis.Kletnieks @ 2003-10-21 2:54 UTC (permalink / raw)
To: Andrew Morton; +Cc: schlicht, linux-kernel, linux-mm, James Simmons
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
On Mon, 20 Oct 2003 18:56:13 PDT, Andrew Morton said:
> Has anyone tried CONFIG_DEBUG_SLAB and CONFIG_DEBUG_PAGEALLOC, see if that
> turns anything up?
Well, I built two test kernels, which hopefully tell us something.. ;)
1) I did a 'patch -R' and backed out the two fbdev patches - and a -test8-mm1
with them removed boots and runs fine with a framebuffer console.
2) Kernel *with* fbdev patch, but no 'vga=794' parm at boot works OK as well. So
it can be in the kernel and not used, and works OK.
3) With fbdev patch and DEBUG_SLAB and DEBUG_PAGEALLOC, it got weird.
It booted semi-OK (sort of - some funkyness mounting filesystems) but suffered some
truly horrid bit-droppings as stuff scrolled. Basically, most character cells that were
"blank" had light grey in the top 2 pixes of the cell, and many non-blanks that didn't
have ascenders had them as well. Not all the pixels were the same grey, either..
Looks like the debugging changed the layout in memory enough for things to almost
work (so less stuff was getting overlaid and we lived longer?), but didn't catch any
memory corruption (or at least neither console nor 'dmesg' saw any messages).
I'm wondering if it's stomping on some memory because the vga=794
parameter tells it to use 1280x1024x16, when the underlying card is really 1600x1200x32?
(Yes, I know this means the vesa is using a small corner of the card's memory)...
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 1:56 ` 2.6.0-test8-mm1 Andrew Morton
@ 2003-10-21 3:49 ` Jeremy Fitzhardinge
-1 siblings, 0 replies; 61+ messages in thread
From: Jeremy Fitzhardinge @ 2003-10-21 3:49 UTC (permalink / raw)
To: Andrew Morton
Cc: Valdis.Kletnieks, schlicht, Linux Kernel List, linux-mm, James Simmons
On Mon, 2003-10-20 at 18:56, Andrew Morton wrote:
> You're using vesafb on nvidia, Jeremy is using vesafb on either radeon or
I get it with radeon and vesafb - I haven't tried on my nvidia system.
J
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
@ 2003-10-21 3:49 ` Jeremy Fitzhardinge
0 siblings, 0 replies; 61+ messages in thread
From: Jeremy Fitzhardinge @ 2003-10-21 3:49 UTC (permalink / raw)
To: Andrew Morton
Cc: Valdis.Kletnieks, schlicht, Linux Kernel List, linux-mm, James Simmons
On Mon, 2003-10-20 at 18:56, Andrew Morton wrote:
> You're using vesafb on nvidia, Jeremy is using vesafb on either radeon or
I get it with radeon and vesafb - I haven't tried on my nvidia system.
J
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 16:32 ` 2.6.0-test8-mm1 Jonathan Brown
@ 2003-10-21 7:28 ` Antonio Dolcetta
0 siblings, 0 replies; 61+ messages in thread
From: Antonio Dolcetta @ 2003-10-21 7:28 UTC (permalink / raw)
To: Jonathan Brown; +Cc: linux-kernel, akpm
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
On Mon, 20 Oct 2003 17:32:03 +0100
Jonathan Brown <jbrown@emergence.uk.net> wrote:
> Well I compiled radeonfb as a module and got this error:
>
>
> WARNING:
> /lib/modules/2.6.0-test8-mm1/kernel/drivers/video/aty/radeonfb.ko needs
> unknown symbol release_console_sem
>
> so the module wont load. I presume you are compiling in radeonfb?
>
yes, I got:
*** Warning: "release_console_sem" [drivers/video/aty/radeonfb.ko] undefined!
while compiling radeonfb as a module
I just compiled it in and it worked.
my (almost, see below) working .config is attached
I do get an oops while unloading uhci-hcd, but sometimes that works and I
get an oops while unloading usbcore instead. will try to test it some more
and send them on list...
still, my latest test with radeonfb was with 2.6-test8 where I would get
some weird fuzzy diagonal bands instead of text scrolling, it looked as if
anything printed on screen was smeared to the right, in this one apart from
the same temporary corruption you have, it works great
ciao
--
Antonio Dolcetta
[-- Attachment #2: .config --]
[-- Type: application/octet-stream, Size: 28447 bytes --]
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
# CONFIG_CLEAN_COMPILE is not set
# CONFIG_STANDALONE is not set
CONFIG_BROKEN=y
CONFIG_BROKEN_ON_SMP=y
#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y
#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
CONFIG_MPENTIUMIII=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_X86_4G is not set
# CONFIG_X86_SWITCH_PAGETABLES is not set
# CONFIG_X86_4G_VM_LAYOUT is not set
# CONFIG_X86_UACCESS_INDIRECT is not set
# CONFIG_X86_HIGH_ENTRY is not set
CONFIG_HPET_TIMER=y
# CONFIG_HPET_EMULATE_RTC is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
CONFIG_X86_MCE_P4THERMAL=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_HAVE_DEC_LOCK=y
CONFIG_BOOT_IOREMAP=y
#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_DISK=y
CONFIG_PM_DISK_PARTITION="hda5"
#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_EFI is not set
# CONFIG_ACPI_RELAXED_AML is not set
#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
# CONFIG_CPU_FREQ_PROC_INTF is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_24_API is not set
CONFIG_CPU_FREQ_TABLE=y
#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=m
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
# CONFIG_X86_POWERNOW_K6 is not set
# CONFIG_X86_POWERNOW_K7 is not set
# CONFIG_X86_POWERNOW_K8 is not set
# CONFIG_X86_GX_SUSPMOD is not set
CONFIG_X86_SPEEDSTEP_CENTRINO=y
# CONFIG_X86_SPEEDSTEP_ICH is not set
# CONFIG_X86_SPEEDSTEP_SMI is not set
# CONFIG_X86_P4_CLOCKMOD is not set
# CONFIG_X86_LONGRUN is not set
# CONFIG_X86_LONGHAUL is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_USE_VECTOR is not set
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_HOTPLUG=y
#
# PCMCIA/CardBus support
#
CONFIG_PCMCIA=m
CONFIG_YENTA=m
CONFIG_CARDBUS=y
# CONFIG_I82092 is not set
# CONFIG_TCIC is not set
#
# PCI Hotplug Support
#
CONFIG_HOTPLUG_PCI=m
# CONFIG_HOTPLUG_PCI_FAKE is not set
# CONFIG_HOTPLUG_PCI_COMPAQ is not set
# CONFIG_HOTPLUG_PCI_IBM is not set
CONFIG_HOTPLUG_PCI_ACPI=m
# CONFIG_HOTPLUG_PCI_CPCI is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_FW_LOADER=m
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_CML1=m
# CONFIG_PARPORT_SERIAL is not set
CONFIG_PARPORT_PC_FIFO=y
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_PC_PCMCIA is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y
#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set
#
# Protocols
#
# CONFIG_ISAPNP is not set
# CONFIG_PNPBIOS is not set
#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_LBD is not set
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
CONFIG_IDE_TASK_IOCTL=y
CONFIG_IDE_TASKFILE_IO=y
#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPNP=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_IDE_TCQ=y
CONFIG_BLK_DEV_IDE_TCQ_DEFAULT=y
CONFIG_BLK_DEV_IDE_TCQ_DEPTH=8
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SGIIOC4 is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
CONFIG_SCSI=m
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_MAX_SD_DISKS=256
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=m
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_REPORT_LUNS=y
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
#
# PCMCIA SCSI adapter support
#
# CONFIG_PCMCIA_AHA152X is not set
# CONFIG_PCMCIA_FDOMAIN is not set
# CONFIG_PCMCIA_NINJA_SCSI is not set
# CONFIG_PCMCIA_QLOGIC is not set
#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
# CONFIG_BLK_DEV_MD is not set
CONFIG_BLK_DEV_DM=m
CONFIG_DM_IOCTL_V4=y
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
CONFIG_IEEE1394=m
#
# Subsystem Options
#
CONFIG_IEEE1394_VERBOSEDEBUG=y
CONFIG_IEEE1394_OUI_DB=y
#
# Device Drivers
#
#
# Texas Instruments PCILynx requires I2C bit-banging
#
CONFIG_IEEE1394_OHCI1394=m
#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=m
# CONFIG_IEEE1394_SBP2 is not set
# CONFIG_IEEE1394_ETH1394 is not set
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_IEEE1394_CMP=m
CONFIG_IEEE1394_AMDTP=m
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
CONFIG_NET_KEY=m
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
# CONFIG_NET_IPGRE_BROADCAST is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_IPV6_TUNNEL=m
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
CONFIG_NETFILTER=y
CONFIG_NETFILTER_DEBUG=y
#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
# CONFIG_IP_NF_TFTP is not set
# CONFIG_IP_NF_AMANDA is not set
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_FILTER=m
# CONFIG_IP_NF_TARGET_REJECT is not set
CONFIG_IP_NF_NAT=m
CONFIG_IP_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_IP_NF_NAT_LOCAL is not set
# CONFIG_IP_NF_NAT_SNMP_BASIC is not set
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_CLASSIFY=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
# CONFIG_IP_NF_COMPAT_IPCHAINS is not set
# CONFIG_IP_NF_COMPAT_IPFWADM is not set
#
# IPv6: Netfilter Configuration
#
# CONFIG_IP6_NF_QUEUE is not set
# CONFIG_IP6_NF_IPTABLES is not set
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=m
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_MII is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
CONFIG_B44=m
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set
# CONFIG_NET_POLL_CONTROLLER is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
#
# PCMCIA network device support
#
# CONFIG_NET_PCMCIA is not set
#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set
#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set
#
# Bluetooth support
#
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
# CONFIG_BT_BNEP is not set
#
# Bluetooth device drivers
#
CONFIG_BT_HCIUSB=m
# CONFIG_BT_USB_SCO is not set
# CONFIG_BT_USB_ZERO_PACKET is not set
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_BCSP_TXCRC=y
CONFIG_BT_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_BT_HCIVHCI=m
#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
CONFIG_INPUT_UINPUT=m
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
# CONFIG_SERIAL_8250_CS is not set
# CONFIG_SERIAL_8250_ACPI is not set
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set
#
# I2C support
#
CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m
#
# I2C Algorithms
#
# CONFIG_I2C_ALGOBIT is not set
# CONFIG_I2C_ALGOPCF is not set
#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
CONFIG_I2C_I801=m
# CONFIG_I2C_NFORCE2 is not set
CONFIG_I2C_PIIX4=m
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIAPRO is not set
#
# I2C Hardware Sensors Chip support
#
CONFIG_I2C_SENSOR=m
# CONFIG_SENSORS_ADM1021 is not set
CONFIG_SENSORS_EEPROM=m
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_W83781D is not set
#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=m
# CONFIG_NVRAM is not set
CONFIG_RTC=m
CONFIG_GEN_RTC=m
CONFIG_GEN_RTC_X=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=m
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=m
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_MATROX is not set
CONFIG_FB_RADEON=y
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_VIRTUAL is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
#
# Sound
#
CONFIG_SOUND=m
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_VERBOSE_PRINTK=y
# CONFIG_SND_DEBUG is not set
#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
CONFIG_SND_VIRMIDI=m
# CONFIG_SND_MTPAV is not set
CONFIG_SND_SERIAL_U16550=m
CONFIG_SND_MPU401=m
#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set
#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set
#
# PCMCIA devices
#
# CONFIG_SND_VXPOCKET is not set
# CONFIG_SND_VXP440 is not set
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
#
# USB support
#
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
CONFIG_USB_DYNAMIC_MINORS=y
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=m
#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
#
# USB Bluetooth TTY can only be used with disabled Bluetooth subsystem
#
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=m
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y
#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_XPAD is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_SCANNER is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set
#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set
#
# Video4Linux support is needed for USB Multimedia device support
#
#
# USB Network adaptors
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
#
# USB port drivers
#
# CONFIG_USB_USS720 is not set
#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GADGET is not set
#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=y
#
# DOS/FAT/NT Filesystems
#
# CONFIG_FAT_FS is not set
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_DEVFS_FS=y
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
# CONFIG_NFS_V4 is not set
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
# CONFIG_NFSD_V3 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_SUNRPC=m
# CONFIG_SUNRPC_GSS is not set
CONFIG_SMB_FS=m
# CONFIG_SMB_NLS_DEFAULT is not set
CONFIG_CIFS=m
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_SMB_NLS=y
CONFIG_NLS=y
#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-15"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=y
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y
#
# Profiling support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_IOVIRT is not set
# CONFIG_MAGIC_SYSRQ is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_SPINLINE is not set
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_KGDB is not set
CONFIG_FRAME_POINTER=y
CONFIG_X86_EXTRA_IRQS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
#
# Security options
#
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=m
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
# CONFIG_CRYPTO_SHA512 is not set
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
# CONFIG_CRYPTO_SERPENT is not set
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_DEFLATE=m
# CONFIG_CRYPTO_TEST is not set
#
# Library routines
#
# CONFIG_CRC32 is not set
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 9:05 ` 2.6.0-test8-mm1 Andrew Morton
` (6 preceding siblings ...)
(?)
@ 2003-10-21 8:03 ` Stephane Jourdois
-1 siblings, 0 replies; 61+ messages in thread
From: Stephane Jourdois @ 2003-10-21 8:03 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Mon, Oct 20, 2003 at 02:05:58AM -0700, Andrew Morton wrote:
> . Included a much updated fbdev patch. Anyone who is using framebuffers,
> please test this.
Hello,
rivafb still doesn't work on my card, but that isn't surprising :
root(pts/7)@saphir:~(102Ko) # lspci -vvn -s 01:00.0
01:00.0 Class 0300: 10de:0181 (rev a2)
Subsystem: 1043:80bb
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: 248 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 4
Region 0: Memory at ee000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at f0000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at effe0000 [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-
Capabilities: [44] AGP version 3.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA- ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
Command: RQ=32 ArqSz=0 Cal=0 SBA- AGP+ GART64- 64bit- FW- Rate=x4
This card is a Geforce4 440 MX.
please note the 10de:0181, whereas in includes/linux/pci_ids.h we have :
#define PCI_DEVICE_ID_NVIDIA_GEFORCE4_MX_440 0x0171
So I tried to replace 0171 with 0181, and the card was detected, but the
frame buffer still doesn't work (blank screen for most resolutions,
corrupted screen for some).
Also, What is that subsystem 1043:80bb (Asustek:device not-known) ?
Should I provide more informataions about my card ?
I'm ready to test any patch needed.
Thanks,
--
/// Stephane Jourdois /"\ ASCII RIBBON CAMPAIGN \\\
((( Ingénieur développement \ / AGAINST HTML MAIL )))
\\\ 24, rue Cauchy X ///
\\\ 75008 Paris / \ +33 6 8643 3085 ///
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 1:56 ` 2.6.0-test8-mm1 Andrew Morton
` (2 preceding siblings ...)
(?)
@ 2003-10-21 8:39 ` Thomas Schlichter
-1 siblings, 0 replies; 61+ messages in thread
From: Thomas Schlichter @ 2003-10-21 8:39 UTC (permalink / raw)
To: Andrew Morton, Valdis.Kletnieks; +Cc: linux-kernel, linux-mm, James Simmons
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
On Tuesday 21 October 2003 03:56, Andrew Morton wrote:
> Valdis.Kletnieks@vt.edu wrote:
> > I've not had a chance to play binary search on those options yet..
> > Graphics card is an NVidia GeForce 440Go, and was previous working just
> > fine with framebuffer over on vc1-6 and NVidia's driver on an XFree86 on
> > vc7. (OK, I admit I didn't stress test the framebuffer side much past
> > "penguins and scroiled text"...)
>
> Thanks. You're now the third person (schlicht@uni-mannheim.de,
> jeremy@goop.org) who reports that the weird oopses (usually in
> invalidate_list()) go away when the fbdev code is disabled.
>
> You're using vesafb on nvidia, Jeremy is using vesafb on either radeon or
> nvidia, not sure about Thomas.
Sorry for not mentioning it!
I use(d) vesafb on a Nvidia GeForce 2 MX 440.
> Has anyone tried CONFIG_DEBUG_SLAB and CONFIG_DEBUG_PAGEALLOC, see if that
> turns anything up?
I didn't yet, but I'll try now...
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1 [matroxfb not working]
2003-10-20 18:49 ` 2.6.0-test8-mm1 Helge Hafting
@ 2003-10-21 11:06 ` Jurriaan
0 siblings, 0 replies; 61+ messages in thread
From: Jurriaan @ 2003-10-21 11:06 UTC (permalink / raw)
To: linux-kernel
From: Helge Hafting <helgehaf@aitel.hist.no>
Date: Mon, Oct 20, 2003 at 08:49:53PM +0200
> On Mon, Oct 20, 2003 at 09:05:39PM +1000, Peter Lieverdink wrote:
> > Re the new framebuffer code, it appears to not work on matroxfb.
> > On bootup the console gets as far as:
> >
> > ...
> > found SMP MP-table at 000f4db0
> > hm, page 000f4000 reserved twice.
> >
> > And then it stops, whereas normally the framebuffer would kick in with a pengiun and continue booting.
> > I boot the kernel with "video=matroxfb:vesa:0x192". When I disable it with "video=matroxfb:off" the system
> > boots fine.
> >
> 2.6.0-test8-mm1 won't start with matroxfb for me either.
> I have
> video=matroxfb:vesa:0x1BB
> This works with 2.6.0-test8, I get two nice penguins.
> With mm1 all I get is lilo printing loading linux...
> and then everything stops. There isn't even a mode switch,
> and no fsck on startup after using reset.
>
Same here:
kernel /boot/vmlinuz-260test8mm1 root=/dev/md3 video=matroxfb:xres:1600,yres:1360,depth:16,pixclock:4116,left:304,right:64,upper:46,lower:1,hslen:192,vslen:3,fv:90,hwcursor=off hdd=scsi atkbd_softrepeat=1
hangs even before the modeswitch.
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 82)
(it's a G450, 32 Mb, AGP).
CONFIG_FB=y
CONFIG_FB_MATROX=y
CONFIG_FB_MATROX_G450=y
CONFIG_FB_MATROX_G100=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FONTS=y
CONFIG_FONT_SUN12x22=y
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
Jurriaan
--
"I want a full apology and a retraction of all these infamous charges."
"I have not yet brought charges," said Bodwyn Wook. "As for apologies,
the record of your conduct speaks for itself. Do you want me to apologize
for citing your record?"
Jack Vance - Araminta Station
Debian (Unstable) GNU/Linux 2.6.0-test8 4276 bogomips 0.44 0.18
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-20 9:05 ` 2.6.0-test8-mm1 Andrew Morton
` (7 preceding siblings ...)
(?)
@ 2003-10-21 15:43 ` bill davidsen
2003-10-21 17:42 ` 2.6.0-test8-mm1 Valdis.Kletnieks
-1 siblings, 1 reply; 61+ messages in thread
From: bill davidsen @ 2003-10-21 15:43 UTC (permalink / raw)
To: linux-kernel
In article <20031020020558.16d2a776.akpm@osdl.org>,
Andrew Morton <akpm@osdl.org> wrote:
|
| ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test8/2.6.0-test8-mm1
|
|
| . Included a much updated fbdev patch. Anyone who is using framebuffers,
| please test this.
|
| . Quite a large number of stability fixes.
|
|
|
| Changes since 2.6.0-test7-mm1:
| +devfs-initrd-fix.patch
|
| Fix initrd when devfs is in use
I casually followed the thread on this, is this a band-aid or a magic
spell of healing? Do you consider this a "real fix" for the various
problems people reported?
| +export-system_running.patch
| +might_sleep-early-bogons.patch
|
| Stomp all the early might_sleep() warnings.
Sort of the same question, were the warnings really bogus, or were
people just not doing the things which might cause a real error?
| +slab-leak-detector.patch
| +slab-leak-detector-tweaks.patch
|
| A slab debugging tool for finding memory leaks: do
|
| echo "slab-name 0 0 0" > /proc/slabinfo
|
| and the kernel will inspect each live object in that cache and will print
| out the code address from which the allocation was performed.
Neat!
| +parport_pc-resource-release-fix.patch
|
| Fix an oopsable resource leak in parport_pc.
I'll try my old parport ZIP drive (ppa) again this weekend.
| +ext3-latency-fix.patch
|
| Improved scheduling latency in ext3.
Did someone have measurements on this?
Compiling as I type.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 15:43 ` 2.6.0-test8-mm1 bill davidsen
@ 2003-10-21 17:42 ` Valdis.Kletnieks
0 siblings, 0 replies; 61+ messages in thread
From: Valdis.Kletnieks @ 2003-10-21 17:42 UTC (permalink / raw)
To: bill davidsen; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
On Tue, 21 Oct 2003 15:43:44 -0000, davidsen@tmr.com (bill davidsen) said:
>
> | +devfs-initrd-fix.patch
> |
> | Fix initrd when devfs is in use
>
> I casually followed the thread on this, is this a band-aid or a magic
> spell of healing? Do you consider this a "real fix" for the various
> problems people reported?
Well, the options were to (a) move it to anywhere except under /dev and (b) to
make it cooperate with devfs. (a) seemed more reasonable when Linus is asking
for a stability freeze...
A *real* fix, which would require re-architecting devfs/udev/whatever and the
whole initrd/initramfs and probably other stuff, should be looked at for 2.7.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 1:56 ` 2.6.0-test8-mm1 Andrew Morton
@ 2003-10-21 17:47 ` James Simmons
-1 siblings, 0 replies; 61+ messages in thread
From: James Simmons @ 2003-10-21 17:47 UTC (permalink / raw)
To: Andrew Morton; +Cc: Valdis.Kletnieks, schlicht, linux-kernel, linux-mm
Okay I see people are having alot of problems in the -mm tree. I don't
have any problems but I'm working against Linus tree. Could people try the
patch against 2.6.0-test8 and tell me if they still have the same results.
I have a new patch here:
http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
@ 2003-10-21 17:47 ` James Simmons
0 siblings, 0 replies; 61+ messages in thread
From: James Simmons @ 2003-10-21 17:47 UTC (permalink / raw)
To: Andrew Morton; +Cc: Valdis.Kletnieks, schlicht, linux-kernel, linux-mm
Okay I see people are having alot of problems in the -mm tree. I don't
have any problems but I'm working against Linus tree. Could people try the
patch against 2.6.0-test8 and tell me if they still have the same results.
I have a new patch here:
http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 17:47 ` 2.6.0-test8-mm1 James Simmons
(?)
@ 2003-10-21 18:53 ` Jurriaan
2003-10-22 17:02 ` 2.6.0-test8-mm1 James Simmons
-1 siblings, 1 reply; 61+ messages in thread
From: Jurriaan @ 2003-10-21 18:53 UTC (permalink / raw)
To: James Simmons; +Cc: linux-kernel
From: James Simmons <jsimmons@infradead.org>
Date: Tue, Oct 21, 2003 at 06:47:41PM +0100
>
> Okay I see people are having alot of problems in the -mm tree. I don't
> have any problems but I'm working against Linus tree. Could people try the
> patch against 2.6.0-test8 and tell me if they still have the same results.
> I have a new patch here:
>
> http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz
>
2.6.0-test8 + this patch boots perfectly here:
kernel /boot/vmlinuz-260test8fb root=/dev/md3 video=matroxfb:xres:1600,yres:1360,depth:16,pixclock:4116,left:304,right:64,upper:46,lower:1,hslen:192,vslen:3,fv:90,hwcursor=off hdd=scsi atkbd_softrepeat=1
This configuration didn't boot in 2.6.0-test8-mm1 (screen stayed in
80x25 VGA mode and it crashed before the mode-switch).
HTH,
Jurriaan
--
Life's really a chocolate box - some do without - others have plenty.
Skyclad - Inequality Street
Debian (Unstable) GNU/Linux 2.6.0-test8 4276 bogomips 0.39 0.17
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 17:47 ` 2.6.0-test8-mm1 James Simmons
@ 2003-10-21 20:23 ` Helge Hafting
-1 siblings, 0 replies; 61+ messages in thread
From: Helge Hafting @ 2003-10-21 20:23 UTC (permalink / raw)
To: James Simmons
Cc: Andrew Morton, Valdis.Kletnieks, schlicht, linux-kernel, linux-mm
On Tue, Oct 21, 2003 at 06:47:41PM +0100, James Simmons wrote:
>
> Okay I see people are having alot of problems in the -mm tree. I don't
> have any problems but I'm working against Linus tree. Could people try the
> patch against 2.6.0-test8 and tell me if they still have the same results.
This patch was fine. 2.6.0-test8 with this patch booted and
looked no different from plain 2.6.0-test8. I am using it for
writing this. The problems must be in mm1 somehow.
Helge Hafting
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
@ 2003-10-21 20:23 ` Helge Hafting
0 siblings, 0 replies; 61+ messages in thread
From: Helge Hafting @ 2003-10-21 20:23 UTC (permalink / raw)
To: James Simmons
Cc: Andrew Morton, Valdis.Kletnieks, schlicht, linux-kernel, linux-mm
On Tue, Oct 21, 2003 at 06:47:41PM +0100, James Simmons wrote:
>
> Okay I see people are having alot of problems in the -mm tree. I don't
> have any problems but I'm working against Linus tree. Could people try the
> patch against 2.6.0-test8 and tell me if they still have the same results.
This patch was fine. 2.6.0-test8 with this patch booted and
looked no different from plain 2.6.0-test8. I am using it for
writing this. The problems must be in mm1 somehow.
Helge Hafting
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 20:23 ` 2.6.0-test8-mm1 Helge Hafting
(?)
@ 2003-10-21 20:36 ` Thomas Schlichter
2003-10-21 20:42 ` 2.6.0-test8-mm1 James Simmons
-1 siblings, 1 reply; 61+ messages in thread
From: Thomas Schlichter @ 2003-10-21 20:36 UTC (permalink / raw)
To: Helge Hafting, James Simmons
Cc: Andrew Morton, Valdis.Kletnieks, linux-kernel, linux-mm
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
On Tuesday 21 October 2003 22:23, Helge Hafting wrote:
> On Tue, Oct 21, 2003 at 06:47:41PM +0100, James Simmons wrote:
> > Okay I see people are having alot of problems in the -mm tree. I don't
> > have any problems but I'm working against Linus tree. Could people try
> > the patch against 2.6.0-test8 and tell me if they still have the same
> > results.
>
> This patch was fine. 2.6.0-test8 with this patch booted and
> looked no different from plain 2.6.0-test8. I am using it for
> writing this. The problems must be in mm1 somehow.
>
> Helge Hafting
Well here I've got same problems for -test8 + fbdev-patch as with -test8-mm1.
I've compiled the kernel with most DEBUG_* options enabled (all but
DEBUG_INFO and KGDB) and see the same cursor and image corruption as with
-mm1 and the same options enabled.
Should I try compiling this kernel without the DEBUG_* options and watch if I
get the invalidate_list Oops again?
I use vesafb on a Nvidia GeForce 2 MX 440 with 64MB Video-RAM.
Regards
Thomas
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 20:36 ` 2.6.0-test8-mm1 Thomas Schlichter
@ 2003-10-21 20:42 ` James Simmons
0 siblings, 0 replies; 61+ messages in thread
From: James Simmons @ 2003-10-21 20:42 UTC (permalink / raw)
To: Thomas Schlichter
Cc: Helge Hafting, Andrew Morton, Valdis.Kletnieks, linux-kernel, linux-mm
> > This patch was fine. 2.6.0-test8 with this patch booted and
> > looked no different from plain 2.6.0-test8. I am using it for
> > writing this. The problems must be in mm1 somehow.
> >
> > Helge Hafting
Yeah!!!
> Well here I've got same problems for -test8 + fbdev-patch as with -test8-mm1.
> I've compiled the kernel with most DEBUG_* options enabled (all but
> DEBUG_INFO and KGDB) and see the same cursor and image corruption as with
> -mm1 and the same options enabled.
>
> Should I try compiling this kernel without the DEBUG_* options and watch if I
> get the invalidate_list Oops again?
Yes. I'm using vesafb and I have no problems. I liek to see what the
problem really is.
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
@ 2003-10-21 20:42 ` James Simmons
0 siblings, 0 replies; 61+ messages in thread
From: James Simmons @ 2003-10-21 20:42 UTC (permalink / raw)
To: Thomas Schlichter
Cc: Helge Hafting, Andrew Morton, Valdis.Kletnieks, linux-kernel, linux-mm
> > This patch was fine. 2.6.0-test8 with this patch booted and
> > looked no different from plain 2.6.0-test8. I am using it for
> > writing this. The problems must be in mm1 somehow.
> >
> > Helge Hafting
Yeah!!!
> Well here I've got same problems for -test8 + fbdev-patch as with -test8-mm1.
> I've compiled the kernel with most DEBUG_* options enabled (all but
> DEBUG_INFO and KGDB) and see the same cursor and image corruption as with
> -mm1 and the same options enabled.
>
> Should I try compiling this kernel without the DEBUG_* options and watch if I
> get the invalidate_list Oops again?
Yes. I'm using vesafb and I have no problems. I liek to see what the
problem really is.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 17:47 ` 2.6.0-test8-mm1 James Simmons
` (2 preceding siblings ...)
(?)
@ 2003-10-21 20:55 ` Panagiotis Papadakos
2003-10-22 17:12 ` 2.6.0-test8-mm1 James Simmons
-1 siblings, 1 reply; 61+ messages in thread
From: Panagiotis Papadakos @ 2003-10-21 20:55 UTC (permalink / raw)
To: James Simmons; +Cc: linux-kernel
I get the following errors during make bzImage
CC drivers/video/aty/radeon_base.o
drivers/video/aty/radeon_base.c: In function `radeonfb_setup':
drivers/video/aty/radeon_base.c:2225: error: `force_measure_pll'
undeclared (first use in this function)
drivers/video/aty/radeon_base.c:2225: error: (Each undeclared identifier
is reported only once
drivers/video/aty/radeon_base.c:2225: error: for each function it appears
in.)
drivers/video/aty/radeon_base.c: In function `__check_force_measure_pll':
drivers/video/aty/radeon_base.c:2263: error: `force_measure_pll'
undeclared (first use in this function)
drivers/video/aty/radeon_base.c: At top level:
drivers/video/aty/radeon_base.c:2263: error: `force_measure_pll'
undeclared here (not in a function)
drivers/video/aty/radeon_base.c:2263: error: initializer element is not
constant
drivers/video/aty/radeon_base.c:2263: error: (near initialization for
`__param_force_measure_pll.arg')
make[3]: *** [drivers/video/aty/radeon_base.o] Error 1
make[2]: *** [drivers/video/aty] Error 2
make[1]: *** [drivers/video] Error 2
make: *** [drivers] Error 2
and
drivers/video/fbmem.c:219: error: `radeonfb_setup' undeclared here (not in a function)
drivers/video/fbmem.c:219: error: initializer element is not constant
drivers/video/fbmem.c:219: error: (near initialization for `fb_drivers[0].setup')
drivers/video/fbmem.c:219: error: initializer element is not constant
drivers/video/fbmem.c:219: error: (near initialization for `fb_drivers[0]')
So propably these should be applied:
--- radeon_base.c_old 2003-10-21 23:57:20.000000000 +0300
+++ radeon_base.c_new 2003-10-21 23:52:24.000000000 +0300
@@ -199,6 +199,7 @@
static int nomodeset = 0;
static int ignore_edid = 0;
static int mirror = 0;
+static int force_measure_pll = 0;
static int panel_yres __initdata = 0;
static int force_dfp __initdata = 0;
static struct radeonfb_info *board_list = NULL;
--- fbmem.c_old 2003-10-21 23:57:46.000000000 +0300
+++ fbmem.c_new 2003-10-21 23:51:54.000000000 +0300
@@ -133,6 +133,7 @@
extern int tx3912fb_init(void);
extern int tx3912fb_setup(char*);
extern int radeonfb_init(void);
+extern int radeonfb_setup(char *options);
extern int epson1355fb_init(void);
extern int pvr2fb_init(void);
extern int pvr2fb_setup(char*);
Panagiotis Papadakos
On Tue, 21 Oct 2003, James Simmons wrote:
>
> Okay I see people are having alot of problems in the -mm tree. I don't
> have any problems but I'm working against Linus tree. Could people try the
> patch against 2.6.0-test8 and tell me if they still have the same results.
> I have a new patch here:
>
> http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 20:42 ` 2.6.0-test8-mm1 James Simmons
(?)
@ 2003-10-21 21:05 ` Thomas Giese
2003-10-22 17:08 ` 2.6.0-test8-mm1 James Simmons
-1 siblings, 1 reply; 61+ messages in thread
From: Thomas Giese @ 2003-10-21 21:05 UTC (permalink / raw)
To: James Simmons; +Cc: linux-kernel
this 2.6.0-mm1 is really very good,
but i would VERY enjoy to have the cloop-device from knopper in it!
we have the cryptloop, why not the very good cloop?
this would be a wonderful combination?
best Regards
Thomas Giese
-----Ursprüngliche Nachricht-----
Von: "James Simmons" <jsimmons@infradead.org>
An: "Thomas Schlichter" <schlicht@uni-mannheim.de>
Cc: "Helge Hafting" <helgehaf@aitel.hist.no>; "Andrew Morton"
<akpm@osdl.org>; <Valdis.Kletnieks@vt.edu>; <linux-kernel@vger.kernel.org>;
<linux-mm@kvack.org>
Gesendet: Dienstag, 21. Oktober 2003 22:42
Betreff: Re: 2.6.0-test8-mm1
>
> > > This patch was fine. 2.6.0-test8 with this patch booted and
> > > looked no different from plain 2.6.0-test8. I am using it for
> > > writing this. The problems must be in mm1 somehow.
> > >
> > > Helge Hafting
>
> Yeah!!!
>
> > Well here I've got same problems for -test8 + fbdev-patch as
with -test8-mm1.
> > I've compiled the kernel with most DEBUG_* options enabled (all but
> > DEBUG_INFO and KGDB) and see the same cursor and image corruption as
with
> > -mm1 and the same options enabled.
> >
> > Should I try compiling this kernel without the DEBUG_* options and watch
if I
> > get the invalidate_list Oops again?
>
> Yes. I'm using vesafb and I have no problems. I liek to see what the
> problem really is.
>
>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 20:42 ` 2.6.0-test8-mm1 James Simmons
@ 2003-10-21 22:53 ` Thomas Schlichter
-1 siblings, 0 replies; 61+ messages in thread
From: Thomas Schlichter @ 2003-10-21 22:53 UTC (permalink / raw)
To: James Simmons
Cc: Helge Hafting, Andrew Morton, Valdis.Kletnieks, linux-kernel, linux-mm
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
On Tuesday 21 October 2003 22:42, James Simmons wrote:
> > > This patch was fine. 2.6.0-test8 with this patch booted and
> > > looked no different from plain 2.6.0-test8. I am using it for
> > > writing this. The problems must be in mm1 somehow.
> > >
> > > Helge Hafting
>
> Yeah!!!
>
> > Well here I've got same problems for -test8 + fbdev-patch as with
> > -test8-mm1. I've compiled the kernel with most DEBUG_* options enabled
> > (all but DEBUG_INFO and KGDB) and see the same cursor and image
> > corruption as with -mm1 and the same options enabled.
> >
> > Should I try compiling this kernel without the DEBUG_* options and watch
> > if I get the invalidate_list Oops again?
>
> Yes. I'm using vesafb and I have no problems. I liek to see what the
> problem really is.
OK, without any of the DEBUG_* options enabled the kernel SEEMS to work with
no problems. But I don't know how I can assure there actually is no memory
corruption...
For me the big question stays why enabling the DEBUG_* options results in a
corrupt cursor and the false dots on the top of each row... (with both
kernels)
And, of course, why enabling vesafb in -mm1 leads to memory corruption. (as
Vladis already mentioned, the same binary works if vesafb is not enabled via
the 'vga=xxx' boot option).
Regards
Thomas
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
@ 2003-10-21 22:53 ` Thomas Schlichter
0 siblings, 0 replies; 61+ messages in thread
From: Thomas Schlichter @ 2003-10-21 22:53 UTC (permalink / raw)
To: James Simmons
Cc: Helge Hafting, Andrew Morton, Valdis.Kletnieks, linux-kernel, linux-mm
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
On Tuesday 21 October 2003 22:42, James Simmons wrote:
> > > This patch was fine. 2.6.0-test8 with this patch booted and
> > > looked no different from plain 2.6.0-test8. I am using it for
> > > writing this. The problems must be in mm1 somehow.
> > >
> > > Helge Hafting
>
> Yeah!!!
>
> > Well here I've got same problems for -test8 + fbdev-patch as with
> > -test8-mm1. I've compiled the kernel with most DEBUG_* options enabled
> > (all but DEBUG_INFO and KGDB) and see the same cursor and image
> > corruption as with -mm1 and the same options enabled.
> >
> > Should I try compiling this kernel without the DEBUG_* options and watch
> > if I get the invalidate_list Oops again?
>
> Yes. I'm using vesafb and I have no problems. I liek to see what the
> problem really is.
OK, without any of the DEBUG_* options enabled the kernel SEEMS to work with
no problems. But I don't know how I can assure there actually is no memory
corruption...
For me the big question stays why enabling the DEBUG_* options results in a
corrupt cursor and the false dots on the top of each row... (with both
kernels)
And, of course, why enabling vesafb in -mm1 leads to memory corruption. (as
Vladis already mentioned, the same binary works if vesafb is not enabled via
the 'vga=xxx' boot option).
Regards
Thomas
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 22:53 ` 2.6.0-test8-mm1 Thomas Schlichter
@ 2003-10-21 23:27 ` Robert Love
-1 siblings, 0 replies; 61+ messages in thread
From: Robert Love @ 2003-10-21 23:27 UTC (permalink / raw)
To: Thomas Schlichter
Cc: James Simmons, Helge Hafting, Andrew Morton, Valdis.Kletnieks,
linux-kernel, linux-mm
On Tue, 2003-10-21 at 18:53, Thomas Schlichter wrote:
> For me the big question stays why enabling the DEBUG_* options results in a
> corrupt cursor and the false dots on the top of each row... (with both
> kernels)
Almost certainly due to CONFIG_DEBUG_SLAB or CONFIG_DEBUG_PAGEALLOC,
which debug memory allocations and frees.
Code that commits the usual memory bugs (use-after-free, etc.) will
quickly die with these set, whereas without them the bug might never
manifest.
Robert Love
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
@ 2003-10-21 23:27 ` Robert Love
0 siblings, 0 replies; 61+ messages in thread
From: Robert Love @ 2003-10-21 23:27 UTC (permalink / raw)
To: Thomas Schlichter
Cc: James Simmons, Helge Hafting, Andrew Morton, Valdis.Kletnieks,
linux-kernel, linux-mm
On Tue, 2003-10-21 at 18:53, Thomas Schlichter wrote:
> For me the big question stays why enabling the DEBUG_* options results in a
> corrupt cursor and the false dots on the top of each row... (with both
> kernels)
Almost certainly due to CONFIG_DEBUG_SLAB or CONFIG_DEBUG_PAGEALLOC,
which debug memory allocations and frees.
Code that commits the usual memory bugs (use-after-free, etc.) will
quickly die with these set, whereas without them the bug might never
manifest.
Robert Love
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 23:27 ` 2.6.0-test8-mm1 Robert Love
(?)
@ 2003-10-22 2:46 ` Valdis.Kletnieks
-1 siblings, 0 replies; 61+ messages in thread
From: Valdis.Kletnieks @ 2003-10-22 2:46 UTC (permalink / raw)
To: Robert Love
Cc: Thomas Schlichter, James Simmons, Helge Hafting, Andrew Morton,
linux-kernel, linux-mm
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
On Tue, 21 Oct 2003 19:27:25 EDT, Robert Love said:
> On Tue, 2003-10-21 at 18:53, Thomas Schlichter wrote:
>
> > For me the big question stays why enabling the DEBUG_* options results in a
> > corrupt cursor and the false dots on the top of each row... (with both
> > kernels)
>
> Almost certainly due to CONFIG_DEBUG_SLAB or CONFIG_DEBUG_PAGEALLOC,
> which debug memory allocations and frees.
>
> Code that commits the usual memory bugs (use-after-free, etc.) will
> quickly die with these set, whereas without them the bug might never
> manifest.
Right. DEBUG_SLAB and DEBUG_PAGEALLOC will change where things end up in
memory. The part that *I* was surprised at was that turning them on did *NOT*
make the code quickly die as expected - but it *did* corrupt the on-screen
image. That's telling me that the DEBUG stuff is setting canaries that end up
in memory locations that the fbdev code thinks are destined for the display
pixels. (And conversely, that when you build without those two debug options,
that the fbdev code is parking those now not visibly corrupted pixels on top of
somebody's pointer chains and that's where the memory corruption is coming
from.
Or I could just be full of it as usual.. :)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 18:53 ` 2.6.0-test8-mm1 Jurriaan
@ 2003-10-22 17:02 ` James Simmons
0 siblings, 0 replies; 61+ messages in thread
From: James Simmons @ 2003-10-22 17:02 UTC (permalink / raw)
To: Jurriaan; +Cc: linux-kernel
> 2.6.0-test8 + this patch boots perfectly here:
Cool :-)
> kernel /boot/vmlinuz-260test8fb root=/dev/md3 video=matroxfb:xres:1600,yres:1360,depth:16,pixclock:4116,left:304,right:64,upper:46,lower:1,hslen:192,vslen:3,fv:90,hwcursor=off hdd=scsi atkbd_softrepeat=1
>
> This configuration didn't boot in 2.6.0-test8-mm1 (screen stayed in
> 80x25 VGA mode and it crashed before the mode-switch).
:-( I wonder if it has to do with the debugging code discussed in the
other emails.
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 21:05 ` 2.6.0-test8-mm1 Thomas Giese
@ 2003-10-22 17:08 ` James Simmons
0 siblings, 0 replies; 61+ messages in thread
From: James Simmons @ 2003-10-22 17:08 UTC (permalink / raw)
To: Thomas Giese; +Cc: linux-kernel
> this 2.6.0-mm1 is really very good,
>
> but i would VERY enjoy to have the cloop-device from knopper in it!
> we have the cryptloop, why not the very good cloop?
>
> this would be a wonderful combination?
Cool. I'm glad people are having wonderful results.
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-21 20:55 ` 2.6.0-test8-mm1 Panagiotis Papadakos
@ 2003-10-22 17:12 ` James Simmons
0 siblings, 0 replies; 61+ messages in thread
From: James Simmons @ 2003-10-22 17:12 UTC (permalink / raw)
To: Panagiotis Papadakos; +Cc: linux-kernel
Applied.
On Tue, 21 Oct 2003, Panagiotis Papadakos wrote:
> I get the following errors during make bzImage
>
> CC drivers/video/aty/radeon_base.o
> drivers/video/aty/radeon_base.c: In function `radeonfb_setup':
> drivers/video/aty/radeon_base.c:2225: error: `force_measure_pll'
> undeclared (first use in this function)
> drivers/video/aty/radeon_base.c:2225: error: (Each undeclared identifier
> is reported only once
> drivers/video/aty/radeon_base.c:2225: error: for each function it appears
> in.)
> drivers/video/aty/radeon_base.c: In function `__check_force_measure_pll':
> drivers/video/aty/radeon_base.c:2263: error: `force_measure_pll'
> undeclared (first use in this function)
> drivers/video/aty/radeon_base.c: At top level:
> drivers/video/aty/radeon_base.c:2263: error: `force_measure_pll'
> undeclared here (not in a function)
> drivers/video/aty/radeon_base.c:2263: error: initializer element is not
> constant
> drivers/video/aty/radeon_base.c:2263: error: (near initialization for
> `__param_force_measure_pll.arg')
> make[3]: *** [drivers/video/aty/radeon_base.o] Error 1
> make[2]: *** [drivers/video/aty] Error 2
> make[1]: *** [drivers/video] Error 2
> make: *** [drivers] Error 2
>
> and
>
> drivers/video/fbmem.c:219: error: `radeonfb_setup' undeclared here (not in a function)
> drivers/video/fbmem.c:219: error: initializer element is not constant
> drivers/video/fbmem.c:219: error: (near initialization for `fb_drivers[0].setup')
> drivers/video/fbmem.c:219: error: initializer element is not constant
> drivers/video/fbmem.c:219: error: (near initialization for `fb_drivers[0]')
>
>
> So propably these should be applied:
>
> --- radeon_base.c_old 2003-10-21 23:57:20.000000000 +0300
> +++ radeon_base.c_new 2003-10-21 23:52:24.000000000 +0300
> @@ -199,6 +199,7 @@
> static int nomodeset = 0;
> static int ignore_edid = 0;
> static int mirror = 0;
> +static int force_measure_pll = 0;
> static int panel_yres __initdata = 0;
> static int force_dfp __initdata = 0;
> static struct radeonfb_info *board_list = NULL;
>
> --- fbmem.c_old 2003-10-21 23:57:46.000000000 +0300
> +++ fbmem.c_new 2003-10-21 23:51:54.000000000 +0300
> @@ -133,6 +133,7 @@
> extern int tx3912fb_init(void);
> extern int tx3912fb_setup(char*);
> extern int radeonfb_init(void);
> +extern int radeonfb_setup(char *options);
> extern int epson1355fb_init(void);
> extern int pvr2fb_init(void);
> extern int pvr2fb_setup(char*);
>
>
> Panagiotis Papadakos
>
> On Tue, 21 Oct 2003, James Simmons wrote:
>
> >
> > Okay I see people are having alot of problems in the -mm tree. I don't
> > have any problems but I'm working against Linus tree. Could people try the
> > patch against 2.6.0-test8 and tell me if they still have the same results.
> > I have a new patch here:
> >
> > http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
2003-10-24 9:35 2.6.0-test8-mm1 Catani, Antonio
@ 2003-10-24 17:52 ` James Simmons
0 siblings, 0 replies; 61+ messages in thread
From: James Simmons @ 2003-10-24 17:52 UTC (permalink / raw)
To: Catani, Antonio; +Cc: linux-kernel
> Hi list i'm trying use 2.6.0-test8-mm1 and it seems to be ok in my
> machine, but I cant use radeonfb driver because my card dosent know by
> the driver, I have a radeon 9600 pro triplex 128 mb , and lspci don't
> know this card like radeonfb, so it's impossible for me test the
> radeonfb driver.
Try the latest patch at
http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz
It is against 2.6.0-test8 vanillia.
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
@ 2003-10-24 9:35 Catani, Antonio
2003-10-24 17:52 ` 2.6.0-test8-mm1 James Simmons
0 siblings, 1 reply; 61+ messages in thread
From: Catani, Antonio @ 2003-10-24 9:35 UTC (permalink / raw)
To: linux-kernel
Hi list i'm trying use 2.6.0-test8-mm1 and it seems to be ok in my
machine, but I cant use radeonfb driver because my card dosent know by
the driver, I have a radeon 9600 pro triplex 128 mb , and lspci don't
know this card like radeonfb, so it's impossible for me test the
radeonfb driver.
Another tricks, is when use kde after two hours the machine freeze and
the only way to stop is or hardware reset or ALT+SysReq+O for the last
tricks I suspect cooling problem, tonight I try to downclok my cpu and
test.
I have also notice a downgrade of ide transfer rate from 2.6.0-mm6 to
2.6.0-test8-mm1 with the first kernel my hdparm -t was 1750 mb fo
second, now with 2.6.0-test8-mm1 is 1250 but the hdparm -T is the same
45 mb for second, I don't use libata patch
I hope it help!
Antonio Catani
Seceti S.p.A
tel 06-5470598
fax 06-5924010
cell 335-1255453
e-mail antonio.catani@seceti.it
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
@ 2003-10-24 0:14 James Vega
0 siblings, 0 replies; 61+ messages in thread
From: James Vega @ 2003-10-24 0:14 UTC (permalink / raw)
To: linux-kernel
Hi,
A kernel oops was generated when I unplugged my Neuros (usb portable audio player). Let me know if you need any more information. Please keep me on the CC: list as I'm not subscribed to lkml yet.
syslog output from usb-storage detection:
hub 2-0:1.0: new USB device on port 2, assigned address 2
SCSI subsystem initialized
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: NEUROS Model: dig. audio comp. Rev:
Type: Direct-Access ANSI
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
drivers/usb/core/usb.c: registered new driver usb-storage
USB Mass Storage support registered.
SCSI device sda: 252928 512-byte hdwr sectors (129 MB)
sda: test WP failed, assume Write Enabled
sda: asking for cache data failed
sda: assuming drive cache: write through
sda: sda1
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Here's the oops:
usb 2-2: USB disconnect, address 2
releasing anticipatory io scheduler
Unable to handle kernel paging request at virtual address 6b6b6b6b
printing eip:
6b6b6b6b
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
CPU: 0
EIP: 0060:[<6b6b6b6b>] Not tainted VLI
EFLAGS: 00010202
EIP is at 0x6b6b6b6b
eax: f74987b0 ebx: f74966e8 ecx: 00000000 edx: f74966e8
esi: f74966f8 edi: c02c0e60 ebp: f7773e10 esp: f7773e04
ds: 007b es: 007b ss: 0068
Process khubd (pid: 115, threadinfo=f7772000 task=f7775900)
Stack: c01d32f5 f74966e8 f74987b0 f7773e24 c01d4c9a f74966e8 f7770de8 c02c0e48
f7773e38 f8990eee f74966e8 f7496994 c02c0e48 f7773e48 f8991ea2 f7770de8
00000000 f7773e58 c01d0808 f7770f68 f7770f90 f7773e70 c01910c7 f7770f90
Call Trace:
[elevator_exit+51/55] elevator_exit+0x33/0x37
[blk_cleanup_queue+36/104] blk_cleanup_queue+0x24/0x68
[_end+946108438/1070283048] scsi_free_sdev+0x7a/0x11a [scsi_mod]
[_end+946112458/1070283048] scsi_device_dev_release+0x15/0x22 [scsi_mod]
[device_release+26/95] device_release+0x1a/0x5f
[kobject_cleanup+76/107] kobject_cleanup+0x4c/0x6b
[_end+946113731/1070283048] scsi_remove_device+0x93/0xa7 [scsi_mod]
[_end+946111848/1070283048] scsi_forget_host+0x16/0x26 [scsi_mod]
[_end+946091622/1070283048] scsi_remove_host+0x1b/0x63 [scsi_mod]
[_end+946195408/1070283048] storage_disconnect+0x2d/0x3c [usb_storage]
[_end+945846806/1070283048] usb_unbind_interface+0x54/0x82 [usbcore]
[device_release_driver+66/81] device_release_driver+0x42/0x51
[bus_remove_device+78/147] bus_remove_device+0x4e/0x93
[device_del+103/148] device_del+0x67/0x94
[_end+945867833/1070283048] usb_disable_device+0x69/0x96 [usbcore]
[_end+945849256/1070283048] usb_disconnect+0xa3/0xe5 [usbcore]
[_end+945856704/1070283048] hub_port_connect_change+0x50/0x286 [usbcore]
[_end+945857540/1070283048] hub_events+0x10e/0x2ba [usbcore]
[_end+945857999/1070283048] hub_thread+0x1f/0xd2 [usbcore]
[default_wake_function+0/24] default_wake_function+0x0/0x18
[_end+945857968/1070283048] hub_thread+0x0/0xd2 [usbcore]
[kernel_thread_helper+5/11] kernel_thread_helper+0x5/0xb
Code: Bad EIP value.
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: 2.6.0-test8-mm1
@ 2003-10-20 11:35 Jan Ischebeck
0 siblings, 0 replies; 61+ messages in thread
From: Jan Ischebeck @ 2003-10-20 11:35 UTC (permalink / raw)
To: akpm; +Cc: lkml
Hi Andrew,
The new framebuffer code for ATI RADEON grfx cards doesn't work correct.
After startup the screen switches to an unsupported mode, flickers and
just shows a small line at the top.I get a freq of 87 hz instead of 60.
Zhuang:~# fbset
mode "1024x768-87"
# D: 44.901 MHz, H: 35.523 kHz, V: 86.960 Hz
geometry 1024 768 1024 768 8
timings 22271 56 24 33 8 160 8
laced true
rgba 8/0,8/0,8/0,0/0
endmode
switching to 60 hz doesn't improve the flickering screen.
(fbset 1024x768-60)
Probably this is connected to a warning about '*dcc2*' function I got
compiling the Radeon driver. I will recompile later to see the warning
again.
my config:
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=y
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
...
Thanks for a new -mm kernel,
Jan
--
Jan Ischebeck <mail@jan-ischebeck.de>
^ permalink raw reply [flat|nested] 61+ messages in thread
end of thread, other threads:[~2003-10-24 17:52 UTC | newest]
Thread overview: 61+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-10-20 9:05 2.6.0-test8-mm1 Andrew Morton
2003-10-20 9:05 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-20 9:40 ` 2.6.0-test8-mm1 Kirill Korotaev
2003-10-20 9:49 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-20 11:05 ` 2.6.0-test8-mm1 Peter Lieverdink
2003-10-20 18:49 ` 2.6.0-test8-mm1 Helge Hafting
2003-10-21 11:06 ` 2.6.0-test8-mm1 [matroxfb not working] Jurriaan
2003-10-20 11:18 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-20 13:22 ` 2.6.0-test8-mm1 Jonathan Brown
2003-10-20 15:00 ` 2.6.0-test8-mm1 Antonio Dolcetta
2003-10-20 16:32 ` 2.6.0-test8-mm1 Jonathan Brown
2003-10-21 7:28 ` 2.6.0-test8-mm1 Antonio Dolcetta
2003-10-20 15:32 ` 2.6.0-test8-mm1 John Cherry
2003-10-20 15:32 ` 2.6.0-test8-mm1 John Cherry
2003-10-20 16:11 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-20 21:48 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-20 21:48 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-20 22:01 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-20 22:17 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-20 22:17 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-20 22:30 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 0:43 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 0:14 ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-21 0:27 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-21 0:27 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-21 0:46 ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-21 1:56 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-21 1:56 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-21 2:54 ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-21 3:49 ` 2.6.0-test8-mm1 Jeremy Fitzhardinge
2003-10-21 3:49 ` 2.6.0-test8-mm1 Jeremy Fitzhardinge
2003-10-21 8:39 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 17:47 ` 2.6.0-test8-mm1 James Simmons
2003-10-21 17:47 ` 2.6.0-test8-mm1 James Simmons
2003-10-21 18:53 ` 2.6.0-test8-mm1 Jurriaan
2003-10-22 17:02 ` 2.6.0-test8-mm1 James Simmons
2003-10-21 20:23 ` 2.6.0-test8-mm1 Helge Hafting
2003-10-21 20:23 ` 2.6.0-test8-mm1 Helge Hafting
2003-10-21 20:36 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 20:42 ` 2.6.0-test8-mm1 James Simmons
2003-10-21 20:42 ` 2.6.0-test8-mm1 James Simmons
2003-10-21 21:05 ` 2.6.0-test8-mm1 Thomas Giese
2003-10-22 17:08 ` 2.6.0-test8-mm1 James Simmons
2003-10-21 22:53 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 22:53 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 23:27 ` 2.6.0-test8-mm1 Robert Love
2003-10-21 23:27 ` 2.6.0-test8-mm1 Robert Love
2003-10-22 2:46 ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-21 20:55 ` 2.6.0-test8-mm1 Panagiotis Papadakos
2003-10-22 17:12 ` 2.6.0-test8-mm1 James Simmons
2003-10-20 19:21 ` [BUG] 2.6.0-test8-mm1 Ramón Rey Vicente
2003-10-20 20:10 ` Andrew Morton
2003-10-20 20:10 ` Andrew Morton
2003-10-20 21:53 ` Ramón Rey Vicente
2003-10-21 8:03 ` 2.6.0-test8-mm1 Stephane Jourdois
2003-10-21 15:43 ` 2.6.0-test8-mm1 bill davidsen
2003-10-21 17:42 ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-20 11:35 2.6.0-test8-mm1 Jan Ischebeck
2003-10-24 0:14 2.6.0-test8-mm1 James Vega
2003-10-24 9:35 2.6.0-test8-mm1 Catani, Antonio
2003-10-24 17:52 ` 2.6.0-test8-mm1 James Simmons
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.