Hi,
I enjoy playing with sid

I just updated to the latest sid on my Averatec Laptop 3250 running
amd processor

which worked fine before. Now when I boot all is fine, i can surf
web using lynx if i stay in console mode. Then when i startx (i have
tried it with kde, gnome, xfce4-session session managers) and
immediately I get kernel errors and then i no longer can use the
network. I am connected by ethernet cable to my local network via eth0
.....


Here are two examples of the the tail of dmesg for two different
kernels:

(only stuff that happens after the startx
is invoked) :


here is dmesg using kernel 2.6.17-2-k7

dmesg|tail
***********

Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery
directory
NFSD: starting 90-second grace period
[drm] Initialized drm 1.1.0 20060810
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 9
PCI: setting IRQ 9 as level-triggered
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKB] -> GSI 9 (level,
low) -> IRQ 9
[drm] Initialized via 2.11.1 20070202 on minor 0
agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up
support for x2 & x1
agpgart: Device is in legacy mode, falling back to 2.x
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
irq 11: nobody cared (try booting with the "irqpoll" option)
[<c014da62>] __report_bad_irq+0x36/0x75
[<c014dc5a>] note_interrupt+0x1b9/0x1f7
[<c014d1a3>] handle_IRQ_event+0x23/0x51
[<c014e57f>] handle_level_irq+0x94/0xc5
[<c010639e>] do_IRQ+0x57/0x71
[<c010476b>] common_interrupt+0x23/0x28
[<c01274dd>] __do_softirq+0x56/0xd3
[<c012759f>] do_softirq+0x45/0x53
[<c0127803>] irq_exit+0x38/0x6b
[<c01063a3>] do_IRQ+0x5c/0x71

[<c010476b>] common_interrupt+0x23/0x28
=======================
handlers:
[<de87795d>]
(rhine_interrupt+0x0/0x654 [via_rhine])
Disabling IRQ #11
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status
0003, PHY status 786d,
resetting...
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0003, PHY status 786d,


and here is what is related to that before! i run the startx
mlaks@AvneiNeizer:~$ dmesg|grep -i irq


ACPI: PCI Interrupt Link [LNKA] (IRQs 4 *11 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 5 9 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs *10 12)
ACPI: PCI Interrupt Link [LNKD] (IRQs 6 7) *0, disabled.
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it s, post
a report
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKC] -> GSI 10 (level,
low) -> IRQ 10
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 7
PCI: setting IRQ 7 as level-triggered
ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LNKD] -> GSI 7 (level,
low) -> IRQ 7
PCI: VIA VLink IRQ fixup for 0000:00:10.0, from 0 to 7
uhci_hcd 0000:00:10.0: irq 7, io base 0x0000e400
ACPI: PCI Interrupt 0000:00:10.1[b] -> Link [LNKD] -> GSI 7 (level,
low) -> IRQ 7
PCI: VIA VLink IRQ fixup for 0000:00:10.1, from 0 to 7
uhci_hcd 0000:00:10.1: irq 7, io base 0x0000e800
ACPI: PCI Interrupt 0000:00:10.2[C] -> Link [LNKD] -> GSI 7 (level,
low) -> IRQ 7
PCI: VIA VLink IRQ fixup for 0000:00:10.2, from 0 to 7
uhci_hcd 0000:00:10.2: irq 7, io base 0x0000ec00
ACPI: PCI Interrupt 0000:00:10.3[D] -> Link [LNKD] -> GSI 7 (level,
low) -> IRQ 7
PCI: VIA VLink IRQ fixup for 0000:00:10.3, from 0 to 7
ehci_hcd 0000:00:10.3: irq 7, io mem 0xdfffdf00
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:12.0[A] -> Link [LNKA] -> GSI 11 (level,
low) -> IRQ 11
eth0: VIA Rhine II at 0x1d800, 00:40:45:25:61:68, IRQ 11.
ACPI: Unable to derive IRQ for device 0000:00:11.1
VP_IDE: not 100% native mode: will probe irqs later
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
de1 at 0x170-0x177,0x376 on irq 15
Yenta: ISA IRQ mask 0x0038, PCI irq 10
ACPI: PCI Interrupt 0000:00:11.6[C] -> Link [LNKC] -> GSI 10 (level,
low) -> IRQ 10
ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [LNKC] -> GSI 10 (level,
low) -> IRQ 10


I have tried booting with irqpoll option, no good, i have tried
noapic, no good.


here is the output using debian stock kernel 2.6.22-1-k7

[drm] Initialized drm 1.1.0 20060810
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 9
PCI: setting IRQ 9 as level-triggered
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKB] -> GSI 9 (level,
low) -> IRQ 9
[drm] Initialized via 2.11.1 20070202 on minor 0
agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up
support for x2 & x1
agpgart: Device is in legacy mode, falling back to 2.x
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
irq 11: nobody cared (try booting with the "irqpoll" option)
[<c014da62>] __report_bad_irq+0x36/0x75
[<c014dc5a>] note_interrupt+0x1b9/0x1f7
[<c014d1a3>] handle_IRQ_event+0x23/0x51
[<c014e57f>] handle_level_irq+0x94/0xc5
[<c010639e>] do_IRQ+0x57/0x71
[<c010476b>] common_interrupt+0x23/0x28
[<c014d1a3>] handle_IRQ_event+0x23/0x51
[<c014d196>] handle_IRQ_event+0x16/0x51
[<c014e56b>] handle_level_irq+0x80/0xc5
[<c010639e>] do_IRQ+0x57/0x71

[<c010476b>] common_interrupt+0x23/0x28
[<c01274dd>] __do_softirq+0x56/0xd3
[<c012759f>] do_softirq+0x45/0x53
[<c0127803>] irq_exit+0x38/0x6b
[<c01063a3>] do_IRQ+0x5c/0x71

[<c010476b>] common_interrupt+0x23/0x28
=======================
handlers:
[<de87795d>]
(rhine_interrupt+0x0/0x654 [via_rhine])
Disabling IRQ #11

I have tried to disable agp with agp=off in /boot/grub/menu.lst but
this did not ..


any ideas what i can do?

mitchell




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Fri, Jul 27, 2007 at 12:30:28PM -0400, Mitchell Laks wrote:
>
> I just updated to the latest sid on my Averatec Laptop 3250 running
> amd processor
>
> which worked fine before. Now when I boot all is fine, i can surf
> web using lynx if i stay in console mode. Then when i startx (i have
> tried it with kde, gnome, xfce4-session session managers) and
> immediately I get kernel errors and then i no longer can use the
> network. I am connected by ethernet cable to my local network via eth0
> ....
>

What happens if you forget desktop environemnents and just run startx
rxvt (or xterm). Many DTEs fitz with the network configs.

What X server are you running?

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Fri, Jul 27, 2007 at 12:30:28 -0400, Mitchell Laks wrote:
> Hi,
> I enjoy playing with sid

Don't we all? Unfortunately Sid sometimes enjoys playing with us as
well...

> I just updated to the latest sid on my Averatec Laptop 3250 running
> amd processor
>
> which worked fine before. Now when I boot all is fine, i can surf
> web using lynx if i stay in console mode. Then when i startx (i have
> tried it with kde, gnome, xfce4-session session managers) and
> immediately I get kernel errors and then i no longer can use the
> network. I am connected by ethernet cable to my local network via eth0
> ....
>
>
> Here are two examples of the the tail of dmesg for two different
> kernels:
>
> (only stuff that happens after the startx
> is invoked) :
>
>
> here is dmesg using kernel 2.6.17-2-k7
>
> dmesg|tail

[...]

> [drm] Initialized drm 1.1.0 20060810
> ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 9
> PCI: setting IRQ 9 as level-triggered
> ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKB] -> GSI 9 (level,
> low) -> IRQ 9
> [drm] Initialized via 2.11.1 20070202 on minor 0
> agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
> agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up
> support for x2 & x1
> agpgart: Device is in legacy mode, falling back to 2.x
> agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
> agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
> irq 11: nobody cared (try booting with the "irqpoll" option)
> [<c014da62>] __report_bad_irq+0x36/0x75
> [<c014dc5a>] note_interrupt+0x1b9/0x1f7
> [<c014d1a3>] handle_IRQ_event+0x23/0x51
> [<c014e57f>] handle_level_irq+0x94/0xc5
> [<c010639e>] do_IRQ+0x57/0x71
> [<c010476b>] common_interrupt+0x23/0x28
> [<c01274dd>] __do_softirq+0x56/0xd3
> [<c012759f>] do_softirq+0x45/0x53
> [<c0127803>] irq_exit+0x38/0x6b
> [<c01063a3>] do_IRQ+0x5c/0x71
> [<c010476b>] common_interrupt+0x23/0x28
> handlers:
> [<de87795d>] (rhine_interrupt+0x0/0x654 [via_rhine])
> Disabling IRQ #11
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
> eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out, status 0003, PHY status 786d, resetting...

[...]

> I have tried booting with irqpoll option, no good, i have tried
> noapic, no good.

Other options to try are "pci=routeirq", "acpi=off" and "nolapic" (plus
combinations of all of the above).

[...]

> I have tried to disable agp with agp=off in /boot/grub/menu.lst but
> this did not ..
>
> any ideas what i can do?

Since this seems to be an interrupt problem it might to see the
output of

cat /proc/interrupts

before and after the network card fails.

We also need to know what cards we are talking about exactly and which
modules are loaded:

lspci | egrep -i 'net|ether|vga|display|video'

lsmod | egrep 'drm|agp|rhine'

--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On 17:19 Sat 28 Jul , Florian Kulzer wrote:
> Other options to try are "pci=routeirq", "acpi=off" and "nolapic" (plus
> combinations of all of the above).

I was away for a few days Florian!
Great ideas!
The one that works was acpi=off. Once I added that in, I no longer had
crash of network after I started X. The others had no effect.

> Since this seems to be an interrupt problem it might to see the
> output of
>
> cat /proc/interrupts
>
> before and after the network card fails.

before the network card fails

CPU0
0: 140497 XT-PIC-XT timer
1: 1399 XT-PIC-XT i8042
2: 0 XT-PIC-XT cascade
7: 0 XT-PIC-XT uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, ehci_hcd:usb4
8: 1 XT-PIC-XT rtc
9: 13673 XT-PIC-XT acpi
10: 5 XT-PIC-XT yenta, VIA8233, VIA82XX-MODEM
11: 156 XT-PIC-XT eth0
12: 4505 XT-PIC-XT i8042
14: 92272 XT-PIC-XT ide0
15: 90 XT-PIC-XT ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0

here is cat /proc/interrupts after the failure

CPU0
0: 168321 XT-PIC-XT timer
1: 1715 XT-PIC-XT i8042
2: 0 XT-PIC-XT cascade
7: 0 XT-PIC-XT uhci_hcd:usb1,uhci_hcd:usb2, uhci_hcd:usb3, ehci_hcd:usb4
8: 1 XT-PIC-XT rtc
9: 17249 XT-PIC-XT acpi, via@pci:0000:01:00.0
10: 5 XT-PIC-XT yenta, VIA8233, VIA82XX-MODEM
11: 200000 XT-PIC-XT eth0
12: 15317 XT-PIC-XT i8042
14: 97894 XT-PIC-XT ide0
15: 90 XT-PIC-XT ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0




>
> We also need to know what cards we are talking about exactly and which
> modules are loaded:
>
> lspci | egrep -i 'net|ether|vga|display|video'

lspci| egrep -i 'net|ether|vga|display|video'

00:09.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI
(rev 01)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II]
(rev 74)
01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3
UniChrome] Integrated Video (rev 01)



>
> lsmod | egrep 'drm|agp|rhine'

lsmod | egrep 'drm|agp|rhine'

before the network crash

via_agp 10304 1
agpgart 32264 1 via_agp
via_rhine 24136 0
mii 5696 1 via_rhine

lsmod | egrep 'drm|agp|rhine'
after the network crash

drm 76628 3 via
via_agp 10304 1
agpgart 32264 2 drm,via_agp
via_rhine 24136 0
mii 5696 1 via_rhine



and now when I startx after booting with acpi=off
this is the tail of dmesg after I startx. Notice there is no kernel
crash of

[drm] Initialized drm 1.1.0 20060810
[drm] Initialized via 2.11.1 20070202 on minor 0
agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up
support for x2 & x1
agpgart: Device is in legacy mode, falling back to 2.x
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode

notice no report bad irq crash from the kernel!

OK. So now what do I do next? I notice that the laptop is very very
hot in running. it is an averatec 3250HX-01.

what do i do next, Florian?

Thank you very much Florian! (

and thanks Douglas as well. I dont know
how to startx with rxvt. Could you explain that? do you mean
saying startx rxvt?)


Mitchell Laks

>
> --
> Regards, | http://users.icfo.es/Florian.Kulzer
> Florian |
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Jul 30, 2007 at 23:31:07 -0400, Mitchell Laks wrote:
> On 17:19 Sat 28 Jul , Florian Kulzer wrote:
> > Other options to try are "pci=routeirq", "acpi=off" and "nolapic" (plus
> > combinations of all of the above).
>
> I was away for a few days Florian!
> Great ideas!
> The one that works was acpi=off. Once I added that in, I no longer had
> crash of network after I started X. The others had no effect.
>
> > Since this seems to be an interrupt problem it might to see the
> > output of
> >
> > cat /proc/interrupts
> >
> > before and after the network card fails.
>
> before the network card fails

[...]

> 9: 13673 XT-PIC-XT acpi
> 10: 5 XT-PIC-XT yenta, VIA8233, VIA82XX-MODEM
> 11: 156 XT-PIC-XT eth0

[...]

> here is cat /proc/interrupts after the failure

[...]

> 9: 17249 XT-PIC-XT acpi, via@pci:0000:01:00.0
> 10: 5 XT-PIC-XT yenta, VIA8233, VIA82XX-MODEM
> 11: 200000 XT-PIC-XT eth0

[...]

> lspci| egrep -i 'net|ether|vga|display|video'
>
> 00:09.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
> 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
> 01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01)

Hmm, once the via driver gets loaded it shares IRQ 9 with acpi and that
makes the via_rhine driver on IRQ 11 crash. That kind of thing can be
difficult to fix. Did your Sid upgrade involve a new kernel? If so then
it might be the simplest thing to go back to the old kernel or to make
do without acpi for now. Otherwise you might have to be prepared to read
the documentation and changelogs of all involved kernel modules and hope
that somewhere there is a module option which fixes this. Since I don't
have this hardware I cannot say anything more.

> lsmod | egrep 'drm|agp|rhine'
>
> before the network crash
>
> via_agp 10304 1
> agpgart 32264 1 via_agp
> via_rhine 24136 0
> mii 5696 1 via_rhine
>
> lsmod | egrep 'drm|agp|rhine'
> after the network crash
>
> drm 76628 3 via
> via_agp 10304 1
> agpgart 32264 2 drm,via_agp
> via_rhine 24136 0
> mii 5696 1 via_rhine
>
> and now when I startx after booting with acpi=off
> this is the tail of dmesg after I startx. Notice there is no kernel
> crash of
>
> [drm] Initialized drm 1.1.0 20060810
> [drm] Initialized via 2.11.1 20070202 on minor 0
> agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
> agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up
> support for x2 & x1
> agpgart: Device is in legacy mode, falling back to 2.x
> agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
> agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
>
> notice no report bad irq crash from the kernel!
>
> OK. So now what do I do next? I notice that the laptop is very very
> hot in running. it is an averatec 3250HX-01.

This may be related to disabling acpi. Did you check if someone has
posted something about this model on tuxmobil.org?

--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org