[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#276351: marked as done (installation-reports: [i386] [pre-rc2] [netinst] dma problem on first reboot)

Your message dated Wed, 08 Sep 2010 03:57:43 +0000
with message-id <E1OtBn5-0004AF-Bn@ravel.debian.org>
and subject line Closing old installation report #276351
has caused the Debian Bug report #276351,
regarding installation-reports: [i386] [pre-rc2] [netinst] dma problem on first reboot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

276351: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=276351
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: normal

Debian-installer-version: pre-rc2, downloaded from d-i website 8.10.04
uname -a: Linux tigerbay 2.6.8-1-686 #1 Thu Oct 7 03:15:25 EDT 2004 i686
Date: 9.10.04, ca. 15.00-23.00 UTC
Method: Booted off larger CD (netinst) with new HD; packages downloaded
via ethernet (Cable,NAT) from the.earth.li

      Machine: DELL Latitude LS
      Processor: Intel Pentium III (Coppermine) stepping 06
      Memory: 128 MB
      Root Device: Hitachi 5K80 (40GB) on /dev/hda
      Root Size/partition table: 39GB on / 1GB swap. 
      	This is from dmesg today:

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 0000:00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xfcd0-0xfcd7, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xfcd8-0xfcdf, BIOS settings: hdc:pio, hdd:pio
hda: HTS548040M9AT00, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 1024KiB
hda: 78140160 sectors (40007 MB) w/7877KiB Cache,
CHS=16383/255/63, UDMA(33)
 /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 >
	    Output of lspci and lspci -n:

0000:00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host
bridge (rev 03)
0000:00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP
bridge (rev 03)
0000:00:07.0 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
0000:00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
0000:00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev
0000:00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 03)
0000:00:0a.0 CardBus bridge: Texas Instruments PCI1211
0000:00:0d.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M
[Tornado] (rev 78)
0000:00:10.0 Communication controller: Lucent Microelectronics WinModem
56k (rev 01)
0000:01:00.0 VGA compatible controller: Neomagic Corporation NM2200
[MagicGraph 256AV] (rev 20)
0000:01:00.1 Multimedia audio controller: Neomagic Corporation NM2200
[MagicMedia 256AV Audio] (rev 20)

0000:00:00.0 0600: 8086:7190 (rev 03)
0000:00:01.0 0604: 8086:7191 (rev 03)
0000:00:07.0 0680: 8086:7110 (rev 02)
0000:00:07.1 0101: 8086:7111 (rev 01)
0000:00:07.2 0c03: 8086:7112 (rev 01)
0000:00:07.3 0680: 8086:7113 (rev 03)
0000:00:0a.0 0607: 104c:ac1e
0000:00:0d.0 0200: 10b7:9200 (rev 78)
0000:00:10.0 0780: 11c1:0448 (rev 01)
0000:01:00.0 0300: 10c8:0005 (rev 20)
0000:01:00.1 0401: 10c8:8005 (rev 20)

	    Base System Installation Checklist:
	    [O] = OK, [E] = Error (please elaborate below), [ ] = didn't
	    try it
		all ok, except:
	    Partition hard drives:  [whish: enlarging not straightforward] 
	    Reboot:                 [E on first boot ]


	    Install went very smooth, just 3 little things:

	    - I found it hard to have the installer abort the first
	      apt-get update. I had made a mistake with my network
	      configuration, resulting in lacking DNS resolution and the
	      apt-get update endlessly looping over this problem. I
	      ended up logging in on another console killing processes
	      until I got back to the 'main' installer menu, where I
	      could change the setting

	    - I wanted a larger swap partition than suggested by the
	      partitioner, and found that process rather complicated.
	      With just two partitions, I'd like to be able to say
	      "enlarge this one", and this is automatically taken to
	      mean "reduce the other one accordingly". Rather than
	      changing partition sizes, the easiest way turned out to be
	      to just delete and re-create the swap partition. I'd like
	      more info/online help available on meaning and use of
	      logical/extended partitions, and why some mounts should be
	      of a certain type.

	    - When rebooting for the first time (the 'smoke test', first
	      time off newly installed HD), when registering the HD
	      (somewhere between the dmesg lines copied above) I got a
	      few error messages about a dma_timer_expiry and dma status
	      codes of 0x21 and 0x58, the whole boot process eventually
	      hanging. As my (very noisy) fan didn't stop turning as it
	      usually does after 2-3 seconds, I switched the laptop off
	      and, when switching it on again, it would boot up just
	      normal (as it has done ever since). The only difference I
	      notice is that I now have two lines
    ide0: BM-DMA at 0xfcd0-0xfcd7, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xfcd8-0xfcdf, BIOS settings: hdc:pio, hdd:pio
	     whereas before (with my old HD), there had only been one...

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (650, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8

--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
- it was reported with a pre-lenny version of Debian
- indications in the installation report give the feeling that
  the reported problem waslying in another software, unrelated to
  D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
  fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful

The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet. 

In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.

You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.

If some problems are found, please report them with a new bug sent
against installation-reports.

Many thanks for your understanding and your help improving Debian,
past and present.

--- End Message ---

Reply to: