linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* 2.6.1-mm1
@ 2004-01-09  9:40 Andrew Morton
  2004-01-09 14:47 ` 2.6.1-mm1 Christoph Hellwig
                   ` (5 more replies)
  0 siblings, 6 replies; 37+ messages in thread
From: Andrew Morton @ 2004-01-09  9:40 UTC (permalink / raw)
  To: linux-kernel, linux-mm


ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm1/


- A big ALSA update.

- Added support for kgdb on the x86_64 platform.  You'll need a couple of
  patches to gdb-6.0 itself to use it properly.  They may be found at

  ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/gdb/gdb-6.0/

- Dropped the remap_file_pages() and prefault work - it is suspected of
  causing stability problems.

- The PCI IDE drivers should work as modules now.

- A significant update to the NFS client.

- A large s390 update.  Various device drivers and IO layer changes there.

  Note that the 's390' patches actually include significant core MM changes
  in the area of pte writeback/invalidate, rmap tweaks, etc.  Relevant
  patches are:

	s390-11-tlb-flush-optimisation.patch
	s390-12-dirty-referenced-bits.patch
	s390-13-tlb-flush-race-fix.patch
	s390-14-rmap-optimisation.patch
	s390-15-superfluous-flush_tlb_range-calls.patch
	s390-16-follow_page-lockup-fix.patch

- Merged the large SN2 update which Pat and Christoph have been discussing.





Changes since 2.6.1-rc2-mm1:


-ppc64-proc-fixes.patch
-ppc64-missing-section-definition.patch
-xfs-update-01.patch

 Merged

+alsa-101.patch

 ALSA update

+kgdb-x86_64-support.patch

 kgdb for x86_64

+uml-build-fix.patch

 Fix the build for UML.

+loop-fd-leak-fix.patch

 Fix file descriptior leak in loop_set_fd()

-sn-console-update.patch
-sn-serial-medusa-fix.patch

 Dropped - these are in the sn2 update, below.

+qla1280-build-fix.patch

 Fix qla1280-update-2.patch

-alsa-sleep-in-spinlock-fix.patch
-alsa-gus-scheduling-in-interrupt-fix.patch

 Now in the ALSA patch.

-68k-369.patch

 Greg had a few issues with this.

-set_cpus_allowed-locking-fix-fix.patch

 Folded into set_cpus_allowed-locking-fix.patch

-remap_file_pages-fixes-2.6.1-A3.patch
-remap_file_pages-prot-2.6.1-H2.patch
-prefault-2.6.0-A0.patch

 These seem to need a litle more work.

+do_no_page-leak-fix.patch

 Fix possible memleak in do_no_page()

+vt-locking-fixes-oops_in_progress-fix.patch

 Suppress warning about console_sem if we're processing an oops.

+drm-include-fix.patch

 Include headers from the right directory.

+kthread-primitive.patch
+use-kthread-primitives.patch

 Rusty's kthread abstraction.  Undecided as to whether we really want this,
 unless hotplug CPU is merged.

+check-for-truncated-modules.patch

 Sanity check for bad module files.

+forcedeth-v20.patch

 Update to the nForce ethernet driver

+alpha-module-relocation-overflow-fix.patch

 Fix module processing on Alpha

+eicon-memory-access-size-fix.patch

 Fix IO port access in this ISDN driver

+ppc32-of-bootwrapper-support.patch

 ppc32 Open Firmware stuff.

+lsi-megaraid-pci-id.patch

 Add a new PCI ID to this driver

+ide-pci-modules-fix.patch

 Maek IDE drivers work as modules.
 
+use-diff-dash-p.patch

 Start a fight over how patches should look.

+use-kconfig-range-for-NR_CPUS.patch

 Use the Kconfig `range' statement for specifying NR_CPUS

+sysfs-pin-kobject.patch

 sysfs oops fix

+bio-documentation-update.patch

 Docco

+nfs-fix-bogus-setattr-calls.patch
+nfs-optimise-COMMIT-calls.patch
+nfs-open-intent-fix.patch
+nfs-readonly-mounts-fix.patch
+nfs-client-deadlock-fix.patch
+nfs-rpc-debug-oops-fix.patch

 NFS update

+s390-01-base.patch
+s390-02-common-io-layer.patch
+s390-03-console-driver.patch
+s390-04-dasd-driver.patch
+s390-05-tape-driver.patch
+s390-06-network-drivers.patch
+s390-07-zfcp-host-adapter.patch
+s390-08-new-3270-driver.patch
+s390-09-32-bit-emulation-fixes.patch
+s390-10-32-bit-ioctl-emulation-fixes.patch
+s390-11-tlb-flush-optimisation.patch
+s390-12-dirty-referenced-bits.patch
+s390-13-tlb-flush-race-fix.patch
+s390-14-rmap-optimisation.patch
+s390-15-superfluous-flush_tlb_range-calls.patch
+s390-16-follow_page-lockup-fix.patch

 s390 and core MM work

+sn01.patch
+sn03.patch
+sn05.patch
+sn06.patch
+sn07.patch
+sn08.patch
+sn09.patch
+sn10.patch
+sn11.patch
+sn12.patch
+sn13.patch
+sn14.patch
+sn15.patch
+sn16.patch
+sn17.patch
+sn18.patch
+sn19.patch
+sn20.patch
+sn21.patch
+sn22.patch
+sn23.patch
+sn24.patch
+sn25.patch
+sn26.patch
+sn27.patch
+sn28.patch
+sn29.patch
+sn30.patch
+sn31.patch
+sn32.patch
+sn33.patch
+sn34.patch
+sn35.patch
+sn36.patch
+sn37.patch
+sn38.patch
+sn39.patch
+sn40.patch
+sn41.patch
+sn42.patch
+sn43.patch
+sn44.patch
+sn45.patch
+sn46.patch
+sn47.patch
+sn48.patch
+sn49.patch
+sn50.patch
+sn51.patch
+sn52.patch
+sn53.patch
+sn54.patch
+sn55.patch
+sn56.patch
+sn57.patch
+sn58.patch
+sn59.patch
+sn60.patch
+sn61.patch
+sn62.patch
+sn63.patch
+sn65.patch
+sn66.patch
+sn67.patch
+sn68.patch
+sn69.patch
+sn70.patch
+sn71.patch
+sn73.patch
+sn74.patch

 SN2 updates




All 393 patches

mm.patch
  add -mmN to EXTRAVERSION

alsa-101.patch
  ALSA 1.0.1

2.6.0-rc1-netdrvr-exp1.patch

kgdb-ga.patch
  kgdb stub for ia32 (George Anzinger's one)
  kgdbL warning fix
  kgdb buffer overflow fix
  kgdbL warning fix
  kgdb: CONFIG_DEBUG_INFO fix
  x86_64 fixes

kgdb-doc-fix.patch
  correct kgdb.txt Documentation link (against  2.6.1-rc1-mm2)

kgdboe-netpoll.patch
  kgdb-over-ethernet via netpoll

kgdboe-non-ia32-build-fix.patch

kgdb-x86_64-support.patch
  kgdb for x86_64 2.6 kernels

uml-build-fix.patch
  Fix UML compilation breakage in fs/proc/task_mmu.c

radeon-line-length-fix.patch
  radeonfb line length fix

scsi-rename-TIMEOUT.patch
  fix scsi.h #define collision

loop-fix-hardsect.patch
  loop: fix hard sector size

loop-fd-leak-fix.patch
  loop: fix file refcount leak

must-fix.patch
  must fix lists update
  must fix list update
  mustfix update

must-fix-update-5.patch
  must-fix update

RD1-open-mm.patch

RD2-release-mm.patch

RD3-presto_journal_close-mm.patch

RD4-f_mapping-mm.patch

RD5-f_mapping2-mm.patch

RD6-i_sem-mm.patch

RD7-f_mapping3-mm.patch

RD8-generic_osync_inode-mm.patch

RD9-bd_acquire-mm.patch

RD10-generic_write_checks-mm.patch

RD11-I_BDEV-mm.patch

cramfs-use-pagecache.patch
  cramfs: use pagecache better

invalidate_inodes-speedup.patch
  invalidate_inodes speedup
  more invalidate_inodes speedup fixes

net-jiffy-normalisation-fix.patch
  NET: Normalize jiffies reported to userspace, in neighbor management code

input-mousedev-remove-jitter.patch
  Input: smooth out mouse jitter

input-mousedev-ps2-emulation-fix.patch
  mousedev PS/@ emulation fix

input-01-i8042-suspend.patch
  input: i8042 suspend

input-02-i8042-option-parsing.patch
  input: i8042 option parsing

input-03-psmouse-option-parsing.patch
  input: psmouse option parsing

input-04-atkbd-option-parsing.patch
  input: atkbd option parsing

input-05-missing-module-licenses.patch
  input: missing module licenses

input-06-Kconfig-Synaptics-help.patch
  Kconfig Synaptics help

input-07-sis-aux-port.patch
  input: SiS AUX port

input-11-98busmouse-compile-fix.patch
  Fix compile error in 98busmouse.c module

input-12-mouse-drivers-use-module_param.patch
  Convert mouse drivers to use module_param

input-13-tsdev-use-module_param.patch
  Convert tsdev to use module_param

keyboard-repeat-fix.patch
  Fix key repeat problems

input-use-after-free-checks.patch
  input layer debug checks

cpu_sibling_map-fix.patch
  cpu_sibling_map fix

acpi-20031203.patch

acpi-20031203-fix.patch

cfq-4.patch
  CFQ io scheduler
  CFQ fixes

config_spinline.patch
  uninline spinlocks for profiling accuracy.

ppc64-syscall6-macro.patch
  add syscall6 macro to ppc64

ppc64-sched_clock-2.patch
  ppc64: add sched_clock

ppc64-32bit-compat-update.patch
  ppc64: 32bit compat update

ppc64-OF-device-tree-update.patch
  ppc64: Change to new OF device tree API

ppc64-numa-sign-extension-fix-2.patch
  ppc64: fix sign extension in numa code

ppc64-bar-0-fix.patch
  Allow PCI BARs that start at 0

ppc64-reloc_hide.patch

ppc64-IRQ_INPROGRESS-fix.patch
  ppc64: revert IRQ_INPROGRESS change

qla1280-update-2.patch
  qla1280 update

qla1280-build-fix.patch
  qla1280.c doesn't compile

sym-speed-fix.patch
  sym2 Ultra-160 fix

aic7xxx_old-proc-oops-fix.patch
  aic7x_old /proc oops fix

aic7xxx_old-oops-fix.patch

ramdisk-leak-fix.patch
  fix memory leak in ram disk

ramdisk-cleanup.patch

intel8x0-cleanup.patch
  intel8x0 cleanups

pdflush-diag.patch

zap_page_range-debug.patch
  zap_page_range() debug

asus-L5-fix.patch
  Asus L5 framebuffer fix

jffs-use-daemonize.patch

get_user_pages-handle-VM_IO.patch

support-zillions-of-scsi-disks.patch
  support many SCSI disks

pci_set_power_state-might-sleep.patch

CONFIG_STANDALONE-default-to-n.patch
  Make CONFIG_STANDALONE default to N

extra-buffer-diags.patch

CONFIG_SYSFS.patch
  From: Pat Mochel <mochel@osdl.org>
  Subject: [PATCH] Add CONFIG_SYSFS

CONFIG_SYSFS-boot-from-disk-fix.patch

slab-leak-detector.patch
  slab leak detector

loop-module-alias.patch
  loop needs MODULE_ALIAS_BLOCK

loop-bio-index-fix.patch
  loop bio indexing fix

loop-highmem.patch
  remove useless highmem bounce from loop/cryptoloop

loop-bio-clone.patch
  loop bio clone optimisation

loop-recycle.patch
  loop bio recycling optimisation

acpi-pm-timer.patch
  ACPI PM Timer

acpi-timer-fixes-A5.patch
  ACPI PM timer fixes

timer_pm-warning-fix.patch

as-regression-fix.patch
  Fix IO scheduler regression

as-request-poisoning.patch
  AS: request poisoning

as-request-poisoning-fix.patch
  AS: request poisining fix

as-fix-all-known-bugs.patch
  AS fixes

as-new-process-estimation.patch
  AS: new process estimation

as-cooperative-thinktime.patch
  AS: thinktime improvement

scale-nr_requests.patch
  scale nr_requests with TCQ depth

truncate_inode_pages-check.patch

local_bh_enable-warning-fix.patch

pnp-fix-2.patch
  PnP Fixes #2

pnp-fix-3.patch
  PnP Fixes #3

alpha-stack-dump.patch

sysfs_remove_dir-vs-dcache_readdir-race-fix.patch
  sysfs_remove_dir Vs dcache_readdir race fix

invalidate_mmap_range-non-gpl-export.patch
  mark invalidate_mmap_range() as EXPORT_SYMBOL

sym2-speed-selection-fix.patch
  Speed selection fix for sym53c8xx

ppc-export-consistent_sync_page.patch
  PPC32: Export consistent_sync_page.

ppc-use-EXPORT_SYMBOL_NOVERS.patch
  PPC32: Change all EXPORT_SYMBOL_NOVERS to EXPORT_SYMBOL in ppc_ksyms.c

ppc-CONFIG_PPC_STD_MMU-fix.patch
  PPC32: Select arch/ppc/kernel/head.S on CONFIG_PPC_STD_MMU.

ppc-IBM-MPC-header-cleanups.patch
  PPC32: Minor cleanups to IBM4xx and MPC82xx headers.

percpu-gcc-34-warning-fix.patch
  fix gcc-3.4 warning in percpu code

nr_requests-oops-fix.patch
  Fix oops when modifying /sys/block/dm-0/queue/nr_requests

netfilter_bridge-compile-fix.patch

aacraid-warning-fix.patch
  aacraid warning fix

atapi-mo-support.patch
  ATAPI MO drive support

mt-ranier-support.patch
  mt rainier support

atapi-mo-support-update.patch
  ATAPI MO support update
  cdrom_open fix

ppp_async-locking-fix.patch
  Make ppp_async callable from hard interrupt

make-try_to_free_pages-walk-zonelist.patch
  make try_to_free_pages walk zonelist

make-try_to_free_pages-walk-zonelist-fix.patch
  zone scanning fix

remove-CardServices-from-pcmcia-net-drivers.patch
  CardServices() removal from pcmcia net drivers

remove-CardServices-from-ide-cs.patch
  From: Arjan van de Ven <arjanv@redhat.com>
  Subject: Re: [PATCH 1/10] CardServices() removal from pcmcia net drivers

remove-CardServices-from-drivers-net-wireless.patch
  remove CardServices() from drivers/net/wireless

remove-CardServices-from-drivers-serial.patch
  Remvoe CardServices() from drivers/serial

remove-CardServices-from-drivers-serial-fix.patch
  serial_cs CardServices removal fix

remove-CardServices-from-axnet_cs.patch
  remvoe CardServices from axnet_cs

remove-CardServices-final.patch
  final CardServices() removal patches

CardServices-compatibility-layer.patch
  CardServices compatibility layer

sysfs-add-simple-class-device-support.patch
  sysfs: add "simple" class device support

sysfs-remove-tty-class-device-logic.patch
  sysfs: remove tty class device logic

sysfs-add-mem-device-support.patch
  sysfs: add mem class

sysfs-add-misc-class.patch
  sysfs: add misc class

vc-init-race-fix.patch
  virtual consle initialisation race fix

sysfs-add-video-class.patch
  sysfs: add video class

sysfs-add-oss-class.patch
  sysfs sound class patch for OSS drivers

sysfs-add-alsa-class.patch
  sysfs sound class patch for ALSA drivers

sysfs-add-input-class-support.patch
  sysfs: input class patch

tridentfb-non-flatpanel-fix.patch
  fix for tridentfb.c usage on CRTs.

CONFIG_EPOLL-file_struct-members.patch
  CONFIG_EPOLL=n space reduction

epoll-oneshot-support.patch
  One-shot support for epoll

kill_fasync-speedup.patch
  kill_fasync speedup

o21-sched.patch
  O21 for interactivity 2.6.0

sched-clock-2.6.0-A1.patch
  Relax synchronization of sched_clock()

sched-can-migrate-2.6.0-A2.patch
  can_migrate_task cleanup

sched-cleanup-2.6.0-A2.patch
  CPU scheduler cleanup

sched-style-2.6.0-A5.patch
  sched.c style cleanups

decrypt-CONFIG_PDC202XX_FORCE-help.patch
  Change cryptic description and help for CONFIG_PDC202XX_FORCE

ide-siimage-seagate.patch

ide-siimage-stack-fix.patch

ide-siimage-sil3114.patch

ide-pdc_old-pio-fix.patch

ide-pdc_old-udma66-fix.patch

ide-pdc_old-66mhz_clock-fix.patch

ide-pdc_new-proc.patch

make-for_each_cpu-iterator-more-friendly.patch
  Make for_each_cpu() Iterator More Friendly

make-for_each_cpu-iterator-more-friendly-fix.patch
  Fix alpha build failure

use-for_each_cpu-in-right-places.patch
  Use for_each_cpu() Where It's Meant To Be

for_each_cpu-oprofile-fix.patch
  for_each_cpu oprofile fix

for_each_cpu-oprofile-fix-2.patch

fa311-mac-address-fix.patch
  wrong mac address with netgear FA311 ethernet card

kernel-locking-doc-end-tags-fix.patch
  Missing end tags in kernel-locking kerneldoc

rcupdate-c99-initialisers.patch
  C99 change to rcupdate.h

68k-339.patch
  M68k floppy selection

68k-340.patch
  M68k head console

68k-341.patch
  M68k head unused

68k-342.patch
  M68k head comments

68k-343.patch
  M68k head pic

68k-344.patch
  M68k head white space

68k-345.patch
  M68k cache mode

68k-346.patch
  M68k RMW accesses

68k-347.patch
  Atari Hades PCI C99

68k-348.patch
  Amiga sound C99

68k-349.patch
  BVME6000 RTC C99

68k-350.patch
  M68k symbol exports

68k-351.patch
  M68k math emu C99

68k-352.patch
  MVME16x RTC C99

68k-353.patch
  Q40 interrupts C99

68k-354.patch
  Sun-3 ID PROM C99

68k-355.patch
  Mac ADB IOP fix

68k-359.patch
  Mac ESP SCSI setup

68k-360.patch
  Mac SCSI

68k-361.patch
  Macfb setup

68k-364.patch
  Mac ADB

68k-365.patch
  ncr53c7xx SCSI

68k-366.patch
  BVME6000 SCSI

68k-367.patch
  Amiga Gayle IDE cleanup

68k-368.patch
  Amiga Gayle E-Matrix 530 IDE

68k-374.patch
  Amiga debug fix

68k-375.patch
  Mac II VIA

68k-377.patch
  M68k asm/system.h

68k-378.patch
  Amiga NCR53c710 SCSI

68k-379.patch
  Amiga core C99

68k-380.patch
  M68k has no VGA/MDA

68k-381.patch
  M68k thread

68k-382.patch
  M68k thread_info

68k-383.patch
  M68k extern inline

68k-384.patch
  NCR53C9x SCSI inline

68k-385.patch
  Cirrusfb extern inline

68k-386.patch
  Genrtc warning

68k-387.patch
  M68k Documentation

68k-390.patch
  Amiga Buddha/CatWeasel IDE

printk_ratelimit.patch
  generalise net_ratelimit (printk_ratelimit)

printk_ratelimit-fix.patch
  parintk_ratelimit fix

freevxfs-MODULE_ALIAS.patch
  MODULE_ALIAS for freevxfs

trident-cleanup-indentation-D1-2.6.0.patch
  reindent trident OSS sound driver

trident-sound-driver-fixes.patch
  trident OSS sound driver fixes

trident-cleanup-2.patch
  trident: use pr_debug instead of home-brewed TRDBG

compound-page-page_count-fix.patch
  fix page counting for compound pages

inia100-fix.patch
  fix inia100 driver

MAINTAINERS-lanana-update.patch
  MAINTAINERS update

devfs-joystick-fix.patch
  fix devfs names for joystick

s3-sleep-remove-debug-code.patch
  s3 sleep: Kill obsolete debugging code

swsusp-doc-updates.patch
  swsusp/sleep documentation update

watchdog-updates.patch
  Watchdog patches

watchdog-updates-2.patch
  Watchdog patches (part 2)

ext2_new_inode-cleanup.patch
  ext2_new_inode nanocleanup

ext2-s_next_generation-fix.patch
  ext2: s_next_generation locking

ext3-s_next_generation-fix.patch
  ext3: s_next_generation fixes

alt-arrow-console-switch-fix.patch
  Fix Alt-arrow console switch droppage

ia32-remove-SIMNOW.patch
  Remove x86_64 leftover SIMNOW code

softcursor-fix.patch
  Fix softcursor

ext2-debug-build-fix.patch
  ext2: fix build when EXT2_DEBUG is set

efi-inline-fixes.patch
  Fix weird placement of inline

do_timer_gettime-cleanup.patch
  do_timer_gettime() cleanup

set_cpus_allowed-locking-fix.patch
  set_cpus_allowed locking
  fix set_cpus_allowed locking even more

rmmod-race-fix.patch
  module removal race fix

remove-hpet-intel-check.patch
  Remove Intel check in i386 HPET code

devfs-d_revalidate-oops-fix.patch
  devfs d_revalidate race/oops fix

laptop-mode-2.patch
  laptop-mode for 2.6, version 6

laptop-mode-doc-update.patch
  Documentation/laptop-mode.txt

e1000-1019-fix.patch
  e1000: device 1019 fix

ali-m1533-hang-fix.patch
  ALI M1533 audio hang fix

start_this_handle-retval-fix.patch
  jbd: start_this_handle() return value fix

remove-eicon-isdn-driver.patch
  remove old Eicon isdn driver

do_no_page-leak-fix.patch
  do_no_page leak fix

vt-locking-fixes.patch
  VT locking fixes

vt-locking-fixes-warning-fix.patch

vt-locking-fixes-oops_in_progress-fix.patch

pid_max-fix.patch
  Bug when setting pid_max > 32k

allow-SGI-IOC4-chipset-support.patch
  allow SGI IOC4 chipset support

oss-dmabuf-deadlock-fix.patch
  OSS dmabuf deadlock fix

workqueue-cleanup.patch
  Remove redundant code in workqueue.c

libata-update.patch
  update libata

tridentfb-documentation-fix.patch
  tridentfb documentation fix

proc_pid_lookup-speedup.patch
  Optimize proc_pid_lookup

bio_endio-clarifications.patch
  clarify meaning of bio fields in the end_io function

rtc-leak-fixes.patch
  2.6.1 RTC leaks.

simplify-node-zone-fields-3.patch
  Simplify node/zone field in page->flags

r8169-oops-fix.patch
  erroneous __devinitdata in the r8169 driver

radeonfb-pdi-id-addition.patch
  Identify RADEON Yd in radeonfb

mpt-fusion-update.patch
  MPT Fusion driver 3.00.00 update

use-soft-float.patch
  Use -msoft-float

DRM-cvs-update.patch
  DRM cvs update

drm-include-fix.patch

raid6-20040107.patch
  RAID-6

kthread-primitive.patch
  kthread primitive

use-kthread-primitives.patch
  Use kthread primitives

check-for-truncated-modules.patch
  check for truncated modules

forcedeth-v20.patch
  forcedeth: v20

alpha-module-relocation-overflow-fix.patch
  Relocation overflow with modules on Alpha

eicon-memory-access-size-fix.patch
  Eicon isdn driver hardware access fix

ppc32-of-bootwrapper-support.patch
  ppc32: OF bootwrapper support

lsi-megaraid-pci-id.patch
  LSI Logic MegaRAID3 PCI ID

ide-pci-modules-fix.patch
  fix issues with loading PCI IDE drivers as modules

use-diff-dash-p.patch
  Fix Documentation/SubmittingPatches to use -p

use-kconfig-range-for-NR_CPUS.patch
  Kconfig: use range for NR_CPUS

sysfs-pin-kobject.patch
  sysfs: pin kobjects to fix use-after-free crashes

bio-documentation-update.patch
  bio documentation update

nfs-fix-bogus-setattr-calls.patch
  NFS: fix bogus setattr calls

nfs-optimise-COMMIT-calls.patch
  nfs: Optimize away unnecessary NFSv3 COMMIT calls.

nfs-open-intent-fix.patch
  nfs: Fix an open intent bug

nfs-readonly-mounts-fix.patch
  nfs: Fix readonly mounts

nfs-client-deadlock-fix.patch
  nfs: Fix a possible client deadlock

nfs-rpc-debug-oops-fix.patch
  nfs: Fix an Oops in the RPC debug code...

m68knommu-module-support.patch
  allow for building module support for m68knommu architecture

m68knommu-module-support-2.patch
  add module support for m68knommu architecture

m68knommu-sched_clock.patch
  sched_clock() for m68knommu architectures

m68knommu-include-fix.patch
  m68knommu include fix

m68knommu-cpustats-fix.patch
  fix cpu stats in m68knommu entry.S

m68knommu-types-cleanup.patch
  use m68k/types.h for m68knommu

m68knommu-find_extend_vma.patch
  implement find_extend_vma() for nommu

s390-01-base.patch
  s390: general update

s390-02-common-io-layer.patch
  s390: common i/o layer

s390-03-console-driver.patch
  s390: console driver.

s390-04-dasd-driver.patch
  s390: dasd driver

s390-05-tape-driver.patch
  s390: tape driver.

s390-06-network-drivers.patch
  s390: network drivers

s390-07-zfcp-host-adapter.patch
  s390: zfcp host adapter

s390-08-new-3270-driver.patch
  s390: new 3270 driver.

s390-09-32-bit-emulation-fixes.patch
  s390: 32 bit emulation fixes.

s390-10-32-bit-ioctl-emulation-fixes.patch
  s390: 32 bit ioctl emulation fixes.

s390-11-tlb-flush-optimisation.patch
  s390: tlb flush optimization.

s390-12-dirty-referenced-bits.patch
  s390: physical dirty/referenced bits.

s390-13-tlb-flush-race-fix.patch
  s390: tlb flush race.

s390-14-rmap-optimisation.patch
  s390: rmap optimization.

s390-15-superfluous-flush_tlb_range-calls.patch
  s390: superflous flush_tlb_range calls.

s390-16-follow_page-lockup-fix.patch
  s390: endless loop in follow_page.

const-fixes.patch
  const vs. __attribute__((const)) confusion

sn01.patch
  sn: Some hwgraph code clean up

sn03.patch
  sn: copyright update

sn05.patch
  sn: namespace cleanup: ioerror_dump->sn_ioerror_dump

sn06.patch
  sn: kill big endian stuff

sn07.patch
  sn: kill $Id$

sn08.patch
  sn: remove unused enum

sn09.patch
  From: Pat Gefre <pfg@sgi.com>
  Subject: Re: [PATCH] Updating our sn code in 2.6] - Patch 009

sn10.patch
  sn: Kill nag.h

sn11.patch
  sn: Kill the arcs/*.h files

sn12.patch
  sn: Delete invent.h

sn13.patch
  sn: General code clean up of sn/io/io.c

sn14.patch
  sn: machvec/pci.c clean up

sn15.patch
  sn: General clean up of xbow.c

sn16.patch
  sn: Remove the bridge and xbridge code - everything not PIC

sn17.patch
  sn: Fix the last patch - missed an IS_PIC_SOFT and needed the CG definition

sn18.patch
  sn: Fix the last patch - missed an IS_PIC_SOFT and needed the CG definition

sn19.patch
  sn: New code for Opus and CGbrick

sn20.patch
  sn: klgraph.c clean up

sn21.patch
  sn: More klgraph.c clean up

sn22.patch
  sn: General module.c clean up

sn23.patch
  sn: shubio.c cleanup

sn24.patch
  sn: General xtalk.c clean up

sn25.patch
  sn: irq clean up and update

sn26.patch
  sn: code pruning - a couple of adds due to the clean up

sn27.patch
  sn: Fix a couple of compiler warnings

sn28.patch
  sn: hcl.c clean up for init failures and OOM

sn29.patch
  sn: Some small bte code clean ups

sn30.patch
  sn: Moved code out of pciio and into its own file - snia_if.c and renamed the functions

sn31.patch
  sn: A few small clean ups

sn32.patch
  sn: Some more minor clean up

sn33.patch
  sn: Remove __ASSEMBLY__ tags from shubio.h

sn34.patch
  sn: Small check for invalid node in shub ioctl function

sn35.patch
  sn: More code clean up - this time ioconfig_bus.c

sn36.patch
  sn: Code changes for interrupt redirect

sn37.patch
  sn: Forget to check in the _reg file

sn38.patch
  sn: Merged 2 files into another (sgi_io_sim and irix_io_init into sgi_io_init)

sn39.patch
  sn: Support for the LCD

sn40.patch
  sn: Missed an include file in the last patch

sn41.patch
  sn: One less panic

sn42.patch
  sn: SAL interface clean up

sn43.patch
  sn: Fixes for shuberror.c

sn44.patch
  sn: Need a bigger max compact node value

sn45.patch
  sn: Use numionodes

sn46.patch
  sn: Change the definition and usage of iio_itte - make it an array

sn47.patch
  sn: Debug clean up in pcibr_dvr.c

sn48.patch
  sn: New pci provider interfaces

sn49.patch
  sn: Fix IIO_ITTE_DISABLE() args

sn50.patch
  sn: Added a missed opus mod and oom mod

sn51.patch
  sn: Added cbrick_type_get_nasid() function

sn52.patch
  sn: Clean up the bit twiddle macros in pcibr_config.c

sn53.patch
  sn: Fixed an oom in pci_bus_cvlink.c

sn54.patch
  sn: Remove the pcibr_wrap... functions

sn55.patch
  sn: printk cleanup

sn56.patch
  sn: pci dma cleanup

sn57.patch
  sn: Make pcibr debug variables static

sn58.patch
  sn: Include file clean up in pcibr_hints.c

sn59.patch
  sn: Added call to pcireg_intr_status_get

sn60.patch
  sn: More code clean up = mostly pcibr_slot.c

sn61.patch
  sn: pcibr_rrb.c cleanup

sn62.patch
  sn: Minor code clean up of pcibr_error.c

sn63.patch
  sn: sn_pci_fixup() clean up or is it fix up ???

sn65.patch
  sn: Remove irix_io_init - replace with sgi_master_io_infr_init

sn66.patch
  sn: Don't call init_hcl from the fixup code

sn67.patch
  sn: Error devenable not used - delete defs

sn68.patch
  sn: Delete unused code in pcibr_slot.c

sn69.patch
  sn: Delete unused pciio.c code (???_host???_[sg]et)

sn70.patch
  sn: Minor clean up for ml_iograph.c

sn71.patch
  sn: Simulator check in pci_bus_cvlink.c

sn73.patch
  sn: Mostly printk clean up and remove some dead code

sn74.patch
  sn: A little re-formatting

list_del-debug.patch
  list_del debug check

print-build-options-on-oops.patch

show_task-free-stack-fix.patch
  show_task() fix and cleanup

oops-dump-preceding-code.patch
  i386 oops output: dump preceding code

lockmeter.patch

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
  Fix 4G/4G and WP test lockup
  4G/4G KERNEL_DS usercopy again
  Fix 4G/4G X11/vm86 oops
  Fix 4G/4G athlon triplefault
  4g4g SEP fix
  Fix 4G/4G split fix for pre-pentiumII machines

4g4g-locked-userspace-copy.patch
  Do a locked user-space copy for 4g/4g

ppc-fixes.patch
  make mm4 compile on ppc

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 XFS fix

dio-aio-fixes.patch
  direct-io AIO fixes
  dio-aio fix fix

aio-fallback-bio_count-race-fix-2.patch
  AIO+DIO bio_count race fix

aio-sysctl-parms.patch
  aio sysctl parms

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-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] 37+ messages in thread

* Re: 2.6.1-mm1
  2004-01-09 14:53 ` 2.6.1-mm1 Wojciech 'Sas' Cieciwa
@ 2004-01-09 14:21   ` Bartlomiej Zolnierkiewicz
  0 siblings, 0 replies; 37+ messages in thread
From: Bartlomiej Zolnierkiewicz @ 2004-01-09 14:21 UTC (permalink / raw)
  To: Wojciech 'Sas' Cieciwa; +Cc: Andrew Morton, linux-kernel, linux-mm


On Fri, 9 Jan 2004, Wojciech 'Sas' Cieciwa wrote:

> On Fri, 9 Jan 2004, Andrew Morton wrote:
>
> [...]
> >
> > - The PCI IDE drivers should work as modules now.

They always have worked as modules, it fixes case when PCI driver tried
to overtake interfaces already controlled by generic IDE code.

> shouldn't ..
> returned warnings like I've posted

You are talking about IDE as module not PCI IDE modules.

--bart

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1
  2004-01-09  9:40 2.6.1-mm1 Andrew Morton
@ 2004-01-09 14:47 ` Christoph Hellwig
  2004-01-09 14:53 ` 2.6.1-mm1 Wojciech 'Sas' Cieciwa
                   ` (4 subsequent siblings)
  5 siblings, 0 replies; 37+ messages in thread
From: Christoph Hellwig @ 2004-01-09 14:47 UTC (permalink / raw)
  To: Andrew Morton; +Cc: linux-kernel, linux-mm, heiko.carstens

On Fri, Jan 09, 2004 at 01:40:03AM -0800, Andrew Morton wrote:
> - A large s390 update.  Various device drivers and IO layer changes there.

The zfcp driver adds a __setup function and lots of idef MODULE code.
Please don't do this for new driver (zfcp is new in 2.6).  the proper
module_param macros work for both modular and builtin use.

adding MODULE ifdefs is a lartable offense :)

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1
  2004-01-09  9:40 2.6.1-mm1 Andrew Morton
  2004-01-09 14:47 ` 2.6.1-mm1 Christoph Hellwig
@ 2004-01-09 14:53 ` Wojciech 'Sas' Cieciwa
  2004-01-09 14:21   ` 2.6.1-mm1 Bartlomiej Zolnierkiewicz
  2004-01-09 15:24 ` 2.6.1-mm1 (compile stats) John Cherry
                   ` (3 subsequent siblings)
  5 siblings, 1 reply; 37+ messages in thread
From: Wojciech 'Sas' Cieciwa @ 2004-01-09 14:53 UTC (permalink / raw)
  To: Andrew Morton; +Cc: linux-kernel, linux-mm

On Fri, 9 Jan 2004, Andrew Morton wrote:

[...]
> 
> - The PCI IDE drivers should work as modules now.

shouldn't ..
returned warnings like I've posted

Sorry.

					Sas.
-- 
{Wojciech 'Sas' Cieciwa}  {Member of PLD Team                               }
{e-mail: cieciwa@alpha.zarz.agh.edu.pl, http://www2.zarz.agh.edu.pl/~cieciwa}

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1 (compile stats)
  2004-01-09  9:40 2.6.1-mm1 Andrew Morton
  2004-01-09 14:47 ` 2.6.1-mm1 Christoph Hellwig
  2004-01-09 14:53 ` 2.6.1-mm1 Wojciech 'Sas' Cieciwa
@ 2004-01-09 15:24 ` John Cherry
  2004-01-09 16:30 ` 2.6.1-mm1 Prakash K. Cheemplavam
                   ` (2 subsequent siblings)
  5 siblings, 0 replies; 37+ messages in thread
From: John Cherry @ 2004-01-09 15:24 UTC (permalink / raw)
  To: Andrew Morton; +Cc: linux-kernel, linux-mm

Linux 2.6 (mm tree) Compile Statistics (gcc 3.2.2)
Warnings/Errors Summary

Kernel            bzImage   bzImage  bzImage  modules  bzImage  modules
                (defconfig) (allno) (allyes) (allyes) (allmod) (allmod)
--------------- ---------- -------- -------- -------- -------- --------
2.6.1-mm1         0w/0e     0w/0e   146w/ 9e  12w/0e   6w/0e    171w/0e
2.6.1-rc2-mm1     0w/0e     0w/0e   149w/ 0e  12w/0e   6w/0e    171w/4e
2.6.1-rc1-mm2     0w/0e     0w/0e   157w/15e  12w/0e   3w/0e    185w/4e
2.6.1-rc1-mm1     0w/0e     0w/0e   156w/10e  12w/0e   3w/0e    184w/2e
2.6.0-mm2         0w/0e     0w/0e   161w/ 0e  12w/0e   3w/0e    189w/0e
2.6.0-mm1         0w/0e     0w/0e   173w/ 0e  12w/0e   3w/0e    212w/0e

Web page with links to complete details:
   http://developer.osdl.org/cherry/compile/

John





^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1
  2004-01-09  9:40 2.6.1-mm1 Andrew Morton
                   ` (2 preceding siblings ...)
  2004-01-09 15:24 ` 2.6.1-mm1 (compile stats) John Cherry
@ 2004-01-09 16:30 ` Prakash K. Cheemplavam
  2004-01-09 21:20   ` 2.6.1-mm1 Andrew Morton
  2004-01-09 19:31 ` 2.6.1-mm1: sound/pci/cmipci.c compile error Adrian Bunk
  2004-01-09 23:37 ` 2.6.1-mm1: drivers/video/sis/sis_main.c link error Adrian Bunk
  5 siblings, 1 reply; 37+ messages in thread
From: Prakash K. Cheemplavam @ 2004-01-09 16:30 UTC (permalink / raw)
  To: Andrew Morton; +Cc: linux-kernel, linux-mm

Hi,

could it be that you took out /or forgot to insterst the work-around for 
nforce2+apic? At least I did a test with cpu disconnect on and booted 
kernel and it hang. (I also couldn't find the work-around in the 
sources.) I remember an earlier mm kernel had that workaround inside.

bye,

Prakash

^ permalink raw reply	[flat|nested] 37+ messages in thread

* 2.6.1-mm1: sound/pci/cmipci.c compile error
  2004-01-09  9:40 2.6.1-mm1 Andrew Morton
                   ` (3 preceding siblings ...)
  2004-01-09 16:30 ` 2.6.1-mm1 Prakash K. Cheemplavam
@ 2004-01-09 19:31 ` Adrian Bunk
  2004-01-09 22:43   ` Andrew Morton
  2004-01-09 23:37 ` 2.6.1-mm1: drivers/video/sis/sis_main.c link error Adrian Bunk
  5 siblings, 1 reply; 37+ messages in thread
From: Adrian Bunk @ 2004-01-09 19:31 UTC (permalink / raw)
  To: Andrew Morton, perex, Takashi Iwai; +Cc: linux-kernel, alsa-devel

On Fri, Jan 09, 2004 at 01:40:03AM -0800, Andrew Morton wrote:
>...
> - A big ALSA update.
>...
> Changes since 2.6.1-rc2-mm1:
>...
> +alsa-101.patch
> 
>  ALSA update
>...

I got the following compile error when trying to compile 
sound/pci/cmipci.c statically into the kernel:

<--  snip  -->

...
  CC      sound/pci/cmipci.o
sound/pci/cmipci.c: In function `alsa_card_cmipci_setup':
sound/pci/cmipci.c:3300: error: `joystick' undeclared (first use in this function)
sound/pci/cmipci.c:3300: error: (Each undeclared identifier is reported only once
sound/pci/cmipci.c:3300: error: for each function it appears in.)
make[2]: *** [sound/pci/cmipci.o] Error 1

<--  snip  -->

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1
  2004-01-09 16:30 ` 2.6.1-mm1 Prakash K. Cheemplavam
@ 2004-01-09 21:20   ` Andrew Morton
  2004-01-09 21:24     ` 2.6.1-mm1 Prakash K. Cheemplavam
  2004-01-09 23:04     ` 2.6.1-mm1 - nforce2 timer patch sum up cheuche+lkml
  0 siblings, 2 replies; 37+ messages in thread
From: Andrew Morton @ 2004-01-09 21:20 UTC (permalink / raw)
  To: Prakash K. Cheemplavam; +Cc: linux-kernel, linux-mm, Bartlomiej Zolnierkiewicz

"Prakash K. Cheemplavam" <PrakashKC@gmx.de> wrote:
>
> Hi,
> 
> could it be that you took out /or forgot to insterst the work-around for 
> nforce2+apic? At least I did a test with cpu disconnect on and booted 
> kernel and it hang. (I also couldn't find the work-around in the 
> sources.) I remember an earlier mm kernel had that workaround inside.
> 

I discussed it with Bart and he felt that it was not a good way of fixing
the problem.  I'm not sure if he has a better fix in the works though..

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1
  2004-01-09 21:20   ` 2.6.1-mm1 Andrew Morton
@ 2004-01-09 21:24     ` Prakash K. Cheemplavam
  2004-01-09 23:04     ` 2.6.1-mm1 - nforce2 timer patch sum up cheuche+lkml
  1 sibling, 0 replies; 37+ messages in thread
From: Prakash K. Cheemplavam @ 2004-01-09 21:24 UTC (permalink / raw)
  To: Andrew Morton; +Cc: linux-kernel, linux-mm, Bartlomiej Zolnierkiewicz

Andrew Morton wrote:
> "Prakash K. Cheemplavam" <PrakashKC@gmx.de> wrote:
>>could it be that you took out /or forgot to insterst the work-around for 
>>nforce2+apic? At least I did a test with cpu disconnect on and booted 
> 
> I discussed it with Bart and he felt that it was not a good way of fixing
> the problem.  I'm not sure if he has a better fix in the works though..
> 
Yes, it is no good fix, but at least better than nothing...don't you agree?

Prakash

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: sound/pci/cmipci.c compile error
  2004-01-09 19:31 ` 2.6.1-mm1: sound/pci/cmipci.c compile error Adrian Bunk
@ 2004-01-09 22:43   ` Andrew Morton
  0 siblings, 0 replies; 37+ messages in thread
From: Andrew Morton @ 2004-01-09 22:43 UTC (permalink / raw)
  To: Adrian Bunk; +Cc: perex, tiwai, linux-kernel, alsa-devel

Adrian Bunk <bunk@fs.tum.de> wrote:
>
> I got the following compile error when trying to compile 
> sound/pci/cmipci.c statically into the kernel:
> 
> <--  snip  -->
> 
> ...
>   CC      sound/pci/cmipci.o
> sound/pci/cmipci.c: In function `alsa_card_cmipci_setup':
> sound/pci/cmipci.c:3300: error: `joystick' undeclared (first use in this function)
> sound/pci/cmipci.c:3300: error: (Each undeclared identifier is reported only once
> sound/pci/cmipci.c:3300: error: for each function it appears in.)

Like this, methinks

diff -puN sound/pci/cmipci.c~cmipci-joystick-fix sound/pci/cmipci.c
--- 25/sound/pci/cmipci.c~cmipci-joystick-fix	Fri Jan  9 14:41:51 2004
+++ 25-akpm/sound/pci/cmipci.c	Fri Jan  9 14:41:59 2004
@@ -3297,7 +3297,7 @@ static int __init alsa_card_cmipci_setup
 	       && get_option(&str,&soft_ac3[nr_dev]) == 2
 #endif
 #ifdef SUPPORT_JOYSTICK
-	       && get_option(&str,&joystick[nr_dev]) == 2
+	       && get_option(&str,&joystick_port[nr_dev]) == 2
 #endif
 	       );
 	nr_dev++;

_


^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1 - nforce2 timer patch sum up
  2004-01-09 21:20   ` 2.6.1-mm1 Andrew Morton
  2004-01-09 21:24     ` 2.6.1-mm1 Prakash K. Cheemplavam
@ 2004-01-09 23:04     ` cheuche+lkml
  1 sibling, 0 replies; 37+ messages in thread
From: cheuche+lkml @ 2004-01-09 23:04 UTC (permalink / raw)
  To: linux-kernel

On Fri, Jan 09, 2004 at 01:20:38PM -0800, Andrew Morton wrote:
> "Prakash K. Cheemplavam" <PrakashKC@gmx.de> wrote:
> >
> > Hi,
> > 
> > could it be that you took out /or forgot to insterst the work-around for 
> > nforce2+apic? At least I did a test with cpu disconnect on and booted 
> > kernel and it hang. (I also couldn't find the work-around in the 
> > sources.) I remember an earlier mm kernel had that workaround inside.
> > 
> 
> I discussed it with Bart and he felt that it was not a good way of fixing
> the problem.  I'm not sure if he has a better fix in the works though..

One of the fixes was about getting timer interrupts on apic. It was a
quick hack from me and definitely wrong. Furthermore, it does
unfortunately nothing against these hangs.

I will try to summarize this problem.

Back in the 2.5 series, timer configuration was :

..TIMER: vector=0x31 pin1=2 pin2=0
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...
..... (found pin 0) ...works.

and interrupt 0 in /proc/interrupts was IO-APIC-edge.

A fix in mp_override_legacy_irq() in arch/i386/kernel/mpparse.c changes
this behavior to :

..TIMER: vector=0x31 pin1=2 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...  failed.
...trying to set up timer as Virtual Wire IRQ... failed.
...trying to set up timer as ExtINT IRQ... works.

and interrupt 0 went to XT-PIC mode, and spurious interrupts on IRQ7
appeared !

It seems that there is no timer connected to pin 2 on the nforce2 apic
when linux tries to find it (MP-BIOS bug with pin1=2). Maybe it is not
connected at all on (all ?) nforce2 motherboards.
However, this configuration information (pin1=2) comes from :

ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)

that is, from the BIOS. This is confusing because if the timer is not
connected to this pin, why the bios tells it is ? OK, this won't be the
first broken bios out there.

After some experimentation, I came across with an interesting result
when I change the INT_SRC_OVR's global_irq to 0 (timer connecter to 
pin 0, not 2), all I have is :

..TIMER: vector=0x31 pin1=0 pin2=-1

and everything is working great, no spurious or streams of IRQ7, not
even a small drift I noticed with other configurations between LOC count
and IRQ0 count in /proc/interrupts. nmi_watchdog=1 doesn't work however
(well it never worked anyway). Others on lkml achieved more or less the
same result with force-setting the timer on pin 0 with
io_apic_set_pci_routing() and nmi_watchdog=1 works this way.

To sum up about the problem :

 - timer is not on pin 2 (or something needs to be done ?)
 - bios lies about it in its INT_SRC_OVR (or expect something to be
   done ?)
 - timer works well on pin 0, through the 8259A or via a hacked
   INT_SRC_OVR or a io_apic_set_pci_routing()
 - timer on ExtINT or timer in lapic+noapic mode leads to spurious IRQ7

But I cannot see a proper fix. Maybe nvidia or motherboard makers could
tell us why there is an INT_SRC_OVR for the timer telling the kernel to 
find it on pin 2 where there is nothing. Intel apic documentation says
this is the correct pin to connect the timer but it does not work on
nforce2 apic. Note that if motherboard makers release a bios with
timer's INT_SRC_OVR on pin 0, this problem magically goes away...
But that would not removes the spurious IRQ7 with local apic but noapic,
since the acpi override would not be looked at, so there might be
another problem.

And this is just the timer problem, the cpu disconnect one is still an
other story. Maybe they are related but the connection is far from
being obvious.

I hope this sum up about one of these two nforce patches helps.

Mathieu

^ permalink raw reply	[flat|nested] 37+ messages in thread

* 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-09  9:40 2.6.1-mm1 Andrew Morton
                   ` (4 preceding siblings ...)
  2004-01-09 19:31 ` 2.6.1-mm1: sound/pci/cmipci.c compile error Adrian Bunk
@ 2004-01-09 23:37 ` Adrian Bunk
  2004-01-10  4:04   ` Thomas Winischhofer
  5 siblings, 1 reply; 37+ messages in thread
From: Adrian Bunk @ 2004-01-09 23:37 UTC (permalink / raw)
  To: Andrew Morton, thomas; +Cc: linux-kernel, jsimmons

On Fri, Jan 09, 2004 at 01:40:03AM -0800, Andrew Morton wrote:
>...
> All 393 patches
>...
> use-soft-float.patch
>   Use -msoft-float
>...

FYI:

This causes the following link error:

<--  snip  -->

...
  LD      .tmp_vmlinux1
drivers/built-in.o(.text+0x55814f): In function `sisfb_do_set_var':
: undefined reference to `__floatsidf'
drivers/built-in.o(.text+0x55816d): In function `sisfb_do_set_var':
: undefined reference to `__divdf3'
drivers/built-in.o(.text+0x55817a): In function `sisfb_do_set_var':
: undefined reference to `__floatsidf'
drivers/built-in.o(.text+0x558196): In function `sisfb_do_set_var':
: undefined reference to `__divdf3'
drivers/built-in.o(.text+0x5581a9): In function `sisfb_do_set_var':
: undefined reference to `__floatsidf'
drivers/built-in.o(.text+0x5581bf): In function `sisfb_do_set_var':
: undefined reference to `__divdf3'
drivers/built-in.o(.text+0x5581cb): In function `sisfb_do_set_var':
: undefined reference to `__adddf3'
drivers/built-in.o(.text+0x5581e0): In function `sisfb_do_set_var':
: undefined reference to `__adddf3'
drivers/built-in.o(.text+0x5581ea): In function `sisfb_do_set_var':
: undefined reference to `__fixunsdfsi'
drivers/built-in.o(.text+0x5584fa): In function `sisfb_do_set_var':
: undefined reference to `__adddf3'
drivers/built-in.o(.text+0x558514): In function `sisfb_do_set_var':
: undefined reference to `__adddf3'
drivers/built-in.o(.text+0x55852e): In function `sisfb_do_set_var':
: undefined reference to `__adddf3'
drivers/built-in.o(.init.text+0x5cde2): In function `sisfb_init':
: undefined reference to `__floatsidf'
drivers/built-in.o(.init.text+0x5cdf5): In function `sisfb_init':
: undefined reference to `__divdf3'
drivers/built-in.o(.init.text+0x5cdff): In function `sisfb_init':
: undefined reference to `__fixunsdfsi'
make: *** [.tmp_vmlinux1] Error 1

<--  snip  -->

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-09 23:37 ` 2.6.1-mm1: drivers/video/sis/sis_main.c link error Adrian Bunk
@ 2004-01-10  4:04   ` Thomas Winischhofer
  2004-01-12  2:58     ` Linus Torvalds
  2004-01-13 19:04     ` Adrian Bunk
  0 siblings, 2 replies; 37+ messages in thread
From: Thomas Winischhofer @ 2004-01-10  4:04 UTC (permalink / raw)
  To: Andrew Morton; +Cc: linux-kernel, jsimmons

Adrian Bunk wrote:

 > On Fri, Jan 09, 2004 at 01:40:03AM -0800, Andrew Morton wrote:
 >
 >> ...
 >> All 393 patches
 >> ...
 >> use-soft-float.patch
 >>  Use -msoft-float
 >> ...
 >
 >

I know. The version of sisfb in 2.6 vanilla is from stone-age. This is 
has been fixed a long time ago in my current development version (and 
will be in 2.4 as soon as Marcelo applies my patch which I sent him 
about a week ago). For 2.6, using my current version requires James 
Simmons's fbdev-patch because of low-level fbdev-interface changes (like 
sysfs usage, etc).

The whole framebuffer stuff in 2.6 is ancient. (Look at the file dates.)

Thomas



-- 
Thomas Winischhofer
Vienna/Austria
thomas AT winischhofer DOT net          http://www.winischhofer.net/
twini AT xfree86 DOT org

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-10  4:04   ` Thomas Winischhofer
@ 2004-01-12  2:58     ` Linus Torvalds
  2004-01-12  4:53       ` Gene Heskett
                         ` (2 more replies)
  2004-01-13 19:04     ` Adrian Bunk
  1 sibling, 3 replies; 37+ messages in thread
From: Linus Torvalds @ 2004-01-12  2:58 UTC (permalink / raw)
  To: Thomas Winischhofer; +Cc: Andrew Morton, linux-kernel, jsimmons



On Sat, 10 Jan 2004, Thomas Winischhofer wrote:
> 
> The whole framebuffer stuff in 2.6 is ancient. (Look at the file dates.)

Note that the fb stuff is ancient because it's basically not maintained as 
far as I'm concerned.

I occasionally get huge drops from James, and they invariably break stuff. 
Which means that I often decide (espcially when trying to stabilize 
things) that I just can't _afford_ to apply the fr*gging patches. Because 
by past experience applying one of the big "everything changes" patches 
tends to break more things that it fixes.

I'm sorry, but this i show it is.  The fbcon people have been changing 
interfaces faster than they have been fixing bugs in the code. Together 
with the fact that most of the development seems to happen in outside 
trees, and nobody ever sends me fixes relative to the released tree, this 
makes for a pretty bad situation.

I really think that development should happen in the regular tree, or at 
least be synched up in reasonable chunks THAT DO NOT BREAK everything.

I realize that some fb developers seem to disagree with me, but the fact 
is, the way things are done now, fb will _always_ be broken. Most people 
for whom the standard kernel works will never test the fb development 
trees, so those trees will never get any amount of reasonable testing. As 
a result, they WILL be buggy, and synching with them WILL be painful as 
hell.

There is a d*mn good reason for why development should happen
incrementally, and in the standard trees, and not in some outside tree. 
For one: testing. For another: figuring out when things break in a timely 
manner.

		Linus

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12  2:58     ` Linus Torvalds
@ 2004-01-12  4:53       ` Gene Heskett
  2004-01-12  5:42         ` Andrew Morton
  2004-01-12  8:58       ` Thomas Winischhofer
  2004-01-12 10:36       ` Andrew Walrond
  2 siblings, 1 reply; 37+ messages in thread
From: Gene Heskett @ 2004-01-12  4:53 UTC (permalink / raw)
  To: Linus Torvalds, Thomas Winischhofer; +Cc: Andrew Morton, linux-kernel, jsimmons

On Sunday 11 January 2004 21:58, Linus Torvalds wrote:
>On Sat, 10 Jan 2004, Thomas Winischhofer wrote:
>> The whole framebuffer stuff in 2.6 is ancient. (Look at the file
>> dates.)
>
>Note that the fb stuff is ancient because it's basically not
> maintained as far as I'm concerned.
>
>I occasionally get huge drops from James, and they invariably break
> stuff. Which means that I often decide (espcially when trying to
> stabilize things) that I just can't _afford_ to apply the fr*gging
> patches. Because by past experience applying one of the big
> "everything changes" patches tends to break more things that it
> fixes.
>
>I'm sorry, but this i show it is.  The fbcon people have been
> changing interfaces faster than they have been fixing bugs in the
> code. Together with the fact that most of the development seems to
> happen in outside trees, and nobody ever sends me fixes relative to
> the released tree, this makes for a pretty bad situation.
>
>I really think that development should happen in the regular tree,
> or at least be synched up in reasonable chunks THAT DO NOT BREAK
> everything.
>
>I realize that some fb developers seem to disagree with me, but the
> fact is, the way things are done now, fb will _always_ be broken.
> Most people for whom the standard kernel works will never test the
> fb development trees, so those trees will never get any amount of
> reasonable testing. As a result, they WILL be buggy, and synching
> with them WILL be painful as hell.
>
>There is a d*mn good reason for why development should happen
>incrementally, and in the standard trees, and not in some outside
> tree. For one: testing. For another: figuring out when things break
> in a timely manner.
>
>		Linus
>-

I can well see your reticence in view of the situation, I think I'd be 
gun-shy too.  Its called prudence.

However, since I've been running 2.6.1-mm1 here, using the rivafb with 
an elderly gforce2-mx2 32 megger, I've noted that when running 
kde-3.1.1a with 8 windows, and a couple of them have multimegabyte 
backdrops, the biggest one being that famous deep space shot from 
hubble of about 4 or 5 months back.  In any other kernel, switching 
to that window took about 12 seconds for the backdrop to be converted 
to 1600x1200x32 and drawn the first time and about 8 seconds for the 
next time.  But with this 2.6.1-mm1 kernel, that repeat window switch 
is so close to instant that I cannot see it being drawn.

So as far as I'm concerned, this particular set of fb patches to 
rivafb *need* to stay in mainline.  I'd sure appreciate it, a bunch.

This ones a winner I think.
>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/

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty: soap,
ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.


^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12  4:53       ` Gene Heskett
@ 2004-01-12  5:42         ` Andrew Morton
  2004-01-12  6:11           ` Valdis.Kletnieks
  2004-01-12  6:21           ` Gene Heskett
  0 siblings, 2 replies; 37+ messages in thread
From: Andrew Morton @ 2004-01-12  5:42 UTC (permalink / raw)
  To: gene.heskett; +Cc: torvalds, thomas, linux-kernel, jsimmons

Gene Heskett <gene.heskett@verizon.net> wrote:
>
> However, since I've been running 2.6.1-mm1 here, using the rivafb with 
>  an elderly gforce2-mx2 32 megger, I've noted that when running 
>  kde-3.1.1a with 8 windows, and a couple of them have multimegabyte 
>  backdrops, the biggest one being that famous deep space shot from 
>  hubble of about 4 or 5 months back.  In any other kernel, switching 
>  to that window took about 12 seconds for the backdrop to be converted 
>  to 1600x1200x32 and drawn the first time and about 8 seconds for the 
>  next time.  But with this 2.6.1-mm1 kernel, that repeat window switch 
>  is so close to instant that I cannot see it being drawn.
> 
>  So as far as I'm concerned, this particular set of fb patches to 
>  rivafb *need* to stay in mainline.  I'd sure appreciate it, a bunch.

There are no significant fbdev patches in 2.6.1-mm1.  There is a DRM
update.

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12  5:42         ` Andrew Morton
@ 2004-01-12  6:11           ` Valdis.Kletnieks
  2004-01-12  6:47             ` Gene Heskett
  2004-01-12  6:21           ` Gene Heskett
  1 sibling, 1 reply; 37+ messages in thread
From: Valdis.Kletnieks @ 2004-01-12  6:11 UTC (permalink / raw)
  To: Andrew Morton; +Cc: gene.heskett, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]

On Sun, 11 Jan 2004 21:42:59 PST, Andrew Morton said:
> Gene Heskett <gene.heskett@verizon.net> wrote:
> >  hubble of about 4 or 5 months back.  In any other kernel, switching 
> >  to that window took about 12 seconds for the backdrop to be converted 
> >  to 1600x1200x32 and drawn the first time and about 8 seconds for the 
> >  next time.  But with this 2.6.1-mm1 kernel, that repeat window switch 
> >  is so close to instant that I cannot see it being drawn.

> There are no significant fbdev patches in 2.6.1-mm1.  There is a DRM
> update.

The 12 seconds coming and 8 seconds going, versus instant, sounds an *awful*
lot like the virtual memory manager making better choices in -mm kernels, so
the pages of pixmap are staying in memory rather than paging out.

Other guess is that o21-sched.patch is DTRT, while the stock scheduler DTWT
for his particular config.

Gene:  Can you tell what exactly your system is doing for the 12/8 seconds?  Is it
CPU bound, or beating on the disk while paging in/out, or just sitting idle?  Leaving
a 'vmstat 1' running while you change backdrops should tell us something.

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12  5:42         ` Andrew Morton
  2004-01-12  6:11           ` Valdis.Kletnieks
@ 2004-01-12  6:21           ` Gene Heskett
  2004-01-12  6:34             ` Andrew Morton
  2004-01-12 16:33             ` Dave Jones
  1 sibling, 2 replies; 37+ messages in thread
From: Gene Heskett @ 2004-01-12  6:21 UTC (permalink / raw)
  To: Andrew Morton; +Cc: torvalds, thomas, linux-kernel, jsimmons

On Monday 12 January 2004 00:42, Andrew Morton wrote:
>Gene Heskett <gene.heskett@verizon.net> wrote:
>> However, since I've been running 2.6.1-mm1 here, using the rivafb
>> with an elderly gforce2-mx2 32 megger, I've noted that when
>> running kde-3.1.1a with 8 windows, and a couple of them have
>> multimegabyte backdrops, the biggest one being that famous deep
>> space shot from hubble of about 4 or 5 months back.  In any other
>> kernel, switching to that window took about 12 seconds for the
>> backdrop to be converted to 1600x1200x32 and drawn the first time
>> and about 8 seconds for the next time.  But with this 2.6.1-mm1
>> kernel, that repeat window switch is so close to instant that I
>> cannot see it being drawn.
>>
>>  So as far as I'm concerned, this particular set of fb patches to
>>  rivafb *need* to stay in mainline.  I'd sure appreciate it, a
>> bunch.
>
>There are no significant fbdev patches in 2.6.1-mm1.  There is a DRM
>update.

Whatever it is, its pure speed on this system here, Andrew.  DRM? 
lemme see if thats even turned on.  Nope "# CONFIG_DRM is not set"
Doing a make xconfig, I see that if I turn it on, there is not a 
driver for my gforce2/nvidia, so I naturally turned it back off.

I do have VIA and agpgart enabled just above it, and over in the 
framebuffer menu, support for framebuffer and nvidia/riva are both 
checked.

Anyway, something has made a huge difference in window switching 
speeds here, someplace between 2.6.0-mm2 and 2.6.1-mm1.  I like it.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty: soap,
ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.


^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12  6:21           ` Gene Heskett
@ 2004-01-12  6:34             ` Andrew Morton
  2004-01-12  6:58               ` Gene Heskett
  2004-01-12  7:03               ` Gene Heskett
  2004-01-12 16:33             ` Dave Jones
  1 sibling, 2 replies; 37+ messages in thread
From: Andrew Morton @ 2004-01-12  6:34 UTC (permalink / raw)
  To: gene.heskett; +Cc: torvalds, thomas, linux-kernel, jsimmons

Gene Heskett <gene.heskett@verizon.net> wrote:
>
> >There are no significant fbdev patches in 2.6.1-mm1.  There is a DRM
>  >update.
> 
>  Whatever it is, its pure speed on this system here, Andrew.  DRM? 
>  lemme see if thats even turned on.  Nope "# CONFIG_DRM is not set"
>  Doing a make xconfig, I see that if I turn it on, there is not a 
>  driver for my gforce2/nvidia, so I naturally turned it back off.
> 
>  I do have VIA and agpgart enabled just above it, and over in the 
>  framebuffer menu, support for framebuffer and nvidia/riva are both 
>  checked.
> 
>  Anyway, something has made a huge difference in window switching 
>  speeds here, someplace between 2.6.0-mm2 and 2.6.1-mm1.  I like it.

Beats me.  Doing that vmstat measurement which Vladis suggests would be
interesting.




^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12  6:11           ` Valdis.Kletnieks
@ 2004-01-12  6:47             ` Gene Heskett
  2004-01-12  7:05               ` Andrew Morton
  0 siblings, 1 reply; 37+ messages in thread
From: Gene Heskett @ 2004-01-12  6:47 UTC (permalink / raw)
  To: Valdis.Kletnieks, Andrew Morton; +Cc: linux-kernel

On Monday 12 January 2004 01:11, Valdis.Kletnieks@vt.edu wrote:
>On Sun, 11 Jan 2004 21:42:59 PST, Andrew Morton said:
>> Gene Heskett <gene.heskett@verizon.net> wrote:
>> >  hubble of about 4 or 5 months back.  In any other kernel,
>> > switching to that window took about 12 seconds for the backdrop
>> > to be converted to 1600x1200x32 and drawn the first time and
>> > about 8 seconds for the next time.  But with this 2.6.1-mm1
>> > kernel, that repeat window switch is so close to instant that I
>> > cannot see it being drawn.
>>
>> There are no significant fbdev patches in 2.6.1-mm1.  There is a
>> DRM update.
>
>The 12 seconds coming and 8 seconds going, versus instant, sounds an
> *awful* lot like the virtual memory manager making better choices
> in -mm kernels, so the pages of pixmap are staying in memory rather
> than paging out.
>
>Other guess is that o21-sched.patch is DTRT, while the stock
> scheduler DTWT for his particular config.
>
>Gene:  Can you tell what exactly your system is doing for the 12/8
> seconds?  Is it CPU bound, or beating on the disk while paging
> in/out, or just sitting idle?  Leaving a 'vmstat 1' running while
> you change backdrops should tell us something.

I can try that with the 2 kernels, but it will have to be after amanda
is done with her nightly tour, which will take another 2.5 hours.  By
then I expect to be sleeping, or hope to be, its 1:30am here now.

Or maybe not, what do I do when "vmstat 1" prints its column headers and segfaults?:
---
[root@coyote linux-2.6]# vmstat 1
   procs                      memory    swap          io     system         cpu
 r  b  w   swpd   free   buff  cache  si  so    bi    bo   in    cs  us  sy  id
Segmentation fault
[root@coyote linux-2.6]#
---
cd'ing to /proc/1, and trying to "cat mem" gets me this:
---
[root@coyote 1]# cat mem
cat: mem: No such process
[root@coyote 1]#
---
Some of the other names there have content, but 'mem' seems to be
a truely empty filename, marked:
-rw-------    1 root     root            0 Jan 12 01:32 mem
but apparently inacessable.

This actually sounds pretty serious, and I did have a hard lockup
in the night last night, had to use the reset button, but I think
that was a cpu overheat, I'd run the heat up cause the missus was
squawking about being cold.

I've rearranged things airwise and got the cpu down to below 70C.
These AMD DX-1600 thoroughbreds really are genuine coffee boilers.
I really should replace it with the cheapest barton cored one, but
this ones been running that hot for 30 months now.  Running seti 24/7
of course doesn't help. :)

Do I need YANP42.6 (Yet Another New Program 4 2.6)?
Sorry, couldn't resist creating a new acronym. :)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty: soap,
ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.


^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12  6:34             ` Andrew Morton
@ 2004-01-12  6:58               ` Gene Heskett
  2004-01-12  7:03               ` Gene Heskett
  1 sibling, 0 replies; 37+ messages in thread
From: Gene Heskett @ 2004-01-12  6:58 UTC (permalink / raw)
  To: Andrew Morton; +Cc: torvalds, thomas, linux-kernel, jsimmons

On Monday 12 January 2004 01:34, Andrew Morton wrote:
>Gene Heskett <gene.heskett@verizon.net> wrote:
>> >There are no significant fbdev patches in 2.6.1-mm1.  There is a
>> > DRM
>> >
>>  >update.
>>
>>  Whatever it is, its pure speed on this system here, Andrew.  DRM?
>>  lemme see if thats even turned on.  Nope "# CONFIG_DRM is not
>> set" Doing a make xconfig, I see that if I turn it on, there is
>> not a driver for my gforce2/nvidia, so I naturally turned it back
>> off.
>>
>>  I do have VIA and agpgart enabled just above it, and over in the
>>  framebuffer menu, support for framebuffer and nvidia/riva are
>> both checked.
>>
>>  Anyway, something has made a huge difference in window switching
>>  speeds here, someplace between 2.6.0-mm2 and 2.6.1-mm1.  I like
>> it.
>
>Beats me.  Doing that vmstat measurement which Vladis suggests would
> be interesting.

See my reply to Vladis of 30 seconds ago, it gets even curiouser!
vmstat 1 segfaults, /proc/1/mem isn't readable.
Interesting indeed.  And I cannot get at the stats with ksysguard, 
"cannot connect to FQDN"  I didn't have that enabled in gkrellm, and 
when I do its just a blank header, so its not getting anything 
either.

Yup, curiouser and curiouser...

Whats interesting in /sys in this area?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty: soap,
ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.


^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12  6:34             ` Andrew Morton
  2004-01-12  6:58               ` Gene Heskett
@ 2004-01-12  7:03               ` Gene Heskett
  1 sibling, 0 replies; 37+ messages in thread
From: Gene Heskett @ 2004-01-12  7:03 UTC (permalink / raw)
  To: Andrew Morton; +Cc: torvalds, thomas, linux-kernel, jsimmons

On Monday 12 January 2004 01:34, Andrew Morton wrote:
>Gene Heskett <gene.heskett@verizon.net> wrote:
>> >There are no significant fbdev patches in 2.6.1-mm1.  There is a
>> > DRM
>> >
>>  >update.
>>
>>  Whatever it is, its pure speed on this system here, Andrew.  DRM?
>>  lemme see if thats even turned on.  Nope "# CONFIG_DRM is not
>> set" Doing a make xconfig, I see that if I turn it on, there is
>> not a driver for my gforce2/nvidia, so I naturally turned it back
>> off.
>>
>>  I do have VIA and agpgart enabled just above it, and over in the
>>  framebuffer menu, support for framebuffer and nvidia/riva are
>> both checked.
>>
>>  Anyway, something has made a huge difference in window switching
>>  speeds here, someplace between 2.6.0-mm2 and 2.6.1-mm1.  I like
>> it.
>
>Beats me.  Doing that vmstat measurement which Vladis suggests would
> be interesting.
I just found that the old standby, top, is apparently showing sane 
memory values.
---
Mem:   514720K av,  511360K used,    3360K free,       0K shrd,   
11468K buff
Swap: 3857104K av,   42292K used, 3814812K free                  
317328K cached
---
So at least one program knows howto get at the data.
-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty: soap,
ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.


^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12  6:47             ` Gene Heskett
@ 2004-01-12  7:05               ` Andrew Morton
  2004-01-12  7:20                 ` Gene Heskett
  2004-01-12 12:38                 ` Gene Heskett
  0 siblings, 2 replies; 37+ messages in thread
From: Andrew Morton @ 2004-01-12  7:05 UTC (permalink / raw)
  To: gene.heskett; +Cc: Valdis.Kletnieks, linux-kernel

Gene Heskett <gene.heskett@verizon.net> wrote:
>
>  Or maybe not, what do I do when "vmstat 1" prints its column headers and segfaults?:

You probably need a new vmstat.  There were quite a few buggy ones around. 
Make sure you have a current procps.



^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12  7:05               ` Andrew Morton
@ 2004-01-12  7:20                 ` Gene Heskett
  2004-01-12 12:38                 ` Gene Heskett
  1 sibling, 0 replies; 37+ messages in thread
From: Gene Heskett @ 2004-01-12  7:20 UTC (permalink / raw)
  To: Andrew Morton; +Cc: Valdis.Kletnieks, linux-kernel

On Monday 12 January 2004 02:05, Andrew Morton wrote:
>Gene Heskett <gene.heskett@verizon.net> wrote:
>>  Or maybe not, what do I do when "vmstat 1" prints its column
>> headers and segfaults?:
>
>You probably need a new vmstat.  There were quite a few buggy ones
> around. Make sure you have a current procps.

And where are they available?  I'm not allergic to ripping out the 
rpms if need be.  Do you have a list of compatible pairings showing 
version numbers to get?

Gah, bedtime..

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty: soap,
ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.


^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12  2:58     ` Linus Torvalds
  2004-01-12  4:53       ` Gene Heskett
@ 2004-01-12  8:58       ` Thomas Winischhofer
  2004-01-12 14:32         ` Moritz Muehlenhoff
  2004-01-12 10:36       ` Andrew Walrond
  2 siblings, 1 reply; 37+ messages in thread
From: Thomas Winischhofer @ 2004-01-12  8:58 UTC (permalink / raw)
  To: Linus Torvalds; +Cc: Andrew Morton, linux-kernel, jsimmons

Linus Torvalds wrote:
> 
> On Sat, 10 Jan 2004, Thomas Winischhofer wrote:
> 
>>The whole framebuffer stuff in 2.6 is ancient. (Look at the file dates.)
> 
> 
> Note that the fb stuff is ancient because it's basically not maintained as 
> far as I'm concerned.

Erm, well, _I_ know. But I assume you meant this message mainly for the 
public.

> I'm sorry, but this i show it is.  The fbcon people have been changing 
> interfaces faster than they have been fixing bugs in the code. Together

You tell me. I actually stopped adapting sisfb for a couple of months 
during the 2.5 development cycle - I could not keep up with the speed of 
substantial changes either.

> with the fact that most of the development seems to happen in outside 
> trees, and nobody ever sends me fixes relative to the released tree, this 
> makes for a pretty bad situation.
> 
> I really think that development should happen in the regular tree, or at 
> least be synched up in reasonable chunks THAT DO NOT BREAK everything.
> 
> I realize that some fb developers seem to disagree with me, but the fact 
> is, the way things are done now, fb will _always_ be broken. Most people 
> for whom the standard kernel works will never test the fb development 
> trees, so those trees will never get any amount of reasonable testing. As 
> a result, they WILL be buggy, and synching with them WILL be painful as 
> hell.

Isn't a large part of the fbcon/dev stuff in current 2.6 broken anyway? 
Could it become worse by merging James' current changes? But I guess 
this question - as well as the rest of your message - is for James to 
answer.

If the lastest and greatest of the fbdev stuff isn't merged with 2.6.2, 
I will revert the interface changes in sisfb and send a patch which 
works with the then-current vanilla kernel.

Thomas

-- 
Thomas Winischhofer
Vienna/Austria
thomas AT winischhofer DOT net          *** http://www.winischhofer.net/
twini AT xfree86 DOT org




^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12  2:58     ` Linus Torvalds
  2004-01-12  4:53       ` Gene Heskett
  2004-01-12  8:58       ` Thomas Winischhofer
@ 2004-01-12 10:36       ` Andrew Walrond
  2 siblings, 0 replies; 37+ messages in thread
From: Andrew Walrond @ 2004-01-12 10:36 UTC (permalink / raw)
  To: linux-kernel

On Monday 12 Jan 2004 2:58 am, Linus Torvalds wrote:
>
> I occasionally get huge drops from James, and they invariably break stuff.
> Which means that I often decide (espcially when trying to stabilize
> things) that I just can't _afford_ to apply the fr*gging patches. Because
> by past experience applying one of the big "everything changes" patches
> tends to break more things that it fixes.
>

I want the new fb stuff very badly.

My particular application is a game which has it's own software 3D renderer, 
so it just needs to be able to blast the frames into video ram. A good fbdev 
would mean not needing X, which would be nice.

Please consider this for inclusion in very early 2.7. And I urge James to work 
with Linus on this. Perhaps when it's stable in 2.7, we can back-port to 
2.6 :)

Andrew Walrond


^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12  7:05               ` Andrew Morton
  2004-01-12  7:20                 ` Gene Heskett
@ 2004-01-12 12:38                 ` Gene Heskett
  1 sibling, 0 replies; 37+ messages in thread
From: Gene Heskett @ 2004-01-12 12:38 UTC (permalink / raw)
  To: Andrew Morton; +Cc: Valdis.Kletnieks, linux-kernel

On Monday 12 January 2004 02:05, Andrew Morton wrote:
>Gene Heskett <gene.heskett@verizon.net> wrote:
>>  Or maybe not, what do I do when "vmstat 1" prints its column
>> headers and segfaults?:
>
>You probably need a new vmstat.  There were quite a few buggy ones
> around. Make sure you have a current procps.

Ripped out 2.0.7 and put in 3.15.something.
rebooted to 2.6.1-rc1-mm2, started x, open a shell and ran vmstat 1
switched to #6, that one really big backdrop window, 8 or 9
seconds to show the backdrop.  Switched back to window 1, instant,
then back to 6, instant.  Back to 1 & kill vmstat.
Here is the vmstat 1 output for that time period.
procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy id wa
 1  0      0 292944  11480  96676    0    0   715   134 1084  2191 59 10 21 10
 1  0      0 293264  11480  96676    0    0     0     0 1273  4856 96  4  0  0
 1  0      0 292400  11488  96676    0    0     0   376 1303  4726 96  4  0  0
 1  0      0 292400  11496  96676    0    0     0    36 1311  3546 98  2  0  0
 1  0      0 292400  11496  96676    0    0     0     0 1071  2414 99  1  0  0
 2  1      0 280352  11528  97252    0    0   600    24 1077  2770 97  3  0  0
 3  0      0 242400  11528  98404    0    0  1152     0 1076  2477 97  3  0  0
 2  0      0 204384  11536  99556    0    0  1152    12 1059  2466 95  5  0  0
 2  0      0 166304  11544 100708    0    0  1152    16 1063  2332 94  6  0  0
 2  0      0 130400  11552 101700    0    0  1000     0 1060  2335 96  4  0  0
 2  0      0 118256  11552 101700    0    0     0     0 1064  2416 98  2  0  0
 2  0      0 116400  11560 101700    0    0     0    12 1052  2363 99  1  0  0
 2  0      0 113520  11568 101700    0    0     0    12 1050  2371 100  0  0  0
 1  0      0 286936  11576 101700    0    0     0    16 1050 13575 83 17  0  0
 1  0      0 287448  11576 101700    0    0     0     0 1128  2649 99  1  0  0
 1  0      0 286936  11576 101700    0    0     0     0 1083  2470 98  2  0  0
 1  0      0 286872  11576 101728    0    0    28     0 1062  2793 98  2  0  0
 1  0      0 287320  11584 101728    0    0     0    16 1052  2306 99  1  0  0
 1  0      0 287712  11592 101728    0    0     0    16 1122  2524 99  1  0  0
 1  0      0 286816  11592 101728    0    0     0     0 1096  2526 99  1  0  0
 1  0      0 286816  11592 101728    0    0     0     0 1056  3281 99  1  0  0
 1  0      0 287648  11592 101728    0    0     0     0 1050  2335 100  0  0  0
 2  0      0 286816  11600 101728    0    0     0   136 1080  2295 99  1  0  0
 1  0      0 287264  11608 101728    0    0     0    16 1057  2315 99  1  0  0
 1  0      0 287584  11608 101728    0    0     0     0 1063  3037 99  1  0  0
 1  0      0 286752  11608 101728    0    0     0     0 1164  2709 95  5  0  0
 1  0      0 287200  11608 101728    0    0     0     0 1061  2785 99  1  0  0
 1  0      0 286688  11616 101728    0    0     0   112 1362  2862 90 10  0  0
 1  0      0 287520  11624 101728    0    0     0    16 1227  2612 94  6  0  0

So it looks as if this fix was there before I noticed it. Now I'll try another
even older boot.
Here is for 2.6.0-test10, the oldest currently in my grub.conf
procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy id wa
 1  0      0 291648  11640  97344    0    0   866   158 1098  2424 54 12 23 12
 1  0      0 291648  11648  97344    0    0     0    36 1204  2788 99  1  0  0
 1  0      0 291648  11656  97344    0    0     0    12 1060  2697 99  1  0  0
 1  0      0 291584  11656  97344    0    0     0     0 1050  2379 99  1  0  0
 1  0      0 292416  11656  97344    0    0     0     0 1049  2365 99  1  0  0
 2  0      0 291584  11664  97344    0    0     0   304 1199  3357 98  2  0  0
 1  0      0 291520  11672  97344    0    0     0    16 1136  3077 99  1  0  0
 3  0      0 284704  11712  97864    0    0   544    36 1101  2856 95  5  0  0
 2  0      0 245216  11712  99016    0    0  1152     0 1076  2375 95  5  0  0
 2  0      0 207584  11712 100296    0    0  1280     0 1060  3062 96  4  0  0
 2  0      0 169184  11712 101448    0    0  1152   788 1201  2370 96  4  0  0
 2  0      0 132384  11736 102368    0    0   928   220 1065  2423 96  4  0  0
 2  0      0 118080  11736 102368    0    0     0     0 1048  2411 97  3  0  0
 2  0      0 115200  11736 102368    0    0     0     0 1051  2399 99  1  0  0
 2  0      0 112384  11736 102368    0    0     0     0 1050  2425 99  1  0  0
 1  0      0 286952  11740 102368    0    0     0     4 1050 13626 83 17  0  0
 1  0      0 286120  11740 102368    0    0     0     0 1052  2362 100  0  0  0
 1  0      0 286952  11748 102368    0    0     0    16 1131  2608 95  5  0  0
 1  0      0 286120  11748 102368    0    0     0     0 1051  2362 100  0  0  0
 1  0      0 286120  11748 102368    0    0     0     0 1050  2346 99  1  0  0
 1  0      0 286000  11756 102396    0    0    28    12 1064  2824 99  1  0  0
 1  0      0 286000  11756 102396    0    0     0     0 1200  2728 96  4  0  0
 1  0      0 286000  11764 102396    0    0     0    16 1056  2704 99  1  0  0
 2  0      0 286000  11764 102396    0    0     0     0 1052  2358 100  0  0  0
 1  0      0 286768  11772 102396    0    0     0    16 1058  2567 99  1  0  0
 1  0      0 285936  11772 102396    0    0     0     0 1061  2422 99  1  0  0
 1  0      0 285936  11772 102396    0    0     0     0 1176  2697 99  1  0  0
 1  0      0 286768  11780 102396    0    0     0    16 1050  3050 98  2  0  0
 1  0      0 285872  11780 102396    0    0     0     0 1051  2382 100  0  0  0
 1  0      0 286704  11780 102396    0    0     0     0 1064  2830 98  2  0  0
 1  0      0 285872  11788 102396    0    0     0    12 1174  2708 99  1  0  0
 1  0      0 286640  11788 102396    0    0     0     0 1053  2590 99  1  0  0
procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy id wa
 2  0      0 286640  11796 102396    0    0     0    16 1098  2513 98  2  0  0
 1  0      0 285744  11796 102396    0    0     0     0 1112  2876 98  2  0  0
 1  0      0 286576  11796 102396    0    0     0     0 1227  2881 97  3  0  0
 1  0      0 286576  11796 102396    0    0     0     0 1054  2434 99  1  0  0
 1  0      0 285760  11804 102396    0    0     0    12 1086  2463 99  1  0  0

So it appears that whatever was done, was done even that early.  Anyway, back to
2.6.1-mm2 for the last one.  But I have to build it first, brb :)
Done, and booted to 2.6.1-mm2.  "vmstat 1" now shows:
procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy id wa
 1  0      0 293120  11696  97416    0    0   869   160 1099  2513 53 12 24 11
 1  0      0 293136  11696  97416    0    0     0     0 1358  5053 96  4  0  0
 1  0      0 293136  11696  97416    0    0     0     0 1135  2651 99  1  0  0
 3  0      0 270656  11720  98248    0    0   856     0 1083  2726 97  3  0  0
 2  1      0 231872  11728  99528    0    0  1280    36 1093  2775 95  5  0  0
 2  0      0 193552  11744 100680    0    0  1152   304 1128  2450 96  4  0  0
 2  0      0 154832  11752 101832    0    0  1160     0 1068  2406 96  4  0  0
 2  0      0 125328  11752 102440    0    0   608     0 1054  2374 95  5  0  0
 2  0      0 118224  11752 102440    0    0     0     0 1048  2357 99  1  0  0
 2  0      0 115360  11760 102440    0    0     0    16 1098  2414 99  1  0  0
 2  0      0 133920  11764 102440    0    0     0   876 1178  3047 98  2  0  0
 1  0      0 287752  11772 102440    0    0     0    12 1096 13784 85 15  0  0
 1  0      0 287752  11772 102440    0    0     0     0 1132  2601 99  1  0  0
 1  0      0 287688  11772 102468    0    0    28     0 1145  2995 99  1  0  0
 3  0      0 287624  11780 102468    0    0     0    16 1121  2636 99  1  0  0
 1  0      0 287624  11788 102468    0    0     0    16 1169  2640 98  2  0  0
 1  0      0 287624  11788 102468    0    0     0     0 1109  2982 99  1  0  0
 1  0      0 287632  11788 102468    0    0     0     0 1215  2797 100  0  0  0
----
for 5 window switches. 1-6-1-6-1.  And that covers the range of whats still
available here on this system.  I hope all this noise is usefull data, but I
suspect it just demos that the old man wasn't paying sufficient attention.
My apologies for the noise.  During the build, I noticed that the advansis
check_region patch was still good.  Its working here just fine and probably
should be pushed.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty: soap,
ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.


^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12  8:58       ` Thomas Winischhofer
@ 2004-01-12 14:32         ` Moritz Muehlenhoff
  0 siblings, 0 replies; 37+ messages in thread
From: Moritz Muehlenhoff @ 2004-01-12 14:32 UTC (permalink / raw)
  To: linux-kernel

Thomas Winischhofer wrote:
> Isn't a large part of the fbcon/dev stuff in current 2.6 broken anyway? 
> Could it become worse by merging James' current changes?

Well, yes. The current version of sisfb works very well on my SIS630 notebook
and the current radeonfb works in most circumstances, while applying James'
code drops over the last months has always lead to visual corruptions of
radeonfb, that make it almost unusable.
It would be very good if the fbdev patches would be available as separate
patches.


^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12  6:21           ` Gene Heskett
  2004-01-12  6:34             ` Andrew Morton
@ 2004-01-12 16:33             ` Dave Jones
  2004-01-12 17:00               ` Gene Heskett
  1 sibling, 1 reply; 37+ messages in thread
From: Dave Jones @ 2004-01-12 16:33 UTC (permalink / raw)
  To: Gene Heskett; +Cc: Andrew Morton, torvalds, thomas, linux-kernel, jsimmons

On Mon, Jan 12, 2004 at 01:21:12AM -0500, Gene Heskett wrote:

 > DRM? lemme see if thats even turned on.  Nope "# CONFIG_DRM is not set"
 > Doing a make xconfig, I see that if I turn it on, there is not a 
 > driver for my gforce2/nvidia, so I naturally turned it back off.
 > 
 > I do have VIA and agpgart enabled just above it

With CONFIG_DRM off, the AGP options may as well be turned off too,
as they do nothing[1] on a system without 3d acceleration.

		Dave

[1] Well, unless you have an Intel i8xx chipset where you need it for
    the horrid framebuffer needs memory through GART hack.
	And in your case, you don't have one of these.

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12 16:33             ` Dave Jones
@ 2004-01-12 17:00               ` Gene Heskett
  2004-01-12 17:04                 ` Dave Jones
  0 siblings, 1 reply; 37+ messages in thread
From: Gene Heskett @ 2004-01-12 17:00 UTC (permalink / raw)
  To: Dave Jones; +Cc: Andrew Morton, torvalds, thomas, linux-kernel, jsimmons

On Monday 12 January 2004 11:33, Dave Jones wrote:
>On Mon, Jan 12, 2004 at 01:21:12AM -0500, Gene Heskett wrote:
> > DRM? lemme see if thats even turned on.  Nope "# CONFIG_DRM is
> > not set" Doing a make xconfig, I see that if I turn it on, there
> > is not a driver for my gforce2/nvidia, so I naturally turned it
> > back off.
> >
> > I do have VIA and agpgart enabled just above it
>
>With CONFIG_DRM off, the AGP options may as well be turned off too,
>as they do nothing[1] on a system without 3d acceleration.
>
>		Dave
>
>[1] Well, unless you have an Intel i8xx chipset where you need it
> for the horrid framebuffer needs memory through GART hack.
>	And in your case, you don't have one of these.

Are you saying I should turn it on, but just not select a specific 
makers chip-boardset?  Or that I should go get a different card?

In which case I'd have about an 80 dollar limit as I'm not a game 
player that needs a 500 dollar video card.  OTOH, as long as I stay 
the hell away from nvidias own drivers, this card has been quite 
bulletproof.  The only thing thats missing is the GLX extensions.

The last time I brought an ATI card home, the box carried no 
indication that it was anything but what it said it was.  But it 
couldn't be made to work, new vendor/product code return.  I called 
ATI on my quarter and was told rather snippishly that it worked fine 
with their windows drivers that were on the cd, and that if I wanted 
support, I had to be running windows.  So I bought a driver from 
xorg, didn't work, same problem, except no refund was available.  I 
got snotty, and they did too.  Screw both of 'em, and the camels that 
rode in on them,  That left nvidia as the other major player, so 
thats what I bought with my refund.  It worked right out of the box.

tvtime, even running full screen, runs just fine here on this old 
card, as does the vlc stuff, but thats the extent of my requirements 
for full motion video.

But, I'm thinking of building another, and certainly open for video 
card suggestions within the 'utility' price range.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty: soap,
ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.


^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-12 17:00               ` Gene Heskett
@ 2004-01-12 17:04                 ` Dave Jones
  0 siblings, 0 replies; 37+ messages in thread
From: Dave Jones @ 2004-01-12 17:04 UTC (permalink / raw)
  To: Gene Heskett; +Cc: Andrew Morton, torvalds, thomas, linux-kernel, jsimmons

On Mon, Jan 12, 2004 at 12:00:19PM -0500, Gene Heskett wrote:

 > Are you saying I should turn it on, but just not select a specific 
 > makers chip-boardset?  Or that I should go get a different card?

Might as well turn it off completely. You have an Nvidia card, and
that isn't supported by DRI. (AGPGART is just a soft-dependancy for AGP
based cards that DRI supports)

 > But, I'm thinking of building another, and certainly open for video 
 > card suggestions within the 'utility' price range.

Apart from the integrated chipsets from Intel/VIA etc sadly, there's really
not much in the graphics world that has 100% opensource drivers any more.
Basically, forget it for the high performance end of the market.
(And these days, even most of the commodity stuff (NVIDIA, ATI etc) falls
 into that bracket)
 
		Dave


^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-10  4:04   ` Thomas Winischhofer
  2004-01-12  2:58     ` Linus Torvalds
@ 2004-01-13 19:04     ` Adrian Bunk
  2004-01-14  0:35       ` Thomas Winischhofer
  1 sibling, 1 reply; 37+ messages in thread
From: Adrian Bunk @ 2004-01-13 19:04 UTC (permalink / raw)
  To: Thomas Winischhofer; +Cc: Andrew Morton, linux-kernel, jsimmons

On Sat, Jan 10, 2004 at 05:04:53AM +0100, Thomas Winischhofer wrote:
> Adrian Bunk wrote:
> 
> > On Fri, Jan 09, 2004 at 01:40:03AM -0800, Andrew Morton wrote:
> >
> >> ...
> >> All 393 patches
> >> ...
> >> use-soft-float.patch
> >>  Use -msoft-float
> >> ...
> >
> >
> 
> I know. The version of sisfb in 2.6 vanilla is from stone-age. This is 
> has been fixed a long time ago in my current development version (and 
> will be in 2.4 as soon as Marcelo applies my patch which I sent him 
> about a week ago). For 2.6, using my current version requires James 
> Simmons's fbdev-patch because of low-level fbdev-interface changes (like 
> sysfs usage, etc).
> 
> The whole framebuffer stuff in 2.6 is ancient. (Look at the file dates.)

Until the framebuffer stuff in 2.6 gets updated, I'm suggesting the 
patch below to mark FB_SIS as BROKEN.

> Thomas

cu
Adrian

--- linux-2.6.1-mm2/drivers/video/Kconfig.old	2004-01-13 20:02:28.000000000 +0100
+++ linux-2.6.1-mm2/drivers/video/Kconfig	2004-01-13 20:02:55.000000000 +0100
@@ -696,7 +696,7 @@
 
 config FB_SIS
 	tristate "SIS acceleration"
-	depends on FB && PCI
+	depends on FB && PCI && BROKEN
 	help
 	  This is the frame buffer device driver for the SiS 630 and 640 Super
 	  Socket 7 UMA cards.  Specs available at <http://www.sis.com.tw/>.

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-13 19:04     ` Adrian Bunk
@ 2004-01-14  0:35       ` Thomas Winischhofer
  2004-01-15 11:32         ` Adrian Bunk
  0 siblings, 1 reply; 37+ messages in thread
From: Thomas Winischhofer @ 2004-01-14  0:35 UTC (permalink / raw)
  To: Adrian Bunk; +Cc: Andrew Morton, linux-kernel, jsimmons

Adrian Bunk wrote:
> On Sat, Jan 10, 2004 at 05:04:53AM +0100, Thomas Winischhofer wrote:
> 
>>Adrian Bunk wrote:
>>
>>
>>>On Fri, Jan 09, 2004 at 01:40:03AM -0800, Andrew Morton wrote:
>>>
>>>
>>>>...
>>>>All 393 patches
>>>>...
>>>>use-soft-float.patch
>>>> Use -msoft-float
>>>>...
>>>
>>>
>>I know. The version of sisfb in 2.6 vanilla is from stone-age. This is 
>>has been fixed a long time ago in my current development version (and 
>>will be in 2.4 as soon as Marcelo applies my patch which I sent him 
>>about a week ago). For 2.6, using my current version requires James 
>>Simmons's fbdev-patch because of low-level fbdev-interface changes (like 
>>sysfs usage, etc).
>>
>>The whole framebuffer stuff in 2.6 is ancient. (Look at the file dates.)
> 
> 
> Until the framebuffer stuff in 2.6 gets updated, I'm suggesting the 
> patch below to mark FB_SIS as BROKEN.

I think that's a bit harsh. It basically works, it just illegally uses 
some FP operations (as it still does in 2.4 until Marcelo finally 
applies the patch I have sent him for three times now - hint, hint)

Thomas

-- 
Thomas Winischhofer
Vienna/Austria
thomas AT winischhofer DOT net          http://www.winischhofer.net/
twini AT xfree86 DOT org

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-14  0:35       ` Thomas Winischhofer
@ 2004-01-15 11:32         ` Adrian Bunk
  2004-01-15 11:42           ` Thomas Winischhofer
  0 siblings, 1 reply; 37+ messages in thread
From: Adrian Bunk @ 2004-01-15 11:32 UTC (permalink / raw)
  To: Thomas Winischhofer; +Cc: Andrew Morton, linux-kernel, jsimmons

On Wed, Jan 14, 2004 at 01:35:00AM +0100, Thomas Winischhofer wrote:
> >
> >Until the framebuffer stuff in 2.6 gets updated, I'm suggesting the 
> >patch below to mark FB_SIS as BROKEN.
> 
> I think that's a bit harsh. It basically works, it just illegally uses 
> some FP operations (as it still does in 2.4 until Marcelo finally 
> applies the patch I have sent him for three times now - hint, hint)

Now that -mm uses -msoft-float, this means that FB_SIS does no longer 
compile...

> Thomas

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
  2004-01-15 11:32         ` Adrian Bunk
@ 2004-01-15 11:42           ` Thomas Winischhofer
  0 siblings, 0 replies; 37+ messages in thread
From: Thomas Winischhofer @ 2004-01-15 11:42 UTC (permalink / raw)
  To: Adrian Bunk; +Cc: Andrew Morton, linux-kernel, jsimmons

Adrian Bunk wrote:
> On Wed, Jan 14, 2004 at 01:35:00AM +0100, Thomas Winischhofer wrote:
> 
>>>Until the framebuffer stuff in 2.6 gets updated, I'm suggesting the 
>>>patch below to mark FB_SIS as BROKEN.
>>
>>I think that's a bit harsh. It basically works, it just illegally uses 
>>some FP operations (as it still does in 2.4 until Marcelo finally 
>>applies the patch I have sent him for three times now - hint, hint)
> 
> 
> Now that -mm uses -msoft-float, this means that FB_SIS does no longer 
> compile...

Well, then mark it BROKEN in -mm....

Thomas

-- 
Thomas Winischhofer
Vienna/Austria
thomas AT winischhofer DOT net          *** http://www.winischhofer.net/
twini AT xfree86 DOT org




^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1
  2004-01-12 17:54 2.6.1-mm1 Jesse Allen
@ 2004-01-12 18:37 ` Prakash K. Cheemplavam
  0 siblings, 0 replies; 37+ messages in thread
From: Prakash K. Cheemplavam @ 2004-01-12 18:37 UTC (permalink / raw)
  To: Jesse Allen; +Cc: linux-kernel

Jesse Allen wrote:
> I didn't think these patches would make it into a kernel tree, except experimental ones.  For one, I don't think we know what's wrong with the nforce2's apic timer.  And second, I don't need the disconnect patch, because I have verfied a BIOS update has fixed C1 disconnect completely for my board. (works on and off)

Isn't is possbile to find out which registers were altered with the new 
bios? Ie. read out registers with out bios and then with new bios adn 
then compare? Then we (well someone smarter than me :)) could make a 
real fix for the nforce2-apic issue.

Prakash

^ permalink raw reply	[flat|nested] 37+ messages in thread

* Re: 2.6.1-mm1
@ 2004-01-12 17:54 Jesse Allen
  2004-01-12 18:37 ` 2.6.1-mm1 Prakash K. Cheemplavam
  0 siblings, 1 reply; 37+ messages in thread
From: Jesse Allen @ 2004-01-12 17:54 UTC (permalink / raw)
  To: PrakashKC; +Cc: linux-kernel

Andrew Morton wrote:
> "Prakash K. Cheemplavam" <PrakashKC@gmx.de> wrote:
> >
> > Hi,
> > 
> > could it be that you took out /or forgot to insterst the work-around for 
> > nforce2+apic? At least I did a test with cpu disconnect on and booted 
> > kernel and it hang. (I also couldn't find the work-around in the 
> > sources.) I remember an earlier mm kernel had that workaround inside.
> > 
>
> I discussed it with Bart and he felt that it was not a good way of fixing
> the problem.  I'm not sure if he has a better fix in the works though..

I didn't think these patches would make it into a kernel tree, except experimental ones.  For one, I don't think we know what's wrong with the nforce2's apic timer.  And second, I don't need the disconnect patch, because I have verfied a BIOS update has fixed C1 disconnect completely for my board. (works on and off)

If anyone needs stability, they should try the C1 disconnect off patch, use athcool, or set it off in the bios (whatever works).  As for me, I'd rather have it not default off because my board now works with it on and keeps my system cooler.

^ permalink raw reply	[flat|nested] 37+ messages in thread

end of thread, other threads:[~2004-01-15 11:44 UTC | newest]

Thread overview: 37+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-01-09  9:40 2.6.1-mm1 Andrew Morton
2004-01-09 14:47 ` 2.6.1-mm1 Christoph Hellwig
2004-01-09 14:53 ` 2.6.1-mm1 Wojciech 'Sas' Cieciwa
2004-01-09 14:21   ` 2.6.1-mm1 Bartlomiej Zolnierkiewicz
2004-01-09 15:24 ` 2.6.1-mm1 (compile stats) John Cherry
2004-01-09 16:30 ` 2.6.1-mm1 Prakash K. Cheemplavam
2004-01-09 21:20   ` 2.6.1-mm1 Andrew Morton
2004-01-09 21:24     ` 2.6.1-mm1 Prakash K. Cheemplavam
2004-01-09 23:04     ` 2.6.1-mm1 - nforce2 timer patch sum up cheuche+lkml
2004-01-09 19:31 ` 2.6.1-mm1: sound/pci/cmipci.c compile error Adrian Bunk
2004-01-09 22:43   ` Andrew Morton
2004-01-09 23:37 ` 2.6.1-mm1: drivers/video/sis/sis_main.c link error Adrian Bunk
2004-01-10  4:04   ` Thomas Winischhofer
2004-01-12  2:58     ` Linus Torvalds
2004-01-12  4:53       ` Gene Heskett
2004-01-12  5:42         ` Andrew Morton
2004-01-12  6:11           ` Valdis.Kletnieks
2004-01-12  6:47             ` Gene Heskett
2004-01-12  7:05               ` Andrew Morton
2004-01-12  7:20                 ` Gene Heskett
2004-01-12 12:38                 ` Gene Heskett
2004-01-12  6:21           ` Gene Heskett
2004-01-12  6:34             ` Andrew Morton
2004-01-12  6:58               ` Gene Heskett
2004-01-12  7:03               ` Gene Heskett
2004-01-12 16:33             ` Dave Jones
2004-01-12 17:00               ` Gene Heskett
2004-01-12 17:04                 ` Dave Jones
2004-01-12  8:58       ` Thomas Winischhofer
2004-01-12 14:32         ` Moritz Muehlenhoff
2004-01-12 10:36       ` Andrew Walrond
2004-01-13 19:04     ` Adrian Bunk
2004-01-14  0:35       ` Thomas Winischhofer
2004-01-15 11:32         ` Adrian Bunk
2004-01-15 11:42           ` Thomas Winischhofer
2004-01-12 17:54 2.6.1-mm1 Jesse Allen
2004-01-12 18:37 ` 2.6.1-mm1 Prakash K. Cheemplavam

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).